Exchange Migration from 2007 to 2013

Eprs_Admin
Eprs_Admin used Ask the Experts™
on
Hi Experts,

Now I have an Exchange Cluster 2007 with two nodes.
I want to migrate to the latest Exchange Version 2013.
Is it possible ?

I also have a vSphere Environment and I want to convert the Exchange 2007 to a virtual machine.
But what about the cluster ?
Can I skip it , because with vSphere I have a Cluster ?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Joseph O'LoughlinSystems Administrator
Commented:
There is quite a lot of information on running MSCS (Clustered Services) on ESXi, e.g.
vsphere mscs setup checklist
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.mscs.doc%2FGUID-E794B860-E9AB-43B9-A6D0-F7DE222695A1.html

So no there is no step that can be skipped.  You need special care with the shared disks, as it's easy to corrupt them, especially with the scsi disk reservation race for the quorum.  So the SAN also needs careful configuration.  

Exchange is resource intensive and you have to tune away most of the benefits of virtualisation, so hopefully any other vm's have a very light load?

I suggest you do it in this sequence.  Physical to virtual one node.  Leave physical in production, vm off.  Out of hours down the physical and upgrade virtual to 2013.  Long checklist there, but by taking shapshots, you may get to do it more than once if there's a mistake,  In another out of hours session get MS clustering working.  When you have clustered exchange 2013 (more cluster configurations possible), in an other ooo session, migrate the current stores physical to virtual.  

A big job.
Eprs_AdminSystem Architect

Author

Commented:
On the VMWARE environment I dont need the windows cluster.
Is it not possible to create a vm with Exchange 2013 and start the migration from physical to virtual ?
Joseph O'LoughlinSystems Administrator

Commented:
You can do an across the wire migration if you like, but while the target is virtualised, the step would not be called p2v.
Ensure you’re charging the right price for your IT

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!

Eprs_AdminSystem Architect

Author

Commented:
Why ?
My cluster is a on premise installation.
The new exchange server will be a vm.
Is it not possible to start the upgrade to Exchange2013 and move all mailboxes to the new vm and all its settings ?
Zacharia KurianAdministrator- Data Center & Network
Commented:
I also have a vSphere Environment and I want to convert the Exchange 2007 to a virtual machine.

If your core intention is to migrate from Exchange 2007 to Exchange 2010, then why do you want to P2V your current exchange 2007? Do you have any specific concerns/ reasons for it (p2v)?

The most suitable option for you is to prepare your exchange 2013 (VM)  and start the migration, if you understand well about VMware cluster setup. It would be worth to go through the below link to understand the Exchange 2013 in VMware.

http://www.vmware.com/files/pdf/Exchange_2013_on_VMware_Design_and_Sizing_Guide.pdf

We have an expert in EE named "Andrew Hancock" and if you go through his articles about VMware (if you haven't read yet), it would help you in many aspects of VMware.
Marshal HubsEmail Consultant

Commented:
Migrating from Exchange 2007 to Exchange 2013 is a trouble task and takes lots of time to complete. So, if you want to save your time and efforts and want to skip the cross forest migration , then you can try any third party exchange migration tool like Stellar Mailbox Extractor for Exchange Server, CodeTwo. With these tools, you would be able to directly export exchange 2007 mailboxes to Exchange 2013 in quick time.
Eprs_AdminSystem Architect

Author

Commented:
OK, but when I export the mailboxes with the 3rd party tool, what about the Server settings ?
How to migrate all the settings ?
Joseph O'LoughlinSystems Administrator

Commented:
Piecemeal.  As we said, it's a big job.
Eprs_AdminSystem Architect

Author

Commented:
in the past I also did a migration from exchange 2003 to 2007 and this was fine.
All settings were taken over.
And I also want to do it with 2007 to 2013.

With p2v I have all the old settings on my new vm and it is not upgraded to 2013.
Joseph O'LoughlinSystems Administrator

Commented:
Was it a migration or an in-place upgrade?
Eprs_AdminSystem Architect

Author

Commented:
it was a migration.
The old server was running in a vm.
I created a new vm with exchange 2007 and then the upgrade started.
Here I also did many things but this is normal I think.
Later I connected to the new exchange 2007 vm and started to move all mailboxes to my new exch2007 vm.

And now I want to do it in the same way from exch2007 to exch2013.
Joseph O'LoughlinSystems Administrator
Commented:
You can migrate again.
That the source is a cluster is nigh irrelevant, but there are no shortcuts during the migration.  Pay attention to the sizing guide in Zach's comment.  Familiarise yourself with both it and all the prerequisites and the process at http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx,
as you don't want to get burnt half way through or end up with an new server without the headroom for growth.
Eprs_AdminSystem Architect

Author

Commented:
This is a nice post, thanks.
Marshal HubsEmail Consultant

Commented:
Firstly set up Exchange 2013 and everything required to set up. Then create some empty mailboxes in Exchange 2013 and then with the help of the software, export the mailbox items in Exchange 2007 directly to those empty mailboxes of Exchange 2013. So, all the data of Exchange 2007 will be migrated to Exchange 2013
Joseph O'LoughlinSystems Administrator

Commented:
And if doing this on a vm, on a host with ample disk space, take snapshots so if needed you can revert.
The advice from Marshal is spot on, as some mailbox structure is lost through indirect migrations.
Eprs_AdminSystem Architect

Author

Commented:
ok, but the step with creating empty mailboxes is strange for me.
I know you can move mailboxes from 2007 to 2013.
But why creating empty mailboxes ?
Joseph O'LoughlinSystems Administrator

Commented:
There's a lovely bug, where if there's a failure when moving (as distinct from copying) a mailbox, it's lost from both the source and destination.  Creating the target first you get almost everything up to the failure.
Eprs_AdminSystem Architect

Author

Commented:
ok I see thanks.
Marshal HubsEmail Consultant
Commented:
In empty mailboxes, you can directly export data from Exchange 2007 using the software.
Eprs_AdminSystem Architect

Author

Commented:
Ok I keep this in mind.
Eprs_AdminSystem Architect

Author

Commented:
I have heard exchange on a vm with NFS protocol is not supported, right ?
Eprs_AdminSystem Architect

Author

Commented:
thanks

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