My internet connection has developed an issue where it has short, fairly frequent interruptions (last maybe 1 to 3 seconds). Comcast is working hard (really) to figure out what is going on. However, I use Retrospect to backup back from my office to my home and vice-versa (with my home machine always the client). Since this issue started, I have been getting frequent -519 errors (network communication failed). Sometimes the client reverts to Status=Ready and sometimes the client continues to be "in use" by the script that was using the client at the time of the interruption.
This morning I decided to do a backup with a remote access window open to the machine at home side by side with the local machine running retrospect. The backup proceeded normally until there was a short (about 2 second) internet interruption. The local machine showed "retrying" until it terminated the script with a -519 error, while the remote machine reverted to Status=Ready, even while the local machine was showing "retrying".
It appears to me that Retrospect is not very robust in reconnecting with a client if there is any kind of internet connection glitch. If I try the same thing with an FTP based backup solution (like SyncBack Pro), It easily recovers from the same kind of glitch.
I find no way of tweaking any of the client settings. Am I missing something or is this backup scenario problematic unless you have a perfect internet connection. I should note that I had no problems before my connection started weirding out.
I should note that I am running Retrospect Multi Server Version 7.6.123 (Driver Update and Hot Fix, version 18.104.22.168) on the local machine and Client 7.6.107 on the remote machine, both running Windows XP, Service Pack 3, with all current updates.