The association of a single object to one job should preferrably stay the same all the time to avoid this scenario. Reassigned objects from one job to another might include running these jobs on another proxy and thus to another repository which would involve a complete new full backup. The best practice is to stay well below (50-75%) the recommended maximum to be able to grow jobs when required and still stay within the limits. Please refer to the recommended configuration maximums for details on how many objects/users can be in one job. Depending on the number of backed up objects there should be multiple jobs for each service. separate Exchange backup, OneDrive backup and SharePoint backup jobs.
While you can backup multiple services within a single job it is recommended to create jobs per service, e.g.
Veeam Backup for Microsoft 365 offers multiple options to create the backup job to protect the environment.īackup jobs can be created based on Users, Groups, Sites, Teams and Organizations.Ĭonfiguring a single backup job is appealing, but the maintenance of a single backup job is challenging because of risks like single point of failure, management, backup duration and restore.Īs a best practice the backup objects should be split to several jobs, depending on the amount of objects but also on the amount of infrastructure (e.g. User-based Services (Exchange, OneDrive).
0 kommentar(er)
