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
- 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 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
- 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
- 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
- Troubleshooting
- 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
- Appendix A. Migrating to MSDP storage
Changing the MSDP shadow catalog path
You can change the location of the catalog shadow copies. Veritas recommends that you store the copies on a different volume than both the storage_path and the database_path . (If you configured a separate path for the deduplication database, the paths are different.)
NetBackup stores the MSDP catalog shadow copies in the following location:
UNIX: /database_path/databases/catalogshadow
Windows: database_path\databases\catalogshadow
Warning:
You can change the shadow catalog path during initial MSDP configuration only. If you change it after MSDP backups exist, data loss may occur.
See About protecting the MSDP catalog.
To change the MSDP catalog shadow path
- Open the following file in a text editor:
UNIX:
/storage_path/etc/puredisk/spa.cfg
Windows:
storage_path\etc\puredisk\spa.cfg
- Find the CatalogShadowPath parameter and change the value to the wanted path.
The volume must be mounted and available.
- After your changes, save the file.
- Restart the NetBackup Deduplication Manager (spad).
- Create the shadow catalog directories by invoking the following command on the MSDP storage server:
UNIX: /usr/openv/pdde/pdcr/bin/cacontrol --catalog backup all
Windows: install_path\&CompanyNameShort;\pdde\cacontrol --catalog backup all
- If an MSDP catalog backup policy exists, update the policy with the new shadow catalog directories. To do so, invoke the following command on the MSDP storage server:
UNIX: /usr/openv/pdde/pdcr/bin/drcontrol --update_policy --policy policy_name
Windows: install_path\&CompanyNameShort;\pdde\drcontrol --update_policy --policy policy_name