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. The error can also occur if the MSDP server is running with the older version of NetBackup. Ensure that the MSDP server is running with NetBackup 10.5 or later. |
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 server 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. |