Problem Description
When performing a SharePoint Online (SPO) restore using Restore to a different site, the destination SharePoint site does not appear in the search results. The search spinner runs briefly and then displays “No Results Found”, even though the destination site is already configured, active, and backed up.
This behavior is commonly observed in Microsoft 365 tenants configured with multiple geo-locations when attempting to restore data between different geo regions.
Cause
This issue is expected behavior.
Druva inSync does not support cross‑geo‑region SharePoint site restores. To ensure restore integrity and compliance with Microsoft 365 geo-boundary rules, the product restricts site restores to only those destination sites that belong to the same SharePoint geo-region as the source site.
During the restore workflow, inSync filters out all sites that reside in a different geo-location. As a result, any destination SharePoint site located in another Microsoft 365 geo will not appear in the search results, even though it is configured and successfully backed up. Internally, the service associates this scenario with a cross‑geolocation restore restriction.
Traceback / Logs
raise SyncError(inSyncError.ECROSSGEOSITERESTORE
Backend diagnostics may show that both the source and destination sites are configured correctly and backed up, but each site is tagged with a different geo-location in the configuration database. During the Restore to a different site operation, the system excludes sites whose geo-location differs from that of the source. While the UI simply displays “No Results Found,” backend logs indicate that the restore workflow has blocked the operation due to a cross‑geo limitation.
This confirms that the behavior is functioning as designed and is not caused by throttling, misconfiguration, or temporary service issues.
Resolution
Expected Product Behavior
Cross‑geo SharePoint site-to-site restores are not supported in Druva inSync. Only sites located within the same Microsoft 365 geo-region or endpoint as the source site will appear as restore targets when using Restore to a different site.
Workarounds
Supported Approach
Restore content to:
The same SharePoint site, or any other site located within the same geo-region as the source site.
For Cross‑Geo Migrations
To move SharePoint content across Microsoft 365 geo-regions, use one of the following approaches:
Restore the data to a site within the source geo and manually migrate the content to the destination region.
Use native SharePoint Online copy/move features.
Use Microsoft or third‑party SharePoint migration tools to transfer content between geo regions.