Moving Exchange 2003 to new hardware With the Same name

I am looking to move an Exchange 2003 enterprise server to new hardware that will run the same version of exchange and the same name and IP address. I think I know what to do but do not want to get burned. Also should I make this server a domain controller or a member server?


Thanks for all your help I am sure this is not the first time you have me asked this.


Thanks

SM
smarcazoAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Joseph HornseyConnect With a Mentor President and JanitorCommented:
You're welcome.

I think what you're describing is an "offline recovery" of the Exchange database.  In this scenario, you basically grab the .stm and .edb files from a failed Exchange server and then bring them up on a different server that has the same name as the original.

The advantage to doing an offline recovery is that it tends to be much faster than doing it the way I originally described.  The downside is that it is very dirty and very dangerous - it is only used during disaster recovery scenarios.  I HIGHLY recommend you do it the slower way.  It's much cleaner and works just as well.  Plus, you have very little chance of losing data.

Another reason why you want to do it the way I described is because that method will expose corruption and other problems with your database.  These problems get corrected during the transfer because the data is rewritten on the other side.

<-=+=->
0
 
Joseph HornseyPresident and JanitorCommented:
I just did this for a customer on Thursday.  Here's what you do:

1. Get a spare machine that is powerful enough to run Exchange.  Install Windows Server, Exchange Server, etc.  Make sure your versions match all of the version on the existing Exchange server.  Now's not the time to upgrade anything.  The machine doesn't have to be great.  Just good enough.

2. Backup all of your Exchange databases using a backup utility.

3. If you're really paranoid (and I am when it comes to Exchange), then stop all of the Exchange services and copy the database files to some network location.  Restart the services.

4. Using Active Directory Users & Computers, move all of the mailboxes to the temp server.

5. Using System Manager, move all of the public folders to the temp server.

6. Using System Manager, move Offline Address Books to temp server.

7. Using System Manager, move Recipient Update Services to temp server.

8.  Uninstall Exchange from original server.  Reboot.

9.  Remove original server from domain.  Reboot.

10.  Rename original server and change its IP address.  Reboot.

11.  Rename new server to match original and change its IP address to match original.  Rebot.

12.  Join new server to domain.  Reboot.

13.  Install Exchange.

14.  Go through steps 4-7 to get all the data to the new server from the temp.

15.  Go through steps 8-10 on temp server.


That's pretty much it.

<-=+=->
0
 
smarcazoAuthor Commented:
Thank you very Much.

Is steps 4-7 like copying the Exchange Information Store files? If i have a copy of those files then do 8-10 would that be the same thing?
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
isaman07Commented:
Use acronis server imagimg software, much faster, reliable and hassle free.
0
 
smarcazoAuthor Commented:
Thank ypou very Much for your Help.  I am going to do it your way. Plus they are paying me by the hour so it all works out !!
0
 
Joseph HornseyPresident and JanitorCommented:
Yeah... that's a good thing.  I started doing this with one customer Thursday afternoon at 5PM.  I left there Friday morning at 10:30AM.  And we're still not finished.  (They have a really, really big Information Store.)

Good luck!

<-=+=->
0
 
isaman07Commented:
Why do you want to keep the same name? I do not like the procedures describe in SplinterCells comments. Just join your new machine the domain, install exchange on it, move everything to the new server then remove the ifrst one, during all the process, you will have no downtime.
0
 
Joseph HornseyPresident and JanitorCommented:
Isaman,

There could be many reasons why.  In the case of the customer I was just working with, they had tons of rules in ISA Server as well as Blackberry Enterprise Server, a bunch of mapped drives, some custom-developed software and some other things that all depended on connecting to Exchange using the name.

I agree with you that if the server name is not an issue, the procedure that I described is rather lengthy and what you describe is the way to go.  However, if he wants to keep the name, this is the way to do it.

<-=+=->
0
 
isaman07Commented:
SplinterCell;
I apologize for my comments, but i ment no harm to you, anyways thanx for your civilized answer, not everyone has the same patience.
0
 
smarcazoAuthor Commented:

SplinterCell5894:
                            I am going though our steps now and step 4 got me lost? were in ADUC do you move mail box's? I thought you did this in System  manger. Thanks for your help again

SM
0
 
Joseph HornseyPresident and JanitorCommented:
SM,

Select one or more accounts, right-click and go to "Exchange Tasks....".  The option to move the mailbox should be there.

<-=+=->
0
 
smarcazoAuthor Commented:
Thanks for you help Again!!!
0
 
Joseph HornseyPresident and JanitorCommented:
You're very welcome!

<-=+=->
0
All Courses

From novice to tech pro — start learning today.