Home > Data Protection > PowerProtect Data Manager > PowerProtect Data Manager: Microsoft SQL Database Backup and Recovery > Centralized restore of SQL Application Direct backups
When the SQL Server data is backed up as part of a SQL Application Direct protection policy, the SQL Server Application Direct backups can be recovered using the centralized restore functionality in the Data Manager UI.
Types of centralized restores of SQL Application Direct backups, depending on the type of database assets:
Note: The centralized restore of a SQL Application Direct backup and the centralized restore of a SQL virtual machine backup cannot be performed simultaneously. For Centralized restore of an Always On availability group (AAG) database and Failover Cluster Instance (FCI) database, the database needs to be taken out of the cluster.
You can restore single or multiple databases from the same SQL host and instance. The databases can be restored either to the original SQL host or to an alternate SQL host with the following requirements:
A centralized restore of a full, differential, or transaction log backup can be performed to a specified SQL host and instance. Centralized restore of SQL Application Direct backups can be performed from the Recovery > Assets > SQL window in the Data Manager UI.
Restore to original database:
Databases can be restored to the original database on the original SQL Server when the SQL host is protected by SQL Application Direct policy and SQL host is running and operational. Backup copies are used for operational restore and for Disaster Recovery purposes.
For a single database restore, the restore can be performed from a most recent copy, a specific copy, or from a point-in-time (PiT) copy.
Copy and point-in-time selection:
A single database restore supports copy and point-in-time (PIT) selection. With copy selection, FULL, DIFF or TLOG can be selected and with PIT selection, roll-forward time can be selected and available only when TLOG backup is selected.
Note: Select roll-forward time in between the timelines of full backup copy and log copy.
Restore to an alternate database:
Databases can be restored to an alternate SQL server where the SQL host may (or may not) be protected by Data Manager and the Application agent must be installed manually and registered for “unprotected” host.
Data Manager provides a rich set of options for restoring SQL databases to alternate locations. For an alternate restore, you can:
The target host must have the application agent installed and registered by the host administrator. Data Manager will automatically discover the target hosts, SQL instances, and SQL databases.
Database file location:
Use the following restore options to specify the file system location where the databases are restored:
Note: When restoring to the original path, the file system paths must exist and filenames must not be in use.
Note: When restoring to a custom location: a) the user can specify one path for data files, and one path for log files, and b) the file system paths must exist.
Tail log backup:
Tail log is supported only for a single database, for backing up the active portion of the database log present on the disk prior to starting the database recovery.
There is an option to enable DD compressed restore, overwrite existing databases, TLOG backup and to disconnect database users prior to restore.
Compressed restore option - Users can use the compressed restore option for saving network bandwidth. However, the compute resource utilization would be more for compressing/decompressing the data.
For restoring multiple databases, a restore can be performed only from the most recent backup copy.
When restoring multiple databases, select the database restore location:
Select options to enable a DD compressed restore and to overwrite existing databases.
Recovery state selection:
You can select one of the following options:
See PowerProtect Data Manager: Microsoft SQL Server User Guide for more details.