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

file read failed(13) ..... Unable to backup System State or Shadow Copy.

Created: 08 Jul 2010 • Updated: 25 Dec 2012 | 6 comments
This issue has been solved. See solution.

A backup job finish with this error:

08.07.2010 09:47:09 - begin writing
08.07.2010 09:47:38 - Error bpbrm(pid=712) from client h07w1-s0001: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
08.07.2010 09:47:46 - Error bpbrm(pid=712) from client h07w1-s0001: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
08.07.2010 09:47:49 - Error bpbrm(pid=712) could not send server status message       
08.07.2010 09:47:52 - end writing; write time: 00:00:43
file read failed(13)

I have try to back up with or without WOFB Windows Open File Backup. Same error. Any idea?

Master: Windows 2003/64 NBU 7.0
Client: Windows 2008/32 NBU 7.0

Comments 6 CommentsJump to latest comment

Andy Welburn's picture

NetBackup tries to backup what is in the Exclude List and then fails with status 69
http://seer.entsupport.symantec.com/docs/354674.htm

Background:
The policy contained ALL_LOCAL_DRIVES directive.

Include: ALL_LOCAL_DRIVES
Exclude List had the following entries:
exclude = Shadow Copy Components:\
exclude = System_State:\
Problem:
bpbkar shows that it is trying to backup Shadow Copy Components & System State which are on the Exclude List which is wrong, and then failing with status 69:
5:17:42.857 PM: [3340.3372] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = ALL_LOCAL_DRIVES
5:17:42.857 PM: [3340.3372] <4> dos_backup::V_VerifyFileSystem: INF - Added: C:\
5:17:42.857 PM: [3340.3372] <4> dos_backup::V_VerifyFileSystem: INF - Added: Shadow Copy Components:\
5:17:42.857 PM: [3340.3372] <4> dos_backup::V_VerifyFileSystem: INF - Added: System State:\
5:17:42.888 PM: [3340.3372] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE ():FS_AttachToDLE() DeviceName:'Shadow?Copy?Components' BackupReason:0x1 Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata.
5:17:42.888 PM: [3340.3372] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:Shadow Copy Components:
5:17:42.888 PM: [3340.3372] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'Shadow Copy Components:\' --> 00000000
5:17:42.904 PM: [3340.3372] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE ():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x1 Failed! (0 xE000FEC9:A failure occurred accessing the Writer metadata.
5:29:13.652 PM: [3340.3372] <2> tar_base::V_vTarMsgW: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.
5:29:13.652 PM: [3340.3372] <4> tar_backup::backup_done_state: INF - number of file directives not found: 1
5:29:13.652 PM: [3340.3372] <4> tar_backup::backup_done_state: INF - number of file directives found: 2
5:29:13.652 PM: [3340.3372] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 69: invalid filelist specification
 
Solution:
This is a known issue with no immediate solution in 7.0 for Windows platforms. This was fixed for UNIX.
The customer can drop back to 6.5.5 on the client and it may prevent the status 69s.
Alternatively, one can modify the policy not to use ALL_LOCAL_DRIVES.
 
Notes: Although Windows 2003 is listed here, this problem exists for all supported Windows platforms.
 
 

SOLUTION
MariusD's picture

i have tryed with

Include: ALL_LOCAL_DRIVES

Exclude List had the following entries:
exclude = Shadow Copy Components:\
exclude = System_State:\

but not work. Come same error. I will try also with not All_Local_Drivers. I hope thats work.

Regards my friends, Marius D.

 

Master: Windows 2008 R2 64 Bit

NBU:  7.5 for Windows

Andy Welburn's picture

because those entries are in the exclude list(s). If you did not originally have these entries in your exclude list(s) then this is unlikely to be the cause of your issue.

richs24's picture

also, use the following 2 commands to check the state of your vss writers and providers

vssadmin list writers
vssadmin list providers

you are looking for the 'no errors' and 'stable' messages after each.

if it doesnt say that, try a reboot

MariusD's picture

on the client or on the master?

Regards my friends, Marius D.

 

Master: Windows 2008 R2 64 Bit

NBU:  7.5 for Windows

Andy Welburn's picture

This will check on the ability of the clients VSS to actually be able to successfuly snapshot (& hence) backup the System_State/Shadow_Copy_Components.

I take it there was no joy from the T/N I provided a link to earlier? ***EDIT*** just seen your reply to that post after writing this!