Troubleshooting guide

Status Codes
116 NetBackup Troubleshooting Guide - UNIX
◆ On other PC clients except Macintosh, create an activity log directory for bpcd
(the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the logging topics
in Chapter 3.
5. Retry the operation and check the resulting activity logs.
6. On Novell systems, check the following:
◆ For the nontarget version of NetBackup for NetWare, the backup class type must
be “NetWare”, and the files list should include a forward slash (/) only. There
should be nothing else in the files list.
To check the class type and files list, start Backup Policy Management and
right-click the name of a class. Click the Attributes tab to check the class type; click
the Files tab to check the contents of the files list.
◆ For the target version, the backup class type must be “Standard”, and the class
files list must be formatted as follows:
/target_name
where a forward slash precedes the variable target_name.
To check the class type and files list, start Backup Policy Management and
right-click the name of a class. Click the Attributes tab to check the class type; click
the Files tab to check the contents of the files list.
Note For the target version, the following NetWare message may be another indicator of
incorrect class type (this message would appear in the Novell client’s bpcd log):
unable to connect to service, scheduled access not specified
Make sure the class type is set to “Standard”.
Status Code: 72
Message: the client type is incorrect in the configuration database
Explanation: The class type attribute in the class configuration indicates that the client is
one type, but the installed software is for another type.
Recommended Action: Verify that the class type attribute for the class is correct. Also, for
UNIX, do not place Apollo and standard clients in the same class.
Status Code: 73
Message: bpstart_notify failed