Link to home
Start Free TrialLog in
Avatar of Raneesh A
Raneesh A

asked on

Move Hyper-V VMs to VMWare

Hi Team,
   can you please guide me on the below scenario on how to porceed the best way.

There is 6 Exchange Servers Running on Version 2013 ( 2 x Edge Server, 2 x CAS Server, 2 x MB Server (5 DB in DAG)).
The Exchnage Servers are running on a Windows Failover Cluster and all are Hyper-V VMs.

We have a new HyperConverged Infra where the HyperVisor is VMware.
I want to move all VMs to VMware and i am planning to use VMWare Vcenter Convertor.


Can you please share your expert views on how to proceed the best way or is there any other ways.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Install VMware Converter, and start the conversions....

You may be better off with a better tool such as Double Take MOVE or build new VMs on the new hypervisors.
I mean you could implement an upgrade of exchange at the same time to be fair.

Rather than migrate the servers, build a new 2019 environment and migrate the mailboxes instead. It'll be longer but at the same time a nice new exchange environment.
Hi,

Your are on the good way. The only thing I can add is: Make sure that your VMware virtual network can reach the domain controller if this one is not part of your VMware infrastructure.

Some advises:
You'll have to turn off all EXC environment before convert them
Don't turn on EXC environment (Hyper-V) in the same time with VMware env. if they are in the same net or not
Turn on EXC env.  (HyperV) just in case of VMware failure

Good luck.
I'm with Alex, build some new servers and migrate Exchange. You can V2V them as Andrew suggests but given the complexity of the solution, I'd shy away from VMware converter (it will do the job, but to do it safely you'd be putting DAG members into maint mode and suspending services etc.)

Plus 2013 to 2019 Exchange migration is easy as peas!

Regards

</p>
Avatar of Sean Bravener
Sean Bravener

as others have mentioned 2019 is the way to go ultimately but if that is not an option, I would suggest building a test VM on the vmware network that you are going to end up on.  make sure that vm can no only reach the AD Server, but also the other mail servers on the old hyper-v environment.  also check that it can reach the outside for mail flow etc.

migrate each server one at a time then thoroughly test, rinse repeat..  

finally when you get to the mailbox servers (I would personally do them last), fail over the mailboxes to one node, migrate the lighter node, then fail mailboxes over to the new location and repeat with the second node.  then rebalance.
Avatar of Raneesh A

ASKER

Thanks Team. Really Apprciated your suggestions.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.