If this is only happening to one client, the issue is likely some kind of intermittent network issue between the client and the server. If you set up ping to run through the backup window and log the results to a file, you should be able to see if the network is dropping.
We see this on some of our replication streams every few days. I'd be curious to hear what you find, especially if it ends up being something other than a loss of network connectivity.
fdxpilot, you may want to work with support for your issue. If it's happening every few days, it sounds like there's something happening on the system that should be looked at.
I see you're way ahead of me! L2 support is already working with Engineering on your issue.
We definitely do our part to keep support and engineering employed. The more eyes on our SRs and ESCs the better. :-) Hopefully sandcruise will open an SR and finds a resolution for the backup issue, too.
fdxpilot, you may want to work with support for your issue. If it's happening every few days, it sounds like there's something happening on the system that should be looked at.
I see you're way ahead of me! L2 support is already working with Engineering on your issue.
The message itself is generic -- it just means that the client has sent messages to the server and hasn't received a reply for (300|600|900|...) seconds. This can happen if there are network issues but it can also happen if the server is read only, under heavy load, etc..
fdxpilot, you may want to work with support for your issue. If it's happening every few days, it sounds like there's something happening on the system that should be looked at.
ionthegeek
2 Intern
•
2K Posts
0
March 7th, 2013 06:00
If this is only happening to one client, the issue is likely some kind of intermittent network issue between the client and the server. If you set up ping to run through the backup window and log the results to a file, you should be able to see if the network is dropping.
fdxpilot
2 Intern
•
143 Posts
0
March 7th, 2013 12:00
We see this on some of our replication streams every few days. I'd be curious to hear what you find, especially if it ends up being something other than a loss of network connectivity.
fdxpilot
2 Intern
•
143 Posts
0
March 7th, 2013 14:00
We definitely do our part to keep support and engineering employed. The more eyes on our SRs and ESCs the better. :-) Hopefully sandcruise will open an SR and finds a resolution for the backup issue, too.
ionthegeek
2 Intern
•
2K Posts
0
March 7th, 2013 14:00
I see you're way ahead of me! L2 support is already working with Engineering on your issue.
ionthegeek
2 Intern
•
2K Posts
0
March 7th, 2013 14:00
The message itself is generic -- it just means that the client has sent messages to the server and hasn't received a reply for (300|600|900|...) seconds. This can happen if there are network issues but it can also happen if the server is read only, under heavy load, etc..
fdxpilot, you may want to work with support for your issue. If it's happening every few days, it sounds like there's something happening on the system that should be looked at.
sandcruise
11 Posts
0
March 29th, 2013 04:00
It doesn't seems to be a communication issue, the on-demand backup completes successfully, only the scheduled backup fails.
ianderson Do you think that upgrading the avamar linux client plugin to a newer version can help us as the client is at a lower version than server
fdxpilot If you find a resolution to the issue, please update
Thanks in advance