Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Backup failed - can't open object

Created: 20 Dec 2013 • Updated: 22 Dec 2013 | 3 comments
This issue has been solved. See solution.

Hi,

nbu server and client are : 7.5.0.6
Client : windows 2008 64bit

Backup all_local_drive with BMR enabled and get below error.
Can anyone help to solve this?
 

SET SNAP_ID=clientapp1_1387454421
Shadow Copy Components:\
 

12/19/2013 19:02:15 - connected; connect time: 0:00:00
12/19/2013 19:02:16 - Info bpbkar (pid=5204) Backup started
12/19/2013 19:02:16 - Info bpbrm (pid=54113) Sending the file list to the client
12/19/2013 19:04:14 - Warning bpbrm (pid=54148) from client clientapp1: WRN - can't open object: System State:\System Files\System Files (WIN32 -536805679: Unknown error)
12/19/2013 19:04:14 - Error bpbrm (pid=54148) from client clientapp1: ERR - Error encountered while attempting to get additional files for System State:\
12/19/2013 19:04:14 - Warning bpbrm (pid=54148) from client clientapp1: WRN - can't open object: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805679: Unknown error)
12/19/2013 19:04:14 - Warning bpbrm (pid=54148) from client clientapp1: WRN - can't open object: System State:\Registry\Registry (WIN32 -536805679: Unknown error)
12/19/2013 19:04:14 - Warning bpbrm (pid=54148) from client clientapp1: WRN - can't open object: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805679: Unknown error)
12/19/2013 19:04:14 - Warning bpbrm (pid=54148) from client clientapp1: WRN - can't open object: System State:\Windows Management Instrumentation\WMI (WIN32 -536805679: Unknown error)
12/19/2013 19:04:49 - Info bptm (pid=54115) media id LV8248 mounted on drive index 1, drivepath /dev/nst8, drivename HP.ULTRIUM6-SCSI.001, copy 1
12/19/2013 19:04:50 - mounted LV8248; mount time: 0:02:36
12/19/2013 19:04:50 - positioning LV8248 to file 861
12/19/2013 19:06:11 - positioned LV8248; position time: 0:01:21
12/19/2013 19:06:11 - begin writing
12/19/2013 19:06:16 - Info bpbrm (pid=54113) media manager for backup id clientapp1_1387454522 exited with status 0: the requested operation was successfully completed
12/19/2013 19:06:16 - end writing; write time: 0:00:05
the requested operation was partially successful  (1)

clientapp2 win2008 64 bit, all_local_drives with BMR enabled, also get the similar error below.

12/19/2013 19:01:35 - Info bpbkar (pid=9652) Backup started

12/19/2013 19:01:35 - Info bpbrm (pid=48291) Sending the file list to the client

12/19/2013 19:02:01 - mounted LV5557

12/19/2013 19:02:01 - positioning LV5557 to file 947

12/19/2013 19:03:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\System State\Background Intelligent Transfer Service\NetBackup_file_info.Win_OS_CLT_G1' is missing. Backing up everything in 'System State:\Background Intelligent Transfer Service'

12/19/2013 19:03:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\System State\NetBackup_file_info.Win_OS_CLT_G1' is missing. Backing up everything in 'System State:'

12/19/2013 19:03:22 - positioned LV5557; position time: 0:01:21

12/19/2013 19:03:22 - begin writing

12/19/2013 20:18:30 - Warning bpbrm (pid=50078) from client clientapp2: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\System State\Background Intelligent Transfer Service\NetBackup_file_info.Win_OS_CLT_G1' is missing. Backing up everything in 'System State:\Background Intelligent Transfer Service'

12/19/2013 20:18:30 - Warning bpbrm (pid=50078) from client clientapp2: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\System State\NetBackup_file_info.Win_OS_CLT_G1' is missing. Backing up everything in 'System State:'

12/19/2013 20:36:02 - Error bpbrm (pid=50078) from client clientapp2: ERR - failure reading file: System State:\_SharedHardlinkData_\2e103e1a.10000.5b40 (WIN32 -536805834: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b42 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b43 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b44 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b45 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b46 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b47 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b48 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b49 (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b4b (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Warning bpbrm (pid=50078) from client clientapp2: WRN - can't open object: System State:\_SharedHardlinkData_\2e103e1a.10000.5b4c (WIN32 -536836987: Unknown error)

12/19/2013 20:36:02 - Info bpbrm (pid=50078) from client clientapp2: TRV - last message being suppressed after 10 occurrences

12/19/2013 20:41:02 - Error bpbrm (pid=50078) socket read failed: errno = 62 - Timer expired

12/19/2013 20:41:02 - Info bpbrm (pid=48291) sending message to media manager: STOP BACKUP clientapp2_1387454482

12/19/2013 20:41:03 - Info bpbrm (pid=48291) media manager for backup id clientapp2_1387454482 exited with status 150: termination requested by administrator

12/19/2013 20:41:03 - end writing; write time: 1:37:41

file read failed  (13)

Operating Systems:

Comments 3 CommentsJump to latest comment

Marianne's picture

Are any VSS errors seen in Event Viewer logs on the client?

Can you use Windows backup utility on the client to run backup of Shadow Copy Components to local disk?

Have a look at this TN: http://www.symantec.com/docs/TECH137514

and http://www.symantec.com/docs/TECH147574

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

SOLUTION
Mark_Solutions's picture

I believe this tech note still apllies to 7.5 - sorts out Win 2008 servers that have the BCD:

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

When using TIR (or not) the log will always refer to the System State / Shadow Copy and regardless will always backup those components in full - so those errors can be ignored - in effect any Shadow Copy Components or System State backups always backup as full even in an incremental backup - it is just that it gets mentioned during TIR backups

Hope these help

Authorised Symantec Consultant

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