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

Dear PavloS2260!

Thank you for taking the time to read my blog and your feedback! The idea behind the blog is a scenario for a Disaster Recovery with Windows application servers where no system is idle. Therefore, we have 2 SAP systems to start with: TS6 and TS7. TS6 is the production system (PRD) and TS7 is the quality assurance system (QAS). The production database is synchronized, depending on the DB by AlwaysOn in case of MS SQL Server and HSR in case of SAP HANA. A copy of the database can be found on the DR site as shown in the first diagram. I want to point out that failing over to a DR site is a judgment call, since changes impacting connected SAP systems might be involved. It may take longer to establish those changes may take longer than waiting for the situation to be resolved on the system side. I want to point out though that the individual sites are protected by local HA measures like clustering the databases and ASCS/SCS. This is not showed in the first diagram, which would have made the diagram too complex. I should have at least mentioned it in the description. So, as you can see in the screenshots of the DEFAULT.PFL, the name of the SAPDBHOST was changed accordingly in order to point to the copy of the primary DB. During an active DR scenario, the QAS system is of course not available. A rename of the SID is not necessary, since both systems are already installed. The adaptation of the showed profiles will suffice. For the synchronization of the SAP executables and log files Windows robocopy is used as described. All the screenshots used in the blog are based on MS Windows with SQL Server.