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
Troubleshooting the MVG errors
The following table lists the MVG error messages and how to troubleshoot those.
Table: The MVG error messages
Error message | Description |
---|---|
Failed to validate the name: <detailed info>. | A specified volume name does not meet the MSDP requirements. |
Listing the data selections failed. OR Checking virtual volume awareness failed. | The error occurs if the MVG server cannot use its default credentials to communicate with some MSDP server of the MSDP disk volumes of the MVG volume. You must change the credentials of the MSDP server. See Configuring the MSDP server to be used by an MVG server having different credentials. The error can also occur if the MVG server cannot connect to the MSDP server. Ensure that the connection is established and the MSDP server is functional. |
Conflict in the configuration on <description>. Note: <description> can be "encryption", "KMS", "WORM", "need Warming (for cold cloud storage)" and so on. | The disk volumes for the MVG volume do not have the compatible settings on WORM, Encryption, KMS, or storage class types if they are cloud volumes. |
Volume <msdp-server>:<volume-name> (dsid:<dsid>) is inactive. | The MSDP server of one disk volume is unreachable or it is an inactive cloud volume. |
Members <msdp-server>:<volume-name1> and <msdp-server>:<volume-name2> have the same server name. | Multiple disk volumes of the same MSDP server are selected to be assigned to one MVG volume. |
Virtual volume already exists. | A duplicate MVG volume name is specified. |
Including both cloud LSU and local LSU in a virtual volume is not expected. | Add a cloud volume to an MVG volume with PureDiskVolumes or add a PureDiskVolume to an MVG volume with cloud volumes. |
Member number (<#>) of the MVG volume exceeds the maximum allowed number (<#>). | This error occurs when you try to assign too many disk volumes to an MVG volume. By default an MVG volume can have up to 8 disk volumes. The number is configurable but is not recommended. |
Maximum allowed MVG volume number (<#>) is reached. | This error occurs when you try to create too many MVG volumes on the MVG server. By default an MVG volume can have up to 64 MVG volumes. The number is configurable but is not recommended. |
It's not allowed to reduce the member number from <#> to <#> for virtual volume <volume-name>. | This error occurs when you try to remove some disk volumes from an MVG volume. |
It's not allowed to change disk volume <msdp-server1>:<volume-name1> to <msdp-server2>:<volume-name2> for virtual volume %s. | This error occurs when you try to insert a disk volume or change the order of the disk volume list of an MVG volume. |
Member <msdp-server>:<volume-name> is not aware of virtual volume. | This error occurs when you try to assign a disk volume of an old MSDP server to an MVG volume. |
Cannot find dsid for member <msdp-server>:<volume-name>. | A bad disk volume name is specified. |
Changing virtual volume assignment failed: No disk pool was found for the disk volume. | The disk volume that is being assigned to an MVG volume does not have a corresponding disk pool configured in NetBackup. |
Changing virtual volume assignment failed: failed to find the disk pool name <dp-name>. | NetBackup web service is not working normally. When the error happens, retry the MVG volume configuration or ensure that the NetBackup web service is working correctly. |