Re: 2000 database restore on 2003

From: Matthew Byrd [MSFT] (matbyrd_at_online.microsoft.com)
Date: 03/18/04 

Date: Thu, 18 Mar 2004 11:00:11 -0500

Mr Binary,

It sounds like you are looking to upgrade your software and do a completely
clean build of the box at the same time. In basic theory this might work.
I would not try it in production with out testing it in a lab first. Also I
would make sure you use offline backups and not online backups (they are a
bit more stable in situations like this).

But to be frank I do not think this scenario will work because when you go
to install Exchange 2003 you will get an error about the server already
existing in AD. At that point you would have to remove the server from AD
... then disconnect and reconnect the users none of which is that hard but
is time consuming and can cause mail loss when email NDRs since the user is
disconnected in AD.

If you goal is to get to E2k3 from E2k and have a clean build of the box
from the OS up then I would recommend the following.

1. In place upgrade the E2k to E2k3.
2. Stop the information store and use eseutil /mh to make sure all edb and
stm files are in a "Clean Shutdown" state
3. Backup the edb and stm files to a safe location
4. Flatten the box
5. Rebuild the box with the same name and join it to the domain
6. Install E2k3 with the /disasterrecovery switch
7. Restore the databases from the safe location making sure to purge and log
files
8. Mount the databases

This should result in a nice new shiny E2k3 server with a minimal of effort
and with minimal risk. This scenario would not work if you are going from
E2k Enterprise to E2k3 Standard. Otherwise it should work fine.

Hope this Helps, 

-- 
Matthew Byrd
Microsoft PSS
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mr binary" <anonymous@discussions.microsoft.com> wrote in message
news:A107321B-9E21-4388-BEAD-C98DE6C8D8E2@microsoft.com...
> Can I perform an restore from an exchange 2000 database backup
(information store or edb file only)  to an exchange 2003 server? Can
anybody tell me if this is possible. I have an exchange2000 server and I
want a fresh exchange and windows 2003 installation on the same hardware.
>
> Arno
>

Relevant Pages

  • RE: Outlook(R) Mobile Access probelms
    ... sorry ut we are about to start ANOTHER clean install. ... Did you use the backup files to restore your SBS Server? ... > Microsoft CSS Online Newsgroup Support ... > check http://support.microsoft.com for regional support phone numbers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2000 and 2003
    ... Verify that both E2K and E2K3 see each other using ESM. ... Check the Recipient Policies for the correct domain name listed as an ... user on the E2K3 server. ... The enterprise RUS should stamp the SMTP VS with the addresses ...
    (microsoft.public.exchange.connectivity)
  • Re: Lingering objects, replication on dcs
    ... Hi Jorge, I looked at the events carefully and I remembered after I did the ... whack, but there's still some replication issues, I noticed it replicates ... # Jorge de Almeida Pinto # MVP Windows Server - Directory Services ... the old 2k DC and then uninstall e2k3, reinstall the 2k3 DC, I'm trying to ...
    (microsoft.public.windows.server.active_directory)
  • Re: can more then one server run on a small business 2003 network
    ... Well, a fresh install will be clean, but as I said, it is not necessary to ... STILL have access to the accounting folders. ... >> the second 2003 DC to a member server if desired and do whatever you need ...
    (microsoft.public.windows.server.sbs)
  • RE: How do out-going mails route from Exch 5.5 to 2003?
    ... Regardless of their location the 5.5 server is going to pass the message to ... the E2k3 server via MTA, E2k3 will them convert the message into SMTP ... Format and push it through the SMTP Connector. ... Are the messages from the 5.5 users backing up in the MTA for the E2k3 ...
    (microsoft.public.exchange.connectivity)