Restore fails with error "socket read failed errno = 62 - timer expired "

Restore fails with error "socket read failed errno = 62 - timer expired "

Article: 100006172
Last Published: 2013-03-29
Ratings: 1 1
Product(s): NetBackup

Problem

Restore fails with error "socket read failed errno = 62 - timer expired"
 

Error Message

Restore results in this message: Error bpbrm (pid=xxxxx) socket read failed: errno = 62 - Timer expired.

Error bpbrm client restore EXIT STATUS 13: file read failed

 

Cause

The NetBackup media server may not be able to send keepalives to the NetBackup client  if the read of  data is taking a long time to complete one buffer of data. When this occurs, the media server may time out after the time specified in the NetBackup Administration Console > Host Properties > Media Servers > Timeouts > Client Read Timeout configuration (300 seconds by default).

 

Solution

Check the value of Client Read Timeout for the media server used for restore.

In the NetBackup Administration Console: 

Host properties > Media Servers > Timeouts > Client Read Timeout

OR

On Unix media server look for the value of CLIENT_READ_TIMEOUT in /usr/openv/netbackup/bp.conf file. 

Set the CLIENT_READ_TIMEOUT value to a big number such as 3600, 7200 or 10800.
 


Was this content helpful?