Exchange 5.5 Recovery

[Tony Ashby]

I just want to verify what steps are needed to recover a
Exchange 5.5 server with multiple sites.
Do I re-install Exchange on the new server and create a
new site (same Domain, Site and Server name) not join an
existing site?
Then do a restore of the stores and directory?
I have done recoveries in the past in a single site
scenario but not one with multiple sites.
Please advice!
Thanks

[Susan]

if you're talking about a recovery server, yes, you create a new site (do
not join existing site), but do not restore the directory...no
need...restore only the Stores, then run the DS/IS consistency check...then
you can recover the data from whatever mailboxes using exmerge...

"Tony Ashby" <tash...@yahoo.com> wrote in message
news:2042901c4596b$525c2600$a601...@phx.gbl...

[anon...@discussions.microsoft.com]

This server will be going back into production. How does
that change this procedure?

>.
>

[Susan]

what, exactly is the objective? replacing an old server? best, easiest way
to do this is to install a new server into your org, then move all the
mailboxes to it (and PFs)...

<anon...@discussions.microsoft.com> wrote in message
news:20b5c01c459f1$7b527b50$a301...@phx.gbl...

[tash...@yahoo.com]

I have a single organization 4 site Exchange system that
I need to replace one of the email servers in with new
hardware. I have to keep the same server name and IP
address because of many disperse systems (applications)
send email via the name and/or IP address of the original
server. So my plan is to build the new server with the
same name, IP address and join the domain when I take the
old production server offline. I will then install on the
new server Exchange 5.5 w/sp4 into a new Org and Site
which will be the same as the one the production server
came from, then restore and include the directory.
Will this allow all the sites to talk to the new server
as before the server migration?
I'm concerned about getting the new server put back into
this mult-site organization and communicating with all
the other servers when I'm done.

Hope this helps.Thanks!!!

>.
>

[Susan]

you have to join the domain before you install Exchange, and if you install
Exchange, you cannot rename the server later...to do what you're
recommending, you have to take the original server down, then do your
install of Exchange, reconfigure any/all connectors, then restore the
directory and the stores. I still think it would be easier for you to bring
up a new server in the org, and move everything to it...and reconfigure
whatever apps need to call the Exchange server for whatever they are
doing...

<tash...@yahoo.com> wrote in message
news:2108601c45a02$094d93d0$a401...@phx.gbl...

[anon...@discussions.microsoft.com]

I agree that it would be easier to bring up the server in
the same site, but unfortunately I don't have that as an
option. I wish I did.
Thanks for your help!

>.
>

[Susan]

OK, this can be done, but it's not fun...here is what I did when I had to do
this one time - note that this will not work unless your new server will
have the same OS and SP as your old server:

Start with full, online backup.
On old Exchange server, note configurations of any/all connectors, TCP
stacks, pager gateways, IMS, etc.
Also note configuration of any OWA implementation (logon accounts, etc.).
When backup is complete, shut down Exchange services.
(Ensure that you know the Local Administrator's logon and password, because
both servers will need to be removed, and re-added to domain, to complete
this next step.)
Rename old server to different name and change IP address.
Rename new server to old Exchange server's name (ensure it is exactly the
same), change IP address to that of old Exchange server (not mandatory, but
a good idea).

Ensure that OS and same service pack as old Exchange server is installed
(and IIS, if you're using OWA).
If this was done already, reinstall applicable SP to NT after changing IP
address and ensuring that WINS, DNS, etc. is set up correctly on new server.
Install Exchange, creating new site (exact same org, site, and server names)
and, of course, using the same Exchange Service Account.
Disable circular logging (because that's the way I had it set, on old
server).
Install any/all connectors that existed on old Exchange server, with exact
same configurations.
Install same Exchange SP that was on old server.
Run Performance Optimizer.
Reboot server.
Shut down all Exchange services except System Attendant.
Restore Directory first.
Restore Information Stores.
Start services.

At this point you can reconfigure your OWA if you are using it, following
the notes you made on your prior setup.

If anything should go horribly wrong (mine went off without a hitch), you
can turn off the new server, rename and re-IP address the old one back to
its original settings, and bring it up.

<anon...@discussions.microsoft.com> wrote in message
news:210d801c45a06$de9ab140$a401...@phx.gbl...