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...

Providing the following information when creating a Sharepoint case will not only help the TSE narrow down the issue, but will help resolving your case faster and more efficient.  The following information will help the TSE outline an action plan before the first call back and WebEx.

1) Environment Information

Master Server Name:   
OS :
NBU Version:

Media Server Name:
OS:
NBU Version :

SharePoint Front Web Server Name:
OS:
NBU Version
SharePoint version :
For SharePoint 2010, please confirm service pack.
To check Service pack, From the SharePoint Admin console -> upgrade and patch management -> check product and patch installation status
If you are running on service pack 1, you must be at NBU 7.1.0.4 or higher
This must be done on ALL nodes in the farm.

SQL Server ( SharePoint back end) Name:
OS...

Providing the following information when creating an exchange case will not only help the TSE narrow down the issue, but will help resolving your case faster and more efficient.  The following information will help the TSE outline an action plan before the first call back and WebEx.

If you are using GRT with exchange, be sure to check out : https://www-secure.symantec.com/connect/blogs/what-information-and-logs-include-when-creating-grt-exchange-case-support

1) Environment Information

Master Server Name:   
OS :
NBU Version:

Media Server Name:
OS:
NBU Version :

Exchange Server  Name:
OS:
NBU Version :
Exchange Version:

If this is a cluster or 2010 DAG please include the following :

Cluster / DAG NAME:
Node Name :
Node Name:
Node Name

If this is exchange 2007 or 2010

CAS server Name :
OS...

Well , here is my deduplication story with NBU 7…..

Be gentle, not good at compositions but had to Blog it (not used  to it either) just in case anyone has the same issues.

These are personal experiences and may not work for you.May give you ideas though

The plan of the new setup was that one those two media srv’s  -the first- receives the data from 385 wan clients and then optimized dudeped them to the second “disaster” media server.Later on we will merge one old nbu 6.0 with the newer one

The files were mostly user files (docs , pst’s, some images and exports of SQLs)

The initial hardware consisted of  NBU 7.01 master server (ESX VM windows 2003 64Bit/2 cores/4GB mem/enough storage).

We had two media servers (must was ibm 3640 x64 , 8Gbyte ram ) with MSDP pools  on some 2TB volumes (sata disks, svc managed , most likely stripe across one or more array ) .The tape library was...