Hi people, we need to mount a datastore that has been previously detached.
It suposed to be an option called: EnableResignature or >DisallowSnapshotLun but is not present at vSphere 5.1.
Can someone has a workarround for this? We just need to mount a datastore without format it!
We use vSphere 5.1 Ent.Plus Lic.
Please Help!
Regards
You can always re-mount a detached datastore to a host if it's still aware that the datastore was just unmounted.
The EnableResignature or DisallowSnapshotLun options are only relevant if you present a new LUN with a VMFS volume to a host that already has a volume mounted with the same VMFS UUID (e.g. a SAN-side snapshot volume).
Since a few ESXi releases you don't even need to set the options manually beforehand. While adding the datastore in the vSphere Client it will just ask you what to do, whether to resignature the volume or not. Resignature just means it assigns another VMFS UUID and datastore name, that's all.
It does not reformat the LUN. So you can safely go ahead and mount the LUN.
Also see:
http://kb.vmware.com/kb/1011387
You can always re-mount a detached datastore to a host if it's still aware that the datastore was just unmounted.
The EnableResignature or DisallowSnapshotLun options are only relevant if you present a new LUN with a VMFS volume to a host that already has a volume mounted with the same VMFS UUID (e.g. a SAN-side snapshot volume).
Since a few ESXi releases you don't even need to set the options manually beforehand. While adding the datastore in the vSphere Client it will just ask you what to do, whether to resignature the volume or not. Resignature just means it assigns another VMFS UUID and datastore name, that's all.
It does not reformat the LUN. So you can safely go ahead and mount the LUN.
Also see:
http://kb.vmware.com/kb/1011387
MKGuy, thanks four your reply.
Your right, our situation is that we re-attach a LUN that has been detached previously; that's why we need to add the "new" datastore without format, because it has a lot of virtual machines.
In the article you mentioned, is the procedure for adding unformatted (see Step 8):
But in our infrastructure this options are not available, that's the reason why I assumed we must modify the above value. (EnableResignature or >DisallowSnapshotLun)
vSphere Client
Thanks in advance
But in our infrastructure this options are not available, that's the reason why I assumed we must modify the above value. (EnableResignature or >DisallowSnapshotLun)
Are you sure this LUN is a valid, consistent VMFS volume? Did you present this LUN to any other system (like a Windows server) in the meantime? Windows loves to automount disks and destroying partition tables out of the blue simply by presenting a disk it can't recognize to it.
If this was a valid VMFS volume the host is able to read, then you would see the options quoted from the article.
To use a previously detached LUN, you'll need to attach it again. See http://kb.vmware.com/kb/2004605 for details and commands.
André
Well, we did some tests and found the answer. The procedure is only removed from the data store, move the LUN to other infrastructure, and the process of assembling data warehouse in the new infraestucture is automatic. That is the reason why no options appear:
"Keep Existing Signature: Persistently mount the LUN (for example, mount LUN across reboots)
Assign a New Signature: resignature the LUN
Format the disk: Reformat the LUN "
So I thank them both for their collaboration.
Regards!