NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- Planning your MSDP deployment
- NetBackup naming conventions
- About MSDP deduplication nodes
- About the NetBackup deduplication destinations
- About MSDP storage capacity
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About the NetBackup Deduplication Engine credentials
- About the network interface for MSDP
- About MSDP port usage
- About MSDP optimized synthetic backups
- About MSDP and SAN Client
- About MSDP optimized duplication and replication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Use fully qualified domain names
- About scaling MSDP
- Send initial full backups to the storage server
- Increase the number of MSDP jobs gradually
- Introduce MSDP load balancing servers gradually
- Implement MSDP client deduplication gradually
- Use MSDP compression and encryption
- About the optimal number of backup streams for MSDP
- About storage unit groups for MSDP
- About protecting the MSDP data
- Save the MSDP storage server configuration
- Plan for disk write caching
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring MSDP server-side deduplication
- Configuring MSDP client-side deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring deduplication plug-in interaction with the Multi-Threaded Agent
- About MSDP fingerprinting
- About the MSDP fingerprint cache
- Configuring the MSDP fingerprint cache behavior
- About seeding the MSDP fingerprint cache for remote client deduplication
- Configuring MSDP fingerprint cache seeding on the client
- Configuring MSDP fingerprint cache seeding on the storage server
- About sampling and predictive cache
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- About MSDP Encryption using external KMS server
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a disk pool for deduplication
- Creating the data directories for 400 TB MSDP support
- Adding volumes to a 400 TB Media Server Deduplication Pool
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- Disabling MSDP client-side deduplication for a client
- About MSDP compression
- About MSDP encryption
- Configuring encryption for MSDP local storage volume
- Configuring encryption for MSDP cloud storage volumes
- Configuring MSDP encryption on different platforms
- About the rolling data conversion mechanism for MSDP
- Modes of rolling data conversion
- MSDP encryption behavior and compatibilities
- Configuring optimized synthetic backups for MSDP
- About a separate network path for MSDP duplication and replication
- Configuring a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- About MSDP replication to a different domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- About trusted primary servers for Auto Image Replication
- About the certificate to use to add a trusted primary server
- Add a trusted primary server
- Remove a trusted primary server
- Enable inter-node authentication for a NetBackup clustered primary server
- Configuring NetBackup CA and NetBackup host ID-based certificate for secure communication between the source and the target MSDP storage servers
- Configuring external CA for secure communication between the source MSDP storage server and the target MSDP storage server
- Configuring a target for MSDP replication to a remote domain
- About configuring MSDP optimized duplication and replication bandwidth
- About performance tuning of optimized duplication and replication for MSDP cloud
- About storage lifecycle policies
- About the storage lifecycle policies required for Auto Image Replication
- Creating a storage lifecycle policy
- About MSDP backup policy configuration
- Creating a backup policy
- Resilient network properties
- Adding an MSDP load balancing server
- About variable-length deduplication on NetBackup clients
- Managing the variable-length deduplication using the cacontrol command-line utility
- About the MSDP pd.conf configuration file
- Editing the MSDP pd.conf file
- About the MSDP contentrouter.cfg file
- About saving the MSDP storage server configuration
- Saving the MSDP storage server configuration
- Editing an MSDP storage server configuration file
- Setting the MSDP storage server configuration
- About the MSDP host configuration file
- Deleting an MSDP host configuration file
- Resetting the MSDP registry
- About protecting the MSDP catalog
- Changing the MSDP shadow catalog path
- Changing the MSDP shadow catalog schedule
- Changing the number of MSDP catalog shadow copies
- Configuring an MSDP catalog backup
- Updating an MSDP catalog backup policy
- About MSDP FIPS compliance
- Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
- About MSDP multi-domain support
- About MSDP application user support
- About MSDP mutli-domain VLAN Support
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- Running MSDP commands with the non-root user
- MSDP cloud support
- About MSDP cloud support
- Create a Media Server Deduplication Pool (MSDP, MSDP Cloud) storage server in the NetBackup web UI
- Creating a cloud storage unit
- Updating cloud credentials for a cloud LSU
- Updating encryption configurations for a cloud LSU
- Deleting a cloud LSU
- Backup data to cloud by using cloud LSU
- Duplicate data cloud by using cloud LSU
- Configuring AIR to use cloud LSU
- About backward compatibility support
- About the configuration items in cloud.json, contentrouter.cfg, and spa.cfg
- Cloud space reclamation
- About the tool updates for cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About restore from a backup in Microsoft Azure Archive
- About Veritas Alta Recovery Vault Azure
- Configuring Veritas Alta Recovery Vault Azure and Azure Government
- Configuring Veritas Alta Recovery Vault Azure and Azure Government using the CLI
- Migrating from standard authentication to token-based authentication for Recovery Vault
- About MSDP cloud immutable (WORM) storage support
- Creating a cloud immutable storage unit using the web UI
- Updating a cloud immutable volume
- 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
- About using the cloud immutable storage in a cluster environment
- Troubleshooting the errors when disk volume creation using web UI fails
- Deleting the immutable image with the enterprise mode
- Deleting the S3 object permanently
- About MSDP cloud admin tool
- About instant access for object storage in cloud
- About NetBackup support for AWS Snowball Edge
- Upgrading to NetBackup 10.3 and cluster environment
- S3 Interface for MSDP
- About S3 interface for MSDP
- Prerequisites for MSDP build-your-own (BYO) server
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 Object Lock In Flex WORM
- S3 APIs for S3 interface for MSDP
- Disaster recovery in S3 interface for MSDP
- Limitations in S3 interface for MSDP
- Logging and troubleshooting
- Best practices
- Monitoring deduplication activity
- Monitoring the MSDP deduplication and compression rates
- Viewing MSDP job details
- About MSDP storage capacity and usage reporting
- About MSDP container files
- Viewing storage usage within MSDP container files
- About monitoring MSDP processes
- Reporting on Auto Image Replication jobs
- Checking the image encryption status
- Managing deduplication
- Managing MSDP servers
- Viewing MSDP storage servers
- Determining the MSDP storage server state
- Viewing MSDP storage server attributes
- Setting MSDP storage server attributes
- Changing MSDP storage server properties
- Clearing MSDP storage server attributes
- About changing the MSDP storage server name or storage path
- Changing the MSDP storage server name or storage path
- Removing an MSDP load balancing server
- Deleting an MSDP storage server
- Deleting the MSDP storage server configuration
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Viewing Media Server Deduplication Pools
- Determining the Media Server Deduplication Pool state
- Viewing Media Server Deduplication Pool attributes
- Setting a Media Server Deduplication Pool attribute
- Changing a Media Server Deduplication Pool properties
- Clearing a Media Server Deduplication Pool attribute
- Determining the MSDP disk volume state
- Changing the MSDP disk volume state
- Deleting a Media Server Deduplication Pool
- Deleting backup images
- About MSDP queue processing
- Processing the MSDP transaction queue manually
- About MSDP data integrity checking
- Configuring MSDP data integrity checking behavior
- About managing MSDP storage read performance
- About MSDP storage rebasing
- About the MSDP data removal process
- Resizing the MSDP storage partition
- How MSDP restores work
- Configuring MSDP restores directly to a client
- About restoring files at a remote site
- About restoring from a backup at a target primary domain
- Specifying the restore server
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- About universal shares
- Advantages of universal shares
- Configuring and using an MSDP build-your-own (BYO) server for universal shares
- MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure universal shares
- Configuring universal share user authentication
- Mounting a universal share created from the NetBackup web UI
- About universal share self-service recovery
- Performing a universal share self-service recovery
- Using the ingest mode
- About universal shares with object store
- Enabling a universal share with object store
- Disaster recovery for a universal share
- Changing the number of vpfsd instances
- Enabling variable-length deduplication (VLD) algorithm for universal shares
- Upgrading to NetBackup 10.3
- About universal share accelerator
- Preparing NetBackup for the universal share accelerator
- Installing the universal share accelerator
- Configure a universal share accelerator
- Creating a protection policy for the universal share accelerator
- About the universal share accelerator quota
- Recovering a point in time for the universal share accelerator
- Deleting a recovered universal share accelerator
- Logging for universal share accelerator
- Logging and reporting for universal share VPFS instance
- Vpfsd logs for fuse operations in universal shares
- Configuring isolated recovery environment (IRE)
- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a NetBackup BYO media server
- Managing an isolated recovery environment on a NetBackup BYO media server
- Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment
- Configuring an isolated recovery environment on a WORM storage server
- Managing an isolated recovery environment on a WORM storage server
- Configuring data transmission between a production environment and an IRE WORM storage server
- Using the NetBackup Deduplication Shell
- About the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Adding and removing local users from the deduplication shell
- Adding MSDP users from the deduplication shell
- Connecting an Active Directory domain to a WORM or an MSDP storage server for Universal Shares and Instant Access
- Disconnecting an Active Directory domain from the deduplication shell
- Changing a user password from the deduplication shell
- Managing VLAN interfaces from the deduplication shell
- Managing the retention policy on a WORM storage server
- Managing images with a retention lock on a WORM storage server
- Auditing WORM retention changes
- Protecting the NetBackup catalog from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing FIPS mode from the deduplication shell
- Encrypting backups from the deduplication shell
- Tuning the MSDP configuration from the deduplication shell
- Setting the MSDP log level from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Managing the cyclic redundancy checking (CRC) service
- Managing the content router queue processing (CRQP) service
- Managing the online checking service
- Managing the compaction service
- Managing the deduplication (MSDP) services
- Managing the MSDP services across the cluster
- Managing the Storage Platform Web Service (SPWS)
- Managing the Veritas provisioning file system (VPFS) configuration parameters
- Managing the Veritas provisioning file system (VPFS) mounts
- Managing the NGINX service
- Managing the SMB service
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup MSDP log files
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Verify that the MSDP server has sufficient memory
- MSDP backup or duplication job fails
- MSDP client deduplication fails
- MSDP volume state changes to DOWN when volume is unmounted
- MSDP errors, delayed response, hangs
- Cannot delete an MSDP disk pool
- MSDP media open error (83)
- MSDP media write error (84)
- MSDP no images successfully processed (191)
- MSDP storage full conditions
- Troubleshooting MSDP catalog backup
- Storage Platform Web Service (spws) does not start
- Disk volume API or command line option does not work
- Viewing MSDP disk errors and events
- MSDP event codes and messages
- Unable to obtain the administrator password to use an AWS EC2 instance that has a Windows OS
- Trouble shooting multi-domain issues
- Troubleshooting the cloud compaction error messages
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About migration from Cloud Catalyst to MSDP direct cloud tiering
- About Cloud Catalyst migration strategies
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- About postmigration configuration and cleanup
- About the Cloud Catalyst migration -dryrun option
- About Cloud Catalyst migration cacontrol options
- Reverting back to Cloud Catalyst from a successful migration
- Reverting back to Cloud Catalyst from a failed migration
- Appendix C. Encryption Crawler
- Index
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-releaseif it doesn't exist. - Create a subdirectory that is called
dataunder 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/vol1and 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.cfgfile 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.