We have some problems with VEB in middle sized organizations. I think it can be useful to write about it, because we have a scenario typical for middle sized paying customer

Generally we are happy with this product, it has big potential but need a lot of improvement for enterprise users. I also use VEB for home with no problems.
Description:
HQ:
Veeam Backup & Replication Enterprise
VMware vSpehere with 5 hosts (3 for servers VM, 2 for VDI)
One NAS on site
One NAS on remote site
Two physical servers
28 branch offices with local branch office server with VEB. Some of them are connected with HQ with slow 2Mbs line.
On these servers we want to backup to HQ only one directory with 2-20GB of data in case of total disaster of branch office. Changes are about 30-200MB/day, so is it not huge amount of data to backup. For backup target we choose Veeam Repository in our HQ on NAS.
Problem 1:
When VEB calculate digest and source directory has 20GB, it takes 7-8 hours on 2Mbs line. And it will eat a whole line. VEB calculate delta file against previous backup on the remote repository. We are able to plan backup in the night, but we would prefer to cut the backup time down. We would prefer to have the archive of backup copies on local server and then transfer it to remote Repository, so VEB will calculate the delta file against the local copy, not a remote backup.
Problem 2:
When we press cancel during calculating digest, we have to wait to end of this operation (sometimes several hours). We need to have a choice to cancel the operation in minutes, not hours.
Problem 3:
When the line fails and scheduled backup did not run, VEB begin the backup again. And we got to the problem no. 2.

Problem 4:
For us is very important, that we have only one console to check backup jobs on daily basis. This is why we choose VEB. But there are a only few features, which we can control or see. It would be great to have a full control over VEB through console. Now we have to log on to 28 servers to make some changes on VEB.
Problem 5:
We need more granularity on backup schedule. Windows Task Scheduler is great example. In our case we do not need backup in weekends, because there are no changes to backup.
I understand that VEB is for free, but we have no problem to pay for some "enterprise" features or an enterprise version of VEB.
Thank you for reading this to the end.