Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Netbackup Sharepoint GRT Backup FTL - snapshot preparation failed - No SharePoint objects to backup., status 72

Created: 18 Oct 2012 | 11 comments
jeppe_ols's picture

I have the setup of the front-end and the back-end servers according the Sharepoint Admin Guide but get errors.

 

Log below

 

10/18/2012 1:39:32 PM - Info nbjm(pid=15323) starting backup job (jobid=462) for client host, policy e42a0138-sharepoint-18, schedule Full 
10/18/2012 1:39:32 PM - estimated 0 Kbytes needed
10/18/2012 1:39:32 PM - begin Parent Job
10/18/2012 1:39:32 PM - begin Sharepoint Granular Snapshot, Step By Condition
Status 0
10/18/2012 1:39:32 PM - end Sharepoint Granular Snapshot, Step By Condition; elapsed time: 00:00:00
10/18/2012 1:39:32 PM - begin Sharepoint Granular Snapshot, Read File List
Status 0
10/18/2012 1:39:32 PM - end Sharepoint Granular Snapshot, Read File List; elapsed time: 00:00:00
10/18/2012 1:39:32 PM - begin Sharepoint Granular Snapshot, Create Snapshot
10/18/2012 1:39:32 PM - started process bpbrm (5776)
10/18/2012 1:39:32 PM - started
10/18/2012 1:39:33 PM - Info bpbrm(pid=5776) host is the host to backup data from    
10/18/2012 1:39:33 PM - Info bpbrm(pid=5776) reading file list from client       
10/18/2012 1:39:33 PM - Info bpbrm(pid=5776) start bpfis on client        
10/18/2012 1:39:33 PM - Info bpbrm(pid=5776) Starting create snapshot processing        
10/18/2012 1:39:35 PM - Info bpfis(pid=3480) Backup started          
10/18/2012 1:39:37 PM - Critical bpbrm(pid=5776) from client host: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72
10/18/2012 1:39:37 PM - Info bpfis(pid=3480) done. status: 72         
10/18/2012 1:39:37 PM - end Sharepoint Granular Snapshot, Create Snapshot; elapsed time: 00:00:05
10/18/2012 1:39:37 PM - Info bpfis(pid=0) done. status: 72: the client type is incorrect in the configuration database
10/18/2012 1:39:37 PM - end writing
Status 72
10/18/2012 1:39:37 PM - end Parent Job; elapsed time: 00:00:05
10/18/2012 1:39:37 PM - begin Sharepoint Granular Snapshot, Stop On Error
Status 0
10/18/2012 1:39:37 PM - end Sharepoint Granular Snapshot, Stop On Error; elapsed time: 00:00:00
10/18/2012 1:39:37 PM - begin Sharepoint Granular Snapshot, Delete Snapshot
10/18/2012 1:39:37 PM - started process bpbrm (5789)
10/18/2012 1:39:38 PM - Info bpbrm(pid=5789) Starting delete snapshot processing        
10/18/2012 1:39:38 PM - Info bpfis(pid=0) Snapshot will not be deleted       
10/18/2012 1:39:40 PM - Info bpfis(pid=616) Backup started          
10/18/2012 1:39:40 PM - Critical bpbrm(pid=5789) from client host: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.host_1350560372.1.0   
10/18/2012 1:39:41 PM - Info bpfis(pid=616) done. status: 1542         
10/18/2012 1:39:41 PM - end Sharepoint Granular Snapshot, Delete Snapshot; elapsed time: 00:00:04
10/18/2012 1:39:41 PM - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
10/18/2012 1:39:41 PM - end writing
Status 1542
10/18/2012 1:39:41 PM - end operation
Status 72
10/18/2012 1:39:41 PM - end operation
the client type is incorrect in the configuration database(72)

 

 

Comments 11 CommentsJump to latest comment

Marianne's picture

status: 72: the client type is incorrect in the configuration database

NetBackup status code: 72

Message: the client type is incorrect in the configuration database
Explanation: The policy type attribute in the policy configuration indicates that
the client is one type, but the installed software is for another type.
Recommended Action: Verify that the policy type attribute for the policy is correct. 
 
 
Please show us your policy config.
On master server, run this command from cmd and post output here:
bppllist <policy-name> -U
(command is netbackup\bin\admincmd)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jeppe_ols's picture

 

This is the output-

e42a0138:/usr/openv/netbackup/bin/admincmd # bppllist -U
Policy:            e42a0138-sharepoint-18

 

 

jeppe_ols's picture

 

e42a0138:/usr/openv/netbackup/bin/admincmd # bppllist e42a0138-sharepoint-18 -U
------------------------------------------------------------

