Reprotect failed with "A recovered disk was not found for replicated disk with UUID xx-xx-xx-xx-xx"
book
Article ID: 338453
calendar_today
Updated On:
Products
VMware Live RecoveryVMware vSphere ESXi
Issue/Introduction
Symptoms: When configuring replication with a seed disk which has a different UUID from the source disk, reprotect failed with "A recovered disk was not found for replicated disk with UUID xx-xx-xx-xx-xx"
Environment
VMware vSphere Replication 8.x
Resolution
The issue is resolved in vSphere Replication 8.3.1.1.
Workaround:
Login to the primary vCenter mob to check the disk's UUID.
For example, go to https://10.186.102.28/mob/?moid=vm-19&doPath=config.hardware and click virtual disk.
Click backing.
Find the UUID for the related source disk.
Using secondary VC mob to set the seed disk UUID to be the same as the source disk uuid: https://secondary.vc.address/mob/?moid=virtualDiskManager&method=setVirtualDiskUuid For example, name = [secondary-esx-2]replicas/TestVm-1/disk_2001.vmdk datacenter = <datacenter type="Datacenter">datacenter-3</datacenter> UUID = 60 00 C2 9c ## ## ## ##-## ## ## ## 16 39 8f 53
Note: VirtualDiskManager.setVirtualDiskUuid API accepts another UUID format.
Performed vm.reload() on the recoveredVM using https://secondary.vc.address/mob/?moid=<VM_ID>&method=reload.