FTL - [rpcess_fs_list() failed. Status 20
Begin with the difinition of error Status 20: invalid command parameter
Logon to the client
look at c:\Program Files\Veritas\NetBackup\Logs\BPFIS
bpfis main: recieve filelist:<NEWSTREAM>
bpfis main: recieve filelist:<Shadow Copy components:\>
bpfis main: recieve filelist:<NEWSTREAM>
bpfis main: recieve filelist:<C:\>
bpfis main: recieve filelist:<NEWSTREAM>
bpfis main: recieve filelist:<D:\>
bpfis main: recieve filelist:<NEWSTREAM>
bpfis main: recieve filelist:<E:\>
bpfis main: recieve filelist:<Continue>
devtomp: Matched GUID \\?\Volume {GUID} to device \Device\HardiskVolume2
onlfi_process_fs_list_fs_entry: Adding file system C:\ to list
devtomp: Matched GUID \\?\Volume {GUID} to device \Device\HardiskVolume3
onlfi_process_fs_list_fs_entry: Adding file system D:\ to list
pbfis: FTL - process_fs_list() failed, status 20
onlfi_thaw: Thawing C:\ using snapshot method VSS
onlfi_thaw: C:\ is not frozen
onlfi_thaw: Thawing D:\ using snapshot method VSS
onlfi_thaw: D:\ is not frozen
bpfis: WRN - snapshot delete returned status 20
bpfis: INF - exit status 20: invalid command parameter
fis_rebuild_from_db: cannot open c:\program files\Veritas\netbackup\online_util\fi_cntl\bpfis.fim<servername>_1258033296.0
=================================================================
The last statement seems to be the problem as the file does not exist.
My guess is that
A change to the virtual server, Or the NetBackup database is corrupt.
=================================================================
Comments
What the servity level of the line ?
Netbackup does a lot of "false positives" so it would be good if you can provide the severity number of the last two lines. The severity number is the number in <>
Severity:
1 = Unknown
2 = Debug
4 = Info
8 = Warning
16 = Error
32 = Critical
Assumption is the mother of all mess ups.
If this post solved you’re questions please send a gratitude by marking it as a solution.
<2> bpfis main: recieve
<2> bpfis main: recieve filelist:<NEWSTREAM>
<2> bpfis main: recieve filelist:<Shadow Copy components:\>
<2> bpfis main: recieve filelist:<NEWSTREAM>
<2> bpfis main: recieve filelist:<C:\>
<2> bpfis main: recieve filelist:<NEWSTREAM>
<2> bpfis main: recieve filelist:<D:\>
<2> bpfis main: recieve filelist:<NEWSTREAM>
<2> bpfis main: recieve filelist:<E:\>
<2> bpfis main: recieve filelist:<Continue>
<2> devtomp: Matched GUID \\?\Volume {GUID} to device \Device\HardiskVolume2
<2> onlfi_process_fs_list_fs_entry: Adding file system C:\ to list
<2> devtomp: Matched GUID \\?\Volume {GUID} to device \Device\HardiskVolume3
<2> onlfi_process_fs_list_fs_entry: Adding file system D:\ to list
<16> pbfis: FTL - process_fs_list() failed, status 20
<4> onlfi_thaw: Thawing C:\ using snapshot method VSS
<8> onlfi_thaw: C:\ is not frozen
<4> onlfi_thaw: Thawing D:\ using snapshot method VSS
<8> onlfi_thaw: D:\ is not frozen
<8> bpfis: WRN - snapshot delete returned status 20
<4> bpfis: INF - exit status 20: invalid command parameter
<32> fis_rebuild_from_db: cannot open c:\program files\Veritas\netbackup\online_util\fi_cntl\bpfis.fim<servername>_1258033296.0
Looks like possible a VSS issue
Have you tried switching to VSP and rerunning the backup?
Status code 20 is a classic indicator of mixed binaries
Make sure everything involved is at the same version. Client and master should match in this case. Your guess may be correct if one was "upgraded" but the other one wasn't...
(Did you happen to say what versions you were running? Why doesn't *everyone* do that when they start a thread here? ;-) )
1) CRZ Good point
1) CRZ
Good point !
Environment:
Windows
OS: Windows 2003 R2 x64
Symantec NetBackup: 6.5.4
Master/Media and all clients are at 6.5.4
upgrade was 2 months ago.
2) rjrumfelt
If all client backups are running then
"Have you tried switching to VSP and rerunning the backup?" seems irrelevant.
As an added note, this particular server is 1 node of a 2 node cluster.
3)
Refocusing on the issue:
<16> pbfis: FTL - process_fs_list() failed, status 20
<4> onlfi_thaw: Thawing C:\ using snapshot method VSS
<8> onlfi_thaw: C:\ is not frozen
<4> onlfi_thaw: Thawing D:\ using snapshot method VSS
<8> onlfi_thaw: D:\ is not frozen
<8> bpfis: WRN - snapshot delete returned status 20
<4> bpfis: INF - exit status 20: invalid command parameter
<32> fis_rebuild_from_db: cannot open c:\program files\Veritas\netbackup\online_util\fi_cntl\bpfis.fim<servername>_1258033296.0
When I attempt to execute a
When I attempt to execute a manual backup on my master/media server I get the following errors in the bpfis log:
Location: C:\Program Files\Veritas\NetBackup\Logs\bpfis
<8> onlfi_initialize_vfms: VfMS error 9; see following messages:
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libfi_auto.dll: the system cannot find the file specified
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libvfms.dll: the system cannot find the file specified
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libfi_FlashSnap.dll: the system cannot find the file specified
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libfi_vxvm.dll: the system cannot find the file specified
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libfi_VMware.dll: the system cannot find the file specified
<8> onlfi_initialize_vfms: Operating system error was reported
<8> onlfi_initialize_vfms: vfm_fi_init: access() error on library /usr/openv/lib/libfi_NAS_writer.dll: the system cannot find the file specified
Resolution to Master/Media Server access() error on library
A search of the Forums found the following link:
https://www-secure.symantec.com/connect/forums/snapshot-could-not-be-created-vmware-method
Copied the vfm.conf and pasted as Copy of vfm.conf
Opened the copy and made the changes suggested in the above link.
renamed vfm.conf to vfm.conf_Original
rename the Copy to vfm.conf
and executed a manual backup
backup was successful
Aha
Good catch, Souleman!
We DO have this in a TechNote, but of course you had to find the answer before I knew what I should have been searching . :)
If anybody comes across this thread, here's our document:
GENERAL ERROR: VMWare Consolidated Backups are failing with "FTL - process_fs_list() failed, status 20"
http://support.veritas.com/docs/305287
This TechNote specifically mentions VMware but not your situation, but the evidence all looks the same and so it the conclusion. Maybe we need to expand it a bit!
Would you like to reply?
Login or Register to post your comment.