SQL Backup Master Help

SQL Backup Master provides the ability to restore multiple databases in a single pass through it's restore queue feature.

 

To begin, launch the Database Backup Recovery Explorer and select the backup and destination from which you wish to restore. This will show a listing of backups that were created by your backup jobs.

 

Click the Actions button in the database listing to add entries to the restore queue.

 

Important: When recovering a database backup from within SQL Backup Master, you should run SQL Backup Master from a Windows account that is a member of the "sysadmin" role in SQL Server.

 

Supported Scenarios

 

SQL Backup Master's restore queue feature can restore multiple full backups or entire backup chains that are comprised of a full backup, a differential backup, and one or more log backups.

 

To create a restore sequence, select the Actions button associated with each backup and select Add to restore queue.

 

To create a full restore chain, first add the full database backup to the restore queue. Then optionally add a single differential backup and one or more log backups. When doing so, you must ensure that you queue the correct backup sequence.

 

Executing the Restore

 

With the Restore Queue populated with your database backups, click the Process Queue button.

 

The Multi-Database Restore Progress window will appear, providing a summary of the Restore Queue's contents, along with a Restore Details view that shows the planned sequence of database restore operations.

 

Click the Start Restore button when you're ready to proceed. A final confirmation message will appear.

 

Important: As with any SQL Server restore operation, this will replace existing data and cannot be undone.

 

Troubleshooting

 

If errors occur during the database recovery process, the database may be left in a non-operational state.

 

For example, say you're restoring a backup chain comprised of a full, a diff, and a log file. If the full and diff restore steps succeed but the log restore fails, the database will be left non-operational. It will now be necessary to repeat the recovery process successfully (perhaps by excluding the log file) in order to return the database to an operational state.

 

If you're restoring a backup chain and receive errors indicating that the database has not been restored to the correct previous state, the restore chain is most likely incorrectly formed.