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
- 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
Adding volumes to a 96-TB Media Server Deduplication Pool
When you configure a storage server for a 96-TB
, you specify the pathname of the first storage volume. Before you can use the , you must add the other two volumes to the disk pool.To add the other volumes to a 96-TB Media Server Deduplication Pool
- On the MSDP storage server, use the crcontrol utility to add the second and third 32-TB volumes to the disk pool. You must include the
data
directories as part of the pathname. The following is the command syntax:/usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition pathname
The following two examples show how to add the pathnames for
/msdp/vol1
and/msdp/vol2
volumes:# /usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol1/data Partition /msdp/vol1/data was added successfully. # /usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol2/data Partition /msdp/vol2/data was added successfully
After the next polling cycle of the NetBackup Remote Manager and Monitor Service, the NetBackup Administration Console displays the new, expanded capacity for the disk pool.
Note:
For a Media Server Deduplication Pool, NetBackup exposes the storage as a single volume in the NetBackup Administration Console. Therefore, if you have a 96-TB Media Server Deduplication Pool, the number of volumes is 1 even though three volumes are used for the storage.
- On the MSDP storage server, you can use the crcontrol utility to verify that the Media Server Deduplication Pool contains the new volumes. If the volumes were added correctly, there should be three mount points as follows:
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat 2 | grep Mount Mount point count: 3 =============== Mount point 1 =============== =============== Mount point 2 =============== =============== Mount point 3 ===============
- To display detailed information about the disk pool, use the crcontrol --dsstat 3 command, as follows:
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat 3