Moving virtual machines from ESXi host to windows server 2008 Hyper V

Harjeet Singh
Harjeet Singh used Ask the Experts™
on
Hello Everybody

we got 2 Dell PE2950 servers [1 domain controller ,  1 exchange server]

Bought New Dell MD3000  
plan is to setup clustering and virtulization using Hyper V and MD 3000 as storage.

here is what am thinking to do

We got 2 spare old DELL PE2650 servers. below are steps i am thiking to perform

1.  Install ESXi on 2 spare servers PE2650's.
2. Convert 2 main physical servers (domain controller and Exchange) to virtual machines and host on 2 spare servers one on each. using VMware converter , Live conversion.
3. Switch off 2 main servers PE2950 and let Virtual machines serve the job for them.
4. Install windows server 2008 enterprise edition on 2 main servers PE2950 and configure with MD 3000 storage and setup Hyper V and clustering.
5. Move Virtual machines(domain controller , Exchange Server) from old spare Dell PE2650  to Newly setup servers. PE2950
6. Switch off OLD server ESXi's and PUT live new setup PE2950 with hyper and virtual machines on it.


I reserched a lot about this and everyting seems fine about all steps, only thing i want to make sure, is it easy and possible to move virtual machines from ESXi to Hyper V setup. Live transfer of virtual machines?
If yes than using which software something from VMware or Windows Virtual machine manager.
and how much time we are expecting to convert physical server to virtual machine and than move vitual machine to new setup, if current size of server is 200 GB.

any help suggestiongs about above process will be much appriciated and yea feel free to advise or change the whole process if you think this is not possible or you can advise some other way of doing this easily and effectively.

Thanks Harry

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Paul SolovyovskySenior IT Advisor
Top Expert 2008
Commented:
The process should work.  I would add another level of backup just in case.  Download eval Acronis or Symantec Backup Exec System Recovery, install on servers and image.  

With the images in hand you can always convert directly or inderectly to vmware VM or MS VMs/VHDs.

Always good to have one backup too many than the other way around
Harjeet SinghTechnical Director

Author

Commented:
yea i allready got  backup softwares and doing daily backups of all machines on external drives and network drives,  

usig both Acronis  and Symmantic Exec.

that's worst case scenario as backup in hand as well.  

am focusing on to do it all live without down time, for safety will be doing on weekend.

which software you suggest for moving virtual machines from old to new servers.  ?
Paul SolovyovskySenior IT Advisor
Top Expert 2008
Commented:
I am not too familiar with Hyper-V but from physical to VMware I would use vConverter.  If use version 4 and keep the volume sizes the same you can configure it to start the conversion process, at the end sync any changes, down the physical and bring up virtual.

Once that is completed you will need to put in the ip address of the server (since your physical nic is no longer present).  Remove Dell OpenManage software and LPT/serial ports since you no longer will use them and you're set.  

I haven't looked at what Hyper-V converter will or wont do yet but I would verify that it not only converts but will sync changes that were made during the conversion process
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

I agree for using P2V to convert Exchange Server but I disagree on using P2V for Domain Controllers.

A better option would be to install a Windows Server 2003 or 2008 VM depending on your Domain Requirements and then promote a new Domain Controller.

Allow replication process to get over and then shutdown the physical domain controller after transferring the FSMO Roles and Global Catalog to the Domain Controller (VM).

Check Event Logs for any Warnings, Alerts or Errors.

Proceed accordingly.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
I missed the DC piece.  I agree with Arun, there may be issues with the AD update number


There is an issue when P2V'ing a DC (Windows 2000 and Windows 2003). It affects the AD's Update Sequence number and can halt DFS replication.
For more information, see the following Microsoft articles:

Windows 2000: http://support.microsoft.com/kb/885875/

Windows 2003: http://support.microsoft.com/kb/875495/
Harjeet SinghTechnical Director

Author

Commented:
We have windows 2008 domain controler with domain level. 2008 as well
Harjeet SinghTechnical Director

Author

Commented:
here are bit more details.

Domain controller - DELL PE2950 windows server 2008 standard edition 32bit with domain functional level 2008 , following rolder,  DNS , DHCP, File services.

Exchange server - DELL PE 2950  windows server 2008 standard edition 64 bit, exchange server 2007 standard edition,   nothing else on it.

the problem you guys saying is that only with domain level 2003 or we are expectin with 2008 as well. please advise.

Paul SolovyovskySenior IT Advisor
Top Expert 2008
Commented:
P2V of domain controller can be done but there may be more cleanup in there especially if you're P2Ving  them twice.  It's best to create a new VM and DCPROMO to a domain controller as well migrate the dhcp scope,etc...
I guess you are using Active Directory Integrated DNS. This being the case if you promote another VM as a Domain Contoller, DNS Zone Data would be replicated to the newly promoted DCs.

Migrating DHCP - http://www.petri.co.il/dhcp-server-migration-made-easy-windows-server-2008.htm
Commented:
I disagree, you need to P2V the domain controller offline. You will run into problems if you do a online p2v conversion. Offline conversion of the DC is what you need. Same thing goes for anything else database related. exchange, SQL, DHCP. etc.

you have a good plan in place, when you go to migration from vMware to Hyper-v use VMM 2008. You can download for free and try it out for a bit. It has the built in tools you need to migrate from vmware to hyper-v

http://www.microsoft.com/systemcenter/virtualmachinemanager/en/us/default.aspx

Commented:
200 GB is quite big, you can expect around 3-5 hours or so depending on your network setup.
Harjeet SinghTechnical Director

Author

Commented:
thanks guys for your tips and hints, am done with this and whole process been ok. I used MSVMM2008 to do all kind of conversations.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial