I am looking for the best ways to achieve the following - migrate existing ESXi and Windows 2003 hosts from FC attached to iSCSI attached, migrate data from the FC connected VNX LUNs to iSCSI connected VNX LUNs.
Here is what I am currently working with:
These four ESXi hosts are connected to the VNX via FC.
We are introducing four more B200 hosts, and want to connect them to the same VNX via iSCSI, and migrate the existing FC LUNs to the new iSCSI LUNs.
What I thought I can do for the ESXi is this.
On the windows side I am planning on following the same strategy, except I am not adding any new hosts, just moving the existing ones from FC to iSCSI, and I have to install iSCSI initiator. However, the questions remain the same:
Appreciate your input.
Why not use PowerPath Migration Enabler for the Win2k3 move? I always prefer PPME, because it's just so darn flexible!
Let us know if that helps!
LUN is a LUN, does not matter how you get to it. I don't see the need to create brand new LUNs, connect new hosts via iSCSI, add them to the same storage group as current hosts. Put currents hosts into maintenance mode, unmount datastores, re-connects hosts using iSCSI , add to the same storage group and rescan.
So the same LUN - LUN 100 for example - can be accessed via FC from the existing production host A, and via iSCSI from the new host B on the same array and in the same ESX storage group, can't it?
Great, thank you very much dynamox.
This would be the plan then:
Could you please elaborate more, as far the actual steps are concerned?
The concept is the same for the Windows standalone hosts. I would unmount the volumes on the host, then remove the host from the storage group on the VNX. Then configure iSCSI on the host.
I would prefer to do a reboot on the host at this point to clean things up. Then create a new host on the array with the new iSCSI initiators, then add that host to the storage group. At that point you can mount the volumes, and all IO will be going across iSCSI.
I don't think PPME is a good option here, you are just changing the IO path to the array, not actually migrating data...
Sure. You can find the PowerPath Migration Enabler documentation on EMC Support. It clearly breaks down the steps involving in performing a PP Migration.
In simplest terms, you provision new LUNs to your Win2K3 servers, but you do not put a Windows signature on them or format them. Next, you create a migration handle in the CLI with Powerpath, indicating what source LUN(s) to copy from and what target LUN(s) to copy to. Then, you enable migration handle, starting the copy process (throttling the copy, if necessary). Once the data is in sync, you select the target LUN(s) in the migration, meaning, you service your I/Os from the new target LUN(s). If you're satisfied with the performance, you can commit the migration and unzone the original source LUN(s).
This works only for your Windows hosts, of course, and is not available for the ESX migration. Also, this would be recommended in a case where you were creating new iSCSI LUNs.
That sounds more like what I need. However, since I have not done this type of migration I have some concerns as to how to do certain steps and not to end up with a server not being able to access the volumes once it is migrated to iSCSI. I need to introduce some details here to make it a bit clearer for myself. I have to migrate two LUNs to iSCSI, which are currently presented to a win2k3 server via FC. The application that is using these LUNs is MS SQL 2005. Below are the steps I intend to follow.
Does this make any sense?