Veeam cloud connect backup jobs best practice

broken image
broken image

Veeam’s Intelligent Load Balancing can handle proxy/repository resources by starting multiple jobs in parallel and consequently using all available proxy/repository resources. The alternative of job chaining is to start the jobs right after each other. For example, if a job as part of a chain fails or stops responding, the entire job chain delivers poor backup success rate.

broken image

Job chainingĬhaining backup jobs should be avoided in general. To mitigate this problem, we recommend to enable Storage Latency Control (also known as Backup I/O Control) settings. 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 VM’s performance (high latency). Also, remember that exclusions have higher priority over inclusions in Veeam Backup & Replication. Monitoring with Veeam ONE is highly recommended in tracking VMs that are under protection. It is quite possible that a VM gets moved to a folder or resource pool that is excluded which makes it unprotected. While exclusions can be very useful, the virtual infrastructure is dynamic and changes rapidly. This site uses Just the Docs, a documentation theme for Jekyll.

broken image

Backup Repository HA using Windows Storage Replica.

broken image