Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 97

Using Metadata, XML File Format

Get Dell PowerVault TL4000 PDF manuals and user guides View all Dell PowerVault TL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 97 highlights

Chapter 8. Using Metadata The Encryption Key Manager must be configured to create an XML file that captures vital information as data is being encrypted and written to tape. This file can be queried by volume serial number to display the alias or key label that was used on the volume. Conversely, the file can be queried by alias to display all volumes associated with that key label/alias. Note: If you do not configure a metadata file, the Encryption Key Manager will not start. As encryption processing is performed, the Encryption Key Manager collects the following data: v Drive Serial Number v Drive WorldWideName v Creation Date v Key Alias 1 v Key Alias 2 v DKi v VolSer When the collected data reaches a certain limit, it is written to an XML file. The default limit, which can be set in the Encryption Key Manager properties file (KeyManagerConfig.properties), is 100 records. Once the file is written, it can be queried as long as the Encryption Key Manager is running. To prevent the file from growing too large, it is automatically rolled over to a new file after a maximum file size is reached. The default maximum file size for rollover, which can also be set in the Encryption Key Manager properties file, is 1 MB. Only a current and a previous file version is saved. The values to set in the Encryption Key Manager configuration properties file are: Audit.metadata.file.name Name of XML file where metadata is saved. This is required. Audit.metadata.file.size The maximum filesize, specified in kilobytes, before rolling the file over from current to previous version. This is optional. The default is 1024 (1MB). Audit.metadata.file.cachecount The number of records to be cached before writing the metadata file. This is optional. The default is 100. XML File Format The file contains records in the following format. FVTDRIVE0000 -Drive Serial Number TESTER -Volume Serial 57574E414D453030 -drive WWN cert2 -Key Alias1 8-1

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
Chapter 8. Using Metadata
The Encryption Key Manager must be configured to create an XML file that
captures vital information as data is being encrypted and written to tape. This file
can be queried by volume serial number to display the alias or key label that was
used on the volume. Conversely, the file can be queried by alias to display all
volumes associated with that key label/alias.
Note:
If you do not configure a metadata file, the Encryption Key Manager will
not start.
As encryption processing is performed, the Encryption Key Manager collects the
following data:
v
Drive Serial Number
v
Drive WorldWideName
v
Creation Date
v
Key Alias 1
v
Key Alias 2
v
DKi
v
VolSer
When the collected data reaches a certain limit, it is written to an XML file. The
default limit, which can be set in the Encryption Key Manager properties file
(KeyManagerConfig.properties), is 100 records. Once the file is written, it can be
queried as long as the Encryption Key Manager is running. To prevent the file
from growing too large, it is automatically rolled over to a new file after a
maximum file size is reached. The default maximum file size for rollover, which
can also be set in the Encryption Key Manager properties file, is 1 MB. Only a
current and a previous file version is saved. The values to set in the Encryption
Key Manager configuration properties file are:
Audit.metadata.file.name
Name of XML file where metadata is saved. This is required.
Audit.metadata.file.size
The maximum filesize, specified in kilobytes, before rolling the file over from
current to previous version. This is optional. The default is 1024 (1MB).
Audit.metadata.file.cachecount
The number of records to be cached before writing the metadata file. This is
optional. The default is 100.
XML File Format
The file contains records in the following format.
<KeyUsageEvent>
<DriveSSN>FVTDRIVE0000</driveSSN>
-Drive Serial Number
<VolSer>TESTER</volSer>
-Volume Serial
<DriveWWN>57574E414D453030</driveWWN>
-drive WWN
<keyAlias2>cert2</keyAlias2>
-Key Alias1
8-1