Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

SYSTEM STATE BACKUP FAILURE

Created: 01 May 2013 | 11 comments

client OS win 2008 NBU verison 7.1.0.2

system state backup failure

GUI logs:

 

05/01/2013 01:00:17 - Info nbjm (pid=29552) starting backup job (jobid=2464324) for client CLIENT.ATT, policy POLICYNAME, schedule INCR
05/01/2013 01:00:18 - Info bpbrm (pid=22379) CLIENT.ATT is the host to backup data from
05/01/2013 01:00:18 - Info bpbrm (pid=22379) reading file list from client
05/01/2013 01:00:18 - estimated 0 kbytes needed
05/01/2013 01:00:18 - Info nbjm (pid=29552) started backup job for client CLIENT.ATT, policy POLICYNAME, schedule INCR on storage unit DDSTU
05/01/2013 01:00:18 - started process bpbrm (pid=22379)
05/01/2013 01:00:19 - connecting
05/01/2013 01:00:20 - Info bpbrm (pid=22379) starting bpbkar on client
05/01/2013 01:00:20 - Info bpbkar (pid=48084) Backup started
05/01/2013 01:00:20 - Info bpbrm (pid=22379) bptm pid: 22393
05/01/2013 01:00:20 - Info bptm (pid=22393) start
05/01/2013 01:00:20 - connected; connect time: 0:00:00
05/01/2013 01:00:21 - Info bptm (pid=22393) using 262144 data buffer size
05/01/2013 01:00:21 - Info bptm (pid=22393) setting receive network buffer to 262144 bytes
05/01/2013 01:00:21 - Info bptm (pid=22393) using 256 data buffers
05/01/2013 01:00:22 - Info bptm (pid=22393) start backup
05/01/2013 01:00:22 - Info bptm (pid=22393) backup child process is pid 22396
05/01/2013 01:00:22 - begin writing
05/01/2013 01:04:59 - Warning bpbrm (pid=22379) from client CLIENT.ATT: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)
05/01/2013 01:04:59 - Error bpbrm (pid=22379) from client CLIENT.ATT: ERR - Error encountered while attempting to get additional files for System State:\
05/01/2013 01:12:55 - Info bpbrm (pid=22379) from client CLIENT.ATT: TRV - object not found for file system backup: EFI System Partition:
05/01/2013 01:12:55 - Info bptm (pid=22393) waited for full buffer 8780 times, delayed 42036 times
05/01/2013 01:12:56 - Info bptm (pid=22393) EXITING with status 0 <----------
05/01/2013 01:12:56 - Info bpbrm (pid=22379) validating image for client CLIENT.ATT
05/01/2013 01:12:56 - Info bpbkar (pid=48084) done. status: 1: the requested operation was partially successful
05/01/2013 01:12:56 - end writing; write time: 0:12:34
the requested operation was partially successful  (1)
 

 

Operating Systems:

Comments 11 CommentsJump to latest comment

sazz.'s picture

TRV - object not found for file system backup: EFI System Partition:

Do you have the EFI boot partition?

What is the status of vssadmin list writers and vssadmin list providers? Make sure the writers are stable and without error. Also are you able to backup up this via the windows itself?

Please check this TN, though the master and client is different but you are hitting the same error message.

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

 

 

Dyneshia's picture

If the workaround does not work,  you may need to open a ticket with support to request the eeb.

From your logs :

 

1:00:51.848 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:00:51.848 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:00:51.848 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - unable to initialize the required BEDS interface
1:00:51.848 AM: [48084.30308] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:EFI System Partition:
1:00:51.848 AM: [48084.30308] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'EFI System Partition:\' --> 00000000
1:01:03.766 AM: [48084.30308] <4> VssSnapshot::V_VssSetMetadata(): INF - Unable to locate DFSR metadata
1:01:04.796 AM: [48084.30308] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
1:01:04.796 AM: [48084.30308] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: Begin
1:01:33.796 AM: [48084.30308] <4> dos_backup::tfs_findfirst: INF - unable to find first file: 'Shadow Copy Components:\System Service\Background Intelligent Transfer Service\'
1:01:33.796 AM: [48084.30308] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - Drive 'C:' added to VSS Volume Set
1:01:38.305 AM: [48084.30308] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - VSS Volume Set snapped
1:01:38.305 AM: [48084.30308] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - About to commence post-snap unbounded association checks
1:01:38.305 AM: [48084.30308] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: End

