===== vSphere: LUNs detected as snapshot LUNs =====

If the datastore doesn't appear in the list, after connecting a spnashot or replica then 2 ways:

Connect to ESX server using Vspere GUI
--> Rescan VMFS
--> Try to Add storage, select a snapshot, and not resign the LUN

Else if it's not working, connect to the ESX using command line:

Mount a snapshot (or clone from replication) on a specific ESX if datastore not automatically reconized:
<cli prompt='#'>
The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # esxcli storage core adapter rescan --all
~ # esxcli storage vmfs snapshot list
4e0adf0c-cefffef9-5203-00101886766c
   Volume Name: VMFS2
   VMFS UUID: 4e0adf0c-cefffef9-5203-00101886766c
   Can mount: true
   Reason for un-mountability:
   Can resignature: false
   Reason for non-resignaturability: the volume is being actively used
   Unresolved Extent Count: 1
~ # esxcli storage vmfs snapshot mount -n -l "VMFS2"
</cli>

-n : is used for non persistent, means in case of reboot, VMFS won't be mounted again

**In case of clone, it important to unmap the clone source to prevent mount problems**

Do a resignature of the clone volume to make it available
<cli prompt='#'>
# esxcfg-volume -r <UUID>
# esxcfg-volume -M <vmfs_name>
</cli>

The datastore should appears as **snap-XXX**, now you can rename IT

FIXME

When registery VM and start it select **I MOVE IT**