nbpax.blogg.se - Veeam exchange backup best practices

As SharePoint offers a wide range of functionalities the implementations within the field are from a simple “hello world” website with a few MB of data to complex document management systems hosting TB’s of data. Subsites, Personal, Teams)Ī special remark is required on the object count for SharePoint Sites.

Mail (Primary, Archive, Shared, PublicFolder).

The tables in this section use the number of objects and their variations as a metric for estimations. The values provided refer to any combination of Online and On-Premises environments that use Microsoft Exchange, Microsoft SharePoint, OneDrive for Business and Microsoft Teams. These values represent what’s currently supported also in light of acceptable performance. Numbers might vary depending on deployments types and available resources. Veeam can handle more, but a “sweet spot” for database load, load balancing and overall processing is about 80-100 concurrently running jobs.Ĭopyright © 2019-2023 Solutions Architects, Veeam Software.This section covers the supported VB365 configuration maximums. A good size for jobs that write to per-VM backup files enabled repositories is 50-200 VMs per job.Īlso, remember that the number of concurrently running backup jobs should not exceed 100. Guest processing and scheduling of jobs that contain multiple snapshots can lead into difficult scheduling situations and jobs spending time waiting for (free) resources. If you split the VMs into multiple jobs, these background processes will run in parallel and thus reduce the overall backup window.īe careful with large jobs when using Storage Snapshots at Backup from Storage Snapshots.

For example, a merge process (writing the oldest incremental file into the full backup file) is started after the last VM finishes backup processing. By using multiple VM per job we will reduce management complexity, as it’s much easier to manage a small amount of jobs than trying to manage hundreds of jobs.Ĭonsider that some tasks within a job are still sequential processes. For per VM backup files: up to 300 VMs per jobĪvoid using one VM per job unless is strictly necessary.For per job backup files: up to 30 VMs per job.This site uses Just the Docs, a documentation theme for Jekyll.Ī job is the trigger for the backup and replication process: It defines where, when and how to protect VM data.Ĭonfiguring 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.

Restoring VMs to an HPE 3PAR with thin disks.Backup Repository HA using Windows Storage Replica.