Unable to mount datastore on second host using same signature

[harsha219]

Using resignatureUnresolvedVmfsVolume_Task method, we can create datastore using a new signature. But how do we create datastore by keeping the same signature using this method? or is there any other method in sdk? Please help.

[Thomas_França]

If you want to keep the same signature while creating a datastore, you would likely need to use a different method or approach, as the purpose of the resignatureUnresolvedVmfsVolume_Task method is to change the signature to avoid conflicts.

If you want to create a new datastore without changing the signature, you would typically use methods that involve formatting or initializing the storage space. However, formatting or initializing a VMFS volume would usually change its signature to ensure uniqueness and avoid conflicts.

It's worth noting that changing a VMFS signature is an advanced operation and should be performed with caution, as it can have implications for data integrity and management within your vSphere environment.

[harsha219 · Accepted solution]

Yes, found out that "resolveMultipleUnresolvedVmfsVolumes" method of HostStorageSystem yields exact result upon specifying the spec UUID resolution to "forcemount".

If I need to mount an existing datastore on second host where there are no datastores, the regular rescan storage option does not create the datastore automatically (which happens if there is at least one datastore assuming lun is from same source). Hence need to force mount.