We are going to perform a migration from FAS2020 to FAS2520 (both dual controller). We would want to perform this without changes in the clients (nfs and cifs mappings, vmware datastores, iscsi connections... etc).
This is what we have to migrate from the FAS2020:
-Filer1: - one volume wich contains 1 VMWARE datastore accesed vía NFS and contains all the virtual machines.
-Filer2: - 3 volumes containing CIFS shares for user files.
- 1 volume containing 1 LUN accesed vía iSCSI for a backup software
Our plan is to do the follwing steps:
-Ask for 4 snapmirror test licenses (one for each controller).
-Set up the new FAS2520 with temporal hostnames and IPs
-Set up a snapmirror relationship to migrate all volumes.
-Stop client access to the old filer and perform an snamirror update. (stop VMWARE virtual machines and backup software, and stop cifs in the filer)
-Break and release snapmirror relationships
-Set up iscsi, cifs and nfs options to match the old ones (iscsi groups, lun mappings,cifs shares and nfs exports).
-Change hostnames and Ips in the old filers (so there is no duplicated ones when we rename the new filers)
-Change hostnames and IPs in the new filers to match the ones mapped in the clients.
-Restart client access
Do you think this is the right procedure? Anyone has any advice about this?
Is it possible to move the location path for the entire Datastore in the Vcenter (with all the virtual machines turnet off)?
I have no experience with iSCSI, will this procedure work for this?
Today I am trying the follwing in the testbed server:
I Initialize snapmirror to other controller.
I Shutdown my server
I Quiesce and break snapmirror
I Put the snapmirrord LUN offline and I change the serial number exactly as it was on source controller
I unmap the old LUN,
I create the same initiator groups.
I put the new LUN online
I map new LUN to the igroup
I Start server
But any partition was mounted. My logical volume is not available
--- Logical volume --- LV Name /dev/VgB/lvB VG Name VgB LV UUID YW5brO-5lHj-KQ1k-8YKa-ggv3-pidA-um9JEq LV Write Access read/write LV Status NOT available LV Size 14.00 GB Current LE 3584 Segments 1 Allocation inherit Read ahead sectors auto
For nodename of the controller is alerady used by vmware host, I think that I cannot change it.