Network and Storage Protocols

How to migrate VMware NFS to a different qtree?

nicholas4704
3,488 Views

Hello

I need to migrate vmware NFS datastore to another FAS array. It could be offline migration. I don't want to click "Ad to Inventory" for every VM.

What is the best way?

I'd like to use qtree SnapMirror, but ESX does not recognize SnapMirrored datastore.

I can create new Datastore and mount snapmirrored but I'll have to do "Add to inventory" for each VM in datastore.

Even if I snapmirror everything to a destinaton qtree then move VMs to the same qtree as on source (in my case root qtree) then change IP and volume FSID.  VMware still does not recognize datastore.

SnapMirror: SourceFiler:/vol/vmware_nfs -> DestinationFiler:/vol/vmware_nfs/qtree

Move VMs to volume root: mv /vol/vmware_nfs/qtree/* /vol/vmware_nfs/

Change FSID Destination FSID = Source FSID

Change IP: Destination IP = Source IP

Thank you.

Nick.

PS.

I managed to do it with iSCSI by changing SCSI id, but no luck with NFS.

2 REPLIES 2

forgette
3,488 Views

ESX recognizes NFS datastores using the host and share path.

So, if you're datastore is mounted as:

10.1.1.2:/vol/datastore

You'll need the same thing on the destination.
Hostname resolution and share path difference can cause issues.
For example, the following are not considered the same datastore:
10.1.1.2:/vol/datastore
10.1.1.2:/vol/datastore/
nor are these:
10.1.1.2:/vol/datastore
myHost:/vol/datastore
nor are these:
10.1.1.2:/vol/datastore
10.1.1.2:/vol/datastore/newQtree

nicholas4704
3,488 Views

Hi

Thanks for reply.

The problem is that it is not enough.

Even if you transfer datastore to different filer and change IP addressESX will not accept that datastore. (in my experience)

Looks like you need NFS handlers copied, not only FSID.

This operation can be done using snapmirror migrate command, but this works only with volumes, not qtrees.

Nick.

Public