06-06-2007 03:56 PM
Message Edited by Rosy on 06-06-200704:06 PM
06-07-2007 07:10 AM
Hello,
This is not Small Business Server, correct?
Try dismounting Recovery Storage Group, then deleting all of the files created by the RSG. Mount the store again, and hit YES to the message that you get. This should create and mount a new, empty RSG database.
Verify the database is able to be overwritten, and then dismount the store.
Reconfigure the restore in Backup Exec, and select the following options selected:
-Purge existing data and only restore the databases and transaction logs from the backup set
-Commit after restore selected
-Mount database after restore NOT selected
Also verify that you are not restoring any public folder stores.
If the restore fails again, look for any ESE errors in the application log on the Exchange server.
Let us know if you have any questions.
06-07-2007 10:55 AM
06-07-2007 11:16 AM
06-07-2007 11:27 AM
06-07-2007 11:32 AM
Rosy,
You won’t necessarily see errors in the application log. Are you even seeing Exchange attempt to restore the database in application log? There maybe informational alerts and not errors.
Can you try taking a live backup of the Exchange Information Store and then restoring it to the RSG, or try restoring from another backup?
Also, try restore to another temp path. Make sure the temp folder is empty prior to the restore.
06-08-2007 09:14 AM
06-08-2007 09:51 AM
Rosy,
Can you create and run a new backup from scratch of the Information Store, and verify that there is no Advance Open File Option selected under the Advance Open File Option settings, and see if you still see VSS being used in the job log of the backup?
Also, are you performing a redirected restore?
It’s odd that you see the backup type as Full and not Snapshot Full in your restore selection list. This is why I haven’t focused on VSS being the issue, but if the backup was in fact a VSS backup then you could be limited on whether or not you can use the RSG. This is starting to sound like this is the issue.
When we perform a restore of Exchange 2003, we have no idea whether the restore is going to the RSG or directly to the production store. We treat each restore the same, and do not perform anything different with the two restores.
This is why there is nothing to configure in Backup Exec to make the restore go into the RSG. This is fully handled by Exchange.Since you can restore to the production store, I suggest either contact use and opening a support case or contacting Microsoft to see if they can determine why the RSG restores are failing.
06-08-2007 10:52 AM
06-12-2007 07:50 AM
06-12-2007 01:05 PM
Message Edited by Dean Bliss on 06-12-200704:06 PM
06-13-2007 01:21 PM
07-09-2007 11:33 PM