How to fix DPM Auto-Protection failures of SQL servers

For longer than I care to admit, my DPM server has had the same error every night about an auto-protection failure on one of my SQL servers. I've looked into it before but never came away with anything useful until recently. I've finally found information on how to fix this annoying issue.

The Advanced Information link in the error will tell you to make sure WMI is in a good state on the machine. The error itself isn't very descriptive. It'll look something like "DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer $serverFQDN."

In my situation, the server's OS is Server 2008 R2 and the SQL Server version was also 2008 R2. At this point, I don't believe that this solution wouldn't work on a different version SQL Server hosted on a different Server OS version.
  1. Open a CMD window as Administrator. 
  2. Change directory to  C:\Program Files (x86)\Microsoft SQL Server\100\Shared
  3. Run the command: mofcomp sqlmgmproviderxpsp2up.mof
You should see something like: Microsoft (R) MOF Compiler Version 6.2.9200.16398
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: sqlmgmproviderxpsp2up.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

If you've been having this issue every night like I have, you can inactivate the alert and rest easy. You can test to see if it's fixed by modifying the Protection Group and try expanding the culprit server. Where you once would see an error message pop up about DPM being unable to enumerate the SQL server instances on that server, there's now no issue. This fix required no reboot of the afflicted server so no interruption to database services should occur.

I hope this helped. If not, may the wind always be at your back and your Google searches fruitful. 

Comments

Popular posts from this blog

Installing CentOS 7 on a Raspberry Pi 3

Modifying the Zebra F-701 & F-402 pens