Virtualisation project sanity check
Hi All
I am just after a sanity check on a project I am working on
Current setup
Hyper-V Cluster 2008 R2, 3 new hosts (HP), two old hosts and iSCSI MSA SAN near capacity.
The new hosts are about a year old but the SAN is old and had failed once.
Proposed setup
Replace with VMware 5.5 (not a Hyper-V fan) and SAS based P2000 HP SAN
There are two older hosts left in the existing Hyper cluster I can utilise as temporary space while one of the new hosts is taken offline to install the SAS HBA, SD and VMware. All of the networking will be replicated and setup
The new SAN is set up and in place, so once the initial hosts are set up in VMware I plan to use VMware converter to V2V the Hyper-V VM's to the VMware cluster. I am going to need a variety of converter versions as there is a mix of 2003 - 2012 OS
Anyone see any issues with the migration from Hyper-V to VMware in this way?
Perhaps some disk alignment post move?
I am just after a sanity check on a project I am working on
Current setup
Hyper-V Cluster 2008 R2, 3 new hosts (HP), two old hosts and iSCSI MSA SAN near capacity.
The new hosts are about a year old but the SAN is old and had failed once.
Proposed setup
Replace with VMware 5.5 (not a Hyper-V fan) and SAS based P2000 HP SAN
There are two older hosts left in the existing Hyper cluster I can utilise as temporary space while one of the new hosts is taken offline to install the SAS HBA, SD and VMware. All of the networking will be replicated and setup
The new SAN is set up and in place, so once the initial hosts are set up in VMware I plan to use VMware converter to V2V the Hyper-V VM's to the VMware cluster. I am going to need a variety of converter versions as there is a mix of 2003 - 2012 OS
Anyone see any issues with the migration from Hyper-V to VMware in this way?
Perhaps some disk alignment post move?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looking to be rid of the Windows Server 2003 servers within the next six months if all goes according to plan
Thanks for the additional tips, exactly what I was after