Recovered datastore mounts with "snap-####" prefix

Products

• VMware Live Recovery
• VMware Site Recovery Manager 8.x

Issue/Introduction

Symptom

• During recovery using VMware Site Recovery Manager or VMware Live Site Recovery with Array Based Replication, the recovered datastores mount with "snap-####" prefix.

Environment

• VMware Live Site Recovery 9.x
  
  
• VMware Site Recovery Manager 8.x
  
  
• Array Based Replication

Cause

• When using Array Based Replication, the datastores in the target site are replica images of the datastores of the source site.
  
  
• For this reason when the LUNs are presented in the target site, during failover or failback, they are detected as snapshots by the ESXi since the information regarding the LUNs in the LVM would not match the information in the wire.
  
  
• Since they are detected as snapshots, they take up the "snap-####"  prefix when they are force mounted by the ESXi hosts in the target site.
  
  
• This is the default behavior while mounting datastores detected as snapshots by ESXi .

Resolution

• To ensure that the datastores are presented with the original names, this default behavior would need to be changed by re-naming the datastore.
  
  
• The below procedure needs to be followed to re-name the datastores:

1. 1. In the vSphere Client, click Site Recovery > Open Site Recovery.
      
      
   2. On the Site Recovery home tab, select a site pair, and click View Details.
      
      
   3. In the left pane, click Configure > Advanced Settings > Storage Provider
      
      
   4. Select a site, and click Edit to modify the storage provider settings.
      
      
   5. Move the slider to change the value of storageProvider.fixRecoveredDatastoreNames

The default value is false "False" - Change the value to "True"

     6. Change the value of storageProvider.fixRecoveredDatastoreNamesDelaySec to 30 seconds

Note: Make the changes for both the sites.

Additional Information

• Change Storage Provider Settings