How to Solve DPM Scheduled Backup Recovery Point Jobs? #SysCtr #SCDPM #DPM

3 Min. Read


System Center Data Protection Manager (SCDPM) is well recognized in the Industry for protection of Microsoft workloads. It protects key Microsoft workloads such as SQL, SharePoint and Exchange as well as virtual machines running on Hyper-V.

As you probably have heard the recent announcement by Microsoft, the DPM team just released SC DPM 2012 R2 UR11 that protect VMware VM backup. This will allow us to have a single backup solution to protected heterogeneous and mixed IT environment. Here are major features of VMware VM Backup. Here are the few highlights of VMware VM backup:

  • Agentless backup
  • Backup at vCenter or ESXi level
  • Backup VMware VM folders
  • Ability to do ILR
  • Protect large data center using DPM Scale Out
  • Backup to Disk/Cloud

You can read about this announcement here: Announcing VMware VM Backup using System Center Data Protection Manager.

I recently came across a strange issue where backup recovery point jobs were not getting executed but the protection status of respective data sources continue to appear as Green/OK in the DPM console as shown in the following screenshot:


Since the protection status for these data sources are displayed as Green/OK, I thought that everything is going well when actually it is not! I noticed that DPM has created only one recovery point and missed the scheduled backup job as shown in the next screenshot:


Fix DPM Scheduled Backup Jobs

When protection groups are created, DPM creates jobs for each data source in SQL Server (DPM Instance) to run the backup (e.g. incremental syncs, express full, etc.) for each data source and other maintenance jobs.

If for some reason the job fails to run, the DPM engine will not be invoked and thus the backup job will not be executed. Since SQL failed to run the command, DPM will not know about this failure and will continue to display the protection status of the data sources as Green/OK which is confusing.

In order to resolve this particular issue, open SQL Server Management Studio and connect to the SQL instance used for the DPMDB database. Expand SQL Server Agent and then expand Jobs.


Check the SQL Server Agent if it’s started, in my case it was disabled.

Right click and click on Start to start the SQL Server Agent.


After the SQL Server Agent is started, you may check the Jobs status.


The GUIDs that you see in the list under Jobs as shown in the screenshot below are Schedule ID for each individual backup job. There are chances that the scheduled jobs are disabled in SQL. In my case, the Jobs are disabled. To check and enable the jobs follow the steps below:


Right-click on the disabled job, and click Enable.

This is ok if you have a fewer jobs, but what if you have a large number of protection groups and many SQL jobs as I have…

PowerShell to the rescue!

The complete script to enable the SQL Server Agent jobs is shown below:

# loading the appropriate .NET assemblies used by SQL Server SMO
 [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | out-null

# Specify DPM SQL Instance
 $serverInstance = New-Object ("Microsoft.SqlServer.Management.Smo.Server") "localhost\MSDPM2012"

# Create an instance of the Jobs object collection from the JobServer property that are disabled
foreach ($jobs in ($serverInstance.JobServer.Jobs | Where-Object {$_.IsEnabled -eq $FALSE}))
 # Enable the Job
 $jobs.IsEnabled = $TRUE

Note: Remember to change the Boolean values from FALSE to TRUE and vice versa to enable or disable the SQL Server Agent jobs.

After running above script, all jobs will be enabled as shown in the next screenshot:


You can run now the jobs manually from SQL Server Management Studio and click “Start Job at Step” or wait for DPM to run the next scheduled backup job.

As you can see in the below screenshot, I had only one recovery point on August 17th, and after I enabled SQL jobs on August 25th, DPM continues to execute and create the recovery points successfully!



I hope this post has been useful. And be sure to periodically check the status of recovery point jobs and their availability by reviewing recovery points on the Recovery task area in the DPM console to avoid any surprises!

If you have System Center Operations Manager, you can setup an alert outside of DPM to monitor for SQL Agent Scheduler failures.

Thanks for reading!



Massive Scalability in Windows Server 2016 HyperV #WS2016

Windows Server 2016 and System Center 2016 Now Available! #WS2016 #SysCtr2016


Let me know what you think, or ask a question...

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to Stay in Touch

Never miss out on your favorite posts and our latest announcements!

The content of this website is copyrighted from being plagiarized!

You can copy from the 'Code Blocks' in 'Black' by selecting the Code.

Please send your feedback to the author using this form for any 'Code' you like.

Thank you for visiting!