You are here: Microsoft SQL Protection > Restoring SQL backups

Restoring SQL backups

The Windows agent supports restore of full, differential, and transaction log backups of SQL databases. When performing a restore, all previous backups in the group are also restored. This means that when you restore a transaction log backup, the master, the latest differential (if any), and all prior transaction log backups are restored as well. Each backup being restored will be its own restore job, and all restore jobs for a group are queued automatically.

Considerations for restoring SQL backups

Consider the following when restoring SQL backups:

The entire database is restored in a live state with each restore operation.
Unitrends does not support granular restore of Microsoft SQL Server database records.
User databases must be restored to the same versions of Microsoft SQL or later.
Databases cannot be restored to a prior version of SQL.
Restore procedures vary depending on what type of backup and database is being restored.
If restoring a SQL cluster backup, the cluster node must be selected.
If restoring a clustered database instance to an alternate location, you must select a path that is on a shared volume that is associated with that SQL instance.
If restoring to an alternate location, only full backups can be recovered.

The following restore procedures are available:

Restoring the master database
Restoring the model and msdb databases
Restoring SQL full backups
Restoring SQL differential and transaction backups
Restoring multiple SQL databases
Restoring a backup when the SQL icon does not display