Solved

Backup of Sharepoint 2010 using Data Protection Manager 2010

Posted on 2010-09-22
3
3,097 Views
Last Modified: 2012-05-10
I could REALLY use help with this, I've tried everything I could possibly think of.

SETUP:
-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

The Problem:
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 [2].
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?

Thanks =)
0
Comment
Question by:mcwaranowicz
  • 2
3 Comments
 

Author Comment

by:mcwaranowicz
ID: 33736166
Update -

I changed the logon account for the SQL service.  I no longer recieve an error message when I expand the SQL server in DPM.  However, I still recieve the same error message when trying to add the WFE Sharepoint Server to a protection group, stating that it cannot detect the configuration of the dependent SQL databases.
0
 
LVL 10

Expert Comment

by:abdulwrite
ID: 33770186
I hope you followed the following steps:
Provide the agent service account required permission in Server Farm
a. Install the SQL Agent in WFE
b. Create the backup account in SQL Server (provide required credentials)
c. Push the agent with required permission.
d. Run the ConfigureSharepoint.exe and complete the required configuration steps.
e. Configure and Protect the SharePoint Farm.

Eventhough you facing the same issue. Remove the agent from SharePoint farm from DPM and follow the steps to re-install and configure.
0
 

Accepted Solution

by:
mcwaranowicz earned 0 total points
ID: 33801755
abdulwrite,  Thanks for the info.  I did follow the steps, and even removed the agent and re-installed it several times.  I finally decided to install an additional WFE on the same server as the backend SQL server and now it works perfectly.  I don't understand why it needed that, but as long as it works I'm happy.
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you looking to recover an email message or a contact you just deleted mistakenly? Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important.
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

948 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now