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
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- 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 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
- 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 bucket-level immutable storage support for Google Cloud Storage
- 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
- Configuring MSDP data integrity checking behavior
- 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
- 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
MSDP volume group best practices
The following are some of the best practices with the MSDP volume group.
Put an MVG server close to the regular MSDP servers of which the physical volumes are grouped by the MVG server.
The MVG server and the load balance media servers of the MVG server can reach the MSDP servers efficiently with low latency and good throughput.
Add the media servers of the regular MSDP servers to the load balance media server list of the MVG server. Consider adding more media servers to the list if there are.
Put an MVG server in a reliable place, which is desired to have physical isolation with the regular MSDP servers.
As an example, the MVG server can be configured on the NetBackup primary server if it is the only MVG server, or on HA-enabled Flex appliance or BYO environment.
The physical volumes in one MVG volume have the similar configuration.
They have similar volume size, similar server CPU/memory, similar disk/network performance. It makes a more balanced load between the physical volumes and MSDP servers.
They are enforced to have the same encryption, KMS, WORM, and other security configuration. The MVG volume creation fails if the settings do not match.
Add a new MVG server only when needed to reduce cost and not compromise on the performance.
Add a new MVG server only when the existing ones cannot meet the requirements. For example, physical isolation between the MVG servers and the MVG volumes is needed. The existing MVG server too small to manage many MVG volumes. The MVG server has too many MVG volumes.
Do not use multiple MVG servers to manage the physical volumes of the same MSDP servers.
Do not have a physical volume assigned to multiple MVG volumes, does not matter if the MVG volumes are managed by the same or different MVG servers.
If an MSDP server has multiple volumes, they can be assigned to different MVG volumes of different MVG servers. However, it is not recommended.
Once a physical volume is assigned to an MVG volume, it's not recommended to use it anymore for NetBackup jobs.
It does not block anything if the physical volume continues being used. You can still use it to restore the pre-existing backup images. The currently working configuration with the physical volume can continue working. To have a more balanced load, remove it from the configuration of the backup policy when it is assigned to an MVG volume.
Deactivate the media server on an MVG server if it is small.
If the MVG server is small, deactivate the media server on the MVG server from NetBackup scheduling jobs on it when there are additional load-balancing media servers for the MVG server. Do not deactivate it if it is the only load-balancing media server of the MVG server.
You can go to NetBackup web UI Storage > Media server, select the MVG server, then click .
You can also run the following NetBackup command:
/usr/openv/netbackup/bin/admincmd/nbemmcmd -updatehost -machinename <mvg-server> -machinestateop set_admin_pause -machinetype media -masterserver <primary-server>