Welcome to Dell Technologies PowerProtect Data Manager
version 19.6 how-to series.
SQL Centralized Restore in PowerProtect Data Manager version 19.6.
Reference Dell Knowledge article number 179910.
This video presents the SQL Centralized Restore Feature
added into PowerProtect Data Manager version 19.6
as it discusses its benefits and describes its use
presented in this video demo.
SQL Centralized Restore is a solution newly added
into PowerProtect Data Manager version 19.6.
This is used to restore
SQL virtual machine app-aware databases and files.
The main point is we will be able to restore the SQL databases
to a running SQL, which may or may not be a part of a policy.
SQL Centralized Restore has a lot of benefits like Centralized Management.
It centralizes SQL backups and restores, which provides simplicity and ease.
As it offers the ability to restore a SQL database
to an alternate server from a centralized restore
no scripting is required, which reduces database admins' workload.
And no need to install SQL Server Management Studio
on each SQL host.
SQL Centralized Restore is capable to restore simple and multiple databases
backed up by SQL virtual machine direct protection policy
to SQL servers running in VMware.
Also it is capable of restoring backup virtual machine images
or files from virtual machine image backup like mdf and ldf files
as well as the capability to restore
to virtual machines not even a part of any policy.
Please note that we can backup tail log in single-database restore
but we can't restore it in the case of multiple-database restore.
We have two restore destinations.
Restore to the original database
which could be used when SQL virtual machine is protected
by PowerProtect Data Manager Virtual Machine App aware policy
and it is used for operational restore and disaster recovery.
And the other option is to restore to alternate database.
It is used for DEV Test refresh and restore rehearsal.
We have three options from which to choose the database file location.
The first one is to restore to the original file path and name
where the file system paths must exist and the file names must not be in use.
Secondly, restore to the SQL instance defaults location.
And the third one is to restore to custom location
where user can specify one path for data files, one path for log files.
Of course, file system paths must exist.
This will be discussed further in the demo.
Instead of going to the client and installing the Microsoft application agent
now you can install it
from the PowerProtect Data Manager graphical user interface
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 PowerProtect Data Manager
make sure that you set credentials before installing the agent
to avoid credentials error.
We have some limitations on the current version
that SQL Centralized Restore is limited to database-level restore
and we will add table-level restore and instance in the next releases.
And currently, there is no support for Quick Recovery
in PowerProtect Data Manager version 19.6.
Let's have a quick demo to have a detailed view
about the SQL Centralized Restore new feature
in PowerProtect Data Manager version 19.6.
Here is a backup already created for a SQL virtual machine
that we will apply SQL Centralized Restore on.
Start SQL Centralized Restore by going to the "Recovery" tab
and for the first time, we will see a version 19.6 SQL option.
Click on "Restore" and check for a single database restore
so we can select a full backup to restore.
Also, we can use the "point in time" option.
We have the option to select destination host
SQL instance and database.
I will choose this host.
And this instance.
And then we'll proceed with selecting from the file location options
either the first one to restore to the same location
where it has been backed up,
or second option to restore to the location
where SQL configurations had been done
or the third option, which will restore to a specified location
for the database files.
Then click "Next."
Select "Options," you can overwrite database or tail log
also you can enable debug log and we can change the recovery state.
Restore with recovery means
that the database will be in an operational mode.
Restore with no recovery means the database will be in maintenance mode.
The last step is to show restore configuration summary.
The second scenario is restoring multiple databases, not a single database.
In this case, we have a limitation that we cannot choose the backup file
we will have to use the latest available copy.
Then click "Next" to select destination
where you can choose the host and the SQL instance.
We have the same set of options for the file location selection.
And we have the same options except the option to enable the tail log backup.
Then we can click on "Next."
Then "Restore" and check the restore progress from the "Jobs" window
as well as filtering a job type.
In PowerProtect Data Manager version 19.6
we have a good feature when we go to "Infrastructure."
Virtual Machine Assets
which is the ability to select the Windows virtual machine
that hosts the SQL virtual machine and apply more options on it.
When adding this Windows virtual machine that hosts the SQL virtual machine
it will create assets or will turn it
into a SQL database as the list shows here.
The good new feature is that we can install the agent manually
from the PowerProtect Data Manager instead of logging in to the virtual machine
and installing it, by choosing the virtual machine
then click on "More Actions," then choose "Install Agent."
However, the first time you will get this error
because you haven't set the credentials for this particular virtual machine.
So, we need to add credentials by clicking on "More Actions"
then to set credentials, then to save it.
Now, we can click again on "More Actions" and select "Install Agent"
then install it.
The agent will be installed successfully without any errors.
Thank you for watching.