Re: 2000 database restore on 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

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

Date: Fri, 19 Mar 2004 15:06:05 -0500

J.H,

You can do a /disasterrecovery install to move to new hardware. That is
outlined in article:

297289 XADM: How to Move Exchange 2000 to New Hardware and Keep the Same
Server
http://support.microsoft.com/?id=297289

822945 How to Move Exchange 2003 to New Hardware and Keep the Same Server
Name
http://support.microsoft.com/?id=822945

What you cannot do is use this method to go from one version of Exchange to
another. It can only be used to change the underlying hardware. Or in my
previous action plan to rebuild the underlying OS.

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.
"J.H" <jpthsd@hotmail.com> wrote in message
news:utQ4bXeDEHA.1228@TK2MSFTNGP11.phx.gbl...
> Wow,,,
>
> So is that it ????????? too much simple ehh ?
>
> So it is instead of doing /disasterrecovery for the same OS & Exchange
2000
> we can do /disasterrecovery for total new OS & Exchange 2003 ? ,,this is
> amazing
> I might try it in my lab though :-)
>
> I've been planning to do /disasterrecovery  to new upgrade hardware and
W2K
> Advanced & Exchange 2000 Ent (current box running on Win2K server &
Exchange
> 2000 Ent).
> My AD is on Win2K DC with SP3 all servers are SP3 !!! Any consideration
for
> doing your
> steps to 2K3 box (OS & Exchange) in W2K domain ?
>
> Thanks,
> J.H
>
> "Matthew Byrd [MSFT]" <matbyrd@online.microsoft.com> wrote in message
> news:OamGbIQDEHA.3852@TK2MSFTNGP10.phx.gbl...
> > 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: REDIR.ASP file in use - access denied when installing Exchange 2003 SP1
    ... To resolve the problem i gave the 'Server Operators' group Full Control ... As soon as this was done the install worked fine. ... > Installation Instructions for Service Pack 1 for Windows Small Business ... What's the exact error message when you are installing the Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Blackberry and MS Exchange Administrator
    ... I understand that you want to install the Exchange ... System Manager components onto a server other than the SBS box. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.admin)