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
Configuring an MSDP catalog backup
Use the following procedure to configure a backup policy for the NetBackup MSDP catalog.
See About protecting the MSDP data.
To configure an MSDP catalog backup
- Verify that the MSDP storage server host (that is, the media server) is an additional server for the NetBackup master server. See NetBackup Management > Host Properties > masterserver_name > Servers > Additional Servers in the NetBackup Administration Console.
If the storage server is not in the Additional Servers list, add the MSDP storage server host to the Additional Servers list. The host must be in the Additional Servers list and cannot be in the Media Servers list.
- On the MSDP storage server, invoke the drcontrol utility and use the appropriate options for your needs. The following is the syntax for the utility:
Windows: install_path\Veritas\pdde\drcontrol --new_policy --residence residence [--policy policy_name] [--client host_name] [--hardware machine_type] [--OS operating_system] [--dsid data_selection_ID] [--NB_install_dir install_directory]
UNIX: /usr/openv/pdde/pdcr/bin/drcontrol --new_policy --residence residence [--policy policy_name] [--disk_pool disk_pool_name] [--client host_name] [--hardware machine_type] [--OS operating_system] [--dsid data_selection_ID]
Descriptions of the options are available in another topic. Note: To ensure that NetBackup activates the policy, you must specify the --residence residence option.
The utility creates a log file and displays its path in the command output.
More Information