Build exchange 2003 from exchange 2000 backup

[vttech]

I currently have an exchange 2000 server on my network named 'mail'. I want to build and exchange server also named 'mail' with the same IP address this way I don't have to worry about the mx record with the ISP or reconfiguring our firewall. the question I have is how can I backup the exchange mailboxes and public folders? this will allow me to disconnect the exchange 2000 server from the network and then build the new exchange 2003 server and then restore the mailboxes and public folders with the back. Can this be done? if so is their some simple docs or site to help me?




Newbie in search of knowledge

 

[58sniper]

You're doing an upgrade to a new version. That's not as easy.

Install Exchange on a new server, with a new name. Follow kb 822931 to migrate. When you're done, upgrade the firewall to point to the new IP. MX record doesn't matter (it points to your firewall), and neither does server name (if you leave the old server up, clients will auto configure to use the new server).

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[adamc1115]

Solution 1:

Use exmerge to export and import all mailboxes.

http://support.microsoft.com/kb/174197

Solution 2:

Create new server names "mail2", with different IP. Migrate mailboxes and everything else. Then rename the server and change the IP once the old one is offline.

http://support.microsoft.com/kb/822931

http://support.microsoft.com/kb/152959

http://support.microsoft.com/kb/275171/

 

[vttech]

kb 822931 is talking about removing the first Exchange Server 2003 computer. OK so I already built the exchange 2003 server with a new name. I assume that the article you are talking about will instruct me how to migrate the mailbox and public folders. then I just configure the firewall to point all smtp port 25 traffic to the new exchange 2003 server. how about OWA since the old server is named mail1 and the new server is named mail2. how will the people access OWA via the web without MX record update.. what about the local LAN DNS would I have to add an MX record there. How will the leaving the old server up reconfigure my end users outlook settings that is pointing to mail1? and how long do I have to leave it up for?

thanks

Newbie in search of knowledge

 

[58sniper]

Your MX record points to your firewall's public IP address, not the actual server. You change the port forwarding in the firewall to forward ports 443 and 25 to the new server (from the old server).

822931 needs to be followed to the T. Follow, but leave Exchange on the old server for a week or so (or long enough for the clients to connect once). That will automatically update Outlook to use the new server.

Zero downtime (if you do it right).

Don't exmerge. You lose single instance storage, and users lose access to some email (downtime).

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[vttech]

OK so 822931 applies to exchange server 2000 in my case even though the article states 'how to remove the first Exchange Server 2003 computer'

I understand that I would not have to update my external mx records that my ISP handles because it point to the firewall.
But how about the CNAME record that would allow my users to type mail2.mydomain.com to access OWA.

One more thing how do I migrate the mailboxes from 2000 to 2003. I tried to right click a mailbox and select all task to move the mailbox. But I had no option in exchange 2000

Newbie in search of knowledge

 

[58sniper]

Move them from the 2003 side.

You're using a CNAME? Externally, nothing changes.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[adamc1115]

If I recall correctly, yes, the exchange 2003 article applies to 2000. (It says it does at the bottom of the article as well.)

You can just change the IP to the old servers IP (as you indicate you wanted to do in the first post) if changing your firewall is not an option... There is nothing that is going to hurt exchange by renaming the server or changing it's IP...