Check my thinking on this: ESX / moving data to another pool

[jamiejunk]

I want to move my data to another pool on the same freenas host. The plan is to replicate a snapshot over to tank2. Later at night I will shut down all the servers, do a manual snapshot and replicate the updates to tank2.

The ESX hosts are expecting a path like /mnt/tank1/esx.
The new path is /mnt/tank2/esx

I'm wondering if I should have created the nfs export like /mnt/export/esx and had that just be a link to /mnt/tank1/esx. Then when I was done with the data move I could have just changed the hard link.

Any thoughts on this?

 

[jamiejunk]

Never mind. I read over the VMware docs and it mentioned VMware uses some sort of hashed UUID on volumes. Apparently even if you say upgrade to a 10 gig nic it borks the setup by changing the UUID.
So much for my disaster recovery plan.