04-09-2018 12:28 AM
Hello, I have 636 errors that only happen on FULL backups and only on some saved drives / FSs.
The problem is on different machines: windows NT AIX REDHAT
On the WINDOWS NT backup, I have this concern; 06/04/2018 19:00:31 - Error bpbrm (pid = 7448) from client HUIXTOCI: ERR - failure reading file: E: \ oracle \ ora81 \ network \ log \ sqlnet.log (WIN32 13: Invalid data. ) read from input socket failed (636)
On UNIX / LINUX servers only this message: read from input socket failed (636)
The DIFFs go very well and when I restart the job in error manually, it passes.
Do you have any ideas ? Thank you.
Solved! Go to Solution.
04-09-2018 03:19 AM
Quite a number of similar discussions here on VOX:
https://vox.veritas.com/t5/NetBackup/Backup-failure-with-error-code-636/td-p/659294
https://vox.veritas.com/t5/NetBackup/Error-636/td-p/770527
https://vox.veritas.com/t5/NetBackup/Inactive-TCP-session-error-636-firewall/m-p/766864
https://vox.veritas.com/t5/NetBackup/Having-trouble-with-636-status-code/td-p/654986
In summary - the general recommentation is to change TCP KeepAlive setting to the same value on the master, media server and client.
04-09-2018 03:19 AM
Quite a number of similar discussions here on VOX:
https://vox.veritas.com/t5/NetBackup/Backup-failure-with-error-code-636/td-p/659294
https://vox.veritas.com/t5/NetBackup/Error-636/td-p/770527
https://vox.veritas.com/t5/NetBackup/Inactive-TCP-session-error-636-firewall/m-p/766864
https://vox.veritas.com/t5/NetBackup/Having-trouble-with-636-status-code/td-p/654986
In summary - the general recommentation is to change TCP KeepAlive setting to the same value on the master, media server and client.