Read from input socket failed (636)

Problem

Error "Read from input socket failed (636)" during the backup is reported by bpbrm on the Media Server.

This issue is observed in MS-Windows, VMware, FlashBackup and other backup types while using tape or disk storage.

Error 636 indicates that the network connection between bpbrm on the media server and bpbkar on the client has been broken.

Error Message

Read from input socket failed (636)
 

Cause

The read from an input socket failed. The underlying connection has been broken.

Solution

Increase the TCP/IP Keep Alive parameters as follows:

WINDOWS - Adjust the TCP  KeepAliveTime and KeepAliveInterval values

KeepAliveTime

Determines how often TCP sends keep-alive transmissions. TCP sends keep-alive transmissions to verify that an idle connection is still active. This entry is used when the remote system is responding to TCP. Otherwise, the interval between transmissions is determined by the value of the KeepAliveInterval entry.

KeepAliveInterval

Determines how often TCP repeats keep-alive transmissions when no response is received. TCP sends keep-alive transmissions to verify that idle connections are still active. This prevents TCP from inadvertently disconnecting active lines.

1. Open the registry editor in the Windows Media Server with regedit or regedt32.

2. Go to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
REG_DWORD: KeepAliveTime

*** If KeepAliveTime isn't there, create it ( value IS case sensitive)
New > DWORD (32 bit) Value > Hexadecimal 

3. Change the value of DWORD "KeepAliveTime" to : 0xDBBA0 (900000 milliseconds or 15 minutes)

The value can be increased or decreased as per the requirement in the media server.
Restart Windows for the changes to apply.

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.

LINUX Media and NetBackup Appliance

# echo 600 > /proc/sys/net/ipv4/tcp_keepalive_time
# echo 60 > /proc/sys/net/ipv4/tcp_keepalive_intvl
# echo 20 > /proc/sys/net/ipv4/tcp_keepalive_probes

TCP Setting Definitions

tcp_keepalive_time
- the interval between the last data packet sent and the first keepalive probe

tcp_keepalive_intvl
- the interval between subsequent keepalive probes

tcp_keepalive_probes
- the number of probes that are sent and unacknowledged before the client considers the connection broken and notifies the application layer

 

Related Articles:

VMware backup with "File Level Recovery" fails with Status 636 due to disconnect between Master and Media Server
https://www.veritas.com/content/support/en_US/article.100012397

Status 87 and Status 40 / 636 on long running Client side deduplication jobs across a slow connection
https://www.veritas.com/content/support/en_US/article.100009509