A SQL full backup of a user database may be recovered to any available SQL server that has been added as an asset to the Unitrends appliance. The database may also be renamed and recovered to a specified alternate path if desired.
A SQL differential or transaction log backup of a user database can only be recovered to the original SQL instance.
When recovering a SQL differential or transaction backup, all previous backups in the group are recovered sequentially. This means that when recovering a transaction backup, all previous transaction backups, the latest differential (if any), and the parent master are also recovered. Each backup is recovered separately, and these backup jobs are queued automatically.
To recover a SQL full, differential, or transaction log backup
|
1
|
Select Recover, and click the Backup Catalog tab. |
|
2
|
Expand the database, and select the backup to recover. Use filter options as necessary to locate a specific database. |
|
3
|
Click Recover. Refer to the following table for additional information on Recovery options:
|
Recovery Target |
Select asset on which you want to recover the database. |
Recovery Instance |
Select the SQL instance to which you want to recover the database.
Notes:
|
•
|
A Master backup can be recovered to any SQL Instance. |
|
•
|
A differential or transaction log backup can only be recovered to the original instance. |
|
Database |
Enter a name for the recovered database. If the original SQL instance is selected and the database matches the original name, the original database files are overwritten during the recovery. Otherwise a new database is created. For system databases, the database name cannot be changed. |
Specify Path |
Enter a path to the recover location.
Notes:
|
•
|
If this field is left blank, the files are recovered to their original locations. |
|
•
|
If recovering to an alternate SQL instance on the same SQL server and no alternate target pathname is specified, the files are recovered to the default path of <Vol>:\UnitrendsRestore, where <Vol> is the volume on the client with the most free space. |
|
•
|
If recovering to an alternate SQL instance, a path is required. |
|
Commands to run pre-restore |
(Optional) Enter commands to be run before the restore. |
Commands to run post-restore |
(Optional) Enter commands to be run after the restore. |