Video Screencast Help

Two Windows clients/status 1 - system state backup failing

Created: 25 Jul 2013 • Updated: 20 Dec 2013 | 8 comments
This issue has been solved. See solution.

NBU Environment:

Master: NBU 7.5.0.4 running on Solaris SunOS 5.10

Media: NBU 7.5.0.4 running on Solaris SunOS 5.10

Clients: Windows Server 2008 running NBU client 7.0

I have two Windows clients that are getting status 1 errors because the system state portion of the backup is failing (see recent job detail for both clients below, looks like very similar errors on each). The file system for both appears to be backing up just fine based on what is available for restore.

07/24/2013 18:03:40 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)

07/24/2013 18:03:44 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

07/24/2013 18:03:44 - Error bpbrm (pid=29371) from client bknhicodcswp01: ERR - Error encountered while attempting to get additional files for System State:\

07/24/2013 18:03:44 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805667: Unknown error)

07/24/2013 18:03:44 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\Registry\Registry (WIN32 -536805667: Unknown error)

07/24/2013 18:03:44 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\Internet Information Services\IISCONFIG (WIN32 -536805667: Unknown error)

07/24/2013 18:03:44 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\Internet Information Services\IISMETABASE (WIN32 -536805667: Unknown error)

07/24/2013 18:03:45 - Warning bpbrm (pid=29371) from client bknhicodcswp01: WRN - can't open file: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805667: Unknown error)

07/25/2013 00:05:46 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

07/25/2013 00:05:50 - Error bpbrm (pid=22745) from client bknhicodcsqlp01: ERR - Error encountered while attempting to get additional files for System State:\

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805667: Unknown error)

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\Registry\Registry (WIN32 -536805667: Unknown error)

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\Internet Information Services\IISMETABASE (WIN32 -536805667: Unknown error)

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\Internet Information Services\IISCONFIG (WIN32 -536805667: Unknown error)

07/25/2013 00:05:50 - Warning bpbrm (pid=22745) from client bknhicodcsqlp01: WRN - can't open file: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805667: Unknown error)

Any ideas?

Thanks,

Wayne

Operating Systems:

Comments 8 CommentsJump to latest comment

Dyneshia's picture

What is in your backup selection for the policy ?

WayneLackey's picture

Backup selection is the same for both clients:

ALL_LOCAL_DRIVES
Shadow Copy Components:\
System State:\

I seem to remember a Symantec engineer telling me that ALL_LOCAL_DRIVES includes the Shadow Copy and System State components; is that accurate? If so, isn't having Shadow Copy and System State in the backup selection along with ALL_LOCAL_DRIVES kind of redundant?

Andy Welburn's picture

ALL_LOCAL_DRIVES "If this directive is used, this directive must be the only entry in the backup"

Shadow Copy Components "implies and/or includes System State:\ if that was not also selected"

Your backup selection will probably result in a duplication of effort - but you could certainly confirm that using the BAR GUI.

The Admin Guide provides a lot more info on *exactly* what each directive backs up.

Marianne's picture

Please upgrade your clients!

There were lots of fixes for W2008 System State backups included in 7.1.0.x patches which will obviously included in 7,5,0.x patches as well.

Some examples of TNs documenting 7.1 fixes:
http://www.symantec.com/docs/TECH144723 
http://www.symantec.com/docs/TECH140077 
http://www.symantec.com/docs/TECH156114 
 

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

Mark_Solutions's picture

As Marianne says - update your clients to get rid of bugs, and as you mention please get rid of the Shadow Copy Components and System State parts of your policy

ALL_LOCAL_DRIVES includes these so you are trying to back then up three times!! If you allow multiple data streams as well then all three would try and run at the same time

Once you are all up to date and have edited your policies then see if you still get errors - there are tech notes relating to some of the ones you have but a lot of stuff has been fixed to see how it goes once you are all tidy

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
Marianne's picture

Backup selection is the same for both clients:

ALL_LOCAL_DRIVES
Shadow Copy Components:\
System State:\

As per Andy and Mark's posts - 

ALL_LOCAL_DRIVES already includes Shadow Copy Components, plus, Shadow Copy Components includes System State.

This is also documented in NetBackup Admin Guide I: http://www.symantec.com/docs/DOC5159

Please edit your policy to only reflect ALL_LOCAL_DRIVES.

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

Dip's picture

07/24/2013 18:03:44 - Error bpbrm (pid=29371) from client bknhicodcswp01: ERR - Error encountered while attempting to get additional files for System State:\

This above Error means the Snapshot that was taken for Registry is no longer there as OS deleted it due to shadow copy space limit. In Windows 2008 you need at least 10% of the total size of each drive allocated for Shadow Copy (OS installation does this be default but sometimes due to different Build process the size changes). To check what is currently configured, right click on C: drive and Properties, click on Shadow Copy, Select C: from the list and click Settings update the size equal to 10% of total disk space (If C: driv eis 50 GB then Shadow Copy should be 5GB). You can then use "vssadmin list shadowstorage" command to check and make sure 10% is allocated.

ilovemywillow's picture

I am having the same issue except shadow copy is disabled on all servers and there is plenty of space.  In spite of having this disabled on all servers one is getting this error while  the others are not.

Mon Aug 26 17:34:07 CDT 2013   nbmediaserver iisclient    Error  80922  Backup  from client ebs-iis1: ERR - Error encountered while attempting to get additional files for System State:\    bpbrm