About MSDP Encryption using NetBackup Key Management Server service
NetBackup incorporates the Key Management Server (KMS) with Media Server Deduplication Pool.
Starting NetBackup 10.1.1 and Flex WORM Storage Server 17.1, MSDP uses envelope encryption with multiple layers of keys to encrypt the data. Each new MSDP data segment is encrypted with a unique data encryption key (DEK) that is generated by an MSDP. Each DEK is encrypted or wrapped by a key encryption key (KEK) that is generated by an MSDP. Multiple DEKs can use the same KEK for encryption until a new active KEK is generated. The KEKs are encrypted using the active root keys that reside in NetBackup KMS or an external KMS. The root keys are not sent to the MSDP. Instead, an MSDP sends the KEK to the NetBackup primary server, which interfaces with the NetBackup KMS or an external KMS to encrypt or decrypt the KEK. The encrypted DEKs and encrypted KEKs are stored within MSDP.
For information on how to convert the legacy KMS encryption to the KEK-based KMS encryption for the previous backup data, See Converting the legacy KMS to KEK-based KMS.
User manages KMS service to create and activate a key. In KMS service, one active key must exist.
You can configure the KMS service from the NetBackup web UI or the NetBackup command line during storage server configuration.
Note:
You cannot disable the MSDP KMS service after you enable it.
If the KMS service is not available for MSDP or the key in the KMS service that MSDP uses is not available, then MSDP waits in an infinite loop and the backup job may fail. When MSDP goes in an infinite loop, some commands that you run might not respond.
After you configure KMS encryption or once the MSDP processes restart, check the KMS encryption status after the first backup finishes.
The keys in the key dictionary must not be deleted, deprecated, or terminated. All keys that are associated with the MSDP disk pool must be in an active or an inactive state.
You can use the following commands to get the status of the KMS mode:
For UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --getmode
For MSDP cloud, run the following keydictutil command to check if the Logical Storage Unit (LSU) is in KMS mode:
/usr/openv/pdde/pdcr/bin/keydictutil --list
For Windows:
<install_path>\Veritas\pdde\crcontrol.exe --getmode
Note:
If you use the nbdevconfig command to add a new encrypted cloud LSU and an encrypted LSU exists in this MSDP, the keygroupname must be the same as the keygroupname in the previous encrypted LSU.
For enabling KMS, refer to the following topics: