Troubleshooting KMS
Use the following procedure to initiate troubleshooting for KMS.
To initiate troubleshooting for KMS
- Determine what error code and description are encountered.
- Check to determine if KMS is running and that the following KMS data files exist:
kms/db/KMS_DATA.dat kms/key/KMS_HMKF.dat kms/key/KMS_KPKF.dat
If the files do not exist, then KMS has not been configured, or the configuration has been removed. Find out what happened to the files if they do not exist. If KMS has not been configured, the nbkms service is not running. If KMS is not running or is not configured, it does not affect NetBackup operation. If you have previously used the ENCR_ prefix for a volume pool name, this name must be changed as ENCR_ now has special meaning to NetBackup.
- Get the KMS configuration information:
Get a key group listing by running the command nbkmsutil - listkgs. Get a listing of all the keys for a key group by running the command nbkmsutil - listkeys - kgname key_group_name.
- Get operational log information such as KMS logs by way of VxUL OID 286 and BPTM logs.
- Evaluate the log information. The KMS errors are handed back to BPTM.
- Evaluate the KMS errors that are recorded in the KMS log.