636 read from input socket failed
Hi, All backups got failed with error 636 due to network connectivity issue between master and media server ( master and media servers are in different networks). Is there any solution for the backu...
Forum Discussion
Does normal communications between master and media server work ?
Are the requested ports opened between them ?
Use the bpclntcmd test to verify how Netbackup looks at this connection
How to verify name resolution for NetBackup (tm) systems, using the "bpclntcmd" command
https://www.veritas.com/support/en_US/article.TECH27430
nbutech wrote:Does normal communications between master and media server work ?
Are the requested ports opened between them ?
Hi
Below is the scenario.
some full backups were running for 9 days and and all of them got errroed (error code 636) due to firewall connectivity issue( network failure) which is between master and media network. The issue got resolved within 2 hours and I couldn't resume the jobs since all are in errored status. I had to resubmit all the jobs from the scratch and lost 9 days time frame. So I want to know if there any option for avoiding this kind of errors in the future.
Thanks
Rajesh
This setup sounds like all kinds of wrong to me.
Why have a firewall if it allows idle connections for more than a day ?
Backups shouldn't run for more than a day either, I would claim a backup that as run for more than week is as good as worthless. Besides that you way too vunerable to glitches within that timeframe as you have discovered.
Really think this needs to be redesigned with focus on backup performance. See the Planning and Performance Tuning guide.
