cancel
Showing results for 
Search instead for 
Did you mean: 

NBU 7.6.1 and issue with SharePoint non-GRT backup

Ziggy1941
Level 4
Partner Accredited

We have a MS SharePoint farm consisting of one front end web-server and two back end SQL server. When I try to use non-GRT backup policy job finished with this error:

23.03.2015 16:53:44 - Info nbjm(pid=28216) starting backup job (jobid=1314) for client sharepoint.ussc.ru, policy sharepoint.ussc.ru, schedule Full  
23.03.2015 16:53:44 - Info nbjm(pid=28216) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1314, request id:{412F721C-D153-11E4-9156-7701A4388FFB})  
23.03.2015 16:53:44 - requesting resource dedup_stu_nbu-s2
23.03.2015 16:53:44 - requesting resource nbu-s2.ussc.ru.NBU_CLIENT.MAXJOBS.sharepoint.ussc.ru
23.03.2015 16:53:44 - requesting resource nbu-s2.ussc.ru.NBU_POLICY.MAXJOBS.sharepoint.ussc.ru
23.03.2015 16:53:44 - Info nbrb(pid=28130) Limit has been reached for the logical resource nbu-s2.ussc.ru.NBU_CLIENT.MAXJOBS.sharepoint.ussc.ru    
23.03.2015 16:53:54 - Info bpbrm(pid=13949) sharepoint.ussc.ru is the host to backup data from     
23.03.2015 16:53:54 - Info bpbrm(pid=13949) reading file list for client        
23.03.2015 16:53:54 - granted resource nbu-s2.ussc.ru.NBU_CLIENT.MAXJOBS.sharepoint.ussc.ru
23.03.2015 16:53:54 - granted resource nbu-s2.ussc.ru.NBU_POLICY.MAXJOBS.sharepoint.ussc.ru
23.03.2015 16:53:54 - granted resource MediaID=@aaaag;DiskVolume=PureDiskVolume;DiskPool=dedup_pool1;Path=PureDiskVolume;StorageServer=nbu-s2.ussc.ru;MediaServer=nbu-s2.ussc.ru
23.03.2015 16:53:54 - granted resource dedup_stu_nbu-s2
23.03.2015 16:53:54 - estimated 0 Kbytes needed
23.03.2015 16:53:54 - Info nbjm(pid=28216) started backup (backupid=sharepoint.ussc.ru_1427111633) job for client sharepoint.ussc.ru, policy sharepoint.ussc.ru, schedule Full on storage unit dedup_stu_nbu-s2
23.03.2015 16:53:54 - started process bpbrm (13949)
23.03.2015 16:53:54 - connecting
23.03.2015 16:53:55 - Info bpbrm(pid=13949) starting bpbkar on client         
23.03.2015 16:53:55 - connected; connect time: 0:00:01
23.03.2015 16:53:56 - Info bpbkar(pid=5180) Backup started           
23.03.2015 16:53:56 - Info bpbrm(pid=13949) bptm pid: 13969          
23.03.2015 16:53:56 - Info bpbkar(pid=5180) change time comparison:<disabled>          
23.03.2015 16:53:56 - Info bpbkar(pid=5180) archive bit processing:<enabled>          
23.03.2015 16:53:57 - Info bptm(pid=13969) start            
23.03.2015 16:53:57 - Info bptm(pid=13969) using 262144 data buffer size        
23.03.2015 16:53:57 - Info bptm(pid=13969) using 30 data buffers         
23.03.2015 16:53:57 - Info bptm(pid=13969) start backup           
23.03.2015 16:53:59 - Info bptm(pid=13969) backup child process is pid 13989       
23.03.2015 16:53:59 - begin writing
23.03.2015 18:06:16 - Warning bpbrm(pid=13949) from client sharepoint.ussc.ru: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\Ïîäêëþ÷åíèå ê Project Service Application/Proxy (SQL/90d8556f-94c9-40a7-9e78-95b3652f7783)
23.03.2015 18:06:29 - Error bptm(pid=13989) system call failed - Connection reset by peer (at child.c.1306)   
23.03.2015 18:06:29 - Error bptm(pid=13989) unable to perform read from client socket, connection may have been broken
23.03.2015 18:06:29 - Error bptm(pid=13969) media manager terminated by parent process       

