1380 - How Redstor enables SaaS data sovereignty

When it comes to the backup of SaaS applications like Microsoft 365 and Google Workspace, there are two things that happen to the data: processing and storage. Processing refers to the backup and recovery of the data as initiated through a user-defined schedule, while storage refers to the physical location of the servers where the backed-up data is hosted. The flow of SaaS data as it is backed up is therefore as follows:

Redstor assists customers in complying with the necessary regulations by supporting region-based data processing and storage, thus enabling data sovereignty. Data processing and data storage can be done in the same or different regions. For customers who run their own Storage Platforms and therefore store their data themselves, only the data processing side is relevant.

By allowing SaaS data processing to occur on a regional basis, Redstor can maintain end-to-end data sovereignty even for customers with a multi-geographic tenancy. In other words, each account is processed and stored in its sovereign territory. This applies to all supported regions (currently US, GB, EU, ZA, AUS, with more to be added).

The diagrams below provide a simplified explanation of the steps for SaaS data processing and storage with Redstor.

For Microsoft 365 services, the account locale is already provided, which means the steps look like this:

 

 

For Google Workspace and other services, the account locale is not provided, which means the steps look like this:

For customers who run their own Storage Platforms, the process is the same except that the locale of the Storage Pool can be assigned by the customer.