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 CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst 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
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
About the MSDP catalog backup policy
Veritas recommends that you protect the MSDP catalog by backing it up. (A NetBackup catalog backup does not include the MSDP catalog.) The NetBackup Deduplication Catalog Policy Administration and Catalog Disaster Recovery utility (the drcontrol utility) configures a backup policy for the MSDP catalog. The policy also includes other important MSDP configuration information.
The MSDP catalog backups provide the second tier of catalog protection. The catalog backups are available if the shadow copies are not available or corrupt.
The following are the attributes for the catalog backup policy that the drcontrol utility creates:
Weeklyand daily .
6:00 A.M. to 6:00 P.M.
The following are the default catalog paths.
/database_path/databases/catalogshadow /storage_path/etc /storage_path/var /usr/openv/lib/ost-plugins/pd.conf /usr/openv/lib/ost-plugins/mtstrm.conf /database_path/databases/spa /database_path/databases/datacheck
database_path\databases\catalogshadow storage_path\etc storage_path\var install_path\Veritas\NetBackup\bin\ost-plugins\pd.conf install_path\Veritas\NetBackup\bin\ost-plugins\mtstrm.conf database_path\databases\spa database_path\databases\datacheck
By default, NetBackup uses the same path for the storage and the catalog; the database_path and the storage_path are the same. If you configure a separate path for the deduplication database, the paths are different. Regardless, the drcontrol utility captures the correct paths for the catalog backup selections.
You should consider the following items carefully before you configure an MSDP catalog backup:
Do not use theas the destination for the catalog backups. Recovery of the MSDP catalog from its is impossible.
Use a storage unit that is attached to a NetBackup host other than the MSDP storage server.
Use a separate MSDP catalog backup policy for each MSDP storage server.
The drcontrol utility does not verify that the backup selections are the same for multiple storage servers. If the backup policy includes more than one MSDP storage server, the backup selection is the union of the backup selections for each host.
You cannot use one policy to protect MSDP storage servers on both UNIX hosts and Windows hosts.
UNIX MSDP storage servers require a Standard backup policy and Windows MSDP storage servers require an MS-Windows policy.