Forum Discussion

Shas's avatar
Shas
Level 4
11 years ago

System State Backup of Netbackup Media server 7.5.6 is completing Partially

Hi ,

Netbackup Media server  is backing up its own drives (C:\ and System state) , and every time backup is completing partially.Please Suggest

Below mentioned are the files which are getting skipped / job details.

27/02/2014 17:15:08 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)
27/02/2014 17:15:08 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\Task Scheduler\TasksStore (WIN32 -536805667: Unknown error)
27/02/2014 17:15:08 - Error bpbrm(pid=9564) from client xxx04: ERR - Error encountered while attempting to get additional files for System State:\
27/02/2014 17:15:09 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\VSS Express Writer Store\WriterMetadataStore (WIN32 -536805667: Unknown error)
27/02/2014 17:15:09 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\Performance Counter\PerformanceCounters (WIN32 -536805667: Unknown error)
27/02/2014 17:15:09 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805667: Unknown error)
27/02/2014 17:15:19 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\System Files\System Files (WIN32 -536805667: Unknown error)
27/02/2014 17:15:20 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\Windows Management Instrumentation\WMI (WIN32 -536805667: Unknown error)
27/02/2014 17:15:20 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\Registry\Registry (WIN32 -536805667: Unknown error)
27/02/2014 17:15:20 - Warning bpbrm(pid=9564) from client xxx04: WRN - can't open object: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805667: Unknown error)
27/02/2014 17:15:28 - Info bptm(pid=6788) waited for full buffer 15541 times, delayed 50649 times    
27/02/2014 17:15:28 - Info bpbkar32(pid=7376) bpbkar waited 27 times for empty buffer, delayed 38 times.   
27/02/2014 17:15:30 - Info bptm(pid=6788) EXITING with status 0 <----------        
27/02/2014 17:15:30 - Info xxx04(pid=6788) StorageServer=PureDisk:xxx04; Report=PDDO Stats for (xxx04): scanned: 46513670 KB, CR sent: 128216 KB, CR sent over FC: 0 KB, dedup: 99.7%
27/02/2014 17:15:30 - Info bpbrm(pid=9564) validating image for client xxx04        
27/02/2014 17:15:31 - Info bpbkar32(pid=7376) done. status: 1: the requested operation was partially successful    
27/02/2014 17:15:55 - end writing; write time: 00:19:09
the requested operation was partially successful(1)
 
NOTE: server name is edited with xxx04 and vssadmin output is attached with this post.
  • Ah - OK - well then we should look at this:

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {96d512ab-4dd4-4af8-999d-5601e9be1ec6}
       State: [7] Failed
       Last error: Timed out

    That wont work again until you have rebooted it...

    After that it is working out why it happened in the first place - there may be a VSS hotfix for 2008R2 or it may be an issue with VSS itself not having enough space for its snapshots

    I see de-dupe mentioned here - if this a MSDP Media Server? - maybe the VSS components need dealing with to exclude the de-dupe drive during snapshots or at least place the snapshot on a different drive (there is a microsoft tech note somewhere that deals with all of that)

    One question though.. why are you backing up the media server? .. there is not a great deal of use on a media server in general - and if it crashed you would need to rebuild it to do its restore - by which time you would already have it back - in general i dont bother backing up media servers unless they host something.

  • What O/S doe you have on the Media Server?

    That selection should really be Shadow Copy Components for anything Windows 2003 onwards

    Try it that way and see what you get

  • Hi Mark,

    O\S is Windows 2008 R2 .

    Backup selection is Shadow Copy Components:\ , apology for mentioning System State in previous post. :)

  • Ah - OK - well then we should look at this:

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {96d512ab-4dd4-4af8-999d-5601e9be1ec6}
       State: [7] Failed
       Last error: Timed out

    That wont work again until you have rebooted it...

    After that it is working out why it happened in the first place - there may be a VSS hotfix for 2008R2 or it may be an issue with VSS itself not having enough space for its snapshots

    I see de-dupe mentioned here - if this a MSDP Media Server? - maybe the VSS components need dealing with to exclude the de-dupe drive during snapshots or at least place the snapshot on a different drive (there is a microsoft tech note somewhere that deals with all of that)

    One question though.. why are you backing up the media server? .. there is not a great deal of use on a media server in general - and if it crashed you would need to rebuild it to do its restore - by which time you would already have it back - in general i dont bother backing up media servers unless they host something.

  • thanks Mark,

    Server is still awaiting for a reboot...

  • As per Mark's excellent post above - there is actually no purpose in backing up a media server...

    Any reason for still pursuing this?

  • Hi Marianne,

    I have suggested the same to the onsite team ....

    However a good news is server is rebooted and backups are completing successfully.

    Thanks to all..Cheers smiley