SharePoint backups fail with Status Code 71

Problem

The SharePoint Farms key on the Front End web and SQL backend servers is either missing or incorrect.

Cause

The Farms key or values are not created during the first SharePoint backup most commonly caused by permission issues.

Solution

1. Log into the Frontend Web Server (FEWS) that you run Central Admin using the account used to backup Sharepoint in NetBackup.

2. Open a command prompt and run the following (replace <clientname> with the name of your FEWS used in the backup policy):

<install_path>\veritas\netbackup\bin\bpresolver.exe query -c <clientname> -ct 8 -init_beds "Microsoft SharePoint Resources:\*"

If FEWS is Windows 2008 or later, you may have to right-click on the command prompt and choose Run as Administrator when running the command.

**To verify the command properly published the registry key, open your registry on your Frontend and SQL servers and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\SharePoint\Farms.
You should have a String Value with the Name set to the <SQL server Name>\<Instance Name, if applicable>\<Config Database Name> and the Data is the <Frontend Web Server Name> in parenthesis (). If you have multiple FEWS they will all be listed and separated by commas. If you have multiple Farms using the same SQL server, the SQL server should have multiple entries for each Farm (see Figure for example).

Note: If the <SQL server Name>\<Instance Name, if applicable>\<Config Database Name> key is not present on the Front-end server, then manually copy this key from the database node to the Front-end server.

3. Re-run the backup. If the backup fails again, review the permissions required to backup the SharePoint environment. Adjust any permissions that do not meet NetBackup minimum requirements