12-07-2012 03:07 AM
HI all ,
backup of Windows client is failing with 69 error - invalid filelist specification
12/04/2012 20:00:03 - Error bpbrm (pid=20889) from client xxx.xxx.xxx.com ERR - ALL_LOCAL_DRIVES file list directive invalid for policy type.
12/04/2012 20:00:03 - connecting
12/04/2012 20:00:03 - connected; connect time: 0:00:00
12/04/2012 20:00:04 - Info bptm (pid=20897) start
12/04/2012 20:00:04 - Info bptm (pid=20897) using 1048576 data buffer size
12/04/2012 20:00:04 - Info bptm (pid=20897) setting receive network buffer to 262144 bytes
12/04/2012 20:00:04 - Info bptm (pid=20897) using 128 data buffers
12/04/2012 20:00:05 - Info bptm (pid=20897) start backup
12/04/2012 20:00:06 - Info bptm (pid=20897) backup child process is pid 20909
12/04/2012 20:00:06 - Info bptm (pid=20897) waited for full buffer 0 times, delayed 0 times
12/04/2012 20:00:06 - begin writing
12/04/2012 20:00:15 - Info bptm (pid=20897) EXITING with status 90 <----------
12/04/2012 20:00:16 - Info bpbkar (pid=15663302) done. status: 69: invalid filelist specification
12/04/2012 20:00:16 - end writing; write time: 0:00:10
invalid filelist specification (69)
Its not new server , suddenly it started failing and vssadmin list writers also works fine , please suggest ..
12-07-2012 03:13 AM
ERR - ALL_LOCAL_DRIVES file list directive invalid for policy type.
What is the policy type?
Please show us policy config:
bppllist <policy-name> -U
12-07-2012 03:21 AM
hi Marriane,
Policy type is MS-WINDOWS
12-07-2012 03:25 AM
Can you please provide the complete outpuot for the bppllist command mentioned above.
Also do you see any error messages on the event viewer (on client ) during the backup.
12-07-2012 03:27 AM
HI,
Run the following Command from cmd
Type "installation path"/ netbackup/bin/admincmd directory:
bppllist <policy-name> -U
12-07-2012 03:35 AM
This issue can occur because the VSS system files are not registered properly.
The Article Includes an executable to resolve the issue or the following steps can be executed manually:
Note: The last commands may not run successfully if you do not have any of the listed dll's on your system.
Check the Status of VSSADMIN LIST WRITERS and then test a backup operation of the client system.
12-07-2012 04:29 AM
We also see a status 90:
12/04/2012 20:00:15 - Info bptm (pid=20897) EXITING with status 90 <----------
12/04/2012 20:00:16 - Info bpbkar (pid=15663302) done. status: 69: invalid filelist specification
Please provide policy output as well as client details:
Windows version on client
NBU version and patch level on client
Has this worked before, or is this a new client?
Can you confirm that port connectivity as well as forward and reverse lookup between master and client is fine?
12-07-2012 02:31 PM
Status 90 can sometimes indicate VSS/snapshot problems. Can you check the Volume Shadow Copy service as well as the Symantec SymSnap services? (I don't know exact names as you didn't provide Windows version) - although it might be better to just reboot than to try to find individual services to stop and restart. Syed's list of instructions looks a little scary to me (as a UNIX guy).
12-07-2012 08:24 PM
@Syed, when you quote from a Technote, please ALWAYS mention the URL.
http://www.symantec.com/docs/TECH164829
The TN references a Microsoft KB article that "Includes an executable to resolve the issue".
12-20-2012 10:36 PM
Thank you all for your suggestions,I will check on them and we have issue with network connectivity , team is working on that .