09-22-2016 07:48 AM
Master/media/client win 2012 r2 and all version 7.7.1
There is firewall in between master and media.
when schedule backup from master backup parent job getting failed with statu 636 and subsequent application backup successfully completed.
followed veritas technote and set keepAliveTime to 900000 on master/media aftre that servers are rebooted but same issue is repeating.
alos set client read and connect timeout from 300 to 900 on all master/media/client
please help on this. alos let know in batch script where i can put the VDI time out value. Is that i need to put inside every db in the script.
VDITIMEOUTSECONDS 900
Solved! Go to Solution.
09-23-2016 01:04 AM
When there is a firewall you should always change the TCP Keepalive to less than the firewalls idle session timeout which is usually something like 5 minutes. This should be done on both servers and clients to stop sessions being closed by the firewall.
If you running one script for the database you only need to put the VDITIMEOUTSECONDS 900 in once, can't remember exactly where it goes, but near the top would make sense.
09-26-2016 05:27 AM
Hi Michael Thanyou so much for you support!
After Setting the KeepAliveTime to 240000 on Master/Media the SQL parent job is not failing and subsequent Default-Application-Schedule backups are completed successfully
09-23-2016 01:04 AM
When there is a firewall you should always change the TCP Keepalive to less than the firewalls idle session timeout which is usually something like 5 minutes. This should be done on both servers and clients to stop sessions being closed by the firewall.
If you running one script for the database you only need to put the VDITIMEOUTSECONDS 900 in once, can't remember exactly where it goes, but near the top would make sense.
09-23-2016 05:13 AM
Hi Michale,
Thanks for the information. I will try reduce and keepalivetime to 250000 and also try VDI timeout.
09-26-2016 05:27 AM
Hi Michael Thanyou so much for you support!
After Setting the KeepAliveTime to 240000 on Master/Media the SQL parent job is not failing and subsequent Default-Application-Schedule backups are completed successfully