Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 193198

'Optimistic locking failure' after failed clean-up

$
0
0

Hello,

 

I have configured five VM's configured successfully with vSphere Replication (VR). One of them that was replicating Ok, after a recovery test that I was trying to do the clean-up, failed with "time-out error more than 900 sec" in the storage phase. The Windows VM has 17 vDisks, and about 4.5TB of data.

 

After this, I tried to execute a new test, and the recovery plan failed with the message "Error creating test bubble image for group..."; with this message I found in http://www.vmware.com/support/srm/srm_releasenotes_5_0_0.html:

To resolve this issue, you must reconfigure replication using the following procedure:

  1. Clean up the recovery plan that has just failed.
  2. Start the Reconfigure wizard for affected the protection group.
  3. Change the location of files that are on the datastore that has been disconnected. Select the same datastore and folder locations.
  4. Agree to reuse the existing disks, as suggested by the wizard. Reconfigure the virtual machine.
  5. The protection group enters a full sync state, during which data consistency is checked. Wait for the process to complete.

Despite the fact that I wasn't aware of any disconnect of the storage, I tried the procedure. Funny was that it asked me twice for each one of the 17 disks the message to reuse the disk (duplicate file found). After this, according to the release notes, it should enter a sync state, however I noticed in the "recent task" that it actuall deleted all vDisks in the replicated datastore and failed the "initial sync".
Having no more other option I was aware of, I stopped replication and try to reconfigure again. When I did that, I got the error "VRM Server generic error. Please check the documentation for any  troubleshooting information. The detailed exception is: 'Optimistic  locking failure'."

So I de-install everything from the Protected and Recovered site (by everything I mean SRM server, the VRM Server and the VR Server from both sites). Reinstall all, reconfigure, try to enable VR on the same 17 disks VM and still having the 'Optimistic  locking failure'.

 

I tested with other VMs and it is working.

 

I saw many hint on this community to try to remove, re-add the VM in the inventory, or even remove the VM, create a new VMX file and re-attached all disks, but I can't do it now, so hopefully someone would have any idea on how to fix this without having to power down the VM in question.

 

My environment is using vCenter 5.0 U1 and SRM 5.0.1.

 

Thanks for any hints,

 

Regards,


Viewing all articles
Browse latest Browse all 193198

Trending Articles



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