|
|
Explanation: The connection between the client and the server was broken. This status code can also appear if the connection is broken between the master and the media server during a backup.
Recommended Action: Do the following, as appropriate:
Try pinging the client from the server. If pinging is not possible, check for loose connections or other network problems.
Verify that the server list settings are correct on both the client and the server. If the backup involves a media server, verify that these entries are correct on both the master and the media server. For example, if a media server does not have a server list entry for the master, it does not accept connections from the master.
On Windows, the master server is designated on the Servers tab in the Master Server Properties dialog box.
See "Using the Host Properties Window" in the Troubleshooting Guide.
On UNIX, Linux, and Macintosh systems the master server is the first SERVER entry in the bp.conf file.
On NetWare target clients the master server name is the first SERVER entry in the bp.ini file.
If you change the server list on a UNIX or Linux master server, for the changes to take effect you must do the following: Stop and restart the NetBackup Request daemon (bprd) and NetBackup database manager daemon (bpdbm). On Windows, stop and restart the NetBackup Request Manager and NetBackup database manager services.
Status code 40 can also be due to denial of a mount request by the operator.
This status code may occur if nbjm was unable to connect to bpbrm or to bpmount. Examine the nbjm unified log (originator ID 117) or the bpbrm or the bpmount legacy logs for more detail on the cause of the error.