For Error code 249:
This is occured basically when the server timed out while waiting for the client to finish sending the file list.
The timing issue involves contention for the
bpdbm process between
bpbrm and
bptm. The result of this contention is that
bpdbm is processing a long request from
bpbrm and the request made by
bptm times out before it is fulfilled.
The solution to this is to create a touch file on the master server to adjust the timeout threshold. By default, the timeout parameters are 5 retries with a sleep interval of 60 seconds. This default can be adjusted with the introduction of a touch file called "
FFREADtries".
The location of the
FFREADtries file for:
UNIX:
/usr/openv/netbackup/
Windows:
..\veritas\netbackup\.
Once the file has been created, values can be added to adjust the default settings. For instance 20 60 can be added to make it have 20 tries with a sleep interval of 60 seconds.
Note:
A cycling of the Master Server services may be necessary to activate the timeout threshold introduced by the
FFREADtries file.
FYI:
http://seer.entsupport.symantec.com/docs/285252.htm
For Error code 42:
All client backups using a particular media server fail, and exit with a NetBackup Status Code 42, network read failed\
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.
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.
To know how to add the media server's media server list, follow the procedure in the TN given below.
http://seer.entsupport.symantec.com/docs/251899.htm