Hi,
Please open an SR (if you haven't already) and upload SRM + vSphere Replication support bundles for both protection and recovery sites.
The VRMS logs are needed to troubleshoot the "Optimistic locking failure".
About the issues experienced:
- there should be details for the real cause somewhere at the end of the "Error creating test bubble image for group ...", both in the UI and in VRMS logs (/opt/vmware/hms/logs at the recovery site VRMS)
- failing to create the test bubble replica image might not be necessarily due to disconnected and re-connected datastore
- reconfiguring the replication group detected either changed target path for one or more of the disks or changed path for the replica of the config files and internally triggered replication unconfigure + configure (this is known issue with vSphere Replication and is being addressed in a future release). The unconfigure part removed the placeholder disks at the recovery site and configure probably failed, as it expected to find the initial copies. If the disk paths weren't changed, unconfigure and configure wouldn't have happened and VRMS would have just updated the datastore managed object id value.
- the appliances have been reinstalled, but perhaps the VRMS database has been preserved and the VRMS configured from the existing database, simply re-installing VRMS and keeping the database won't change anything for a VM's replication configuration
To be able to troubleshoot the "Optimistic locking failure" we need to take a look at the VRMS logs and see what is wrong with the replication settings/state for that particular VM.
Regards,
Martin