Troubleshooting: Recover operation in case of add/remove disks

Following are some issues that you may encounter in case of add/remove disks if you perform recover operation on resiliency group:

Table: Recover operation in case of add/remove disks

Recover operation in case of add/remove disks	Description	Solution
If a disk is added to a workload which is protected by DR enabled resiliency group, risk appears on the resiliency group for the newly added disk. In this case all operations are blocked except recover. For example: A virtual machine has 3 disks attached and a new disk is attached.	After performing recover operation, the workload will be up on the target data center with the same configuration before adding a new disk. Risk for new disk should disappear from the source data center. After performing resync operation, replication should become healthy with the current disk configuration (3 disks) and newly added disk from the source data center is present on datastore unattached from the virtual machine or Replication Gateway.	If you migrate back to the source data center, virtual machine is up with 3 disks. At this time you can attach the new disk back to the virtual machine and perform the edit operation.
If a disk is removed from a workload which is protected by DR enabled resiliency group, risk appears on the resiliency group for the removed disk. In this case all operations are blocked except recover. For example: A virtual machine has 3 disks attached and a disk is removed.	After performing recover operation, the workload will be up on the target data center with the same configuration before adding a new disk. Risk for removed disk should disappear from the source data center. After performing resync operation, this operation fails as the disk is missing from the source data center.	You need to delete the resiliency group and recreate If in case creating a new resiliency group is not supported on the target data center, follow the steps provided to recover from this situation.

Recover operation in case of add/remove disks

Description

Solution

If a disk is added to a workload which is protected by DR enabled resiliency group, risk appears on the resiliency group for the newly added disk. In this case all operations are blocked except recover.

For example: A virtual machine has 3 disks attached and a new disk is attached.

After performing recover operation, the workload will be up on the target data center with the same configuration before adding a new disk.
Risk for new disk should disappear from the source data center.
After performing resync operation, replication should become healthy with the current disk configuration (3 disks) and newly added disk from the source data center is present on datastore unattached from the virtual machine or Replication Gateway.

If you migrate back to the source data center, virtual machine is up with 3 disks. At this time you can attach the new disk back to the virtual machine and perform the edit operation.

If a disk is removed from a workload which is protected by DR enabled resiliency group, risk appears on the resiliency group for the removed disk. In this case all operations are blocked except recover.

For example: A virtual machine has 3 disks attached and a disk is removed.

After performing recover operation, the workload will be up on the target data center with the same configuration before adding a new disk.
Risk for removed disk should disappear from the source data center.
After performing resync operation, this operation fails as the disk is missing from the source data center.

You need to delete the resiliency group and recreate
If in case creating a new resiliency group is not supported on the target data center, follow the steps provided to recover from this situation.

Troubleshooting: Recover operation in case of add/remove disks

Feedback

Feedback