Exchange restore fails

[Eksistenz]

I'm trying to restore an Exchange 2003 Private Information store using Backup Exec 10, rev 5484, sp3. I've created the Recovery Storage Group in Exchange nand added the Priv info store to it, and it's offline, but when I run the restore I get the following message from BE:

Unable to restore some Microsoft Exchange components because one or more of the ddatabses are currently mounted. Use the Exchange System Manager to dismount the databases, and then retry the job.

Any suggestions?

Thanks in advance,

Paul

 

[Prydonian]

Eksistenz;

You have to log into the admin account on the exchange server and run the Exchange System Manager.

Expand SERVERS on the tree in the left hand pane.
Expand your exchange server and storage group.
Right click the mailbox store and select properties.
Click on the database tab and tick the box that says 'Allow this database to be overwritten by restores' and click OK.
Right click the mailbox store again and dismount the database.

You can now run the restore which will work. It will also apply all of the transaction logs and remount the store when it's finished (as long as you selected that option). Just be aware that depending on the size of your mailbox store, it can take up to 30 minutes to apply the transaction logs and remount the store while the BackupExec progress bar sits at 99% complete, leading some to think it has hung. Be Patient!!

Mike, The IT Guy.

Life is too short to drink warm beer....

 

[steveot]

Upgrade to Backup Exec 10d. If you look at 5520 there is a hotfix for this event after performing the steps above.

10d will have all the hotfixes from 5484 and 5520

 

[Eksistenz]

Thanks for your responces.

I discovered what the problem is - it's a result of the backup being a snapshot one. BExec cannot redirect snapshot backups to a recovery storage group - whish a right pain.
However, I cannot find any reference as to how you do a backup WITHOUT using snapshots!

Any ideas?

 

[Eksistenz]

Found the solution - you have to turn off Advanced Open File option.

This is a pain as well, as it means that if you include your Exchange backup in a job backing up a file server, you can't use the open file option on the file server, as it's a 'per job' setting.

Going to see if there's a way of chaining backup jobs, so I can run a file server backup, then when it finishes, run an Exchange backup straight afterwards.