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
Adding volumes to a 400 TB Media Server Deduplication Pool
When you configure a storage server for a 400 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.The following are the minimum hardware requirements for adding volumes to a 400 TB MSDP:
CPU: A 64-bit processor with a minimum clock rate of 2.4-GHz is required. A minimum of 8 cores are required, 16 cores are recommended.
Memory: Minimum 256 GB. You may need to add more memory if you have additional roles performed by the same media server. For example, when the media server is used as a VMware backup host, an NDMP backup agent and a primary server.
Swap: 64 GB
Storage:
Metadata disk: RAID 0+1 is recommended, with at least 1 TB of space.
Veritas recommends eight mount points, each mount point must have a separate RAID group, a RAID 6 is recommended. Both the metadata disk and data disk should have more than 250 MB/sec of read or write speed.
File Systems: NetBackup supports VxFS, XFS, or Ext4, but VxFS is recommended. The number of storage volumes can vary based on your setup. The maximum amount of storage space is 400 TB. The following procedure uses 8 file systems of 50 TB each for the example.
See About provisioning the storage for MSDP.
To add volumes to a 400 TB Media Server Deduplication Pool
- On the MSDP storage server, you must create, format, and mount new storage volumes. One of the storage volumes must have 1 TB or greater of storage space (this storage is for metadata). The other storage volumes can equal up to 400 TB of storage space.
This procedure uses 8 file systems of 50 TB each for the example.
Note:
The number of storage volumes can vary based on your setup. The maximum amount of storage space is 400 TB.
- Mount a 1 TB storage volume (for metadata) at:
/msdp/cat
- Mount the eight storage volumes on:
/msdp/vol1 ... /msdp/vol8
- Create a touch a file at
/etc/nbapp-release
if it doesn't exist. - Create a subdirectory that is called
data
under each mounted volume:/msdp/vol1/data ... /msdp/vol8/data
- Configure the MSDP through the Storage Server Configuration Wizard and Ensure that the Use alternate path for deduplication database option is checked.
- Provide the storage path as
/msdp/vol1
and the database path as/msdp/cat
. - Add additional 50 TB storage volumes to the deduplication pool:
/usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol2/data ... /usr/openv/pdde/pdcr/bin/crcontrol --dsaddpartition /msdp/vol8/data
- Verify that the deduplication pool contains the new volumes using the following command:
/usr/openv/pdde/pdcr/bin/crcontrol --dsstat 2 | grep Mount Mount point count: 8
To enable 400 TB support, create the following file:
mkdir c:\etc echo Windows_BYO > "c:\\etc\\nbapp-release"
The sizing recommendations for Windows are the same as they are for Linux. One of the storage volumes must have 1 TB of storage space and the other storage volumes can equal up to 400 TB of storage space. Using Windows, there are a few additional requirements:
The DCHeaderHashSize setting in the
<MSDP Storage DIR>\etc\puredisk\contentrouter.cfg
file must be modified to be 2000000 / number_of_volumes. For example, with the full eight mount points, set the DCHeaderHashSize to 250000.The volume that is used should be present as nested volumes, not as letter drives (C: Or E:). Veritas qualified this solution using NTFS volumes.
The following is an example volume layout and each data#
directory is a nested mount:
"msdp_data" :["f:/msdp/data1" ,"f:/msdp/data2" ,"f:/msdp/data3" , "f:/msdp/data4","f:/msdp/data5","f:/msdp/data6", "f:/msdp/data7"], "f:/msdp/data8"], "msdp_cat" :["f:/msdp/cat" ]
The crcontrol syntax is the same as Linux. On Windows, crcontrol is located in <INSTALL_DRIVE>\Program Files\Veritas\pdde\
. For example:
C:\Program Files\Veritas\pdde\crcontrol --dsaddpartition f:\msdp\data2
Note:
MSDP storage capacity has a defined maximum and not following these settings can result in performance-related issues due to data not being balanced across all volumes.
For more information about MSDP storage capacity review the following section:
Note:
NetBackup supports a pool size up to 400 TB. A pool can be a smaller size and expanded later by adding additional volumes.