Exchange 2010 Std. Physical to Virtual Migration SAN to SAN

I have to perform a physical to virtual migration of Exchange 2010 with over 2TB of data.  To P2V with converter is not an option because of the downtime it will incur.  What is the best method to move Exchange over without using that method.  Create DAG and let it replicate between the physical and virtual, stand up a new exchange server in vSphere 5.5 or ?
Who is Participating?
Stand up a new (or two new) Exchange Servers in your new virtual environment, configure as required (DAGs, client access redundancy, etc.) then move the mailboxes from the old environment to the new.

Zero downtime of the system, and only a few seconds for each mailbox when the move request completes and Exchange must complete its final synchronization of mailbox data and update Active Directory mailbox placement metadata. You also get fresh databases, so avoid dragging any issues with the old databases over to the new environment.

Points to watch out for: you will generate a lot of transaction logs on the new environment when moving this data; make sure you have a mitigation strategy in place, either a sufficient amount of space, regular incremental backups to truncate them, or *shudder* circular logging temporarily enabled.

If you plan to deploy a DAG on top of a virtual environment, make sure you configure the VMs with host affinity options so they are (by default) placed on separate virtual host machines. Last thing you want is your cluster falling over because all the VMs roamed to a single host, which later failed.
...Install 2 Exchange on VM & include that Exchange VM box into DAG replication. Once replication will get complete mount the databases into vm Exchange box....And then remove the Physical boxes from DAG replication ...And do the decommission part.

Note if that physical box containing PF, then make sure PF replication has been migrate to vm exchange boxes.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You've not considered the "SYNC" Option! We've done larger migrations of over 5TB, with downtime reduced to 30 minutes out of hours!

It then does not make any difference how long the initial sync or copy, replication takes. and then when the full sync has occured, complete another Sync, 1 hour before Cutover, and then out of hours do the Swap!


HOW TO:  Synchronize changes when completing a P2V or V2V with VMware vCenter Converter Standalone 5.1

and if you wanted limited downtime, down to seconds and minutes...we use Double Take MOVE!
or use Double Take Move

HOW TO: Migrate physical, virtual and cloud based workloads with real-time replication to VMware vSphere (ESXi) using Double-Take MOVE
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.