Troubleshooting guide

Chapter 4, Status Codes and Messages 161
Status Codes
1. Verify that the NetBackup database manager (bpdbm) process (NetBackup Database
Manager service on Windows NT/2000) is running.
2. Examine the All Log Entries report for the appropriate time frame to gather more
information about the failure.
3. For detailed troubleshooting information, create activity log directories for bpsched
and bpdbm on the master server and retry the operation. Then, check the resulting
activity logs.
Status Code: 208
Message: failed reading user directed file list
Explanation: An error occurred when the backup scheduler (bpsched) attempted to read
the list of files requested for a user backup or archive. This error indicates either a
client-server communication problem, or a system problem on the master server where
the NetBackup scheduler process (bpsched) is running.
Recommended Action: For detailed troubleshooting information, create activity log
directories for bpsched and bprd on the master server and retry the operation. Then,
check the resulting activity logs.
Status Code: 209
Message: error creating or getting message queue
Explanation: An error occurred when the backup scheduler (bpsched) attempted to
create an internal message queue construct for interprocess communication. This error
indicates a problem on the master server and is most likely due to a lack of system
resources for System V interprocess communication.
Recommended Action: Create a bpsched activity log directory on the master server and
retry the operation. Then, determine the type of system failure by examining the error
message in the bpsched activity log.
On UNIX servers, also gather the output of the ipcs -a command to see what system
resources are currently in use.
Status Code: 210
Message: error receiving information on message queue
Explanation: An error occurred when one of the backup scheduler (bpsched) processes
attempted to receive a message from another bpsched process on an internal message
queue construct. This error indicates a problem on the master server and is likely due to
problems with or a lack of system resources for System V interprocess communication.