Backup of Sharepoint 2010 using Data Protection Manager 2010
Posted on 2010-09-22
I could REALLY use help with this, I've tried everything I could possibly think of.
-Sharepoint 2010 running on Windows Server 2008 x64.
-Backend database for Sharepoint is SQL 2008 R2, running on remote server - Windows Storage Server 2008 x64
-Data Protection Manager 2010 running on Windows Server 2008 x64
I'm unable to configure a protection group on DPM to protect sharepoint. When I try to create a protection group I get the list of servers with agents installed. I expand the WFE server and am presented with All Shares, All Volumes, SharePoint and System Protection (which is normal). If I expand SharePoint, I can see another little sharepoint logo with no service name - it SHOULD say my service name there. If I try to 'check' it for backup anyway, I get the following error message:
DPM cannot protect this SharePoint farm as it cannot detect the configuration of the dependent SQL databases. (ID: 32008)
1) Ensure that the SharePoint VSS writer is reporting contnet databases on the front-end web server.
2) Verify that the SQL server VSS writer is enabled and running in a healthy state on all the back-end SQL Server machines.
3) Verify if some of the databases that are part of this SharePoint farm are already being protected by DPM. To protect the Sharepoint farm, remove these databases from protection and delete their existing recovery points.
If I try to expand the back-end SQL server for protection I get the following message:
Details - DPM is unable to enumerate \\<server>\<SQL Instance> on comptuer <server> (ID: 3055)
Recommended action - Please ensure that \\<server>\<SQL Instance> is accessible to protection agent.
BUT - when I close that message, I'm able to expand "All SQL Servers" and select any database for backup - including the WSS_Content database and the configuration database.
I have run 'configuresharepoint.exe' successfully on the WFE and have used the -ResolveAllSQLAliases parameter. All of the VSS writers are enabled, running and are in a healthy state. I can open SQL Management studio on the WFE, DPM Server and the SQL Server and access the SQL database without an issue.
I have also found that if I try to run SQLCMD on the SQL server, I recieve the following message:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server .
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a conneciton to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
SQL is configured to allow remote access and Shared Memory, TCP and Named Pipes are all enabled.
Oh, I've also:
- Run stsadm -o registerwsswriter
- Had file shares protected on the SQL Server. I have removed all protection of EVERYTHING on the SQL server and have even uninstalled the agent and reinstalled the agent, rebooting after each.
- Heard there could be an issues with some search services on the WFE. I checked them all, they're all running and can be restarted (they really exist)
- Checked all of the databases referenced by SharePoint and checked in SQL to ensure that all the databases do indeed exist.
I'm very stuck at this point and desperate for a solution. I know it's a tough one dealing with 3 different products, but can provide some assistance?