Article Number: 541725

printer Print mail Email

RecoverPoint for Virtual Machines: ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2

Summary: CG goes into error state due to 1 or more devices were removed from production VM

Primary Product: RecoverPoint for Virtual Machines

Product: RecoverPoint for Virtual Machines more...

Last Published: 21 Apr 2020

Article Type: Break Fix

Published Status: Online

Version: 4

RecoverPoint for Virtual Machines: ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2

Article Content

Issue


Errors seen in logs:

CLI:
ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2
ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME-1.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2

The above ERROR will have to have the below in order to be relevant for this KB. 

ERROR: The VMDKs of VMs in production group [CG name, Remote Copy Name] are not identical to their copies (VM_NAME_scsix:x size:size, VM_NAME-1_scsix:x size:size). There are VMDKs missing from production. Add VMDKs with the same port type and ID and the same size as the original (which causes a volume sweep), or unprotect and reprotect the production VMs (which causes journal loss and full sweep).
Cause
1 or more devices were removed from production VM, however RecoverPoint still has the settings for the missing devices.
Resolution
From the plugin, on the protection tab, type in the VM name (there may be more than 1 e.g. VM_NAME | VM_NAME-1 as you can see from the above ERROR: User volume), click on the correct VM pertaining to the ERROR, click Edit on the right under the list of protected VMDKs, then look for the below "VMDK was deleted by user" as you see below:

User-added image

Once you find "VMDK was deleted by user" uncheck the box next to it and press OK. *Before you do this, please get the customer's permission!*
Notes

Issue


Errors seen in logs:

CLI:
ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2
ERROR: User volume [CG name, Copy, CG_RSET_VM_NAME-1.copy.shadow_x_x_scsi] cannot be accessed by: RPA 1, RPA 2

The above ERROR will have to have the below in order to be relevant for this KB. 

ERROR: The VMDKs of VMs in production group [CG name, Remote Copy Name] are not identical to their copies (VM_NAME_scsix:x size:size, VM_NAME-1_scsix:x size:size). There are VMDKs missing from production. Add VMDKs with the same port type and ID and the same size as the original (which causes a volume sweep), or unprotect and reprotect the production VMs (which causes journal loss and full sweep).
Cause
1 or more devices were removed from production VM, however RecoverPoint still has the settings for the missing devices.
Resolution

From the plugin, on the protection tab, type in the VM name (there may be more than 1 e.g. VM_NAME | VM_NAME-1 as you can see from the above ERROR: User volume), click on the correct VM pertaining to the ERROR, click Edit on the right under the list of protected VMDKs, then look for the below "VMDK was deleted by user" as you see below:

User-added image

Once you find "VMDK was deleted by user" uncheck the box next to it and press OK. *Before you do this, please get the customer's permission!*

Notes

Article Attachments

Attachments

Attachments

Article Properties

First Published

Wed Mar 04 2020 14:44:11 GMT

First Published

Wed Mar 04 2020 14:44:11 GMT

Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters