Blog Post

Running SAP Applications on the Microsoft Platform
6 MIN READ

DR scenario for SAP Windows application servers with the focus on ASCS/ERS using Azure Files SMB

SteffenMueller's avatar
SteffenMueller
Icon for Microsoft rankMicrosoft
Apr 10, 2023
Management Summary   A disaster exists if a primary side (Region) becomes entirely unavailable due to major outages. Within the region the system is protected by WSFC and redundancy measur...
Updated Apr 06, 2023
Version 1.0
PavloS2260's avatar
PavloS2260
Copper Contributor
Aug 30, 2023

This is great idea, thank you posting this. However, second system cannot act as QA without any systems being idle according to the diagram we have DB sync going on. Which means that for second system to function as QA it should have separate DB or not have sync going on (which defeats the purpose of the DR)

 

In addition, in order to leverage DR properly you have to have the same SIDs to avoid repopulating xml to the system and renaming integrations that are using SID. Alternatively change SIDs during DR, which is quite cumbersome on the Windows since you have SID tied to AD'based login domain\SIDadm domain\sapServiceSID. Although possible if RTO is quite substantials.

 

All the above to clarify that this design can 100% be used as DR quite effectively, however using this configuration for PRD + QA (DR) will not quite work unless RTO allows for system rename.