Migration will be from 2007 to 2010/2013 then from 2010/2013 to 2016
Why do we need to migrate from 2007 to 2010/2013 then from 2010/2013 to 2016?
As per Microsoft limitations, we cannot migrate to any version of Exchange without passing the next version
Process plan & schedule day's to Migrate Exchange Server 2007 to Exchange 2016:
Decommissioning Exchange Server 2007 Process :
The steps to decommission Exchange Server 2007 are listed below:
1. Backup Exchange Server along with its User Mailbox database(s) and Public Folder database(s)
2. Migrate user mailboxes with their complete properties and settings to another Exchange Server
3. Migrate Public Folders to another Exchange Server
4. Disable Local Continuous Replication of User Mailbox Database and Public Folder Database
5. Remove User Mailboxes
6. Stop the usage of Exchange Server 2007
7. Remove the Public Folder Database
7a. Force removal of Public Folder Database
8. Remove the User Mailbox Database
9. Remove the Storage Groups
10. Remove or move the Offline Address Book (OAB)
11. Move Routing Group Connector to another Exchange Server
12. Remove Exchange Administrative Group, if no other Exchange Server is installed in the domain.
13. Uninstall Exchange Server 2007
Hardware & Software Requirements:
- 2 Servers for Migration steps.
- 2 Server’s if we need to establish 2 parallel Exchange server’s one as a backup server.
- 2 SAN/NAS Storage Virtual Disks if we going to use DAG as High Available Database with the same drive letter.
- Windows Server 2012 R2 /2016 License.
- Windows Server UsrCALs
- Exchange Server 2016 License.
- Exchange Server UsrCALs
-- Mailbox Exchange Repair & Recovery Software, in case we got corrupted data.
- Offline Copy of the mailbox database:
-Exchange database (.edb)
- Transaction log (.log file).
-Checkpoint file (.chk).
-Reserve log files (.jrs).
-Temporary file (tmp.edb).
How to Calculate Space for new Exchange Server :
Space depends on Number of Org Users, Here we have 200 users, with 4GB Quota
(200 * 4GB ) +(200*15MB)= (800GB +3000MB ) (no of mailbox’s * Quota ) + ( no of mailbox’s * whitespace) Active
(200 * 4GB ) +(200*15MB)= (800GB +3000MB ) For use ( Database Availability Groups ) DAG’s for High Available Passive
Whitespace isn't freed up until after the retention period is passed for the mailboxes you have moved, also not all the space of a mailbox will be freed up so trying to stop stores expanding by moving mailboxes out of them doesn't really work, you would be better off moving the mailboxes to a fresh store and removing the old store, this will give you the added advantage of defragging the store as well and should result in smaller databases
Edited by: Andrew Leniart
Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.