neilpotter wrote:Bottleneck tends to be network if there have been a lot of new files through the day, or Source if there are a lot of changes, I assume because of CBT?
CBT is always used starting from the second run, so the stats should look more or less the same unless you're using different source datastore to retrieve VM data. In your case,if the more data you push the more it tends to be network bottleneck, then it could be indeed the expected behavior.
neilpotter wrote:For clarity, the proxy server is also the remote repo.
The RAM seems to maxed from when the job starts processing the info but I think it drops when files actually start to be transferred over. Its almost the first half an hour of the job when it's working out what needs to be transferred I think
Try increasing the RAM configuration, and let us know if that improves the server uptime or not.