NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Disaster recovery in S3 interface for MSDP
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
Checking the image encryption status
Use msdpimgutil encryptionreport command-line utility to check the MSDP pool encryption status or image encryption status on the storage server.
This command-line utility does the following:
Reports the MSDP pool encryption status.
It lists the data encryption setting and KMS encryption setting for all LSUs.
Reports the image data encryption status for the given image.
Reports the image KMS encryption status for the given image.
Provides KMS key IDs used for the given encrypted image.
Provides the unencrypted data container IDs.
If encryption is disabled, provides encryption protection guidance.
msdpimgutil encryptionreport command-line utility is located at the following locations:
UNIX:
/usr/openv/pdde/pdcr/bin/msdpimgutil
Windows:
install_path\Veritas\pdde\msdpimgutil.exe
To check the image encryption status
- Run the following command to check the MSDP pool encryption status. It lists data encryption setting and KMS encryption settings for all LSUs.
msdpimgutil encryptionreport --systemcheck
For example,
msdpimgutil encryptionreport --systemcheck ==== Dedup system encryption check ==== Found Local LSU LSU's Data encryption setting is enabled. LSU's KMS encryption setting is enabled. Found Cloud LSU aws_vraxmyan9148 LSU's Data encryption setting is disabled. LSU's KMS encryption setting is disabled. Found Cloud LSU aws2_vraxmyan9148 LSU's Data encryption setting is enabled. LSU's KMS encryption setting is enabled. ** Follow the NetBackup Deduplication Guide to enable Data/KMS encryption (contentrouter.cfg). ** Encryption Crawler: Encryption Crawler is unavailable for WORM Deduplication pools or data stored on Cloud Tier.
- Check the encryption settings of the image in the MSDP pool.
It reports the image data encryption status, image KMS encryption status, KMS key IDs, and the unencrypted data container IDs used for the given image. If encryption is disabled, provides encryption protection guidance.
msdpimgutil encryptionreport --backupid <backup id> --copy <copy number> [--verbose | -v]
--backupid: Backup ID of the image.
--copy: Copy number of the image.
--verbose or -v: Verbose is used to output KMS key IDs for the KMS encrypted image or the data containers IDs for the unencrypted image.
Note:
This command may run for a long time if the image consumes a large number of data containers.
For example,
msdpimgutil encryptionreport --backupid backupid --copy 1 --verbose ==== Dedup system encryption check ==== Found Local LSU LSU's Data encryption setting is enabled. LSU's KMS encryption setting is enabled. ==== Dedup image encryption check ==== Found image (2|/client/policy|backupid_C1) in Local LSU. Image Data encryption setting is enabled. Image KMS encryption setting is enabled. Image data segments are found in 16 data containers, 16 data containers are KMS encrypted. The following unique KeyID is needed for image recovery. KeyID: 87f49487cd13e9d30c4891e146721354f53f26b82945a8b23eb859a0b8416929