23.03.2015 18:06:34 - Info nbu-s2.ussc.ru(pid=13969) StorageServer=PureDisk:nbu-s2.ussc.ru; Report=PDDO Stats (multi-threaded stream used) for (nbu-s2.ussc.ru): scanned: 88506903 KB, CR sent: 72130318 KB, CR sent over FC: 0 KB, dedup: 18.5%, cache disabled
23.03.2015 18:06:34 - Error bpbrm(pid=13949) could not send server status message       
23.03.2015 18:06:34 - Info bpbkar(pid=5180) done. status: 13: file read failed       
23.03.2015 18:06:34 - end writing; write time: 1:12:35
file read failed (13)

Tell me which way to look for a solution?

11 REPLIES 11

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Can you verify that the database is indeed still available in SQL? It seems like the job started and was writing but then failed?

VoropaevPavel
Level 4
Partner Accredited

Also please confirm database version, SQL 2014 at SP back-end is not yet supported.

Ziggy1941
Level 4
Partner Accredited

May be you are right. I will try to restart job next night...

Ziggy1941
Level 4
Partner Accredited

No, we are using MS SP 2013 and MS SQL 2012...

sdo
Moderator
Moderator
Partner    VIP    Certified

MS SQL 2012 - which patch version?  AAG ?

Ziggy1941
Level 4
Partner Accredited

MS SQL 2012 version - 11.0.3000.0

What is "AAG"?

sdo
Moderator
Moderator
Partner    VIP    Certified

Always-on Availability Group.

Ziggy1941
Level 4
Partner Accredited

No, do not use it..

sdo
Moderator
Moderator
Partner    VIP    Certified

1) Did your re-run 'next night' also fail with same problem - of writing for a while, and then failing?

2) Have you seen this SharePoint blueprint:

https://www-secure.symantec.com/connect/articles/netbackup-76-blueprints-sharepoint

...have a read... does it offer any clues as to maybe something not quite right with your config?

3) Can you share the policy config?

bppllist POLICY_NAME -U

Ziggy1941
Level 4
Partner Accredited

Nope (((( The same result:

24.03.2015 17:56:16 - Warning bpbrm(pid=15711) from client sharepoint.ussc.ru: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\Ïîäêëþ÷åíèå ê Project Service Application/Proxy (SQL/90d8556f-94c9-40a7-9e78-95b3652f7783)
24.03.2015 17:56:34 - Info bpbkar(pid=4492) bpbkar waited 27406 times for empty buffer, delayed 32175 times.   
24.03.2015 17:56:38 - Info nbu-s2.ussc.ru(pid=15780) StorageServer=PureDisk:nbu-s2.ussc.ru; Report=PDDO Stats (multi-threaded stream used) for (nbu-s2.ussc.ru): scanned: 89121299 KB, CR sent: 72478601 KB, CR sent over FC: 0 KB, dedup: 18.7%, cache hits: 0 (0.0%)
24.03.2015 17:56:41 - Error bptm(pid=15780) media manager terminated by parent process       
24.03.2015 17:56:41 - Error bpbrm(pid=15711) could not send server status message       
24.03.2015 17:56:42 - Info bpbkar(pid=4492) done. status: 13: file read failed       
24.03.2015 17:56:42 - end writing; write time: 2:23:12
file read failed (13)

Ziggy1941
Level 4
Partner Accredited

Yes, the same problem when you restart when I restart this job.

I can't find what is not quite right in configs ((

nbu-s2:/usr/openv/netbackup/bin/admincmd # ./bppllist sharepoint.ussc.ru_non-GRT -U
------------------------------------------------------------

Policy Name:       sharepoint.ussc.ru_non-GRT

  Policy Type:         MS-SharePoint
  Active:              yes
  Effective date:      03/23/2015 10:55:34
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     5
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           dedup_stu_nbu-s2
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows       sharepoint.ussc.ru

  Include:  Microsoft SharePoint Resources:\

  Schedule:              Full
    Type:                Automatic Backup
    Frequency:           every 1 day
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    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:
          Sunday     21:00:00  -->  Monday     08:00:00
          Monday     21:00:00  -->  Tuesday    08:00:00
          Tuesday    21:00:00  -->  Wednesday  08:00:00
          Wednesday  21:00:00  -->  Thursday   08:00:00
          Thursday   21:00:00  -->  Friday     08:00:00
          Friday     21:00:00  -->  Saturday   08:00:00
          Saturday   21:00:00  -->  Sunday     08:00:00