Hi All, We are running Exchange 2007 on Win 2003 servers. I have a user whose mailbox I need to recover. I created a Recovery Storage Group, then moved the Database and Log files off of tape to the appropriate RSG folders. When I try to to mount the Recovery Storage Group using the Troubleshooting Assistant, it gives me the following error: Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-544) Any help is appreciated, thanks. Edit: I found something that suggested I run: Eseutil /p then /d then Isinteg Fair enough, I'll try it, but I also read that you should stop the Information Store while using Eseutil. I'm not sure exactly what stopping the Information Store will do, but I assume it will cause down time for the users? Is it a good idea for me to stop it while using Eseutil on a dismounted RSG database? Has anyone else tried this? Also, the DB is 55GB, anyone have any idea how long it might take to run those commands while the Information Store is stopped?

Why not simply restore the database from tape directing it to the RSG using the backup software's restore capabilities? ( Rather than copying it?)

Hi Super, Because the exchange store wouldn't have been gracefully dismounted during a backup, running eseutil (most important) and isinteg are definitely necessary before mounting your recovery group. Those commands can only be used on databases which are dismounted. Since your not actually working on your live store, there is no reason to dismount and perform those commands on a working database. But, if you were ever to do so, for general maintenance for example, the process is generally around an hour for every 5gb .. but this completely depends on so many factors such as hardware, it's generally impossible to predict. Also, something that seems to get a lot of people when mounting a recovery group is disk space, for various reasons. You can not mount the recovery database on a network share, it needs to reside on a local disk. A lot of people try this because there may not be enough space on the exchange server, but you also need to bear in mind that running these commands will also require additional disk space in order to complete the process. Regards, Nathan Owen (MCSE, MCITP Server Admin) - Please remember to click "Mark as Answer" on the post that helps you. Links: www.mad-monkey.co.uk - www.capitalnetworks.co.uk

If you have not already run the /P etc ..... I have seen this happen when logs are not played during restore. In such a case you can just do a eseutil /cc and point to the temporary location where logs have been restored to... this should allow you to mount the databaseTroy Werelius www.Lucid8.com