Unsolved
This post is more than 5 years old
236 Posts
0
3059
How to migrate existing ESXi and Windows hosts from FC attached to iSCSI attached
Hi All,
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:
- Four existing ESXi 5.5 hosts configured in a VMware cluster. Two standalone Win2k3 hosts. Host are UCS B200.
- One VNX5200.
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.
- Configure four new hosts as part of the existing ESXi cluster. I am not going to zone them to the VNX.
- Configure the VNX, the existing hosts and the new hosts for iSCSI. I need the existing hosts to see the iSCSI LUNs so that I could move the VMs to them. I am not sure how to deal with the existing hosts. They are already logged in and registered on the VNX via FC and they are in the storage group for ESX hosts, so how do I register them via iSCSI, if I have to do that at all?
- Connect the new hosts to the VNX via iSCSI, they have to be logged in and registered.
- Put the new hosts in the existing ESXi storage group where I have the FC attached hosts. If I do that, will they see the FC attached LUNs? I assume they would, as the storage protocol - FC or iSCSI - should not matter here, as I am accessing different LUNs via different protocols, not the same LUN via two protocols (FC and iSCSI), which is not supported.
- Configure the new LUNs and put them in the existing ESXi storage group. I am not quite clear on this either: the new hosts will see the new LUNs via iSCSI, as this will be the only protocol configured for them. However, how will the existing ones see them - via FC or via iSCSI? How do I make sure that the existing hosts see the new LUNs via iSCSI only, if that is at all possible?
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:
- They are already logged in and registered on the VNX via FC and they are in the storage group for ESX hosts, so how do I register them via iSCSI, if I have to do that at all?
- How do I make sure that the existing hosts see the new LUNs via iSCSI only, if that is at all possible?
Appreciate your input.
umichklewis
1.2K Posts
0
June 28th, 2016 12:00
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!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 28th, 2016 13:00
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.
victory_is_mine
236 Posts
0
June 29th, 2016 09:00
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?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 29th, 2016 13:00
yes
victory_is_mine
236 Posts
0
June 30th, 2016 08:00
Great, thank you very much dynamox.
This would be the plan then:
victory_is_mine
236 Posts
0
August 16th, 2016 12:00
Could you please elaborate more, as far the actual steps are concerned?
storagtetalk
1 Rookie
1 Rookie
•
53 Posts
0
August 16th, 2016 15:00
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...
umichklewis
1.2K Posts
0
August 17th, 2016 07:00
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.
victory_is_mine
236 Posts
0
August 17th, 2016 09:00
Thanks, but that probably will not work, I am not looking to migrate any data from one volume to another, just changing the type of connection from host to array, the volumes stay the same.
victory_is_mine
236 Posts
0
August 17th, 2016 09:00
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?
umichklewis
1.2K Posts
0
August 17th, 2016 11:00
Understood - got hung up on the "move data from FC" in the post title.
Thanks!
Karl