Troubleshooting guide

Chapter 4, Status Codes and Messages 111
Status Codes
1. Execute a df to see if the system can read the mount table.
2. On an SCO system, code 60 can occur because the mount-point path name exceeds 31
characters, which is the maximum allowed on an SCO system. The bpbkar activity
log on the client will show a message similar to the following:
bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406
To eliminate these errors for future backups, create a mount point with a shorter name
and symbolically link the long name to the short name.
3. For detailed troubleshooting information, create a bpbkar activity log directory, retry
the operation, and examine the resulting log.
Status Code: 61
Message: wbak was killed
Explanation: The wbak process on the Apollo was killed.
Recommended Action: Try the backup again.
Status Code: 62
Message: wbak exited abnormally
Explanation: The wbak process on the Apollo exited abnormally.
Recommended Action: Try running wbak by hand to determine the source of the
problem. Direct the output of the wbak command to /dev/null to avoid filling up your
file system and use the following parameters:
-l -nhi -pdtu -stdout -nwla and -full or -af date
Status Code: 63
Message: process was killed by a signal
Explanation: A kill signal was sent to the client process.
Recommended Action: This is usually caused by someone intentionally terminating a
backup.
Status Code: 64
Message: timed out waiting for the client backup to start
Explanation: The client did not send a ready message to the server within the allotted
time.