I’m going through the process of installing VMWare Site Recovery Manager (SRM) 6.1 in our production environment, which is currently running vSphere 6.0U1.
We use Nimble Storage arrays and have elected to make use of array based replication (ABR) for data replication between sites.
During our initial testing and doing full failovers of some dev applications, I noticed that the datastore name within vCenter for the protected volume on the SAN was getting renamed, and had a prefix of snap-5b356a02-VolumeName
SRM doesn’t modify the underlying SAN volume / LUN name at all.
You could just go ahead and rename the datastore within vCenter to remove this prefix, but I had a look through the advanced options in the SRM 6 manual and found the following setting:
To implement this advanced setting;
- Browse to the vSphere Web client and click on the Site Recovery plugin
- Click on Sites > Select your first site > Manage > Advanced Settings > Storage Provider > Edit
- Scroll down to storageProvider.fixRecoveredDatastoreNames and tick the box to enable this setting
Also note that there is another advanced setting related to this, which is storageProvider.fixRecoveredDatastoreNamesDelaySec – “Change the time that Site Recovery Manager waits before removing the snap-xx prefix applied to recovered datastore names. The default value is 0 seconds.”
Rinse and repeat for any other sites that you have paired within SRM