IMHO, relying on restore points is a less ideal method for keeping retention in check. It just makes things more complex than it need to be. Retention based on age is a much simpler (reliable) retention method. With restore point method I have to make sure I count how many restore points i'm going to use. If i decided to run a few one off backups, now I have to make sure I temporarily increase my restore points. It would be so much easier if it just kept data for "x" period of time, no matter how many backup's a made. On top of that, a great option to go with it, would be the ability to delete a restore point and basically merge the blocks in (mid-stream if need be). I've personally spoken not only with other Veeam users about this, but with your own sales engineers, and most are in agreement. Not to say that i'm speaking for the majority here. CommVault would be an example of how i think retention is done right...
For the enterprise manager, I'm not sure I'm following. I have a standard license and an enterprise license. Are you saying i can import both into enterprise manager and then distribute them and manage each discrete Veeam Server (single pane of glass)?
For the single tape drive, seriously, absolutely a ridiculous design (for enterprises). I have 50TB+ of data to backup, 4 tape drives and 120 slots. I'm supposed to manually load balance all of that? You automatically pick proxy servers for backup/replication based on job load, tape needs the same automation / capability. I get its a v1.0, but for me, I still need CommVault for tape, which stinks.
For the workflows, PowerShell is great, and I'm fine with PowerShell, except not everyone is good at powershell. I get that workflows wouldn't be easy, but it's something that would totally be useful.
Finally, in looking at how Veeam works with tape, it's just ugly IMO. I'm not even talking about your tape v1.0 implementation here, i'm saying in general. Your product is just not tape friendly. Here's the problem, If I have a large VM, that i'm sending to DR (4TB for example). If I need to restore one folder out of that VM, i need to restore the 4TB file from tape to disk just so I can get access to folder "x". It would be awesome if there was a way to have the VM's stored in min-flat files that were spanned based on some sector algorithm or something. Meaning if I have a 4TB vm, break it up into %adjustable GB chunk size% chuncks and Veeam would know what chunks are needed to recover file / folder "x". I don't know, maybe since you're doing image based backups that wouldn't work, but who knows, there's companies that recover data from failed drives so it has to be possible.
Anyway it probably sounds really negative, but I do love your product, I just want to see more enterprise ideas incorporated into the product.