In an effort to combat that, I've repeated the command multiple times in the script. This way, if the script aborts, it can start up again. Or that was the theory, anyway.
The problem is that when the script aborts, the window doesn't terminate. If I cancel the window, the script automatically starts again as expected. The user intervention required, however, sort of defeats the purpose.
Note this problem is more likely to happen the more network traffic there is, for example, online backups also occurring at the same time.
I really just need something that is more fault-tolerant. I don't really care what it errored on if it can simply resync again after a retry.