Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- 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
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- MSDP cloud support
- About MSDP cloud 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
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
Troubleshooting MSDP catalog backup
The following subsections provide information about MSDP catalog backup and recovery.
Table: MSDP drcontrol codes and messages describes error messages that may occur when you create or update a catalog backup policy. The messages are displayed in the shell window in which you ran the drcontrol utility. The utility also writes the messages to its log file.
Table: MSDP drcontrol codes and messages
Code or message
Fatal error in an operating system or deduplication command that the drcontrol utility calls.
The command cannot find the necessary NetBackup configuration information.
The user who invoked the command does not have administrator privileges.
A command option or argument is required.
The policy name that you specified already exists.
This error code is passed from the NetBackup bplist command. The MSDP catalog backup policy you specified does not exist or no backups exist for the given policy name.
Fatal error in the drcontrol utility.
For more information about status codes and error messages, see the following:
The Troubleshooter in the NetBackup Administration Console.
The NetBackup Status Codes Reference Guide available through the following webpage:
If NetBackup detects corruption in the MSDP catalog, the Deduplication Manager recovers the catalog automatically from the most recent shadow copy. That recovery process also plays a transaction log so that the recovered MSDP catalog is current.
Although the shadow copy recovery process is automatic, a recovery procedure is available if you need to recover from a shadow copy manually.