Skip to main content

Geographic Redundancy


Geographic redundancy involves distributing data and resources across multiple geographic locations to ensure continuous service availability or for disaster recovery purposes

image of solution diagram
Copy to clipboard

Solution Diagram Resources
You can download the Solution Diagram as a .drawio file for offline use. Alternatively, you may view and edit the Solution Diagram directly on draw.io.
Please note that any changes made online will need to be saved locally if you wish to keep them.

A basic setup of geographic redundancy involves SAP BTP Application or a service subscribed to multiple subaccounts in different regions. These services or applications also need artifacts, data, events, etc., to be synchronized across the regions and often require more sophisticated strategies and additional components.

The following sections provide sample strategies for various SAP BTP services and applications to achieve geographic redundancy which needs to be used based on specific use cases

SAP Build Work Zone, Standard Edition

This service can be subscribed to in both regions. If one region becomes unavailable, the other region’s Work Zone can handle all requests. However, this setup results in different personalization data in each region’s SAP Build Work Zone, affecting the look and feel. Additionally, users, roles, and business content such as HTML5 applications, Content Providers, and other configurations including Sites, must be synchronized between the two regions to ensure consistency. For more information, refer to the SAP Build Work Zone documentation.

Various work zone artifacts can be transported across regions using the Transport management service or manually. For more information, refer to SAP Build Work Zone - Transporting Content.

SAP Integration Suite - Cloud Integration

Setting up Integration Suite instances in both subaccounts supports multi-region capabilities for simple cloud integration iFlows. However, for more complex iFlows requiring data persistence, the data becomes region-specific and is managed internally by Cloud Integration. Using external data persistence typically requires SAP HANA Cloud, which is region-specific and does not automatically replicate data across regions. An additional solution is needed to manage this. For more details, see the SAP Integration Suite documentation

SAP Integration Suite - Advanced Event Mesh

The Advanced Event Mesh DMR clusters can help replicate messages across regions instead of using region-specific JMS queues, which are region bound, but this requires an extra solution to manage the process. Deploying and undeploying iFlows to reestablish event connectivity per region must also be managed. For more details, see the SAP Integration Suite, Advanced Event Mesh.

SAP HANA Cloud

SAP HANA Cloud does not natively support data replication across regions. To ensure that applications built on SAP BTP using SAP HANA Cloud DB are multi-region compatible, data must be replicated across different regions. Smart Data Access (SDA) and Remote Table Replication (RTR) can be used to replicate data from one region to another, but a custom solution is required to manage replication topology changes during regional unavailability. For more information, refer to the SAP HANA Cloud documentation.

SAP CAP Applications

Applications built using the SAP Cloud Application Programming Model (CAP) must be deployed in both subaccounts, and SAP HANA Cloud data synchronization between the two subaccounts is required. For more details, see the SAP CAP documentation.

While the multi-region architecture is viable for several SAP BTP services, challenges arise when stateful components such as a database or events come into play. Synchronizing these across regions requires numerous steps, adding complexity to the architecture. To simplify this orchestration process, we developed an open-source project called Multi-Region Manager, which functions as a control plane to manage synchronization, to control the failover and for other functionalities. Learn more about this here: Multi-Region Manager

These examples illustrate only a few of the SAP BTP services, and as new services/applications are need to adapt this architecture, a thorough analysis is necessary to ensure they are compliant with multi-region requirements. The priority and characteristics of each service will dictate the strategies required for achieving robust multi-region setup.