Help with exchange store restore
Hi,Hope you can help!I am trying to restore an exchange store to a recovery storage group to extract one mailbox via exmerge.The backup product we use is CommVault, and we are not restoring from the latest backups. It does not seem to have an option to allow a hard recovery of the store during therestore (e.g. last backup set). It is an online backup as far as I know and when reading how to mount a store in a RSG from an online backup, I understand I need to run a hard recovery. However, I have no restore.env file anywhere to be seen from the restoration process or on the exchange server, so I cannot see how to do the hard recovery?Can anyone please help!Kind RegardsSteve
December 5th, 2009 3:40pm
Right - got a bit further - found a restore.env in the CommVault folder.Now when I run a eseutil /CC I get the error below:Microsoft(R) Exchange Server Database UtilitiesVersion 6.5Copyright (C) Microsoft Corporation. All Rights Reserved.
Operation terminated with error -107 (JET_errInternalError, Fatal internal error) after 0.16 seconds.This is from running eseutil from c:\program files \exchsrvr\bin or the RSG folder
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2009 4:24pm
Is it exchange 2003 or 2007?Was the back up valid? Any events getting logged after running eseutil/cc?Also see if these helps you out, they are not exaclty the error that you are getting.http://support.microsoft.com/kb/299000/en-ushttp://support.microsoft.com/kb/823016/en-usFor reference: For exchange 2003 : http://www.msexchange.org/tutorials/Exchange_Server_2003_Mailbox_Recovery.htmlFor exchange 2007 : http://www.petri.co.il/using_rsg_in_exchange_2007.htmRaj
December 5th, 2009 5:24pm
Thanks for your reply.Its exchange 2003.The backup completed without any errors as far as I know (its the first time we have tried a restore!). No events are getting logged, but if I try to mount the DB via system maanger it says it needs a hard repair.I will have a read of the KB articles.Many thanks
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2009 8:33pm
Steve,Hard repair is always the last option that you should take. Try eseutil /mh and see which log file which is reqd. to make the DB consistent.Raj
December 5th, 2009 9:39pm