Netbackup Key Management Service (KMS) Status Codes


The NetBackup Key Management Service (KMS) feature is included as part of the NetBackup Enterprise Server and NetBackup Server software. An additional license is not required to use this functionality. KMS runs on NetBackup and is a master server-based symmetric Key Management Service. The KMS manages symmetric cryptography keys for the tape drives that conform to the T10 standard. KMS has been designed to use volume pool-based tape encryption. KMS is used with the tape hardware that has a built-in hardware encryption capability. An example of a tape drive that has built-in encryption is the IBM ULTRIUM TD4 cartridge drive. 


KMS is also used with disk volumes associated with NetBackup AdvancedDisk storage solutions. KMS runs with Cloud storage providers. KMS runs on Windows and UNIX. KMS generates keys from your passcodes or it auto-generates keys. The KMS operations are done through the KMS command line interface (CLI) or the Cloud Storage Server Configuration Wizard (when KMS is used with Cloud storage providers). The CLI options are available for use with both nbms and nbmkmsutil.

Here is the list of KMS status code :

1    Failed to initialize the ORB
2    Failed to create a new Key Group
3    Failed to create a new Key
4    Failed to modify Key Group details
5    Failed to modify Key details
6    Failed to delete the Key Group
7    Failed to fetch Key Group details
8    Failed to fetch Key(s) details
9    Failed to fetch Key Store statistics
10    Failed to modify Host Master Key
11    Failed to modify Key Protection Key
12    Failed to register OBVs with ORB
13    Request timed out. NBSL service might be down
14    Failed to establish a session with NBSL
15    Failed to get Modifiable Facet Instance. KMS service might be down
16    Failed to narrow to Modifiable Facet Instance
17    Failed to get Queryable Facet Instance. KMS service might be down
18    Failed to narrow to Queryable Facet Instance
19    Failed to get Control Facet Instance. KMS service might be down.
20    Failed to narrow to Control Facet Instance
21    Failed to get Exim Facet Instance. KMS service might be down.
22    Failed to narrow to Exim Facet Instance
23    New Key Group creation is successful
24    New Key creation is successful
25    Key Group details are updated successfully
26    Key details are updated successfully
27    Key Group deletion is successful
28    No Key Groups were found
29    No Keys were found
30    Host Master Key update is successful
31    Key Protection Key update is successful
32    Missing or duplicate option: %s
33    All the options are mutually exclusive
34    Options %s %s are mutually exclusive
35    Invalid option or value: %s
36    Unknown option used
37    Invalid value for %s: %s
38    Invalid value for %s: %s
39    Invalid operation
40    Failed to get Key Group details
41    Failed to get Host Master Key ID
42    Failed to get Key Protection Key ID
44    Failed to get KMS service manager instance
45    Failed to quiesce Keystore
46    Failed to unquiesce Keystore
47    Failed to get keystore quiesce status
48    Key Store quiesce is successful
49    Key Store unquiesce is successful
50    Failed recover Key with known Tag
51    Key recovery is successful
52    Failed to delete the Key
53    Key deletion is successful
54    Authentication failed check NBAC credentials
55    Access denied on this operation check NBAC permissions
56    Authorization failed check NBAC credentials
57    Nothing to modify
58    Keystore successfully exported
59    Failed to export keystore
60    Successfully imported keystore file
61    Failed to import keystore file into the KMS Database
62    Failed to read file. Please check the format and try again
63    You must provide the Salt value to recover the key
1287    Invalid characters found in name: %s\n -- Valid character set: A-Z a-z
    0-9, _, -, :, . and space -- Name should start with A-Z or a-z or 0-9



Source : veritas.com

Please Select Embedded Mode To Show The Comment System.*

Previous Post Next Post