On performing the recover operation when the risk Existing disk is detached from virtual machine is present on the resiliency group, resync operation may fail.(33645)
Resync operation after recover might fail as there is no disk on the source data center, and editing or recreating a resiliency group is not allowed. Due to this, the virtual machine would be stuck in the cloud and there is no simple way to migrate back to the premise using Resiliency Platform console.
Workaround: Need to follow the below steps to resolve this issue.
Fetch the disk ID, disk name, and disk size from the database for the disk which is removed.
Create the same size disk on the source data center datastore.
Change the disk ID of the new disk from IMS to the disk ID of the disk which is removed.
Rename the disk from vCenter server to the name of the disk which is removed.
Perform resync operation from Resiliency Platform console. Perform migrate operation to source data center. After migration, detach disk risk will be raised on the resiliency group.
Perform full edit operation on the resiliency group. Risk is resolved after the edit operation.