A job is the trigger for the backup and replication process: It defines where, when and how to protect VM data.
Configuring a job may look easy and straight forward, but there are some consideration to keep in mind, such as: Exclusions, chaining and what method is best for a given backup repository.
- For per job backup files: 30 VMs per job
- For per VM backup files: 300 VMs per job
Consider that some tasks within a job are still sequential processes. For example, a merge process (writing the oldest incremental file into the full backup file) is started after the last VM finishes backup processing. If you split the VMs into multiple jobs, these background processes will run in parallel and thus reduce the overall backup window.
Be as well careful with large jobs when using Storage Snapshots at Backup from Storage Snapshots. Guest processing and scheduling of jobs that contain multiple snapshots can lead into difficult scheduling situations and jobs spending time waiting for (free) resources. A good size for jobs that write to per-VM backup files enabled repositories is 50-200 VMs per Job.
Also, remember that the number of concurrently running backup jobs should not exceed 100. Veeam can handle more, but a “sweet spot” for database load, load balancing and overall processing is about 80-100 concurrently running jobs.