Can you post the bpbkar log?
Also, when loading the page for your post, the sidebar showed a few posts with error 69 mentioned. One of them talks about tech note: http://www.veritas.com/docs/000017926 Check that too.
As your problem seems to be related to VSS/System state this blog:
might be of help. In my experience most often the problem is a too small shadow storage area.
I tried many things:
1) I checked the VSS Writers: (all good):vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-
(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: {6f2cc347-8109-45b5-a9b5-bcb3a45a1816}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {b6e524b8-04a5-406c-8153-0a0187317e5b}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {8e3b348b-086f-40e7-a963-44a5fed92bf1}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7a0504c6-6770-473d-a3d7-b6f87b764db7}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {5312c4be-1c60-4162-a3d8-aaac86c70890}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {9ef4cbe3-3a82-4645-9e20-425cc0997a51}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f0da1a64-6376-40d5-a725-60671f9dc9ac}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {86e1afd4-3f48-448a-981d-b239fbd8879a}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {d97a0e4e-8db6-4d05-970b-b2a3e6358911}
State: [1] Stable
Last error: No error
2) I checked the VSS provider (all good)
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}
3) There are volumes that exceed 62 TB, I extended the registry key value HKEY_LOCAL_MACHINE \ SOFTWARE \ Veritas \ NetBackup \ BEDS \ Engine \ Misc \ BescLargeDiscBlock to 68 and I started the job but still the same thing
https://www.veritas.com/support/en_US/article.TECH206217
4) To registre the VSS, the OS is already Windows 2008 R2 SP1 (so Nothing to do)
https://www.veritas.com/support/en_US/article.000015843
5) I rebooted the server several times, but still the same problem
Version: 1.0.0.7
Is this the most verbose bpbkar log you can provide? For example, bpbkar enumerates the providers.
Michael suggested that you may not have enough space allocated to snap the G: drive. You can use vssadmin to answer check your snapshot limit.
You migrated to 7.6.0.4? Why not 7.7.x?
I tested this solution and I runed the job, but still the same results.
Please find attached the log files of bpbkar:
01:18:12.987 [8052.10876] <4> dos_backup::tfs_scannext: INF - detected renamed/new directory:<G:\NBU_Catalog>, forcing full backup
01:18:12.987 [8052.10876] <2> tar_base::V_vTarMsgW: INF - Excluded: G:\NBU_Catalog
01:18:12.987 [8052.10876] <4> dos_backup::tfs_scannext: INF - detected renamed/new directory:<G:\System Volume Information>, forcing full backup
01:18:12.987 [8052.10876] <4> dos_backup::tfs_scannext: INF - detected renamed/new file:<G:\System Volume Information\tracking.log>, forcing backup
01:18:13.003 [8052.10876] <4> dos_backup::tfs_scannext: INF - no more path list entries
01:18:13.003 [8052.10876] <4> tar_backup::backup_endarg_state: INF - finish error count: 0
01:18:13.003 [8052.10876] <4> tar_backup::backup_endarg_state: INF - finish fatal count: 0
01:18:13.003 [8052.10876] <4> tar_backup_tfi::backup_arg_state: INF - remember start error count: 0
01:18:13.003 [8052.10876] <4> tar_backup_tfi::backup_arg_state: INF - remember start fatal count: 0
01:18:13.003 [8052.10876] <4> dos_backup::tfs_scanstart: INF - starting scan for file directive:<System State:\>
01:18:13.003 [8052.10876] <4> dos_backup::tfs_scanstart: INF - starting scan using name:<System State:\>
01:18:13.003 [8052.10876] <4> dos_backup::tfs_scanstart: INF - in 'backup' mode
01:18:13.018 [8052.10876] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x2 Failed! (0xE000FEC3:A failure occurred accessing the SnapShot coordinator.
)
01:18:13.018 [8052.10876] <2> tar_base::V_vTarMsgW: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.
01:18:13.018 [8052.10876] <4> tar_backup_tfi::backup_done_state: INF - number of file directives not found: 3
01:18:13.018 [8052.10876] <4> tar_backup_tfi::backup_done_state: INF - number of file directives found: 5
01:18:13.018 [8052.7888] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
01:18:13.018 [8052.10876] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
01:18:13.018 [8052.10876] <4> send_msg_to_monitor: INF - in send_msg_to_monitor()...
01:18:13.034 [8052.10876] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 69: invalid filelist specification
01:18:13.034 [8052.10876] <4> tar_backup_tfi::backup_done_state: INF - Not waiting for server status
01:18:14.048 [8052.10876] <4> dos_backup::ClearDFSRArchiveBits: INF - no DFSR file list was created, No bits cleared.
01:18:14.048 [8052.10876] <4> ov_log::OVLoop: Timestamp
01:18:14.048 [8052.10876] <4> OVStopCmd: INF - EXIT - status = 0
01:18:14.048 [8052.10876] <2> tar_base::V_Close: closing...
01:18:14.048 [8052.10876] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
01:18:14.064 [8052.10876] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000101
01:18:14.064 [8052.10876] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): ubs specifics: 0x001d0000
01:18:14.204 [8052.10876] <16> dtcp_read: TCP - failure: recv socket (580) (TCP 10053: Software caused connection abort)
01:18:15.218 [8052.10876] <16> dtcp_read: TCP - failure: recv socket (580) (TCP 10053: Software caused connection abort)
01:18:16.232 [8052.10876] <16> dtcp_read: TCP - failure: recv socket (580) (TCP 10053: Software caused connection abort)
01:18:17.246 [8052.10876] <16> dtcp_read: TCP - failure: recv socket (580) (TCP 10053: Software caused connection abort)
01:18:17.246 [8052.10876] <4> OVShutdown: INF - Finished process
01:18:17.246 [8052.10876] <4> WinMain: INF - Exiting D:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
