Chapter 8. Using MetadataThe Encryption Key Manager must be configured to create an XML file thatcaptures vital information as data is being encrypted and written to tape. This filecan be queried by volume serial number to display the alias or key label that wasused on the volume. Conversely, the file can be queried by alias to display allvolumes associated with that key label/alias.Note: If you do not configure a metadata file, the Encryption Key Manager willnot start.As encryption processing is performed, the Encryption Key Manager collects thefollowing data:v Drive Serial Numberv Drive WorldWideNamev Creation Datev Key Alias 1v Key Alias 2v DKiv VolSerWhen the collected data reaches a certain limit, it is written to an XML file. Thedefault limit, which can be set in the Encryption Key Manager properties file(KeyManagerConfig.properties), is 100 records. Once the file is written, it can bequeried as long as the Encryption Key Manager is running. To prevent the filefrom growing too large, it is automatically rolled over to a new file after amaximum file size is reached. The default maximum file size for rollover, whichcan also be set in the Encryption Key Manager properties file, is 1 MB. Only acurrent and a previous file version is saved. The values to set in the EncryptionKey Manager configuration properties file are:Audit.metadata.file.nameName of XML file where metadata is saved. This is required.Audit.metadata.file.sizeThe maximum filesize, specified in kilobytes, before rolling the file over fromcurrent to previous version. This is optional. The default is 1024 (1MB).Audit.metadata.file.cachecountThe number of records to be cached before writing the metadata file. This isoptional. The default is 100.XML File FormatThe file contains records in the following format.FVTDRIVE0000 -Drive Serial NumberTESTER -Volume Serial57574E414D453030 -drive WWNcert2 -Key Alias18-1
