Tag Archives: DPM

Fixed: DPM could not enumerate sql server instances using windows management instrumentation

Problem

We are using DPM 2012 to backup our SharePoint 2010 farm using the SharePoint connector in DPM (not SQL backups). I ran the configuresharepoint.exe -enablesharepointprotection followed by configuresharepoint.exe -resolveallsqlaliases (we are using SQL aliases) on one of our Web Front End Servers as required. I then verified that the SharePoint VSS Writer service was Started and running under the account I had specified using configuresharepoint.exe.

I then proceeded to add the server to our SharePoint Protection Group. When I clicked on server to select the SharePoint farm, DPM threw up the following error:

DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer dbserver.example.com

We are running Windows Server 2008 R2 and SQL Server 2008 R2 as our database server.

Solution

In order to fix the error:

  1. Login to your database server
  2. Open Command Prompt and browse to C:\Program Files (x86)\Microsoft SQL Server\100\Shared
  3. Run the command: mofcomp sqlmgmproviderxpsp2up.mof

You should see the following message:

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!

Now go back to your DPM server and try to add your SharePoint farm. The error should no longer appear.

 

Comments ( 2 )

Data Protection Manager 2012 incompatible with SharePoint 2010 + SQL Server 2005

Problem

When you try to back up a SharePoint 2010 farm running SQL Server 2005 with DPM 2012. DPM is unable to backup the farm and consistently reports that the ‘Replica is inconsistent’.

Symptoms of the problem:

DPM Agent logs on the SharePoint WFE (C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\WssCmdletsWrapperCurr.errlog)

2.810 31 WssSqlAliasHelper.cs(375)   NORMAL Getting SPDatabase for [databaseName: sp_content_metahub], [instanceName: sqlserver]
1934 241C 11/25 04:06:02.810 31 WssSqlAliasHelper.cs(406)   NORMAL Found corresponding SPDatabase object
1934 241C 11/25 04:06:02.810 31 WssDatabaseHelper.cs(255)   NORMAL Getting the logical path for [fullInstanceName sqlserver],[SpDatabase.Name sp_content_metahub]
1934 241C 11/25 04:06:02.825 31 WssDatabaseHelper.cs(308)   NORMAL Database does not exist or is not mirrored
1934 241C 11/25 04:06:02.825 31 WssDatabaseHelper.cs(272)   NORMAL returning [sqlLogicalPath sqlserver]
1934 241C 11/25 04:06:03.247 31 WssSqlAliasHelper.cs(179)   NORMAL Unable to get the server name for the [SqlAlias: sqlserver]
1934 241C 11/25 04:06:03.247 31 WssSqlAliasHelper.cs(375)   NORMAL Getting SPDatabase for [databaseName: SP_CONTENT_INTRANET], [instanceName: sqlserver]
1934 241C 11/25 04:06:03.247 31 WssSqlAliasHelper.cs(406)   NORMAL Found corresponding SPDatabase object
1934 241C 11/25 04:06:03.247 31 WssDatabaseHelper.cs(255)   NORMAL Getting the logical path for [fullInstanceName sqlserver],[SpDatabase.Name SP_CONTENT_INTRANET]
1934 241C 11/25 04:06:03.263 31 WssDatabaseHelper.cs(308)   NORMAL Database does not exist or is not mirrored
1934 241C 11/25 04:06:03.263 31 WssDatabaseHelper.cs(272)   NORMAL returning [sqlLogicalPath sqlserver]
1934 241C 11/25 04:06:03.685 31 WssSqlAliasHelper.cs(179)   NORMAL Unable to get the server name for the [SqlAlias: sqlserver]

Application log on SQL Server

Source:        SQLWRITER
Date:          24/11/2012 1:39:52 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sql1.domain.com
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 5198
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: The path specified by "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4429\Microsoft SQL Server\Data\Microsoft SharePoint\SP_Content_Mysite.mdf" is a UNC path. UNC path is not supported in failover clustered enviornment.

It looks like the agent is having trouble getting the correct path to the database and this can be referenced in the server logs on the SQL server. The DPM agent is trying to use a UNC path to locate the database but apparently this is not supported in a clustered environment.

Solution

DPM 2012 is not compatible with SharePoint 2010 and SQL Server 2005 when running SharePoint backups through a DPM agent on a SharePoint Web front end. This problem has been confirmed by Microsoft and is due to the way DPM 2012 backs up the SharePoint farm. It takes auto-recoverable snapshots to allow for optimized SharePoint recoveries but auto-recoverable snapshots are not supported in SQL Server 2005.

They also confirmed that it is unlikely that a hotfix will be released in the near future to fix the problem.

Unfortunately, there is no solution to this problem as it appears that SharePoint backups were never considered in DPM 2012 when running on SQL Server 2005. The proposed work-arounds from Microsoft are:

  1. Use DPM 2010 instead to back up the SharePoint farm.
  2. Upgrade to SQL Server 2008 or later.
  3. Don’t use Clustering.
Comments ( 0 )