Restore requirements and limitations for Microsoft SQL Server
Consider the following before you restore a SQL Server snapshot:
Ensure that you close SQL Management Studio before you restore a SQL Server snapshot.
This is applicable only if you are restoring the snapshot to replace the current asset (Overwrite existing option) or restoring the snapshot to the same location as the original asset (Original Location option).
In case of a SQL instance disk-level restore to a new location fails if the target host is connected or configured.
In such a case, to complete the SQL Server snapshot restore to a new location successfully, you must perform the restore in the following order:
First, perform a SQL Server disk-level snapshot restore.
Ensure that you restore the disk snapshots of all the disks that are used by SQL Server. These are the disks on which SQL Server data is stored.
Then, after the disk-level restore is successful, perform the additional manual steps.
See Additional steps required after a SQL Server instance snapshot restore.
NetBackup Snapshot Manager does not support discovery, snapshot, and restore operations for SQL databases that contain leading or trailing spaces or non-printable characters. This is because the VSS writer goes into an error state for such databases.
Refer to the following for more details:
Before you restore a SQL Availability Group (AG) database, perform the pre-restore steps manually.
New location restore of system database is not supported.
If destination instance has AG configured, restore is not supported.
If database exists on new location destination and the overwrite existing option is not selected, the restore job will fail.
If the overwrite existing option is selected for database that is a part of an AG, the restore job will fail.
For system database restore, the SQL Server version must be same. For user databases, restore from a higher SQL version to a lower version is not allowed.
Default timeout of 6 hours is not allowing restore of larger database (size more than 300 GB). Configurable timeout parameter value can be set to restore larger database.