I setup a backup job to store all my backups onto a USB HDD, and simply take it offline. This was after reading the scary Malware can delete your backups.
After creating my BCJ and set a interval of 30 days (as I want to update the drive once a month). I had an issue where apparently the BCJ defaulted to using any repo (That's nice when I only have one local and one offsite which is over a crappy 5 mbps connection) and I was surprised that one VM was stuck as resources have been defined and it wasn't moving. I figured what was the case when I had only one other BCJ running which uses my offsite repo, which is set to run only 1 job at a time (cause of the weak connection between my sites). This was how I discovered the default setting. So I changed it to use my local repo only and decided to re-sync the job.
Sure enough the task started, but I noticed it was transferring reallllly weird, so gapped. What could be causing this?!?!
Hello Zew,
You may enable more slots on the target repository to parallel writing operations.
As the picture shows the bottleneck is target, not network.
Thanks
Thanks for the quick reply, but I still don't get why it's hanging? The BCJ only copies one VM at a time, it should be a consistent write rate for a single VM copy process before moving to the next....
Is it maybe that the graph is showing some cache data, (vPower NFS or something) and I'm not actually seeing the actual writes to the USB drive?
