Quantcast
Channel: VMware Communities: Message List - Backup & Recovery
Viewing all articles
Browse latest Browse all 5692

Long story... Replication crippled most of our backups. What can we do now?

$
0
0

And here we go...

 

On March we decided to use VDP and VR. We're running vSphere 5.1 U1, according to the matrices below we installed VDP 5.5.5 and VR 5.1.2.

 

 

 

Later, on April, we patched VDP from 5.5.5.180 to 5.5.6.56. We also decided to demote VR and work with VDP only.

 

So the VR appliance was shutdown, deleted, removed from the extensions according to VMware documentation, and here we are...

 

This week we tried to restore a VM from VDP... surprisingly we got this error message:

 

 

Ok, we've found this KB and is not worked... then we've found this instructions to cleanup some VM orphaned properties from VR. And guess what? We're still unable to restore past-replicated VMs... same error above.

 

I've researched a little bit and I found a difference between the .VMX and .VMX~ files from these VMs: even after cleanup the replication properties using the vim-cmd hbrsvc/vmreplica.disable VM_ID, the files look like this...

 

 

So we took a drastic action... we've shutdown one of these affected VMs, removed if from inventory and re-inventoried it to make it read the VMX files again... the VR dirty on VMX files disappeared, but we're still unable to restore SEVERAL previously replicated VMs.

 

What can we do now?

 

Regards,

FABrizzolla


Viewing all articles
Browse latest Browse all 5692

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>