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

backup partially successul with WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

Created: 14 Aug 2013 • Updated: 20 Aug 2014 | 16 comments
This issue has been solved. See solution.

i encounter an error while backuping several Windows 2008R2 clients with error message :

 

WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

 

Master server is Netbackup 7.1 on linux

Clients netbackup version is 7.5

Clients OS version is Windows 2008 R2

backup object is ALL_LOCAL_DRIVES

 

anyone have an idea

Operating Systems:

Comments 16 CommentsJump to latest comment

Marianne's picture

Master server is Netbackup 7.1 on linux

Clients netbackup version is 7.5

Above version mix is NOT supported. 

See Version Compatibility TN: http://www.symantec.com/docs/TECH29677  

Either remove NBU 7.5 software from client and install NBU 7.1 followed by 7.1.0.4 patch and also verify that 7.1.0.4 patch is installed on master and media server, or
Upgrade master to 7.5, followed by 7.5.0.6 patch.

 

Let us know how it goes once you have supported version mix on server and client.

 

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

Vickie's picture
Is there any successful backup for this client ?
I guess there should not be,  as its not compatible with Master Server NBU Version.
 
Regards,
Vickie
melissa windows's picture

thanks for your answer.

 

I make the change but i still have the problem.

now i have :

Master server is Netbackup 7.1 on linux

Clients netbackup version is 7.1.0.4

 

What can i do next?

 

 

Marianne's picture

Check VSS writers on the client: 
vssadmin list writers

Also check Event Viewer logs for VSS errors.

Other possibilities:

http://www.symantec.com/docs/TECH177496 

http://www.symantec.com/docs/TECH140077 (but fix should be included in 7.1.0.4) 

For further throubleshooting, ensure bpbkar and bpfis log folders exist on client under ...\netbackup\logs. 

Copy logs to reflect process name (e.g. bpfis.txt) and post as File attachments.

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

Will Restore's picture

Also be sure to upgrade your Master Server to 7.1.0.4

 

Will Restore -- where there is a Will there is a way

melissa windows's picture

Thanks

 

Marianne :

=> no error with wss writers all in stable state

I don't use à junction path so i'm not concerned with http://www.symantec.com/docs/TECH177496

I already try the fix shown in http://www.symantec.com/docs/TECH140077 but it doesn't solve the problem :-(

I create the logs folders for bpbkar and bpfis

error is :

14 août 2013 16:14:05 - Warning bpbrm (pid=4107) from client acdevboxi1: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)
14 août 2013 16:14:05 - Error bpbrm (pid=4107) from client acdevboxi1: ERR - Error encountered while attempting to get additional files for System State:\

i attache the 2 logs files
 

WR :

Why do i need to upgrade mastet Server to 7.1.0.4?

regards

 

 

 

AttachmentSize
bpbkar-081413.txt 54.04 KB
bpfis-081413.txt 79.7 KB
Will Restore's picture

OK, looks like Master upgrade is not required but it's generally good to do so

http://www.symantec.com/business/support/index?page=content&id=TECH181132&key=15143

 

And it looks like your client backup job is trying to do Cumulative Incremental without first doing a Full (both Schedules must be in the Policy)

Will Restore -- where there is a Will there is a way

mrbill14's picture

I find that this error is almost always something with the VSS writers (at the OS level).

I also usually see an error in the Event log (Application log) where it faults bpbkar32.exe:

Log Name:      Application
Source:        Application Error
Date:          8/14/2013 8:02:24 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Faulting application name: bpbkar32.exe, version: 6.5.0.0, time stamp: 0x4cffb58e
Faulting module name: bpbkar32.exe, version: 6.5.0.0, time stamp: 0x4cffb58e
 

I find that running the FIX_VSS.bat file on the client almost always fixes it.

I attached it as a text file.

AttachmentSize
FIX_VSS.txt 1.75 KB
melissa windows's picture

Hi everyone!

 

mrbill14 : I haven't any VSS errors in application log

and regarding bpkar logfiles netbackup create successfully the snapshot for c drive

but it fails on E: drive

 

I tried a full backup and i found the same error.

16:14:04.833: [3284.5388] <2> ov_log::V_GlobalLogEx: ERR - beds_ss_access::V_OpenForRead(): FS_OpenObj() Failed! (0xE000FEDD:A failure occurred accessing the object list.

while trying to save drive E:

 

mrbill14's picture

Sorry for the lateness of the reply.

No, after running the script, it doesn't require a reboot.

 

Melissa:  The VSS errors are mostly on the root drive (C:), because that's where the System State files are...  not that VSS couldn't be the cause of other volumes not to "snapshot".  It's just usually the case that it's the root drive (with the System State) that causes the problems.

Your error - "A failure occurred accessing the object list" - sounds like it's having a problem reading the drive or the file list has changed (dramatically) from the time it enumerated the drive and the time it is backing it up.

Is this a clustered disk (part of a Windows cluster) or something?  Maybe the disk (E: drive) flipped over to the other host during the backup?

Is this a SAN LUN?  Maybe the drive is getting knocked off line or the server is having problems connecting to it (especially under heavy loads - as Netbackup tends to load up the network - so, in the case of a iSCSI drive, maybe flooding the network?)...

Will Restore's picture

Try Windows backup without NetBackup

 

wbadmin  start  systemstatebackup  -backupTarget:E: 

Will Restore -- where there is a Will there is a way

melissa windows's picture

I everybody.

 

I solved the problem with symantec support.

in bpbkar log we found :

11:24:09.437: [7328.3380] <2> ov_log::V_GlobalLog: INF - Status 0x0000007B returned calling FindFirstFile for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy259\program files (x86)\subversion/bin in brUtil::GenerateFileList

The error 0x0000007B is defined by Microsoft as:
ERROR_INVALID_NAME 123 (0x7B) - The filename, directory name, or volume label syntax is incorrect.

http://www.symantec.com/business/support/index?page=content&id=TECH150097

 

The imagepath for the svn service is not formated correctly as a valid windows path.

I correct the path in registry and everything is ok and backup are successfull.

thanks a lot to everyone

Will Restore's picture

Interesting Subversion laugh

no such text in bkbkar file posted last week

Will Restore -- where there is a Will there is a way

mrbill14's picture

Glad to hear you got this one solved!

On a slightly different note, I had a Windows 2008 R2 cluster that has a service that is clustered (Control-M scheduler).  As a clustered service, the service would follow (or roll over) the active node master.  (Whichever node was the master, this service would roll over to it.  Which means the other node doesn't have it, which would cause the backups to fail.)

I found this script (I don't take credit for it) on the Microsoft Technet blogs which runs a powershell script that checks for any invalid or incorrect services (in the registry).  See attached.  (Posted it as a text file, will have to rename the file with a .ps1 extension.)  Also, you will probably have to set the PowerShell Execution Policy to unrestricted.  See second attachment for explanation.

http://blogs.technet.com/b/askcore/archive/2010/06/18/ps-script-for-blog-enumeration-of-the-files-failed.aspx

Thinking that this would have been helpful in your situation. (?)  I'm posting it here in case anybody else happens across this particular situation.

 

AttachmentSize
GetInvalidImagePathsV2.txt 9.78 KB
Running the PowerShell script.txt 468 bytes
SOLUTION