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
- 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
- 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
- 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 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
Configuring MSDP fingerprint cache seeding on the storage server
On the storage server, the NetBackup seedutil utility creates a special seeding directory for a client. It populates the seeding directory with image references to another client and policy's backup images. The following is the pathname of the seeding directory:
database_path/databases/catalog/2/#pdseed/client_name
(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.)
When a backup runs, NetBackup loads the fingerprints from the #pdseed
directory for the client. (Assuming that no fingerprints exist for that client in the usual catalog location.)
Information about when to use this seeding method and how to choose a client from which to seed is available.
See About seeding the MSDP fingerprint cache for remote client deduplication.
To seed the fingerprint cache from the storage server
- Before the first backup of the remote client, specify the clients and the policy in the following format:
UNIX: /usr/openv/pdde/pdag/bin/seedutil -seed -sclient client_name -spolicy policy_name -dclient destination_client_name
Windows: install_path\Veritas\pdde\seedutil -seed -sclient client_name -spolicy policy_name -dclient destination_client_name
Note:
NetBackup treats long and short host names differently, so ensure that you use the client name as it appears in the policy that backs it up.
- Repeat the command for each client that you want to seed with fingerprints.
- Verify that the seeding directories for the clients were created by using the following command:
seedutil -list_clients
- Back up the clients.
- After the client or clients are backed up, remove the seeding directories for the clients. The following is the command syntax:
seedutil -clear client_name
After one full backup for the client or clients, NetBackup clears the seeding directory automatically. If the first backup fails, the seeded data remains for successive attempts. Although NetBackup clears the seeding directory automatically, Veritas recommends that you clear the client seeding directories manually.