NetBackup status code: 142
Message: file does not exist
Explanation: To back up a VxFS file system with Snapshot Client, the VxFS file system on the client must be patched with correct, dynamically linked libraries. If the correct VxFS libraries are not installed, the backup fails with status 142.
The following appears in the log:
For most snapshot backups, the following message appears in the
/usr/openv/netbackup/logs/bpfislog on the client:09:36:48.299 [527] <32> fs_dev_rt_check: FTL - snapshot method: nbu_snap abort - required VxFS dynamic linked libraries for NetBackup are not installed. Please visit the Veritas support website, and refer to Technote number 262225 for further information.
For the backups that run from a FlashBackup policy, the following appears in the
/usr/openv/netbackup/logs/bpbkarlog on the client:10:09:56.566 [1146] <32> bpfsmap: FTL - bpfsmap: FlashBackup abort - required VxFS dynamic linked libraries for NetBackup are not installed. Please visit the Cohesity Technical Support website, and refer to Technote number 262225 for further information. 10:09:56.571 [1146] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 142: file does not exist 10:09:56.573 [1146] <4> bpbkar Exit: INF - EXIT STATUS 142: file does not exist
The bpexpdate, bpimmedia, bpimport, and bpverify commands return this status code if you cannot gather disk pool, disk volume, disk pool volume, disk media IDs, or server type information.
The bpbkar returns this status code if a checkpoint clone is missing, or if a frozen image backup does not return the snapshot information.
Recommended Action: Install the VxFS dynamic libraries on the NetBackup client and try the backup again.
Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.