1) These numbers show percent of time the given data processing stage was busy versus waiting for other stages to provide or accept the data. Do not expect the numbers across all processing stages to add up to 100%, as busy time of each processing stage is measured separately and independently.
Looks like your main bottleneck is the "Source" - production storage disk reader component. The percent busy number for this component indicates percent of time that the source disk reader spent reading the data from the storage. For example, 97% busy means that the disk reader spent almost all of the time reading the data, because the following stages are always ready to accept more data for processing.
It looks like you've reached the max performance of your source datastore. You can also try to use hotadd proxy, compare the numbers and then stick to transport mode with best performance rates. What are the processing rates for those jobs?
3) VMs of same OS with similar applications have a lot of similar data blocks, which are deduplicated by Veeam Backup Proxy. Basics are covered in the related User Guide section
. More info can be found on the forum
4) Powershell scripts are discussed in the related subforum
. There are lots of handy scripts, take a look! Here is
a one we are talking about.
And yes, we will take it into consideration as the feature request. Thanks for the feedback!