Backup procedure and migration to new server

[apostasy1]

Some background information: We're running Exchange 5.5 Server on a Windows NT 4.0 box. While it serves its purpose, it's approaching 10 years of age and needs replacement. Our environment is comprised of only 20 users or so. We use internal E-Mail, a public Calendar, and a public Contacts list.

My questions are as follows:

I plan on setting up a new Exchange 5.5 Server on a Windows 2000 Server box. I wish to migrate all E-Mail accounts, E-Mails, and public folders to the new server. Is this as simple as copying the private and public .edb files to the new server? (I'm assuming not.)

Once the new server is set up, how do I go about backing up the Exchange data on a daily basis? Should I use ntbackup or is there some other utility?

Thank you for your assistance,

--

 

[zbnet]

You haven't mentioned NT domains etc - if Active Directory is involved, you are looking more at a migration scenario than a hardware-style DR situation (which is loading one server's config and data onto a new server).

faq10-6004 has some info about this, and good advice about backing up 5.5.

Have you considered doing the job properly and moving to an Exchange 2003 server?

 

[apostasy1]

Active Directory is not involved.

My knowledge of Exchange Server, domains, DNS, Active Directory, etc. is very limited. I'd prefer to not go the route of Exchange 2003.

 

[zbnet]

You can do what you want, there are a few ways to approach it. If you have limited experience of Exchange, you might want to get some experienced help for this migration - or get some spare hardware, set up a lab, and play with some test migrations using your production backups until you're happy you can do what you need to do.

Exchange 5.5 runs happily on Windows 2000 as its operating system, if there is no AD involved it doesn't look any different from an NT point of view - but you still need your NT4 domain to work properly. Both Exchange 5.5 and NT4 are fast becoming dinosaurs, you willl have to bite the bullet and upgrade at some point in the future, support and knowledge about them will become less easy and more expensive to get in the future.

The section "Full Server Restore" from the document mentioned in the FAQ I already pointed you to is a good place to start.

 

[netometer]

Hi!
There are two approaches in moving Exchange 5.5 to new hardware:

1. Adding the new W2k server to the domain as a second Exchange 5.5 server, moving the resources to it and decommissioning the old Exchange 5.5 server:

http://www.netometer.net/video/index.html?tutorials/move55/index.html

2. Replacing the old Exchange 5.5 by using Offline/Online backup:

http://www.netometer.net/video/index.html?tutorials/replace55/index.html

Both are transparent to the end user – you do not have to reconfigure the clients.
I would recommend you the first approach.

NetoMeter

http://www.netometer.net

 

[apostasy1]

zbnet & netometer,

Thank you both for the links. The migration procedure appears to be pretty simple and straightforward - at least, for what I plan on doing. I've already successfully set up a lab at home.

Although Exchange 5.5 is approaching the status of "outdated", I'll just keep it for the time being. As crummy as this sounds, I suspect that I'll no longer be an employee at this company by the time a more recent version is needed.

Thanks again.

--