ARob720
asked on
Exchange 2007 Transition (and offsite move)
I am building out a series of 64bit, 2003 R2 servers (AD, NAS, Exchange 2007, Web) with the intent of moving them offsite to rented rack space at Verizon's colo facility. I already have a router, switch and separate domain in this location. The idea is to gain continuity by moving our services and nationwide VPN termination offsite to a more secure, reliable power and AC environment. The AD and NAS servers are already built and running on my local domain/subnet, but are not yet moved. I am building these services in an IBM BladeCenter S. The move will require IP changes and some routing configuration local and remote.
My question is, should I wait until after I have already moved AD, and VPN termination to the new facility, before I build the Exchange 2007 server? Then build 2007 in the environment in which it is going to reside, IP, Subnet, etc. Or can I build Exchange 2007 locally, Transition from 2003, move Mailboxes, and decommission Exchange 2003 then 'Forklift" the entire BladeCenter S. AD NAS, Exchange et al.
I do not have a test environment and with email being the company's life's blood, I only have one shot at this.
Thank you.
My question is, should I wait until after I have already moved AD, and VPN termination to the new facility, before I build the Exchange 2007 server? Then build 2007 in the environment in which it is going to reside, IP, Subnet, etc. Or can I build Exchange 2007 locally, Transition from 2003, move Mailboxes, and decommission Exchange 2003 then 'Forklift" the entire BladeCenter S. AD NAS, Exchange et al.
I do not have a test environment and with email being the company's life's blood, I only have one shot at this.
Thank you.
ASKER
Speed - The colo is considered to be on the backbone of the Internet and I have multiple Ts coming into my HQ. If data transfer is slow after the move then we will invest in a Point-to-Point T.
My plan is to move the 2003 AD to the colo and promote that to be the GC for the domain. I will keep local ADs at few of my sites as well as one at our HQ. I may use DFS for the data (NAS) depending on overall speed.
From your response are you recommending making my decision in this order:
A) Build in Colo (As long as inter-site speed is good) - 1. Move AD to colo. 2. Build Exchange 07 in place, and move mailboxes in groups, gauging speed. 3. Decommission local Exchange 03.
B) Forklift (If speed is slow) - 1. Build locally at HQ with local Subnet/IP. 2. Move Mailboxes etc. to 07 server, 3. Forklift AD & Exchange together to colo 4. Change IPs, routing, MX, etc.
Typing it out I am leaning towards A as, in that scenario, I will always have Exchange 03 to go back to if something were to go wrong in the move. I can build at the colo and move a few test mailboxes then do the rest in manageable groups. I do regular full backups of my infostores.
My plan is to move the 2003 AD to the colo and promote that to be the GC for the domain. I will keep local ADs at few of my sites as well as one at our HQ. I may use DFS for the data (NAS) depending on overall speed.
From your response are you recommending making my decision in this order:
A) Build in Colo (As long as inter-site speed is good) - 1. Move AD to colo. 2. Build Exchange 07 in place, and move mailboxes in groups, gauging speed. 3. Decommission local Exchange 03.
B) Forklift (If speed is slow) - 1. Build locally at HQ with local Subnet/IP. 2. Move Mailboxes etc. to 07 server, 3. Forklift AD & Exchange together to colo 4. Change IPs, routing, MX, etc.
Typing it out I am leaning towards A as, in that scenario, I will always have Exchange 03 to go back to if something were to go wrong in the move. I can build at the colo and move a few test mailboxes then do the rest in manageable groups. I do regular full backups of my infostores.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you. The Exchange 07 server will reside in an IBM BladeCenter Chassis which also contains AD so with the current hardware I cannot test AD or routing without bringing Exchange along for the ride. Although through your comments I have decided to get a second chassis for HQ (local LAN), therefore giving the capability to build and test locally, then move out to the data center with confidence.
Install Exchange 2007 on local site - move the mailboxes and public folders etc.
Fork Lift the server - work with the routing configuration once your server is placed on the new site.
Yes, you need to remember that you are working with live database - this means before you work with moving the boxes - for heaven sake please take Exchange backup - also the downtime is also involved in this case - but idea looks fool-proof provided your transportation is also fool-proof ;)