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 stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Configuring deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About MSDP Encryption using NetBackup Key Management Server service
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- 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 volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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 object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- About the cloud direct
- 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
- Disaster recovery in S3 interface for MSDP
- 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
- About MSDP data integrity checking
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Universal share scale out
- Managing universal share services
- Troubleshooting issues related to universal shares
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- 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 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
Using multiple MSDP nodes for multistream backups on MSDP cluster
In the MSDP cluster environments, balancing the load across multiple nodes is crucial for maintaining optimal performance. MSDP has either a single node configuration or a cluster configuration. MSDP cluster configurations such as Flex Scale, Cloud Scale, and MSDP volume groups may have multiple nodes. These clustered configurations allow for enhanced scalability and performance for multistream backups.
Starting with NetBackup 11.0, a new policy attribute Use multiple MSDP nodes is introduced to improve load balancing for multistream backups on MSDP cluster storage servers. This feature enables the distribution of backup streams across the multiple MSDP nodes, optimizing throughput, and reducing potential congestion on individual nodes.
Before NetBackup 11.0, the policy name prefix MSDPLB+ was used to enable the use of multiple MSDP nodes for multistream backups. While functional, the MSDPLB+ naming convention was not always the most convenient, and prompted the introduction of the new policy attribute in NetBackup 11.0.
Consider the following points when using this option:
This policy attribute is designed to use only for multiple stream backups on the MSDP cluster storage servers. For a single-node MSDP storage server, this attribute has no effect.
This policy attribute is not available for the following policy types. Some of these policy types already have more advanced features that handle the distribution of backup streams across multiple MSDP nodes. For others, using multiple MSDP nodes is not applicable due to the nature of the policies.
Oracle
Epic-large-file
Universal-share
MSDP-object-store
The media server must be running NetBackup 11.0 or later to use this option. If the storage server is configured with the media servers of an earlier version, the backup job fails with the job status code 213. However, for environments running earlier versions, the MSDPLB+ policy prefix can still be used to enable load balancing across multiple MSDP nodes.
For smaller backups, we recommend not enabling this option. Without this option enabled, deduplication on the same node is the most efficient way to minimize storage and network utilization.
If the client data is large and the backup job cannot finish within the backup window, enable this option to use multiple MSDP nodes for parallel data processing, reducing backup time.
Some client applications might not send backup data to NetBackup in a same order as the previous backups. In such cases, MSDP may require more storage and network resources across nodes to manage the data streams. Enabling this option for these types of applications may reduce system efficiency.
See Enabling the media server and MSDP engine affinity in the MSDP cluster.