bigjon-x64
asked on
VMFS label missing on cloned replica
During a recent DR test one of my replicated volumes was missing a VMFS label and I wasn't able to get it mounted. After the rescan, I did the normal add storage and when I selected that volume, instead of asking to resig or keep the existing signature, it asked me to format as VMFS5 or VMFS3.
I tried multiple snapshots and different servers and they all wanted to format.
vSphere 5.1 attached to Equallogic connected via iSCSI.
I tried multiple snapshots and different servers and they all wanted to format.
vSphere 5.1 attached to Equallogic connected via iSCSI.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need VAAI and make sure snapshots are offloaded to equallogic, so that the replica is accurate and usable
ASKER
esxcfg-volume -l returns
VMFS UUID/label: NA
Can Mount: No (some extents missing)
Can resignature: No (some extents missing)
Extent Name naa.6090a0b8a0550a2d7e3435 ca4a25347b :1 range 857127608576 -857127608831 (MB)
I don't remember extending the volume since the last test.
VMFS UUID/label: NA
Can Mount: No (some extents missing)
Can resignature: No (some extents missing)
Extent Name naa.6090a0b8a0550a2d7e3435
I don't remember extending the volume since the last test.
This is the reason it cannot be mounted, it does not appear to be complete or is corrupted.
Are you using the recommended Dell Equallogic Virtual Storage Manager for VMware vSphere on your Hosts and vCenter Server, which provides you with a GUI, interface to Create Smart Copies (SAN Snapshots) and Replicas, which can be mounted from within vSphere vCenter Server.
Are you using the recommended Dell Equallogic Virtual Storage Manager for VMware vSphere on your Hosts and vCenter Server, which provides you with a GUI, interface to Create Smart Copies (SAN Snapshots) and Replicas, which can be mounted from within vSphere vCenter Server.
ASKER
Yes and no. The replication for this volume was set up prior to VSM and hasn't had a problem in previous D.R. tests, so it wasn't a big priority to change. Is the best course to create a new data store, configure replication, and storage vmotion the affected VMs?
I think I would test, create a new datastore, configure replication on this new datastore and LUN, and then check and present to VMware ESXi.
ASKER
Thanks for the help.