You recover a database within SQL Backup Master by running the Database Backup Recovery Explorer and then clicking the Recover action link associated with a specific database backup file. The Recover Database window will be shown.
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 System Administrator role in SQL Server.
The backup summary panel indicates the following:
•Database name - The name of the source database that will be recovered.
•Backup type - The type of database backup being recovered.
•SQL Server instance - The instance of SQL Server to which the database backup will be recovered.
•Target database - The name of the target database to which the backup file will be recovered.
To restore the database backup file to a different SQL Server instance than the one that created it, click the hyper-linked SQL Server instance name and choose a SQL Server instance.
To restore the backup to a different database, either select a new database name (via the drop-down arrow) or type in a new one.
During the database recovery process, SQL Backup Master can either leave the database in a "ready to use" (e.g. running, full recovered) state or it can be left in a non-operational state.
You would normally elect to leave the database in a non-operational state only if you planned on executing additional recovery steps (such as recovering subsequent differential or transaction log backups) immediately thereafter. For more information regarding the sequencing of restore operations, please consult your SQL Server product literature.
When you are ready to recover the database backup, click the Begin Recovery button.
SQL Backup Master will then execute the following steps:
1.The database backup file will be downloaded from its current backup destination. This file will be stored in the temporary database backup folder assigned to the backup job.
2.The backup file will be decompressed (and possibly decrypted) using the compression/encryption settings currently defined for the related backup job.
3.Any existing connections to the target database will be terminated.
4.The database (or log file) will be restored.
5.Temporary database files will be cleaned up, etc.
IMPORTANT: Any existing data in the database being restored by the backup process. This operation cannot be undone unless you create a backup immediately prior to the restore.
See also: Manual database backup recovery