Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2003 crashed - bad backup 2

Status
Not open for further replies.

frankygee

Technical User
Mar 9, 2004
41
GB
I have a single server network W2k3 and E2k3.
The server crashed. I have reinstalled W2K3 and E2K3 but am not sure of the exact path of the original MDBDATA folder.
Is ther a way to find out from the log files where the original database files were located on the server.

Also is ther a way to restore with only the edb and stm files.
 
I have a single server network W2k3 and E2k3."

"The server crashed. I have reinstalled W2K3 and E2K3"

At this point I would say no. AD is gone, and with it the configuration for your original exchange install. Your best bet at this point is to mount new blandk databases, create new users, and use a 3rd party tool like powercontrols from Ontrack to recover the mail from the old .edb and stm files.

 
Hi xmsre,
thanks for the advice.
A few other posers.
I may be able to access the System state. Is there a way to recover the recipient objects from this list (there is an extensive list of contacts to recover.)

Also is there a way to recover the exchange configuration ie organisation name, database path and admin and file names for exchange databases from either chk or log files.

Sorry for the ambiguity but inherited this problem from some one who reinstalled the server before checking the integrity of the backups. I have access to log and cchk file but from old backups.
 
Org, site and server name are put in during install. If you know them, just install it.

Then use Ontrack or Aelita Recovery Manager to get the data off tape as best as possible.
 
Thanks for the advice.
Will have a look at the products.
If they can read an unmounted edb as stated and pull out mailboxes and insert into a new store then should solve the problem.
A bit on the pricey side though. However saving on IT support was what got them to this point in the first place.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top