I looked into this and it appears that BESR basically moves the recovery point from the backup destination to the source server and then copies it to the offsite copy location - this clearly explains the performance problems you describe.
We are in the process of logging a request to see if the code can be changed so this process is more efficient. This may take some time but we are aware of the issue and your concerns so thanks for reporting this.
Let me know if you have any further questions on this subject.
1. Do you know if the code has been changed yet? Or if not when it will be? I only ask as I'm using BESR to image eight servers and the current way BESR works means a lot of data heading over the network.
2. It would seem that if you are using the BESR Managment Solution you can configure a Dedicated Offsite Copy Task and assign this task to a single computer. This single computer is then responsible for copying images from onsite destination to offsite desination. Is there any way to configure a Dedicated Offsite Copy Task when you aren't using BESR Managment Solution?