Policy Name:       e42a0138-sharepoint-18

  Policy Type:         MS-SharePoint
  Active:              no
  Effective date:      10/18/2012 10:27:44
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           slp_e42a0138_e42a0139_6m
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  yes
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   e42a0127.lfad.lfnet.se

  Include:  Microsoft SharePoint Resources:\AllWebs

  Schedule:              Full
    Type:                Automatic Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Calendar sched: Enabled
      Allowed to retry after run day
      Saturday, Week 1
      Saturday, Week 2
      Saturday, Week 3
      Saturday, Week 4
      Saturday, Week 5
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     02:00:00
          Monday     18:00:00  -->  Tuesday    02:00:00
          Tuesday    18:00:00  -->  Wednesday  02:00:00
          Wednesday  18:00:00  -->  Thursday   02:00:00
          Thursday   18:00:00  -->  Friday     02:00:00
          Friday     18:00:00  -->  Saturday   02:00:00
          Saturday   18:00:00  -->  Sunday     02:00:00

  Schedule:              Differential-Inc
    Type:                Differential Incremental Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Calendar sched: Enabled
      Monday, Week 1
      Tuesday, Week 1
      Wednesday, Week 1
      Thursday, Week 1
      Friday, Week 1
      Monday, Week 2
      Tuesday, Week 2
      Wednesday, Week 2
      Thursday, Week 2
      Friday, Week 2
      Monday, Week 3
      Tuesday, Week 3
      Wednesday, Week 3
      Thursday, Week 3
      Friday, Week 3
      Monday, Week 4
      Tuesday, Week 4
      Wednesday, Week 4
      Thursday, Week 4
      Friday, Week 4
      Monday, Week 5
      Tuesday, Week 5
      Wednesday, Week 5
      Thursday, Week 5
      Friday, Week 5
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     02:00:00
          Monday     18:00:00  -->  Tuesday    02:00:00
          Tuesday    18:00:00  -->  Wednesday  02:00:00
          Wednesday  18:00:00  -->  Thursday   02:00:00
          Thursday   18:00:00  -->  Friday     02:00:00
          Friday     18:00:00  -->  Saturday   02:00:00
          Saturday   18:00:00  -->  Sunday     02:00:00

Marianne's picture

See p. 67 of NBU for Sharepoint manual:

 

Allow multiple data streams : For SharePoint policies, do not select this option. SharePoint policies do not support multiple data streams.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Marianne's picture

Do you Activate and Deactivate the policy before and after each backup attempt?

Active:              no

Backup Type in the first schedule also does not seem right. 

If I look on p.69, supported backup types are:
Full Backup
User Backup

Cumulative Incremental backup:  This type of backup is not supported for SharePoint Server.
Differential Incremental backup
 
Automatic Backup (the type of your 1st schedule) does not appear in the list.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jeppe_ols's picture

Yes I deactived the policy.

 

I have updated the policy with your updates and I still get the same error.

 

 

captain jack sparrow's picture

Deactivate this policy

and create new from scratch. Sometimes policy gives issues despite everything LOOKS Ok

 Cheers !!!

CJS

 

Gaurav Kaushal's picture

Hi I think the issue is that you are taking granular backup with Differential Incremetal Schedule.

  Granular Restore Info:  yes
   :
  Schedule:              Differential-Inc
  Type:                Differential Incremental Backup

Does this also happen for a Full GRT backup?

Thanks and Regards.
~gk

Nils K. Schøyen's picture

I'm facing the same problem... NBU 7.5.0.4 on server & client. Win 2008R2 and Sharepoint 2010.

FULL backup with Enable granular recovery checked.

30.jan.2013 13:37:30 - begin Sharepoint Granular Snapshot: Create Snapshot
30.jan.2013 13:37:31 - started process bpbrm (pid=7808)
30.jan.2013 13:38:14 - Info bpbrm (pid=7808) SRV-SQL is the host to backup data from
30.jan.2013 13:38:14 - Info bpbrm (pid=7808) reading file list from client
30.jan.2013 13:38:14 - Info bpbrm (pid=7808) start bpfis on client
30.jan.2013 13:38:14 - Info bpbrm (pid=7808) Starting create snapshot processing
30.jan.2013 13:38:35 - Info bpfis (pid=28820) Backup started
30.jan.2013 13:38:38 - Critical bpbrm (pid=7808) from client SRV-SQL: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72
30.jan.2013 13:38:38 - Critical bpbrm (pid=7808) from client SRV-SQL: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72
30.jan.2013 13:38:38 - Critical bpbrm (pid=7808) from client SRV-SQL: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72
30.jan.2013 13:38:38 - Info bpfis (pid=28820) done. status: 72
30.jan.2013 13:38:38 - end Sharepoint Granular Snapshot: Create Snapshot; elapsed time 0:01:08
30.jan.2013 13:38:38 - Info bpfis (pid=0) done. status: 72: the client type is incorrect in the configuration database

 

 

 

# bppllist MS-SHAREPOINT -U
------------------------------------------------------------

Policy Name:       MS-SHAREPOINT

  Policy Type:         MS-SharePoint
  Active:              yes
  Effective date:      06/28/2012 08:09:15
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         BACKUP
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  yes
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   srv-sp

  Include:  Microsoft SharePoint Resources:\
            Microsoft SharePoint Resources:\AllWebs

  Schedule:              FULL
    Type:                Automatic Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Friday     00:00:00  -->  Monday     00:00:00
 

 

Ideas anyone?

 

BR,

 

Nils

 

mikent's picture

@Jeppe_ols,

Please verify the following:

- Make sure you setup the domain\user_name and pasword on each client (frontend/backend) from Client host properties in Windows Client -> SharePoint

- Make sure you setup Distribute Application Restore Mapping as follow:

  frontend      backend

  frontend      clusternode1

  frontend      clusternode2

  frontend      cluster-vip-name

You need to map both FQNs and shortname

- Make sure Netbackup Client service and Netbackup Legacy Client Service is configured with domain\user_name and pasword

- Make sure File server role (NFS Client) is installed on both system (frontend/backup) and also on your media server

 

./nathan

 

BR,

Nathan Mike

Senior System Engineer

LPI1-C and CLA-11 Novell Certified Linux Administrator

+320473954944