Forum Discussion
Basically you need to solve the network connectivity, and you should not go for incomplete but successfully backups.
But without more information we will not be able you. Need information like Server OS, are there firewall between master and media.
- Rajeshgang8 years agoLevel 3
OS -Linux
Firewall is there between media and master
- Rajeshgang8 years agoLevel 3
Michael_G_Ander wrote:Basically you need to solve the network connectivity, and you should not go for incomplete but successfully backups.
---
Due to errored jobs we are forced to start backups from the beginning whcih actually waste the time.
In case any connectivity issue happens between master and media then the backup jobs( especially full backups) will get the status incomplete? then we can resume the jobs once the network issue get solved.
Rajesh
- Michael_G_Ander8 years agoLevel 6
Set the TCP keepalive on master, media and clients to less than the firewall idle session timeout (Usually around 5 minutes)
- Rajeshgang8 years agoLevel 3
Michael_G_Ander wrote:Set the TCP keepalive on master, media and clients to less than the firewall idle session timeout (Usually around 5 minutes)
Hi Michael,
Here are the configurations currently we have
tcp keep alive interval on firewall - 36 hours
net.ipv4.tcp_keepalive_intvl = 60 seconds on both master and media server
net.ipv4.tcp_keepalive_time = 549 seconds on both master and media server
Thank you all for the valuable replies.
- Marianne8 years agoLevel 6
For failed jobs to go to Incomplete status that can be resumed, you need to enable Checkpoints in Policy Attributes.
This option is only available for Standard and MS-Windows policy types - not for Agent policy types.
Related Content
- 12 years ago
- 12 years ago
- 10 years ago