Let’s create a Protection Policy to back up something. Login to Power Protect Data Manager (PPDM), and navigate to Protection > Protection Policies and click Add.
Give the policy a name and select the type of resource to back up. I will select Virtual Machines and click Next.
Select the type of protection you want.
Crash Consistent: Select this option to capture all of the virtual machine disks at the same time and back up the data to storage targets to create a transactionally-consistent backup for VMWare virtual machines. Use this option for Windows and Linux virtual machines, and for guest operating systems that have applications other than the SQL Server.
Application Aware: Select this option to perform a virtual machine image backup that will create an application-consistent SQL Server backup with transaction log protection and truncation. Enabling virtual machine application aware snapshots also enables self-service recovery of SQL Server data from this backup by using the SQL Server Management Studio and Dell EMC ItemPoint. This option requires vSphere version 6.5 or 6.7 and VMware Tools version 10.1 or later.
Exclusion: Select this option to exclude assets in this group from protection activities and protection rule assignment.
Select your VM’s to add to the Protection Policy and click Next.
We now need to create a schedule for the backup policy. Click Backup.
There’s quite a few choices to make.
I will choose a daily backup with retention of 30 days and a full backup once a week. Below, I click on the ‘i’ with a circle around it to make sure we get a full understanding of what’s going on. Click OK.
We now can review the schedule details.
We could make adjustments if needed, or perhaps make a SLA for the backup. Or, perhaps set a retention lock or change the vNIC to be used for the backup Policy.
If we did create an SLA, it would look like the following screen. But I will cancel out of the SLA and just click Next.
We can select optimization options if we like. Perhaps capacity or Performance is more important. We could also enable swap files, or disable quiesce for file system of the VM. But generally speaking these options in their default state look fine to me. Below, I’ll go into more detail on each option.
Optimize for Performance. This sounds like a great default option. Performance! yes!…
Optimize for Capacity. Perhaps I’m low on storage space on my DDVE and willing to make a trade off from Performance. And honestly, if my job depended on it, I’d rather have a slow back up than no back up. But that’s on me to make sure I’ve planned accordingly.
Exclude swap info. I can’t think of a reason why I’d want to back up swap.
Info on Quiesce System. This option is always a good idea.
Changing the settings back to default as generally speaking that’s best. I want performance, I don’t care about swap, and I want anything in memory to be written to disk or synced to disk. If this was an in-memory database, I would have instead chosen Purpose Type of Application Aware, versus Crash Consistent.
Review all details and if we like it, click Finish. We can always click edit or back to make adjustments.
Since I am backing up VM’s that are not using VMware-tools, I also add the VM root credentials.
I could also install VM-tools and do it that way.
After installing VM-tools, we can see it created the snapshot in VCenter.
We are getting a compression factor of 21 x. in DDVE.
In PPDM, we can also do a restore or view copies.
If I click View Copies, I can do a file level restore versus an entire VM or individual virtual disk (vmdk).
Below is Restore option.
If I click View Copies instead, I have more choices.
From here, we can do a file level restore if desired.
We can restore to the original VM or to somewhere else.