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 KMS 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
- 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 immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- 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
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- 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 installation issues
- 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
About Cloud Catalyst migration cacontrol options
NetBackup has multiple cacontrol options that help with cleanup of images and help to make the Cloud Catalyst migration more successful.
Note:
Multiple cacontrol command options are not intended to be run directly because running the nbdecommision command activates the cacontrol option. Carefully review all options in Table: cacontrol options.
Table: cacontrol options lists the cacontrol command options that you can use during the Cloud Catalyst migration and how to use those options.
Table: cacontrol options
cacontrol option | Description |
---|---|
buildcloudcatalystobjects | Location: /usr/openv/pdde/pdcr/bin/cacontrol --catalog buildcloudcatalystobjects <lsuname> <lsuname> = Name of the MSDP Cloud LSU that was migrated from CloudCatalyst. This option creates a lookup table for image sharing after successful migration to the MSDP cloud tier. After migration, this command should be run on the image sharing server and then the services on that server should be restarted. |
cleanupcloudcatalystobjects | Location: /usr/openv/pdde/pdcr/bin/cacontrol --catalog cleanupcloudcatalystobjects <lsuname> <lsuname> = Name of the MSDP Cloud LSU that was migrated from CloudCatalyst. This option removes unused Cloud Catalyst objects from the cloud after successful migration to the MSDP cloud tier server. This command can be run as an optional step which may be run a few days or weeks after the migration. This option cleans up any Cloud Catalyst objects which the new MSDP cloud tier server does not need. Do not run unless confident that the migration was successful since you cannot revert to Cloud Catalyst to access the data once this command is run. |
migratecloudcatalyst | Location: /usr/openv/pdde/pdcr/bin/cacontrol --catalog migratecloudcatalyst <lsuname> <cloudcatalystmaster> <cloudcatalystmedia> [skipimagesharing] [start_with] <lsuname> = Name of the MSDP Cloud LSU to be migrated from CloudCatalyst. <cloudcatalystmaster> = Master server name. <cloudcatalystmedia> = Media server hostname of the CloudCatalyst server to be migrated. [skipimagesharing] = Flag which indicates to skip migrating the image sharing data from CloudCatalyst to the new MSDP Cloud LSU. [start_with] = Indicates the point at which to resume a failed migration after the cause of the failure has been addressed. The nbdecommission -migrate_cloudcatalyst command calls this cacontrol command as needed. Do not run this cacontrol directly. Instead, use the nbdecommission -migrate_cloudcatalyst command to perform the migration. |
migratecloudcatalyststatus | Location: /usr/openv/pdde/pdcr/bin/cacontrol --catalog migratecloudcatalyststatus <lsuname> <lsuname> = Name of the MSDP Cloud LSU being migrated from CloudCatalyst. The nbdecommission -migrate_cloudcatalyst command calls this cacontrol command as needed. Do not run this cacontrol directly. Instead, use the nbdecommission -migrate_cloudcatalyst command to perform migration. |