Video Screencast Help

backup failing with 69 error(invalid filesystem specification)

Created: 07 Dec 2012 | 9 comments

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 ..

 

Comments 9 CommentsJump to latest comment

Marianne's picture

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

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

Deepak G's picture

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.

Syed saied's picture

HI,

Run the following Command from cmd

Type "installation path"/ netbackup/bin/admincmd directory:

bppllist <policy-name> -U

 

Thanks In Advance...

Syed Saied

If the suggestion has helped to solve your problem, please mark the post as a solution

Syed saied's picture

This issue can occur because the VSS system files are not registered properly.

Solution

The Article Includes an executable to resolve the issue or the following steps can be executed manually:

  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
  3. On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
  4. Exit Registry Editor.
  5. Click Start, click Run, type services.msc, and then click OK.
  6. Right-click the following services one at a time. For each service, click Restart:
    • COM+ Event System
    • COM+ System Application
    • Microsoft Software Shadow Copy Provider
    • Volume Shadow Copy
  7. Now register the associated DLLs
  8. Click Start, click Run, type cmd, and then click OK.
  9. Type the following commands at a command prompt. Press ENTER after you type each command.
  10. cd /d %windir%\system32
  11. Net stop vss
  12. Net stop swprv
  13. regsvr32 ole32.dll
  14. regsvr32 oleaut32.dll
  15. regsvr32 vss_ps.dll
  16. vssvc /register
  17. regsvr32 /i swprv.dll
  18. regsvr32 /i eventcls.dll
  19. regsvr32 es.dll
  20. regsvr32 stdprov.dll
  21. regsvr32 vssui.dll
  22. regsvr32 msxml.dll
  23. regsvr32 msxml3.dll
  24. regsvr32 msxml4.dll

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.

 

 

Thanks In Advance...

Syed Saied

If the suggestion has helped to solve your problem, please mark the post as a solution

Marianne's picture

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?

 

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

CRZ's picture

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).


bit.ly/76LBN | APPLBN | 75LBN

Marianne's picture

@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".

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

siri416's picture

Thank you all for your suggestions,I will check on them and we have issue with network connectivity , team is working on that .