Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

After restoring some mail stores, mounting them in the recovery storage group errors out. So far a repair with eseutil (which the log says was successful) and a server reboot has been tried. A defrag is currently running on the mail store

I need to go through this again to post the exact error codes, so I will be updating this question. But I thought someone who does this a lot might have a "More times than not..." answer in the meantime.

An Internal Processing Error has occurented. Try restart the exchange ... (Nothing more useful here)
ID no: c1041724
Exchange System Manager

Events:

Event Type: Error
Event Source:   MSExchangeIS
Event Category: General 
Event ID:   9519
Date:       4/13/2010
Time:       9:40:20 AM
User:       N/A
Computer:   MAIL01
Description:
Error 0xfffff764 starting database "Recovery Storage Group\Denver" on the Microsoft Exchange Information Store. 

Data:
0000: 46 61 69 6c 65 64 20 74   Failed t
0008: 6f 20 61 74 74 61 63 68   o attach
0010: 20 74 6f 20 4a 65 74 20    to Jet 
0018: 44 42 00                  DB.    

Event 2:

Event Type: Error
Event Source:   MSExchangeIS
Event Category: General 
Event ID:   9518
Date:       4/13/2010
Time:       9:40:20 AM
User:       N/A
Computer:   MAIL01
Description:
Error 0xfffff764 starting Storage Group .... CN=InformationStore/CN=Recovery Storage Group on the Microsoft Exchange Information Store. 
MDB failed to start. 
share|improve this question

2 Answers 2

up vote 1 down vote accepted

When you restored the EDB, did you restore the log chain and STM (as joeqwerty points out) as well? I'm not 100% positive on how NetBackup does it's backups, but it probably uses VSS, which means that when the backup is taken, the EDB is in an inconsistent state. A VSS backup will flush the cache to disk, but it doesn't roll the logs into the database. When you're setting up the RSG and trying to mount the database, make sure that you have the EDB, STM, and logs from the same backup timestamp. When you mount the database, the logs will be rolled into the EDB, bringing it to a consistent state, and it should mount.

share|improve this answer
    
STM file is there, but I didn't chose to restore the log files... But shouldn't the estutil after a hard recovery put it in a consistent state? –  Kyle Brandt Apr 13 '10 at 14:32
    
I would definitely start there then. If you still have some problems mounting, try doing a fresh restore of EDB, STM, and logs and mounting that. It's a possibility that running ESEutil against it modified it and invalidated the log chain (that's a long shot, but I'm just trying to think ahead). –  Holocryptic Apr 13 '10 at 14:37
    
@ your edit... Did you run ESEutil in hard recovery (/C)? technet.microsoft.com/en-us/library/aa998075%28EXCHG.65%29.aspx and technet.microsoft.com/en-us/library/aa997478%28EXCHG.65%29.aspx. I would try to do a soft recovery first using a fresh restore of the EDB, STM and logs first before doing a hard recovery. –  Holocryptic Apr 13 '10 at 14:53
    
I thought we did, but apparently talking to the exchange person he didn't, so that seems likely what could be wrong. –  Kyle Brandt Apr 13 '10 at 15:17
    
Did you follow the steps on page 61 here? : exftpp.symantec.com/pub/support/products/… –  Holocryptic Apr 16 '10 at 20:20

EventID.net suggests that the problem might be a missing streaming file (.stm) for the DB in question.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.