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

Need help restoring exchange 5.5. can not start services.

Status
Not open for further replies.

nwyabe

MIS
Jun 26, 2003
2
US
Exchange 5.5 (sp3) on NT4(sp6). Exchange app on C: drive. databases on f: which is a 6 disk, raid 5 array. A/C in the server room went out over the weekend and I lost 2 hard drives destroying the array and data. Thus far I have been able to restore:

f:\exchsrvr\dsadata\dir.edb (dir.pat, edb.log, res1.log, res2.log)
f:\exchsrvr\mdbdata\priv.edb (pub.edb, pub.pat, priv.pat, edb082AC.log)

When I restored the logical drive, I had to create the f:\exchsrvr and substructure folders in order for ArcServe to restore the data files. Then I went to Services to start up the exchange services. Received mostly "dependency service or group failed to start", and when trying to start MS Exchange Directory received "1067: process terminated unexpectedly".

I've heard it is very difficult to recover a 5.5 database. Of course, as with most disaster recovery, you don't know how deep you're in until you are in it. Any and all help needed. Thanks.

Nate
 
Hi,

I get these error s occationally, when I do my heart sinks.

Basicall I think it is due to a corrupt message in either MTS-IN or MTS-OUT, you neeed to get a small util and rummage around the db and delete the offending item.

Fairly hairy stuff and I expect it is very easy to snarl the db totally.

So far I have been able to recover using the following method.


although, of late I have been unable to delete single messages, and I had to use the 'empty folder' call, which is a bit severe, especially if the problem has been sitting around for a few hours and the queues are filling up.

Good luck.
 
MJoyce is right. Its hair raising (or for me falling out) stuff to repair exchange dbs. You might want to try this if the IMC won't start. in the imcdata directory look and see if there is a file called queue.dat. Make a copy of it and delete the thing. Try starting the IMC. Bad messages in this file can cause the IMC not to start............
 
Thanks. I got this figured out last night. A corrupt log file and mta. Removed log file, copied mta from CD to mtadata, applied service pack to mta. Everything started right up. Thank <insert diety of choice>!!! =)

Nate
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top