You can perform a centralized restore of a full backup of a SQL system database in the
PowerProtect Data Manager UI.
Steps
In the
PowerProtect Data Manager 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 SQL 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 SQL 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 SQL host and instance.
Select the check box next to the SQL master, model, or msdb database, and click
Restore.
The restore wizard opens on the
Select Copy page.
On the
Select Copy page, click the
DD icon in the left pane. You can select the primary or secondary DD.
The right pane displays the available backup copies.
In the right pane, select the check box next to the full backup copy that you want to restore, and then click
Next.
On the
Select Destination page, the
Host,
SQL Instance, and
Database fields are prepopulated for the system database. You cannot edit the field values on the page.
NOTE You can only restore a system database to the original host and instance, overwriting the source database.
Click
Next to continue.
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.
On the
Select Options page, select any the following options, and then click
Next:
NOTE The tail-log backup option is not supported for a system database.
Overwrite Databases WITH REPLACE—Enables the overwrite of the existing database.
NOTE When the database exists but the
Overwrite Databases WITH REPLACE option is not selected, the restore fails.
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.
On the
Summary page:
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.
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.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\