SharePoint Node not visible for browsing in NetBackup BAR GUI.

Some days back I came across another scenario where even after providing the correct credentials in host properties of all the clients in the SharePoint farm and adding all the required privileges to the account running backup (as defined in my previous post), we still do not see the Microsoft SharePoint Node when we try to browse for backup and subsequently the backup fails with status 2.

We can see that Spswrapper.exe running in the task manager but the SharePoint node is still not visible. The reason that i found was that one of my Shared Service Applications Databases was in offline state and hence the user account was not able to talk to the database and we were getting exception during GetTopology.

The error in the spswrapper.log was something like this.

“Message : Cannot open database “WebAnalyticsServiceApplication_StagingDB_b12b91fd-73ef-4134-a04b-c57033909d49” requested by the login. The login failed.

Login failed for user ‘Domain\userAccount’.”

This is indicative of some issue with WebAnalyticsService Database. Go to the SQL Backend and launch SQL Management Studio and see if the database is down or the user account has permission to that database. Resolving this will let us see the SharePoint node in NetBackup and backup shall proceed just fine.

 

SharePoint Backup using NetBackup SharePoint Agent fails with status 2.

SharePoint Backup using NetBackup SharePoint Agent fails with status 2.

The SharePoint backup fails with status 2 mainly because of configuration issues. There is a checklist that we should adhere to while doing a SharePoint backup.

1. The NetBackup cilent service is being started by a domain account

2. The account running backup should have the following privileges.
–  “Replace a process level token”
–  “Debug programs”
–  “Log on as a Service”
–  “Allow to logon Locally”

These are set via (administrator tools – Local security policy – Local policies – User rights assignment)
This needs to be done for all servers in the SharePoint farm, including SQL back end.

3. The account should be Local administrator rights on all servers in the SharePoint farm.

4. .Net Framework 3.5 at minimum for SharePoint 2010 and  .Net Framework 2.0 for SharePoint 2007.

5. The client in the policy should be the one running Central Admin Service in the SharePoint Farm.

6. In the host properties of master server, go to windows clients->SharePoint and add the SharePoint Farm Admin account there.
This account is used to launch SPSWrapper.exe process which talks to SharePoint.

7. If you are running windows server 2008, UAC (User Access Control) should be disabled.

8. In Internet Explorer options disable “Check for Publisher Certificate Revocation” and “Check for Server Certificate Revocation”.

You can also refer to the following tech note by Symantec.

http://www.symantec.com/business/support/index?page=content&id=TECH146218