Dell PowerProtect Data Manager Appliance 5.12.0.1 Microsoft SQL Server User Guide

Centralized restore of multiple Microsoft SQL Server databases

You can perform a centralized restore of the full or transaction log backups of multiple Microsoft SQL Server databases in the PowerProtect Data Manager Appliance UI.

1. In the PowerProtect Data Manager Appliance UI, select Restore > Assets and select the SQL tab.

   The Restore window displays all the databases that are available for restore.

   To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

   • The Host/Cluster/Group Name column lists the hostnames.
   • The Application Name column lists the Microsoft SQL Server instance names.
   • The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

   NOTE Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft SQL Server host and instance.
2. Select the check box next to each database that you want to restore, or in a filtered view, select multiple databases through a check box in a column heading, and then click Restore.
   The restore wizard opens on the Select Copy page.
3. On the Select Copy page, click the Protection Storage icon in the left pane for the primary or secondary source Protection Storage.

   The right pane displays a message that the restore operation uses the latest copy on the storage target, when available. The most recent full or transaction log backup copy is restored.

   NOTE If a transaction log backup is the most recent copy, the entire backup chain from the base full backup is restored. If you need to restore older backup copies, use a single database restore to restore the backup copies one at a time.

   Click Next to continue.

4. On the Select Destination page, the Host and SQL Instance fields are prepopulated, but you can click Select for each field to specify the host and instance as needed.
   NOTE

   Microsoft SQL Server system databases (master, model, msdb) can only be restored to the original host and Microsoft SQL Server instance. If the required host is not listed, follow the instructions in Considerations for centralized Microsoft SQL Server application-aware restores.

   If you specify a Microsoft SQL Server instance that is part of an Always On Failover Cluster Instance, the database restore is directed to the active node.

   Click Next to continue.

5. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

   • Original file location (location at backup time)

     NOTE If the directory path cannot be created during the centralized restore, the restore fails.
   • Default file location as set by Microsoft SQL Server

   • User-specified file location

     NOTE

     When you select this option, you must specify the restore file directories for the database files and log files.

     To restore a database to a different name, ensure that you specify a custom destination directory that is different from the directory that contains the source mdf and ldf files.

6. On the Select Options page, select any the following options, and then click Next:

   • Overwrite Databases WITH REPLACE—Overwrites the existing databases during the restore operation.

     NOTE

     When a database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

     After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

   • Compressed Restore—Uses DD Boost compression for the restore operation.
   • Disconnect Users—Disconnects the database users before the restore operation.
   • Troubleshooting—Enables the debug log, setting the debug level to a value of 9.

   • Restore State—Select one of the following options:

     • RESTORE WITH RECOVERY—Leaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.
     • RESTORE WITH NO RECOVERY—Leaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.
7. On the Summary page:
   1. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.
      NOTE When the specified database name matches the name of an existing database, the restore overwrites the existing database.
   2. Click Restore.
      The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.