This article documents Limitations and Considerations when using Veeam Backup for Microsoft 365 to protect Microsoft 365 with the Multi-Geo feature enabled.
Veeam Backup for Microsoft 365 6.0 and newer
The Multi-Geo feature is fully supported but has the following limitations:
In Multi-Geo organizations, the backup of a team with a preferred data location set to a region different from the initial region may fail with the error:
(502) Bad Gateway
Veeam Explorer for Microsoft SharePoint
For non-personal Multi-Geo sites, restoring to another geolocation different from the default is not supported.
If a personal SharePoint Online site was enabled for Multi-Geo after it had been backed up, it could only
be restored to the location configured at the time of backup. Restore to a new location after a
site has been moved to a new geo is not supported.
Teams sites restore to a Multi-Geo organization using Basic authentication is not supported.
Veeam Backup for Microsoft 365 5d and older
Veeam Backup for Microsoft 365 fully supports Exchange Online mailbox backups for Multi-Geo configured tenants.
SharePoint Online / OneDrive for Business
Backup is only supported for Personal Multi-Geo SharePoint Online sites.
For Multi-Geo SharePoint Online Personal sites and OneDrive for Business, backup is supported with the following limitations:
Personal sites must be selected for processing as User objects. For more information, see the Back Up Following Objects section of Veeam Backup for Microsoft 365 User Guide.
After data migration, a full backup will be performed for the site on the next backup job run. This limitation is caused by an inability to gather the required information on site changes after it has been migrated to a different region. At the same time, backup consistency is preserved without any data duplication.