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 can also 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 destination.
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 capacity support and hardware requirements.
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.
Cohesity recommends that you use a descriptive naming convention for the mount point names.
- Create, format, and mount nine new file systems. One file system must have 1-TB storage space and the other eight 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 file
/etc/nbapp-releaseif 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 an MSDP storage server. Ensure that the Use alternate path for deduplication database option is selected. Provide the storage path as
/msdp/vol0/dataand 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
If a non-root user is used for the NetBackup media server, run the following command to change the owner of the newly created volumes to the NetBackup media server service user:
chown -R <NBU-service-user>:root <MSDP-volume-path>
- 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