Troubleshooting guide

Status Codes
154 NetBackup Troubleshooting Guide - UNIX
◆ If the client is not in such a class, either add a schedule of the appropriate type to an
existing class that has this client or create a new class that has this client and a
schedule of the appropriate type.
Status Code: 199
Message: operation not allowed during this time period
Explanation: A user backup or archive has been requested and this client is not in a class
that has a user backup or archive schedule with an open backup window. This error
implies that there is an appropriate class and schedule combination for this client.
Recommended Action: Determine the classes to which this client belongs that also have a
schedule of the appropriate type (either user backup or archive).
◆ If possible, retry the operation when the backup window is open.
◆ If the backup window is not open during appropriate time periods, adjust a backup
window for a schedule in one of the classes.
Status Code: 200
Message: scheduler found no backups due to run
Explanation: When checking the class and schedule configuration, the NetBackup
scheduler process (bpsched) did not find any clients to back up. This could be due to:
◆ No backup time windows are open (applies only to full and incremental schedules).
◆ Classes are set to inactive.
◆ The clients were recently backed up and are not due for another backup (based on
Frequency setting for the schedules).
◆ Classes do not have any clients.
Recommended Action: Usually, this message can be considered informational and does
not indicate a problem. However, if you suspect a problem:
1. Examine the NetBackup All Log Entries report to see if there are any messages in
addition to one indicating that the scheduler found nothing to do.
2. Examine the class configuration for all classes or the specific class in question and
determine if any of the reasons mentioned in the Explanation section above apply.
3. To obtain detailed troubleshooting information, create a bpsched activity log
directory on the master server and retry the operation. Check the resulting activity
log.