Hi all, on an Exchange Server 2007 I did create a Recovery Storage Group. After restoring a Database from Backup I was not able to mount it. Right now It has the 'Clean Shutdown' Status but I'm not able to mout the Recovery Database. C:\Users\administrator>eseutil /mh E:\MailboxDatabase3\RSG20120706115049\MailboxDatabase3.edb Repair Count: 2 Bad Checksum Error Count: found (2) Old bad Checksum Error Count: found (2) C:\Users\administrator>isinteg -s mail -fix -test alltests brings following error message in event viewer: ID: 9519 Source: MSExchangeIS Error code is: 0xfffff9bf I think still isinteg is not able to fix the database it will not mout! eseutil /k brings no changes! The transaction logs does not exist completely! Regards, Soheil

To run, ISINTEG requires a mounted database.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, I know from older Version of Exchange you had to run isinteg -patch switch to restore the information store. Is the switch -fix not the same by isinteg an Exchange Server 2007? What should be fixed with switch -fix before the db is mounted? ExTRA shows "Clean Shutdown" for this DB after I did run eseutil /R option. Now I don'nt understand why it's not possible to mount the DB!? The only information I have is 'Bad Checksum Error Count:found (2)". Regards, Soheil

Couple of points here; All Exchange Aware Backups are ALWAYS in a dirty/inconsistent state If you restore the logs along with the database files you should be able to tell the backup software to roll/commit the logs upon completion of the mount OR manually roll/commit them and for more info read this http://technet.microsoft.com/en-us/library/bb123479%28EXCHG.80%29.aspx and this http://technet.microsoft.com/en-us/library/bb123919%28v=exchg.80%29.aspxThe only time you would need to do a repair is if A: the logs were not available or B: the logs will not roll/commit because of database or log corruption if you do find that you are in need of a repair and upon completion it will not mount then you should try an eseutil /d to defrag the database since many times that will fix the issue and allow you to then mount in the RSGAlternatively if you are open to 3rd party utilities check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp which can open any offline database so that you can Browse, Search, Export Mailboxes, Folders and Items to PST or Recover data directly from the offline database into any Production Exchange server, even cross version like 2003 --> 2007 --> 2010 etc. NOTE: DigiScope does not need to run on an Exchange Server and if a database is corrupt DigiScope can do the repair directly NOTE2: DigiScope 4.0 will be released shortly and one of the new features allows for the opening of a database that has is in a dirty state without requiring log rollup or repair. If you are interested in checking it out just contact support and they will see if its possible to get you into the final BETA Troy Werelius www.Lucid8.com Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

I am not a database internals expert, but it would seem to me that a bad checksum indicates a corrupt database.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, me too ;-) I did try it with another database file. One problem was the enabled option 'circular logging' by the storage groupe! After restore any db log files war missing. I did do following steps to fix the database: 1. do the steps in this KB: http://www.symantec.com/business/support/index?page=content&id=TECH51555 2. checking the Database with ExTA Status of db was 'Dirty Shutdown' 3. eseutil /pe:\rsg\mailboxdatabase.edb after 6821.531 sec. it was finished. edb Size 92 GB 4. eseutil /mh e:\rsg\mailboxdatabase.edb Status of db was 'Clean Shutdown' 5. isinteg -s mailserver -fix -test alltests 6. mounting mailserver\rgs\mailboxdatabase.ebd by ExTA Regards, Soheil