SQL Centralized Restore in PowerProtect Data Manager (PPDM) version 19.6

This video KB presents the SQL Centralized Restore feature added in PPDM version 19.6, as it discusses its benefits and describes how to be used, this is presented in a short demo video.

What is SQL Centralized Restore
SQL Centralized restore is a solution newly added into the PPDM v19.6 used to restore SQL VM app aware databases and files.

The main point is that we are able to restore the SQL databases to a running SQL which may or may not be a part of a policy.

Benefits:      
SQL Centralized restore has a lot of benefits, such as:     

• Centralized Management.
• It centralizes SQL backups and restores Which provides simplicity and ease.
• As it Offers the ability to restore SQL DB to alternate server from centralized restore.
• No scripting is required which reduces DBAs workload.
• And no need to install SQL SSMS on each SQL host.

Capabilities:     

• SQL Centralized restore is able to restore Simple and multiple database Restore backed up by SQL VM Direct Protection policy to SQL servers running in VMWare.
• Also, it is able to restore Backup VM image, or files from VM image backup like mdf and ldf files.
• As well as the ability to restore to VMs not even a part of any policy.
• Note that we can backup the tail log in single database restore, but, we cannot restore it in multiple Databases restore case.

Restore Destination:     
We have two restore destinations:     

• Restore to the original database. This may be used when SQL VM is protected by PPDM VM App aware policy and it is used for operational restore and disaster recovery.
• The other option is to Restore to alternate database. It is used for DEV Test Refresh and restore rehearsal.

Database File Location:      
We have three options to choose the Database file location:     

• The first is to Restore to the original file path and name where the file system paths must exist and the filenames must not be in-use.
• The second is to Restore to the SQL instance defaults location.
• The third is to Restore to custom location where the user can specify one path for data files, one path for log files. Of course, the file system paths must exist. This will be discussed further in the Demo.

Centralized Microsoft App Agent Install:     
Instead of going to the client and install the Microsoft application agent, now you can install it from the PPDM   GUI without going to the SQL client itself.   

By going to Infrastructure > Assets > choose Virtual machine > click on more actions > Install Agent.
But, before you install it from PPDM, make sure that you set credentials before installing the agent to avoid credentials error.

Limitations:      
We have some limitations on the current version:      

• SQL Centralized restore is limited to Database level restore. We will add table level restore and instance in the next releases.
• Currently, there is no Support for Quick Recovery in PPDM 19.6

Demo:      
Here is a backup already created for SQL VM where we apply SQL centralized restore on.

1. Start SQL centralized restore by going to the Recovery tab, seen for the first time in version 19.6 SQL option.
2. Click on Restore and check for Single DB restore, select Full backup to restore. Also, we can use the point in Time option.

3. Click Next.
4. Select options:      

5. Last step is to show restore configurations summary.

Second Scenario: 

1. Restoring multiple databases, not a single database. In this case, we have a limitation that we cannot choose the backup file, we must use the latest available copy.
2. Click Next to select destination where you can choose the host and the SQL Instance.

3. Click on next, then Restore and check the restore progress from the Jobs window as well as filtering the job type.

In PPDM version 19.6, we have a good feature when we go to Infrastructure, VM assets, which is the ability to select the windows VM that hosts the SQL VM, and apply more options on it.

When adding this windows VM that hosts the SQL VM, it creates asset source and turns it into SQL databases list as shows here.

The new feature is that we can install the agent manually from the PPDM instead of logging in to the VM. Install it by choosing the VM > click on more actions > choose Install agent. However, the first time you get this error because you have not set the credentials for this particular VM.

We must add credentials by clicking on more actions > Set credentials > Save it.

Now, click on more actions again and select install agent then install it. The agent is installed successfully without any errors.

Refer to this video which is also published on YouTube: