STATUS CODE 42: When running a backup of all clients using a particular media server, all backups fail with Exit Status 42, network read failed.

Problem

STATUS CODE 42: When running a backup of all clients using a particular media server, all backups fail with Exit Status 42, network read failed.

Error Message

<16> logERROR: cannot log message to error database, error = network read failed
<16> get_image_info: db_getIMAGE() failed: network read failed (42)
<2> send_brm_msg: ERROR 42
<2> bptm: EXITING with status 42 <----------

Solution

Overview:  
All client backups using a particular media server fail, and exit with a NetBackup Status Code 42, network read failed.  

Troubleshooting:
Enable the bptm log file on the media server by creating the folder /usr/openv/netbackup/logs/bptm on UNIX media servers and <install_path>\VERITAS\NetBackup\logs\bptm on Windows media servers.

Log files:
The bptm log file will show the following error message:
<2> logconnections: BPDBM CONNECT FROM 10.30.20.45.1408 TO 10.10.20.45.13721
<2> get_string: read 0 of 8 bytes from socket
<2> get_string: (8) network read() error:  An existing connection was forcibly closed by the remote host.
<2> db_getdata: get_string() failed: An existing connection was forcibly closed by the remote host.  (10054) network read error (-3)
<2> db_startrequest: protocol error 1
<2> db_begin: db_startrequest() failed: network read failed
<2> get_long: (1) cannot read (byte 1) from network: An existing connection was forcibly closed by the remote host.
<2> db_getdata: get_string() failed: An existing connection was forcibly closed by the remote host.  (10054) network read error (-3)
<2> db_end: no DONE from db_getreply(): network read failed
<2> db_ERROR: db_begin() failed: network read failed
<16> logERROR: cannot log message to error database, error = network read failed
<16> get_image_info: db_getIMAGE() failed: network read failed (42)
<2> send_brm_msg: ERROR 42
<2> bptm: EXITING with status 42 <----------

Resolution:
When the media server is trying to connect to the master server, the connection is being rejected by the master because the media server is not on the master server's list of media servers. It is also possible that the media server does not have an entry of itself in the server list on the media server.

To resolve this error, add the media server to the master server's media server list. Check the media server and verify the media server name is there on it's own server list.

UNIX master server:
Add the following entry to /usr/openv/netbackup/bp.conf.
SERVER = <MediaServerName>

When no backups or restore operations are running stop and restart the NetBackup daemons for the changes to take effect.

Windows master server:
From the Admin Console | Host Properties | Master Server, proceed to the Server tab and add the media server to the server list.
When no backups or restore operations are running stop and restart the NetBackup Services for the changes to take effect.

OR

Add the media server to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
Name: SERVER
Type: REG_MULTI_SZ
Data: <MediaServerName>

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

When no backups or restore operations are running stop and restart the NetBackup Services for the changes to take effect.
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)