Upgrading the Exchange Server hardware 2

[RadioActiveLamb]

I have an immediate need to upgrade the hardware from under the Exchange server. Currently, running Exchange 5.5 on NT 4 with antique hardware on an NT 4 domain. I'm hoping that some of you folks can help me bypass any roadblocks.

In the end, I need the new box to have the same name as the old box.

I would also like the new box to be running Windows 2000 Server (This is a luxury, not a requirement).

I need to minimize the down-time (of course).

There are about 100 mailboxes that need to move with it.

There is a RightFAX connector that will also need to move.



Here's my plan, so-far:

1. Build a bdc on the LAN, then remove it.
2. Put the new BDC on it's own LAN and promote it.
3. Install the new Exchange box on the new 2nd domain.
4. Install Exchange 5.5, patch it to the latest.
(here's where it gets fuzzy)
5. Backup old exchange box onto tape.
6. Shut-down old box and remove it from the LAN.
7. Install new box on the LAN, restore the tape.

8. Presto?? Am I done?

If any of you have done something similar, please let me know. Am I going about this all-wrong? Is there a way to back-up the old server by shutting-down the exchange services, then copy them over the freshly installed files on the new server (with those services off, of-course)?

Thanks to anyone!
Jeff Lamb

 

[Maruis]

Hi

There are a few ways you can do this.
The one you are planning is good. With one difference, you can build a replica box complete offline" meaning not part of your domain or on your network" Drop the old box off the network bring the new one in and restore your tape back up.
If all fails you can switch back in no time.

Have fun


Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[RadioActiveLamb]

Thanks for the tip. This makes sense. In order to do it this way, it seems that I'd have to wait to install Exchange until after I join the new box to the domain. The current box was installed using the domain admin account as the service account (ack!).

Is there an easy (file copy) way to backup the old exchange box? Backing-up with Veritas sometimes takes 8 hours, if I back-up individual mailboxes.
Jeff Lamb

 

[ilpadrino]

Didn't you say you were using an NT 4 domain? If you make the new machine a domain controller, and install windows2k server you're introducing a whole realm of problems -- you're upgrading your domain to win2k.

you can't put win2k on a dc and also maintain an nt4 pdc. but you could just make the new exchange server a member server with win2k. if this is possible, it might be better anyway. let other machines act as dc's. hope this helps.

joe

 

[RadioActiveLamb]

No, I realize that this shouldn't be a DC, and I never said anything about making it one. I think you misunderstood when I mentioned joining the server to the domain. This is a stand-alone Exchange box in an NT4 domain. The current box is running NT4, but I'd rather have it run Win2K as a member server, if it will get along with Exchange 5.5.

After I install Exchange on the new member server, can I file-copy the message store and configuration from the old box instead of using a tape backup? Are there registry entries that need to be copied-over too?
Jeff Lamb

 

[Maruis]

Regading the problem you have with the log on ID:

Here you can do it as you said or you can create a new ID on the offline box. When you bring it online just add the old ID to give you the same rights for the back-up.
I would prefer doing it this way. Then you have a seperate ID for your exchange box and it is not part of your overall Domain admin. Call it a backdoor if you want. The last thing you need someone fiddeling with your mail server.

As to the back-up you do not need to go to brick level. Standard exchange back-up of the database's and logs will do just fine. Call it a test run if you like. Remember you want to do the transition with the least amount of impact.

So start on a Friday evening and then you have the whole weekend to work on it. If all else fails you can go back to your old server in now time. Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[RadioActiveLamb]

This does help. Thank you. I have a question about a 'standard Exchange backup'. To me, the standard backup is using Veritas on a backup server. it backs-up the Exchange server and individual mailboxes. The problem with this is that it takes about 8-10 hours to complete. Since the entire message store is several gigs, I was hoping to bypass the Veritas method and just copy the files. This would reduce the backup time to minutes. What method do you use to backup/restore Exchange?
Jeff Lamb

 

[ladyj]

If you can take the server down, maybe over the weekend, you could add a drive on the old server, turn off exchange services and copy pretty fast. Then move the drive to the new machine. You can probably use an ide drive. I don't see where you need the machine to be a bdc... follow the kb article on moving exchange to new box. Its not all that simple. Be sure and run optimizer on old box and document what is on what partition. After its all working upgrade to w2k.

 

[Zelandakh]

This worked for me last week:

1. Upgrade PDC to Windows 2000 – this will run DCPromo
2. Make note of Site and Organisation name
3. Make note of directory locations (perfwiz)
4. Make note of IMS and Distribution lists
5. Export exchange directory to .csv file for reference.
6. Copy Exchsrvr directories onto new W2K Server
7. Take existing exchange offline
8. Remove account for existing exchange from domain.
9. Rename new W2k Server to that of existing mail server
10. Change IP Address to that of old mail server
11. Run DCPromo (this will get accounts)
12. Install Exchange 5.5 on W2K with correct site and organisation name + install necessary ServicePacks and hostfixes
13. Copy over old exchange data to same locations as before
14. Start System Attendant and Directory Service
15. Run Isinteg –patch
16. Run remaining services
17. Add IMS
18. Install Active Directory Connector.
19. Probably need to change the port that Exchange LDAP uses (390 or 391 see Q293376)
20. Upgrade to Exch2K
21. Install SP3
22. Check Distribution lists
23. Check random mailboxes
24. Install Antivirus software and backup agents.
Check internet mail flow.

Hope it helps.

 

[RadioActiveLamb]

Zelandakh (If that is, indeed, your real name),

Thank you. This is very helpful. I won't be upgrading the network to an AD, or upgrading the Exchange box to Exch2K, but the rest is very helpful. Just for clarity, is IMS the Internet Mail Service? Doesn't that get installed at step 12? If so, why add it again at step 17?

Thanks again!
Jeff Lamb

 

[hannahsh]

Hi there Jeff

First get all users to clean their mailbox's out and get shut of as much waste as possible - small is beautiful

Also I assume user accounts are upto date and only current employees are listed ? if not good time to have that yearly check - audit and cleanup - that we all hate

Backup - the IDE hard drive sounds good to me if you dont have a fast DLT drive or invest in a DVDRAM - good excuse to buy one for this and there cheap now.

Veritas is bullet proof - I know and wouldn't use anything else, after 8.2 its my 3rd arm and DR is simply perfect.

How have you configured the disks I have this setup
mirror apps (x 2 hot spare)Internal
raid 5 messages (X5 hot spare)san
mirror logs (x2 hot spare)san

I ran servers for years and never once lost them, only 3200 controller and I lost 2 in 3 years - horrible things they are.

try and make sure logs have been completed and even turn them off before you backup and this will reduce any problems significantly. Check the numbers and see if there is only empty logs - then there is no catch up to be done. I think it should only take an hour or so with 100 box's and stop the downlink ofcourse so no new ones build up !!
Have you a cache raid controller - dont use them there crap for exchange and can lead to huge problems - I turn caching off as the logs can take care of any message surges.

Everyone should add a footer to outgoing e-mails for a few days/week that e-mail will be down for x hours !! your backside is then covered !!

Comments welcome, I guess some might disagree or not but in my experience these pointers are vital for a good DR test and I have done many under SLA contracts, all 100% successfull over the years. I have not covered anything already suggested above all looks pretty sound there !!

But 100 users and server gig - not good admin control get them to remove to personal folders, minimum amount of server retention is a must expecially if you were to lose the box

 

[Zelandakh]

Jeff,

Line 12 is Exchange 5.5 with the right site NAME. Line 17 is installing the internet mail service.

Other than that, it does appear to work on our test rigs and bearing in mind we've tried it over a dozen times to get it right, we've pared that list down to something that works irrespective of the hardware!!!

And No, this is not my real name but I like to keep my Tek-Tips presence and my work/job/real life separate. If my boss found out how many posts I've made to this site... they wouldn't think about the money they've saved in consultancy bills over the years.........