Error ID: 32511
Applies To: System Center Data Protection Manager 2010
Event ID 32511 — Data Protection Manager
To provide feedback about the types of information that would help you resolve this error, please contact the DPM Documentation Team.
Details
Product |
Data Protection Manager |
ID |
32511 |
Source |
|
Version |
3.0 |
Symbolic Name |
|
Message |
One or more databases could not be protected automatically because auto-protection failed. If the databases belong to a SharePoint farm, then the farm recovery points will continue to get created without these databases. |
User Action for SQL Server
The effected Windows 2008 SQL Server may be missing WMI classes. This prevents DPM 2010 from being able to query WMI for ServerSettings so we can auto-protect new SQL databases created in instances on that server.
Do the following steps to verify that this is the issue.
Procedure to verify if DPM is unable to query WMI
From the Run dialog box, start Windows Management Instrumentation Tester (wbemtest).
Click Connect.
Type the namespace as root\Microsoft\SqlServer\ComputerManagement10.
Click Query.
Run the following query SELECT * FROM ServerSettings.
If this fails on the affected protected server both remotely and locally with the error number 0x80041010 and Description: Invalid Class.
To resolve this issue we need to run mofcomp.exe to re-compile a SQL .mof template to re-add the classes to WMI.
For SQL 2008 or SQL 2008 R2, from an administrative command prompt run the following command: C:\>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
User Action – For Auto-protection
To fix auto-protection, resolve the errors and run AutoProtectInstances.ps1 from DPM Management Shell.
User Action – For SharePoint databases
If the databases belong to a SharePoint farm then go to the Protection tab and run Modify Protection for the protection group containing the SharePoint farm. In the wizard, expand the SharePoint front-end web server node on the Select Group Members page and complete the wizard. Then run consistency check on the SharePoint farm.