NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- 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
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- 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
- Configuring and using universal shares
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
About provisioning the storage for MSDP
NetBackup requires that the storage is exposed as a directory path.
Provision the storage as follows:
Up to 64 TBs | |
400 TBs |
How many storage instances you provision depends on your storage requirements for your backups. If your requirements are greater than one deduplication node can accommodate, you can configure more than one node.
See About MSDP deduplication nodes.
Optimized duplication and replication also can affect the number of nodes you provision.
See About MSDP optimized duplication and replication.
Other NetBackup requirements may affect how you provision the storage.
See About MSDP storage and connectivity requirements.
How to provision the storage is beyond the scope of the NetBackup documentation. Consult the storage vendor's documentation.
See About the NetBackup deduplication destinations.
See Planning your MSDP deployment.
Provision the backup storage so that it appears as a single mount point to the operating system.
Because the storage requires a directory path, do not use only the root node (/) or drive letter (E:\) as the storage path. (That is, do not mount the storage as a root node (/) or a drive letter (E:\).
If you use a separate disk volume for the deduplication database, provision a 1-TB volume on a different mount point than the backup data storage.
NetBackup supports 400 TBs of storage in a single
on certain operating systems.See About MSDP storage capacity.
Before you configure the MSDP storage server, you must provision the volumes. Each volume must conform to the following items:
Formatted with a file system that NetBackup supports for MSDP. The same file system must be used for all volumes.
Reside on a separate disk from the other volumes that you allocate for the MSDP storage.
Mounted on a separate mount point on the computer that you want to use as the MSDP storage server.
Veritas recommends that you use a descriptive naming convention for the mount point names.
- Create, format, and mount 9 new file systems - one file system must have 1 TB storage space and the other 8 file systems must have 50 TB storage space each.
- Mount the 1 TB file system at /msdp/cat and the 50 TB file systems on /msdp/vol0, /msdp/vol1 and so on until each volume is mounted.
- Create a touch a file
/etc/nbapp-release
if it does not exist. - Create a subdirectory named data under each mounted volume. For example,
/msdp/vol0/data
,/msdp/vol1/data,
/msdp/vol2/data
, and so on. - Configure MSDP through the Storage Server Configuration Wizard. Ensure that the Use alternate path for deduplication database option is selected. Provide the storage path as
/msdp/vol0/data
and the database path as/msdp/cat
. - Add additional 50 TB file systems to the deduplication pool:
/usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol1/data /usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol2/data till volume 07... /usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol7/data
- Review the following command output to verify the created volumes:
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat 2 | grep Mount Mount point count: 7
More Information