VPG outside of ZORG. Errors from recovery side. VPG Customer_104272_MCREC28606004 contains resources that are not assigned to the ZORG ASG_DJR_104272. Move the protected resources to the ZORG or change the contents of the VPG. Details: VM rpr00610 uses a root resource pool, but it belongs to a ZORG. ; VM rpr00620 uses a root resource pool, but it belongs to a
ZORG. ; VM rpr00611 uses a root resource pool, but it belongs to a ZORG. ; VM rpr00621 uses a root resource pool, but it belongs to a ZORG. ; Datastore Customer_104272_M4DST28606001
P700, in use by VM rpr00621 (volume scsi:0:1), is not part of the ZORG. ; Datastore Customer
104272_M4DST28606001_P700, in use by VM rpr00621 (volume scsi:0:0), is not part of the ZORG.
Received an email regarding the above warning. We logged into the zcm to view the vCenter cloud resources and saw that Customer_104272_M4DST28606001_P700 was missing from here. After adding this in, we resolved most of the warning, however, the “VM
Received an email regarding the warning VPG outside of ZORG. There are two steps to resolve this as it is both affecting by Datastores and VMs as seen by the VM or Datastore prefixes:
- Resolving the datastore issue a. Double check the resources (either vSphere or VCD - this instance was on vSphere) on the ZCM, found that the Customer_104272_M4DST28606001_P700 was missing. After adding this in it was removed from the warning.
- Resolving “VM
uses a root resource pool, but it belongs to a ZORG” a. Looking at the error, it is from the recovery side. Looking at vSphere, the VM’s were correctly in a resource pool, however, the VPG had been configured to dump them at the cluster level (ZVM → locate VPG → edit VPG → Replication → Default Recovery Servers). This was then changed to the resource pool (from Customer_104272Cluster01 → RP:Customer_104272-Cluster01 Normal). When saving, there was a warning saying that this change only effects new VMs and not the existing VMs. To change this, you edit this in the VM settings section.