Forum Discussion

3 Replies

  • In the resolver log you get:

    10:54:19.354 [10820.4668] <16> bpresolver_main(): bpresolver could not resolve the passed directive set.

    This could be caused by a few things - most likely permissions issues (NetBackup client service / netbackup legacy network service)

    Take a look at the solution in this thread for a user that faced a similar error as he nicely outlines everything that was required:

    Hope this helps

  • A status 2 is either permissions or a known issue in NBU 7.5.x.

    Go thorugh the following Sharepoint confguration check list.  If you have confirmed everything and still getting a status 2, patch all servers in the farm to which contains the fix.


    Sharepoint configuration check list :

    1.  NetBackup Client version should be the same as the Master Server, and should be installed on all servers in the SharePoint farm, even SQL backend.   For SharePoint 2010 SP 1 or GRT you must be on or higher.


    2.  The NetBackup Client service should be started by a Domain Account.  (MUST be in format“domain\user”)

          (additional services are needed for GRT, please see GRT Section)


    3.  The domain account in Step 2 must have the following privileges and permissions:

      a.  "Replace a process level token" and "Debug Programs" (Administrator Tools - Local Security Policy - Local Policies - User Rights Assignment) for all servers in the SharePoint farm, backend SQL included.

      b.  Local Administrator rights on all servers in the SharePoint farm.

      c.  Within SharePoint Central Administrator, the Domain Account is specified as a SharePoint Farm


      d.  The System Administrator role on the SQL Server for the SharePoint databases.


    4.  At a minimum, you must have at least .NET Framework 3.5 installed on all servers in the SharePoint Farm.


    5. Ports 13782 (bpcd) and 13724 (vnetd) between all Servers in the SharePoint farm and between the Media Server and Master. The ports must be opened bi-directionally.


    6.  Under Host Properties - Clients on the Master server, under the Windows Client - SharePoint section, make sure that the Domain Account from step 2 is specified there, with the syntax as follows:  DOMAIN\Username  (not just the Username).  Do this for every client/server member of the SharePoint farm.


    7.  Create a "beds" directory under <install path>\NetBackup\logs\ on each of the SharePoint farm servers (SQL included)


    8.  Under Host Properties - Master Server, there is a Distributed Applications section.  For the first field, put in the name of the Front end server in the SharePoint policy, and in the 2nd field, the name of the SQL server hosting the SharePoint databases.


    9. From the Front End web server specified in the policy, Right click on the NetBackup Backup, Archive, and Restore (BAR) GUI and  select "Run as Administrator" .  You should be able to see Microsoft SharePoint Resources objects there. If you do not see objects, check the farm topology and make sure you have not missed any of the steps on that server.


    7.  In the first policy (non-granular), the client selection is a Front End Web server for the SharePoint portal.  The backup selection for your first policy should be: "Microsoft SharePoint Resources:\"


    8. Make sure you do not have the "Enable Granular Recovery" box checked.


    9.  In the client selection, the frontend server should be specified.


    10.  You may now test you SharePoint Backup.


    Addition steps for SharePoint  GRT


    For setting up GRT backups of SharePoint, the Media server (if it is a Windows box) and the SQL server need to be running Windows 2003 R2 (or greater) with the following hot fix applied:


    - In addition The Media server doing the backup/restore operations MUST have NFS Server components installed and running, as outlined in the SharePoint Administration Guide for NetBackup.


    - The Frontend and Backend  servers must have Client for NFS


    See Tech Note for details on NFS -


    -The backups can only be Full backups, and must be taken to a disk storage unit, not tape.  Be sure that the policy reflects this as well as having the "Enable Granular Recovery" box checked.  Please see the following tech note which lists what type of disk storage types are support for GRT - 


    -  Since GRT only supports Disk, backups can be staged off to tape media at a later time, but the initial backup must be to disk.  If you stage the backup image to tape, you must duplicate the image back to disk before a restore can be attempted.  For best performance, Symantec recommends that the disk storage unit being used as a target for GRT backups be located locally on the media server as direct SCSI or SAN attached disks. The use of disk storage units that write to network based file systems ( NFS or CIFS ) is not recommended. Performance degradation or read errors may result when the media server presents the backup image via NFS to the client or proxy client if the NFS exported image itself is residing on a network file system ( NFS or CIFS ).


     - In addition to the Netbackup Client service, the Netbackup Legacy  Client Service  and Legacy Network services should be service should be started by a Domain Account.  Please refer to #2 and #3 above.


     - For GRT Restores, you must run the BAR from the Front end server.


    - In addition to 13782 (bpcd) , 13724 (vnetd)  the 111 ( port map) ,  and 7394 (nbfsd )  need to be open.


    - NFS comunnication can be tested by using

       Until these tests compelte suucessful, the backup will not compelte.

  • What's your NBU version & patch level? 

    Note that it should all be consistent across your master, media server, web frontend & SQL backend host.

    Take a look at this technote as well: