How to fix corrupted priv1.stm?

Last night our Exchange backup failed due to a "corrupt database file". I checked the app log in Event Viewer on the Exchange server and saw the following:

Event Type:      Information
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      221
Date:            3/30/2010
Time:            7:40:08 AM
User:            N/A
Computer:      TLCX*****
Description:
Information Store (7428) First Storage Group: Ending the backup of the file F:\Program Files\Exchsrvr\mdbdata\priv1.edb.

For more information, click http://www.microsoft.com/contentredirect.asp.







Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      217
Date:            3/30/2010
Time:            7:50:18 AM
User:            N/A
Computer:      TLCX*****
Description:
Information Store (7428) First Storage Group: Error (-613) during backup of a database (file F:\Program Files\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore.

For more information, click http://www.microsoft.com/contentredirect.asp.

So from the first notification and Event Type (Information) it seems that priv1.edb backed up fine and the byte count on the backup server shows this. However, the second notification shows that there is a problem with priv1.stm. I imagine that if something goes wrong and we need to restore the mailstore from last night, we will not be able to do so because of the corrupted priv1.stm. How can I repair this? We are using the Enterprise version of Exchange 2003, if we create another Storage Group and another mail store and move all users to the new store, and backup this store, will we still have the same issue? Well let me back up a bit (pardon the pun), first of all what effect if any will moving the users to a new storage group and store have on the users' email accounts? I appreciate any help. Thanks
bachma0507Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
Please have a read of the following article which should resolve your issue:
http://support.microsoft.com/kb/555146
eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
Should allow you to recreate your STM file.
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bachma0507Author Commented:
So it seems from these instructions that basically the priv1.stm file will be 0 bytes after the re-creation, and all data associated with the original file will be lost, is this correct? I know the the KB article says that if the users mainly use Outlook to connect to the database, then data loss for these users will be minimal, and most of my users do use Outlook. However, the size of the priv1.stm file is about 15GB and losing 15GB of data is mind boggling to me. But I guess if there's no other way, then I do not have a choice, especially if this corrupted stm file is jeopardizing any future attempts of data restore for our mail store.
0
Alan HardistyCo-OwnerCommented:
You can copy the file elsewhere if you have room and then rebuild it - it will recreate what it can from the info it has.
Either way - if your current one is corrupt - what choice do you have?
0
nesan1984Commented:
You cannot repair a corrupted *.stm alone. You need to repair both the *.edb and *.stm files as a set. The following links should clarify this:

http://technet.microsoft.com/en-us/library/aa997215%28EXCHG.65%29.aspx
http://technet.microsoft.com/en-us/library/bb217660%28EXCHG.80%29.aspx
http://www.mike-tech.com/article.php?gif=exchange2k3&article=304

Regards,
Nesan R.

0
abhiyCommented:
The error you getting is -613 which means JET_errSLVReadVerifyFailure caused if there is a Checksum error in SLV file during backup.

Point 1. Do not directly jump to /CreateStm as it would make you loose 15GB strainght and may cause to loose some more from .Edb. This is because the command you use is Eseutil /P /CreateStm which also runs on the .Edb file while creating a blank .Stm file

The STM file contains all mails that has been sent/recieved using OWA apart from attachments and straming data.

So what to do:

1. Go through http://support.microsoft.com/kb/318429.
2. Alternatively, if this is Ent. version you can move the MBXs to different store and mount the original store with blank one and move abck the MBX again to original store. (Moving MBXs between the stores will not cause any harm. Moreover you will not have any downtime and the process is invisible to the end users).
3. If you still plan to got for Eseutil /p /createstm, please have a flat file copy of the .edb and .stm files somewhere as backup.
4. Once you are done fixing the issue, take an online backup as soon as possible.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.