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
The MSDP server maintenance
In a routine node maintenance such as upgrade, EEB installation, OS patching, and system restart we recommend that you intervene to reduce the impact on deduplication ratio or a job failure.
Use MSDP command-line of the MVG server or NetBackup web UI to set the node in the maintenance mode before the routine maintenance and reset afterwards. The MVG server does not move the client policy assignment from the node in maintenance to another node. The new backup jobs may fail temporarily if the node is not stable or functional during the maintenance.
Run the following MSDP commands on the MVG server:
cacontrol --mvg set-mvg-maintenance <msdp-server>
cacontrol --mvg unset-mvg-maintenance <msdp-server>
cacontrol --mvg get-mvg-maintenance
Example:
PATH=$PATH:/usr/openv/pdde/pdcr/bin cacontrol --mvg set-maintenance-mode vramvg037340.rsv.ven.veritas.com Updated virtual volumes: mvg-local cacontrol --mvg get-maintenance-mode MSDP servers in maintenance mode: vramvg037340.rsv.ven.veritas.com Virtual volumes which have the MSDP servers in maintenance mode: mvg-local cacontrol --mvg unset-maintenance-mode vramvg037340.rsv.ven.veritas.com Updated virtual volumes: mvg-local cacontrol --mvg get-maintenance-mode No MSDP servers found in maintenance mode.
On the NetBackup web UI, go to the Disk Pool webpage of an MVG volume, select and edit a disk volume of an MVG volume, then switch the mode between "Maintenance" and "Normal".
Alternatively, you can deactivate the corresponding backup policies temporally during the node maintenance.
Alternatively, if the maintenance cycle is short, you can use or tune out the MVG rebalance freezing time on the MVG server, so that the MVG server does not move the client policy assignment out if the node can be back to stable within the MVG rebalance freezing time. By default, the value is 0.5 hour. It can be tuned by MVG Controller API:
curl -K /uss/config/certificates/controller/.curl_config https://localhost:10100/v1/agent/mvg/loadbalance/config -d '{"asmt_rb_freezing_timeout": 3600 }' -X PATCH
Check the tuning parameters:
curl -K /uss/config/certificates/controller/.curl_config https://localhost:10100/v1/agent/mvg/loadbalance/config