:03:34.696 AM: [48084.30308] <4> dos_backup::tfs_findfirst: INF - unable to find first file: 'Shadow Copy Components:\System Service\Background Intelligent Transfer Service\'
1:04:59.124 AM: [48084.30308] <2> ov_log::V_GlobalLogEx: ERR - beds_ss_access::V_OpenForRead(): FS_OpenObj() Failed! (0xE000FEDD:A failure occurred accessing the object list.
1:04:59.124 AM: [48084.30308] <2> tar_base::V_vTarMsgW: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)
1:04:59.124 AM: [48084.30308] <2> tar_base::V_vTarMsgW: ERR - Error encountered while attempting to get additional files for System State:\
1:10:22.902 AM: [48084.30308] <4> dos_backup::tfs_scanstart: INF - Backup Special Objects request AFTER System State:
1:10:40.545 AM: [48084.30308] <4> dos_backup::tfs_getinfo: INF - current object (System State:) is a parent of previous (object (System State:\COM+ Class Registration Database\COM+ REGDB)
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - unable to initialize the required BEDS interface
1:12:55.906 AM: [48084.30308] <2> tar_base::V_vTarMsgW: TRV - object not found for file system backup: EFI System Partition:

 

This was an old 7.1 bug.  Your best bet would be to patch to 7.1.0.4 and each patchset is cumulative and contains a ton of fixes from the previous patchset.

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

rookie11's picture

 

C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 
 
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {d5aba48b-1ea6-44e8-b727-cdf2e9b934a1}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {d7ccd1b7-f07d-4582-b52a-aab54af9b7ba}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {ab2c147e-9798-4390-ba08-b4a9033c45b9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {fc8b1dfd-2a86-4b75-a94f-45d5186c499f}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {2c9ade4d-7df2-4bb0-ab63-057d8c2d0432}
   State: [5] Waiting for completion
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {58bd8bbc-b77f-4ef0-ab71-004d0731ac78}
   State: [1] Stable
   Last error: No error
 
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {29af19ff-4508-4f36-b1cf-8b362f991b54}
   State: [1] Stable
   Last error: No error
 
 
system state backup done successfully by windows backup utility
sazz.'s picture

fair enough, i have seen it on windows 2008 sometimes it having this issue backing up the reserved partition of 100 mb that doesn't have the drive letter assigned. Can you please assign the drive letter to that reserved partition and try a backup.

If that doesn't resolve the issue try below steps:

1> Upgrade the version of client as this one had lot of issues. I would prefer upgrading everything in your enviornment to 7.5.0.4

2> If that is not the thing you wana do then please look at these TN and try the steps as mentioned.

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

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

 

Dyneshia's picture

Hello rookie11 , were you able to patch up the enviorment and review the reccomnded tech notes ? Are you still having an issue ?

Twinkle Sapra's picture

We are also facing the same issue. Upgraded to 7.1.0.4 , still no luck.

Dyneshia's picture

Are you still getting :

 

1:01:38.305 AM: [48084.30308] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - About to commence post-snap unbounded association checks
1:01:38.305 AM: [48084.30308] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: End :03:34.696 AM: [48084.30308] <4> dos_backup::tfs_findfirst: INF - unable to find first file: 'Shadow Copy Components:\System Service\Background Intelligent Transfer Service\'
1:04:59.124 AM: [48084.30308] <2> ov_log::V_GlobalLogEx: ERR - beds_ss_access::V_OpenForRead(): FS_OpenObj() Failed! (0xE000FEDD:A failure occurred accessing the object list.
1:04:59.124 AM: [48084.30308] <2> tar_base::V_vTarMsgW: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)
1:04:59.124 AM: [48084.30308] <2> tar_base::V_vTarMsgW: ERR - Error encountered while attempting to get additional files for System State:\
1:10:22.902 AM: [48084.30308] <4> dos_backup::tfs_scanstart: INF - Backup Special Objects request AFTER System State:
1:10:40.545 AM: [48084.30308] <4> dos_backup::tfs_getinfo: INF - current object (System State:) is a parent of previous (object (System State:\COM+ Class Registration Database\COM+ REGDB)
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - bedsEFIInit():DLE_FindByName() for 'EFI>System>Partition' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.
1:12:55.906 AM: [48084.30308] <2> ov_log::V_GlobalLog: ERR - unable to initialize the required BEDS interface

Twinkle Sapra's picture

We are still getting the isssue even after upgrade to 7.1.0.4. Working with Symantec but no luck :(

sazz.'s picture

HI Twinkle,

Are you posting on behalf of rookie11, as we are not getting any update on this thread from rookie11? If you are a different user then please post in a new thread with your exact error message and issue.

 

mikent's picture

@rookie11,

Is it a Cluster node? if so, you need to define drive letter only in backup selections instead of ALL_LOCAL_DRIVES becasue there VSS provider is not 'Cluster aware' and System State is getting mapping device information for File system that are not currently mounted on the acrtive/passive node from the Cluster.

There is a w2koptions command that allow to you to ingone drive letter but it is tricky and recommanded because in case of failover you can be in trouble.

If it is not a Cluster node, then you should provide more information about your client.

./nathan

BR,

Nathan Mike

Senior System Engineer

LPI1-C and CLA-11 Novell Certified Linux Administrator

+320473954944