I am not sure if this is a limitation of my physical hardware or if it is the software itself. However, I would like the throughput to be faster. Who would not like things to be faster? 

It would be nice if StarWind could come up with a best practice document for configuration. I had to do some playing around in my environment with test runs to get the configuration that really allowed for the maximum amount of throughput that I was going to get with the software. Once I had figured out what worked best, the solution was rather fast for backing up 30+ TB of data

The main thing that I felt could be improved was having an estimated time of completion for the virtual tape uploads to the cloud.

There is no easy way to determine how long an upload took to complete without looking into the logs, which is very cumbersome.  I’m also unable to search by tape and have to manually scroll through the list when troubleshooting.  I spoke with their support and was able to add it as a feature request. Starwind VTL is in constant development and after my discussion with them, I found out that they are planning to include this feature in the next release.

It's a very technical product so some more user-friendliness and UX would go a long way. It sort of has to be very technical though because it is trying to marry old school tape library technology with new school cloud storage technology and act as a bridge between backup software that uses VTL for offloading. An easier way obviously would be to do away with the need for VTL and just go straight to B2 out of Veeam — like a plugin maybe. Not sure if that's possible with how Veeam works.

The solution's training process and online documentation could be more thorough.

The initial installation can be complex and should be simplified.