Troubleshooting guide

Status Codes
84 NetBackup Troubleshooting Guide - UNIX
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!
If this error is encountered, try one of the following (the first is preferred):
◆ Set maximum OTM cache size to zero (0); at run time, OTM will determine how
much cache is needed and set it accordingly.
◆ Increase either the initial OTM cache size or the maximum OTM cache size on
your own, depending on the requirements of your installation and your usage of
OTM.
If resizing OTM cache does not fix the problem, you may not have enough free disk
space.
Status Code: 12
Message: file open failed
Explanation: An open of a file failed.
Recommended Action: Check the NetBackup Problems report. Try to determine the file
and why the error occurred. A possible cause is a permission problem with the file. For
detailed troubleshooting information, create an activity log directory for the process that
returned this status code. Then, retry the operation, and check the resulting activity log.
Status Code: 13
Message: file read failed
Explanation: A read of a file or socket failed. Possible causes include:
◆ I/O error reading from the file system.
◆ Read of an incomplete or corrupt file.
◆ Socket read failing. A socket read failure can be caused by a network problem or a
problem with the process that is writing to the socket.
Recommended Action:
1. Check the NetBackup Problems report for clues on where and why the problem
occurred.
2. For a FlashBackup client, check the /var/adm/messages log for errors like the
following:
Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache
/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable