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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

completely dead Exchange/SBS server, no logs, just EDB and STM

Status
Not open for further replies.

gurner

Technical User
Feb 13, 2002
522
US
I was wondering if anyone could shed any light or give us some pointers, cheers

There was a pretty spectacular server crash at a place last week that resulted in a degraded Raid5, no file system, nothing, on an old spec not particulary quick cheap Dell PE

now this was not a particularly well documented system, and the only seeming copy of the Exchange system is the EDB and STM files, as it appears that the backups (that were extremely flakey) were removing the Log files, and the base exchange files are all that was left from a manual copy from the weekend.

after 4 hours rebuilding the degraded disks on the Raid5, and then an unexpected 200gb Chkdisk over another 3-4 hours on another partition, and 3 hours re-installing SBS. it was majorly against the clock, and blue screened after an Active Directory restore mode restore.

so rather than waste more time and faff around the decision was taken to do a fresh install over another 3-4 hours (as it was 10 users, 9 of which were using Outlook Cached Exchange mode)

A brand new server was installed, exchange was configured, accounts were created, client pcs updated, OST files copied to PST files, and back again to new mailboxs, all went fine, albeit new profiles on a new domain etc.

problem was due to the poor documentation there was a slight change in the domain name, the characters 'ltd' were missed off from copying the old setup.

There is one user that wasnt using Cached Exchange mode, who has subsequently lost a years worth of emails. We have one day old copies of both the EDB and STM files, but no logfiles from the server which wont mount on the new server build (the domain and exchange storage group structure are different)

there are copies of these copies, one set is untouched restored from tape, the other one has had a hard repair run on it to get it to a clean shutdown state.

The prolonged use of it isnt nessasary, we just need to get it mounted to try and ExMerge data out, but it wont mount.

We have a test server with exactly the same name as the pre-crash server, with a new test AD domain with the 'ltd' part on it, Exchange installed to the same storage group structure.

but doing a Dfrag, Repair and ISInteg, and mount doesnt work, there are variuos errors, the most prevalent are

Error 0xfffffae7

Error c1041724 with an Event ID 9519 when tried to recover database on different server.

in fact there are postings on some other places with people that have been in the same boat, i.e. having just EDB and STM files but no logs or system state. but theres no replies to them.

has anyone come across this or has experiance?

just pointers will be ok, ie. mounting an exchange db to different server, with different domain (possibly) and exchange organisation (poss again) and none of the old users, just so we can ExMerge it.

Cheers

Gurner
 
You can use Ontrack Power Contols utility to get the mail out of stm and edb files and dump it into pst(s)
 
nice, that program looks great, the demo certainly worked a treat, but i couldnt export any of it. suspect the wallet people will squeak when when the cost is banded about tho

we've managed to retrieve week old transaction logfiles, which are transferring at the mo.

anyone know the best method of working with these?

we still have a test server with the same AD name and Exchange org (but they're still new builds not a restore, so guids are different etc)

theres a hard repaired set of db files, and an untouched one from a tape, but the tape one is likely to be out by however much time and wont match the logfile dates i suppose

am i right in thinking the 'eseutil /cc' command now we have a log and a chk file?


Gurner
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top