Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1443
  • Last Modified:

Can't mount mailbox store

Hi,

our clietns sbs 2003 server got turned off (not clean shutdown) early this morning and since then whilst the server is up and running, the exchange databases wont mount.
the error is:

SOURCE: ESE
Event ID 453

Information Store (4580) First Storage Group: Database E:\Program Files\Exchsrvr\mdbdata\priv1.edb requires logfiles 7474-7475 in order to recover successfully. Recovery could only locate logfiles starting at 7475

I dont know where to find these files but if they have gone, what can I do?
Thanks
0
teknite
Asked:
teknite
  • 5
  • 4
1 Solution
 
Shreedhar EtteCommented:
- You need to repair the exchange database.

- What is the size of the database?

- Steps to be perfomed:
a. Backup the Exchange Database.
b. Perform the repair on the database by executing command eseutil /p priv1.edb
c. Perform the defrag on the database by executing command eseutil /d priv1.edb
d. Perform isinteg

- Also refer this article:
http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html
0
 
MegaNuk3Commented:
Or just search the server for *.log and see if you can find the missing log file...

Another thing you can try is renaming the e00.chk file the trying to mount the store and that will replay all available log files and hopefully make your DB consistent
0
 
MegaNuk3Commented:
Another thing you can do is:
Eseutil /ML E00
and see if it thinks you are missing logs or if they are corrupt
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
tekniteAuthor Commented:
Hi
The database size is 9gb in total.
I'll try the renaming of the chk file first then do the repair etc.
Thanks
0
 
tekniteAuthor Commented:
eseutil /ML E00 shows no damaged log files found.
renaming of .chk file didn't help
thanks
0
 
MegaNuk3Commented:
Can you do
Eseutil /ml e00 >>logcheck.txt
and post logcheck.txt
0
 
tekniteAuthor Commented:
i'm currently running a defrag after running a repair that fixed a database corruption.
once the defrag has finished i'll see whta happens.
thanks
0
 
MegaNuk3Commented:
/P should always be a last resort as it physically cuts out errors which might be your whole message or attachments table... Hopefully it has done minimal loss to your data.
0
 
tekniteAuthor Commented:
Thanks, after the repair and defrag, the system is back up and running.
Thanks
0
 
MegaNuk3Commented:
When you have time. Dismount the store and do eseutil /mh on it and have a look at the RepairCount, if the RepairCount is 2 or less then that DB is safe to leave running in production
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now