Backup failling with error code 69(invalid filelist specification)

[sanjaynaidu]

Backup is failling with 69 error in one of the windows 2008 client.

Media server and client is same windows 2008 server with veritas 7.5.6

Master server is : Linux  2.6.32-279.22.1.el6.x86_64 #1 SMP Tue Feb 5 12:18:08 PST 2013 x86_64 x86_64 x86_64 GNU/Linux.

could see that incremental backups are successfully, only full and accelerator backups are failing.

Please find the logs:

Lease find the logs investigating furthur....
07/01/2014 02:42:33 - Error bpbrm (pid=25728) from client ABC: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.JBD - accelerator sent 69766473728 bytes out of 69655629312 bytes to server, optimization 0.0%
07/01/2014 02:42:35 - Error bptm (pid=25730) media manager terminated by parent process
07/01/2014 02:42:51 - Info prdbks (pid=25730) StorageServer=PureDisk:prd; Report=PDDO Stats for (prd): scanned: 68024213 KB, CR sent: 614372 KB, CR sent over FC: 0 KB, dedup: 99.1%
07/01/2014 02:42:52 - Error bpbrm (pid=25728) could not send server status message
07/01/2014 02:42:53 - Info bpbkar (pid=3936) done. status: 69: invalid filelist specification
07/01/2014 02:42:53 - end writing; write time: 14:14:47
07/01/2014 02:42:55 - Info bpbrm (pid=6375) Starting delete snapshot processing
07/01/2014 02:42:55 - Info bpfis (pid=0) Snapshot will not be deleted
07/01/2014 02:42:58 - Info bpfis (pid=9676) Backup started
07/01/2014 02:42:58 - Critical bpbrm (pid=6375) from client ABC: cannot open D:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.ABC_1404156474.1.0
07/01/2014 02:42:58 - Info bpfis (pid=9676) done. status: 1542
07/01/2014 02:42:58 - Info bpfis (pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
invalid filelist specification  (69)

Could anyone Please give the solution for this issue on priority as backups are failling every day.

[RamNagalla]

Error bpbrm (pid=25728) from client ABC: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.

So what is the status of the VSS writers?

are they looking fine?

 check below commands

vssadm list writers

and make sure there is no errors.. 

also please post the bpbkar log for the failed job .

[watsons]

Check event logs as well, look for any VSS error: http://www.symantec.com/docs/TECH164829

[sanjaynaidu]

Hi Nagalla,

Thanks for ur immediate response, Please find VSS writer output and bpbkar logs as attachment.

Please verify and do the needful.

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: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Writer Instance Id: {f3954e6b-e95e-4c9c-a683-2ed47426a723}

   State: [1] Stable

   Last error: No error

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {68131529-b023-41ad-add1-00a46ca45fed}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Writer Instance Id: {1cd11dc3-24b0-49b8-a04d-adccececf5d8}

   State: [1] Stable

   Last error: No error

Writer name: 'BITS Writer'

   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

   Writer Instance Id: {9006dc0a-8e82-4e9b-9bb4-62314c1dfb2c}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {26a7b932-da95-473a-aa73-09fc247309c1}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {4cb839d6-b832-4d77-a2f4-de34ed57c116}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {9cdf4687-69e4-4587-ac9b-776c86816594}

   State: [1] Stable

   Last error: No error

[RamNagalla · Accepted solution]

by any chance does this client/media server have the disk which is haivng the size more than  57 TB,

 if yes please have  a look in below Tech note and do necessory changed suggested in T/N

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

Reference log from bpbkar log:-

8:06:36.033 AM: [8688.10232] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x400 Failed! (0xE000FEC3:A failure occurred accessing the SnapShot coordinator.
)

[sanjaynaidu]

Hi  Watson,

Thanks for ur quick response and technote.

Thanks for ur quick respone.

Hi Nagalla

Thanks for ur quick solution and your valuable tech note.

Moreover here our media server is having disk more than 62 TB size.

Worked on the issue by refering your tech note...

Issue got fixed and resolved.

ThankQ all once again for helping in sorting the issue.