ryanj1987
asked on
Store Fails Repair - 4001 (JET_errFileIOBeyondEOF)
Long story short, server blue screen - exchange wouldnt mount when it came back up. tried a bunch of different things that led me to this step (eseutil /p). How do i get it back to a clean shutdown state, even if i loose some mail from the day it went down? Assume back ups aren't an option (NTBackup is also throwing an error).
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Looking into the files the priv1.stm had a file size of 0 (which struck me as odd). I renamed the file and recreated the stream file using eseutil /p /createstm. It recreated the stream and completed the repair.
Ref: http://blog.sirkevi.com/files/Fixing_Exchange_error_-4001_JET_errFileIOBeyondEOF.php
Ref: http://blog.sirkevi.com/files/Fixing_Exchange_error_-4001_JET_errFileIOBeyondEOF.php
1. Create a Recovery Storage Group, and do not mount it.
2. Restore your old backup to this RSG
3. Place the log files in the same directory where you created the RSG. Pay attention to your backup date and pick the delta going forward between the logs and the backup.
4. At this point you need to run eseutil /cc [Path to restore.env] to attempt to replay your log files.
5. Mount your stores in RSG and merge the email back into your rebuilt DB.
If there are absolutely zero working backups, then I'd ask how many users you had previously and if they used Cached Exchange Mode. If you have a low enough number of users, you could also take the easy way out:
1. Rebuild Exchange from scratch, re-creating user mailboxes
2. Go to each client in offline mode and export their mail to a .PST
3. Add the new account in Exchange and import the .PST
I have never tried replaying log files to a blank DB, but I guess you could do that, too.
Good luck,
T