Skip to main content
Druva Documentation

Multi-Geo support for SharePoint Online and Teams

This topic provides information about few considerations for administrators to protect SharePoint Online and Teams data whenever your organization enables Multi-Geo in its Microsoft 365 tenant.

Overview

  • The Multi-Geo Storage Mapping option is available only on the SharePoint app on the inSync Management Console. You cannot create Multi-Geo Storage Mapping from the Teams app on the inSync Management Console.
  • The Multi-Geo Storage Mapping option is available only for Multi-Geo tenants.
  • For Teams, Conversations data is backed up at the central geo location. Files and Wiki data that is backed up as a part of SharePoint Online and displayed as Teams sites, Multi-Geo Storage Mapping is supported as per SharePoint Online mappings defined.

Druva inSync provides support for protecting SharePoint Online and Teams data for Microsoft 365 Multi-Geo tenants. This feature helps administrators meet their data residency requirements.

With this support, Druva inSync enables you to do the following:

  • Automatically discover all the sites (SharePoint and Teams' sites) from each geo location.

  • Automatically identify new geo locations enabled in Microsoft 365 tenants.

  • Automate the storage assignment for the discovered sites and not configured sites from all the mapped geo locations.

Use the Multi-Geo Storage Mapping feature to automate the storage assignment for the discovered and not configured sites from all the mapped geo locations.

Multi-Geo Storage Mapping refers to the mapping of your Microsoft 365 geo locations with Druva inSync Storage to enable backup and restore of SharePoint and Teams sites according to the geographic location as per your business needs. 

With Multi-Geo Storage Mapping for SharePoint Online, Druva inSync allows you to do the following:

  • Automatically discover newly added sites (SharePoint and Teams' sites) with new geo locations.
  • Map these newly discovered sites (SharePoint and Teams' sites) with the available Druva inSync Storage regions for backup and restore.
  • Automate the storage assignment for the newly discovered sites from all the mapped geo-locations from the Auto-Configuration wizard on the inSync Management Console. 

Prerequisite

  • Microsoft 365 tenant has Microsoft 365 Multi-Geo feature enabled i.e your Microsoft 365 tenant is a Multi-Geo tenant. For more information, see Microsoft 365 Multi-Geo.
  • Ensure that the Auto discover sites for backup option is enabled.

Pre-req auto discover.png

Enable Multi-Geo capabilities for Microsoft 365 tenant

Microsoft allows you to enable Multi-Geo capabilities for your Microsoft 365 tenant. By enabling Multi-Geo capabilities on the tenant, you can have a single Microsoft 365 tenant that spans across multiple data center geographies, and have full control over where the data is stored. Currently, Multi-Geo is supported for Exchange Online, OneDrive, and SharePoint.


In a Multi-Geo tenant, information about geo locations, groups, and locations is mastered in the Azure active directory (AD).  Administrators can use service admin centers to manage geo locations. For more information, see Microsoft documentation.

You may have to reach out to a Microsoft account representative to enable this feature for your Microsoft 365 tenant.

Enable data locations

Management of Multi-Geo feature is available through the SharePoint admin center. For more information, see Microsoft blog post.

When a user creates a SharePoint site in a Multi-Geo environment, the user’s Preferred Data Location (PDL) is used to determine the location where the site is created. If no PDL is set for the user, the site will be created in the central location. If the user's PDL changes and there is a need to move the site to a new location, PowerShell Commands can be triggered to move the site from one location to another.

Use the PowerShell Commands mentioned below to move SharePoint sites to a specific location.

Sites with no associated groups

  • Start-SPOSiteContentMove -SourceSiteUrl <siteURL> -DestinationDataLocation <DestinationDataLocation> -DestinationUrl <DestinationSiteURL>

Sites associated with a group

  • Set-SPOUnifiedGroup -PreferredDataLocation <PDL> -GroupAlias <GroupAlias>

  • Get-SPOUnifiedGroup -GroupAlias <GroupAlias>

  • Start-SPOUnifiedGroupMove -GroupAlias <GroupAlias> -DestinationDataLocation <DestinationDataLocation>

  • Get-SPOUnifiedGroupMoveState -GroupAlias <GroupAlias>

For more information, see Microsoft documentation.

Get Started

Druva inSync must have permissions to access SharePoint Online and Teams data to protect it. Before you begin with the Multi-Geo storage mapping, ensure that you complete the configuration steps to protect your SharePoint Online and Teams data. For more information on how to provide Druva inSync access to SharePoint Online and Teams data, see,

After the configuration is complete,  on the inSync Management Console, navigate to Data Sources> Microsoft 365. On the Overview page, on the left-hand side, click SharePoint. Druva inSync discovers all the standalone SharePoint sites and Teams sites (That have Files and Wiki data of Teams) within your organization. By default, the App Status of all the discovered sites is Not Configured.

For Microsoft 365 Multi-Geo tenants, a notification message is displayed when Druva inSync discovers sites with new geographic locations (geo locations).  This notification appears every time when Druva inSync discovers sites with a new geo location.

To configure the discovered sites with multiple geo locations for backup and restore, you can create Multi-Geo storage mappings from three locations on the inSync Management Console:

3 options_mutli-geo_storage.png

Multi-Geo Storage Mapping through Notification Message

Tenant not authorized.png

Procedure

  1. On the inSync Management Console menu bar, click Data Sources > Microsoft 365. An overview page that provides a holistic view of all the configured Microsoft 365 app appears.
  2. On the left-hand panel, click SharePoint. If the Multi-Geo feature is enabled for the Microsoft 365 tenant, a message that notifies that Druva inSync has discovered sites with new geo locations is displayed.
  3. Click the Multi-Geo Storage Mapping link within the message. The Multi-Geo Storage Mapping pop-up appears with a list of all the Microsoft 365 Geo locations enabled in your Microsoft 365 tenant.
  4.  On the Multi-Geo Storage Mapping > Druva inSync Storage, click the dropdown to view the list of available Druva inSync storage regions and assign one as per your requirement.
  5. Click Save to save the defined storage mappings. 
  6. A notification pop-up appears. Review the message and then click OK
  • If you want to automatically assign storage to all the Not Configured sites and the sites that will be discovered in the future, you must enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration Settings wizard.
  • If you do not enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration Settings wizard. you have to assign the storage manually for each discovered site.
  1. Click Auto Configuration. On the Auto Configuration Settings wizard, select the checkbox for the Auto assign storage as per Multi-Geo Storage Mapping setting and then click Save. A confirmation pop-up appears. Click Assign Storage, if you want to assign storage to all the Not Configured sites according to the Multi-Geo  Storage Mapping.

Druva inSync will now backup sites based on the storage mappings provided.

You can view and update the Multi-Geo storage mapping using View Mappings from the Auto Configuration Settings wizard.

Note: When you update a storage mapping for a particular geo location, this new mapping will take effect only for the newly discovered and added sites for that geo location. The existing sites within that geo location continue to be backed up as per the old storage mappings.

For example, India geo location is currently mapped to <ABC> storage. Marketing site is a part of India geo location and is mapped to <ABC> storage. Now, you change the storage mapping for India to <XYZ> storage.  In the subsequent discovery cycle,  for the existing Marketing site, storage mapping continues to be <ABC> storage and not <XYZ>. The newly discovered sites in India will be mapped to the updated <XYZ>. storage.

Multi-Geo Storage Mapping through more options icon

You can define and create Multi-Geo Storage Mapping using more options icon besides Auto Configuration.

More options for multi-geo.png

Procedure

  1. On the inSync Management Console menu bar, click Data Sources > Microsoft 365. An overview page that provides a holistic view of all the configured Microsoft 365 app appears.
  2. On the left-hand panel, click SharePoint. If the Multi-Geo feature is enabled for the Microsoft 365 tenant, a message that notifies that Druva inSync has discovered sites with new geo locations is displayed.
  3. Click the  Icon-more options_updated.png  icon beside Auto Configuration and then click Multi-Geo Storage Mapping. The Multi-Geo Storage Mapping pop-up appears with a list of all the Microsoft 365 Geo locations enabled in your Microsoft 365 tenant.
  4.  On the Multi-Geo Storage Mapping > Druva inSync Storage, click the dropdown to view the list of available Druva inSync storage regions and assign one as per your requirement.
  5. Click Save to save the defined Multi-Geo storage mappings. 
  6. A notification pop-up appears. Review the message and then click OK
  7. Click Auto Configuration. On the Auto Configuration Settings wizard, select the checkbox for the Auto assign storage as per Multi-Geo Storage Mapping setting and then click Save. A confirmation pop-up appears. Click Assign Storage, if you want to assign storage to all the Not Configured sites according to the Multi-Geo  Storage Mapping.
  • If you want to automatically assign storage to all the Not Configured sites and the sites that will be discovered in the future, you must enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration wizard.
  • If you do not enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration wizard. you have to assign the storage manually for each discovered site.

Druva inSync will now backup sites based on the storage mappings provided.

You can view and update the Multi-Geo storage mapping using View Mappings from the Auto Configuration Settings wizard.

Note: When you update a storage mapping for a particular geo location, this new mapping will take effect only for the newly discovered and added sites for that geo location. The existing sites within that geo location continue to be backed up as per the old storage mappings.

For example, India geo location is currently mapped to <ABC> storage. Marketing site is a part of India geo location and is mapped to <ABC> storage. Now, you change the storage mapping for India to <XYZ> storage.  In the subsequent discovery cycle,  for the existing Marketing site, storage mapping continues to be <ABC> storage and not <XYZ>. The newly discovered sites in India will be mapped to the updated <XYZ>. storage.

Multi-Geo Storage Mapping using Auto Configuration wizard

If you have not defined the Multi-Geo Storage Mapping using the notification message and you click Auto-Configuration. You can define and create Multi-Geo Storage Mapping using Create Mapping option on this wizard as well.

Create mapping using Auto-Config wizard.png

Procedure

  1. On the inSync Management Console menu bar, click Data Sources > Microsoft 365. An overview page that provides a holistic view of all the configured Microsoft 365 app appears.
  2. On the left-hand panel, click SharePoint. If the Multi-Geo feature is enabled for the Microsoft 365 tenant, a message that notifies that Druva inSync has discovered sites with new geo locations is displayed.
  3. Click Auto Configuration. On the Auto Configuration Settings wizard click Create Mapping. The Multi-Geo Storage Mapping pop-up appears with a list of all the Microsoft 365 Geo locations enabled in your Microsoft 365 tenant.
  4.  On the Multi-Geo Storage Mapping > Druva inSync Storage, click the dropdown to view the list of available Druva inSync storage regions and assign one as per your requirement.
  5. Click Save to save the defined Multi-Geo storage mappings. Once you have successfully defined the Multi-Geo Storage Mapping using Create Mapping option, this option is renamed to View Mappings.
  6. After you save the Multi-Geo storage mappings, on the Auto Configuration Settings wizard, select the checkbox for the Auto assign storage as per Multi-Geo Storage Mapping setting and then click Save. A confirmation pop-up appears. Click Assign Storage, if you want to assign storage to all the Not Configured sites according to the Multi-Geo  Storage Mapping.
  • If you want to automatically assign storage to all the Not Configured sites and the sites that will be discovered in the future, you must enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration wizard.
  • If you do not enable the Auto assign storage as per Multi-Geo Storage Mapping setting from the Auto Configuration wizard. you have to assign the storage manually for each discovered site.

Druva inSync will now backup sites based on the storage mappings provided.

Note: Once you have  successfully defined the Multi-Geo Storage Mapping using Create Mapping option, this option is renamed to View Mappings.

You can view and update the Multi-Geo storage mapping using View Mappings from the Auto Configuration Settings wizard.

Note: When you update a storage mapping for a particular geo location, this new mapping will take effect only for the newly discovered and added sites for that geo location. The existing sites within that geo location continue to be backed up as per the old storage mappings.

For example, India geo location is currently mapped to <ABC> storage. Marketing site is a part of India geo location and is mapped to <ABC> storage. Now, you change the storage mapping for India to <XYZ> storage.  In the subsequent discovery cycle,  for the existing Marketing site, storage mapping continues to be <ABC> storage and not <XYZ>. The newly discovered sites in India will be mapped to the updated <XYZ>. storage.

Use Case: Auto assign storage is enabled, new geo location is discovered but not mapped

In this scenario, for successful backup and restore, you must create and define storage mapping for the new geo location that is discovered.

Auto config-newgeo_not_mapped_overlap.png

For more information on how to create Multi-Geo Storage Mapping, see:

Use Case: Microsoft 365 tenant upgraded to Multi-Geo tenant

When a Microsoft 365 tenant has Multi-Geo feature enabled, the tenant is referred to as Multi-Geo tenant. For a Microsoft 365 tenant upgraded to Multi-Geo tenant, backups continue for configured sites as per defined backup settings. For Not Configured sites, Multi-Geo Storage Mapping is required.

In this scenario, after the discovery of sites, the Multi-Geo tenant gets a notification message stating discovered sites with new geo locations. Administrators must create Multi-Geo storage mappings to enable backup and restore for these discovered sites as per required geo locations.

For more information on how to create Multi-Geo Storage Mapping, see:

All the administrators' activities, such as create and update Multi-Geo Storage Mapping, are displayed on the Governance > Audit Trails page. For more information, see the Audit Trails page.

Things to consider

  • Restore to a different site: In this case, only those sites that belong to geo locations of the source site will be searched.
  • Restore to a new site: In this case. the new site is created at the same geo location as the source site. For example, if the geo location of source site is India, the new site will also be created in India geo location.
  • When you migrate the SharePoint site across geo location, the new URL of the site and its old URL, both based on its geo location,  would be treated as separate sites in Druva inSync. You cannot restore the data from the backup snapshot of the site with an older URL to a site with new URL.

 

  • Was this article helpful?