Re: Exchange 2000 Disaster Recovery
- From: "Dave Goldman [MSFT]" <dgoldman@xxxxxxxxxxxxxxxx>
- Date: Tue, 14 Nov 2006 10:13:16 -0500
Your best bet in this situation is to bring up dialtone databases so that
you are up and running. You can then put up a recovery server and trying
your disaster recovery to get the data. If all fails as a last resort you
might want to look towards Quest as they have a utility that you can
download as a trial that will let you pull the mail out of the databases
with out them being mounted and online.
Now if you decide to put up a second server you need to make sure that you
isolate that server as you dont want to this to be part of your production
enviornment. If you do it this way the server can have the same name. The
server name only comes in to play if you need to mount the public folder
store, however you are only after the email at this point. Again the safest
way is to make sure you have an isolated network and get those stores
mounted. Once you have done this you can get the data to pst and them remove
exchange from the box or keep all of the services disabled and get the pst
files moved over for the users so they can access them.
Dgoldman
"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13235FF8-42E8-43D9-93F6-AB865ED3B613@xxxxxxxxxxxxxxxx
Situation:
Exchange 2000 Server is also a DC, and the GC for the domain (early
consultant). UPS failure in the rack caused box to go down hard about 4
weeks ago. After much frustration, a restore to a previous day on the
Exchange stores brought us back up (although now I feel there was still
corruption). Fast forward, ordered new box, installed OS & Exchange (NOT
a
DC this time). However, before moving over, UPS failed again. Attempts
at
eseutil and isinteg were useless, and now the corruption is at the OS
level.
Applications see the root drive as full (even with about 500MB free). Had
to
reset TEMP variables to another partition just to get MMC & System Manager
to
run. Stores won't mount, and the OS won't run a restore in Veritas
(corrupt
catalogs, not enough free space errors).
I have the new box up and running, as a different name, but I need to
recover as much mail as possible from the previous one. I'm really
looking
for strategies of best practice here, as I've never quite had so many
problems converge at once.
1. Should I attempt to blow away the current mail server and trust tape
backup, hope that gets things up and running (leery because it's DC & GC)
long enough to either Mailbox Move, ExMerge the data out, or just flat out
PST exports the long way, whatever works.
-OR-
2. Should I delete users mailboxes in AD, create new ones on the new
server, and let them get up and running right now on the new server, and
THEN
work on recovering older data?
Option 2 is appealling (albeit because they have no e-mail), but I'm
worried
about having the 2 Exchange servers running simultaneously while working
on
recovering data on the old one, and I'm also worried about recovering
after I
get the old one up and the stores mounted. If I've deleted their mailbox
in
AD, created a new one on the new server that was blank and they are
working
on, can I create a dummy user account, attach it to the old mailbox to
extract data, then import that into the new mailbox? (Seems like a very
long
way around, but the thought of tape restoring Exchange, AD & GC servers in
one shot is less than appealing as well).
All advice appreciated, thank you!
.
- Prev by Date: Re: Virtual SMTP authentication
- Next by Date: Re: Stopping Inbound Mail
- Previous by thread: IMF filter updates not working
- Next by thread: RE: IMF Not Updating (IMFv2) / IMF will not update
- Index(es):
Relevant Pages
|
