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
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- 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
- 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
Updating an MSDP catalog backup policy
You can use any NetBackup method to update an MSDP catalog backup policy manually. However, you should use the NetBackup Deduplication Catalog Policy Administration and Catalog Disaster Recovery (drcontrol) under the following circumstances:
To add the client name of the storage server to the policy's client list.
To update the --OS value.
To update the --hardware value.
To update the backup selection if you modified any of the following configuration values:
Any of the following values in the
spa.cfg
file (section:variable pairs):StorageDatabase:CatalogShadowPath
StorageDatabase:Path
Paths:Var
The
spa.cfg
orcontentrouter.cfg
locations in thepdregistry.cfg
file.
To update an MSDP catalog backup
- On the MSDP storage server, invoke the drcontrol utility and use the appropriate options for your needs. The following is the syntax for an update operation:
UNIX: /usr/openv/pdde/pdcr/bin/drcontrol --update_policy --policy policy_name [--client host_name] [--hardware machine_type] [--OS operating_system]
Windows: install_path\Veritas\pdde\drcontrol --update_policy --policy policy_name [--client host_name] [--hardware machine_type] [--OS operating_system] [--OS operating_system] [--NB_install_dir install_directory]
Descriptions of the options are available in another topic.
The utility creates a log file and displays its path in the command output.