While exclusions can be very useful, the virtual infrastructure is dynamic and changes rapidly. It is quite possible that a VM gets moved to a folder or resource pool that is excluded which makes it unprotected.
Monitoring with Veeam ONE is highly recommended.
Also remember that exclusions have higher priority over inclusions in Veeam Backup & Replication.
Chaining backup jobs is convenient in certain circumstances, but should be used with caution. For example, if a job as part of a chain fails or stops responding, the entire job chain delivers poor backup success rate.
Intelligent Load Balancing (ILB) can handle proxy/repository resources by starting multiple jobs in parallel and consequently using all available proxy/repository resources. This allows optimal task scheduling and provides the shortest backup window.
Too many jobs accessing the same disk will load the storage significantly; this makes the job run slower or may have a negative impact on the VMs performance. To mitigate this problem,you can utilize Storage Latency Control (or Backup I/O Control) settings.
Veeam has a load balancing method that automatically allocates proxy resources making a choice between all proxies managed by Veeam Backup & Replication that are available.
While configuring a backup job, you can disable the automatic proxy selection. Instead, you can select individual proxies from the list of proxies managed by Veeam backup server, and assign them to the job. This is a very good way to manage distributed infrastructures; it also helps to keep performance under control.
For example, you can back up a cluster residing on a multiple blade chassis. In this case, if using virtual proxies, keep the proxies’ load well-balanced and optimize the network traffic.
Dedicated proxies can be also very helpful if you use a stretched cluster and do not want proxy traffic to cross inter-switch links.
You can use Proxy Affinity to allow only specific proxies to interact with a given repository.
Tip: To optimize load balancing in a distributed environment where backup proxies are located in multiple sites, it is recommended to select all proxies from the same site in the corresponding job.
Using per-job backup files: Grouping VMs running the same operating system or deployed from similar templates into a single job will increase deduplication rate.
Using per-VM backup files can increase performance due to parallelism, but will decrease deduplication as it will deduplicate each individual VM chain only (and not across all VMs in the job).