Extend scenario files by DR scenarios 2

Author: msjuergent

articles/virtual-machines/workloads/sap/hana-vm-operations-storage.md

@@ -52,9 +52,12 @@ Given that low storage latency is critical for DBMS systems, even as DBMS, like
 
 **Recommendation: As stripe sizes for the RAID 0 the recommendation is to use:**
 
-- 64 KB or 128 KB for **/hana/data**
+- 256 KB for **/hana/data**
 - 32 KB for **/hana/log**
 
+> [!IMPORTANT]
+> The stripe size for /hana/data got changed from earlier recommendations calling for 64 KB or 128 KB to 256 KB based on customer experiences with more recent Linux versions. The size of 256 KB is providing slightly better performance
+
 > [!NOTE]
 > You don't need to configure any redundancy level using RAID volumes since Azure Premium and Standard storage keep three images of a VHD. The usage of a RAID volume is purely to configure volumes that provide sufficient I/O throughput.
 

articles/virtual-machines/workloads/sap/sap-supported-product-on-azure.md

@@ -56,12 +56,16 @@ You need to check:
 
 - Whether the SAP applications you are running, are covered by the minimum releases stated. If not, you need to define a new target release, check in the SAP Product Availability Matrix, what operating system builds and DBMS combinations are supported with the new target release. So, that you can choose the right operating system release and DBMS release
 - Whether you need to update your SAP kernels in a move to Azure
+- Whether you need to update SAP Support Packages. Especially Basis Support Packages that can be required for cases where you are required to move to a more recent DBMS release
 
 
 The next section goes into more details on other SAP products and DBMS releases that are supported by SAP on Azure for Windows and Linux. 
 
 > [!NOTE]
-> The minimum releases of the different DBMS is carefully chosen and might not always reflect the whole spectrum of DBMS releases the different DBMS vendors support on Azure in general. Many considerations were taken into account to define those minimum releases. There is no effort to test and qualify older DBMS releases
+> The minimum releases of the different DBMS is carefully chosen and might not always reflect the whole spectrum of DBMS releases the different DBMS vendors support on Azure in general. Many SAP workload related considerations were taken into account to define those minimum releases. There is no effort to test and qualify older DBMS releases. 
+
+> [!NOTE]
+> The minimum releases listed are representing older version of operating systems and database releases. We highly encourage to use most recent operating system releases and database releases. In a lot of cases, more recent operating system and database releases took the usage case of running in public cloud into consideration and adapted code to optimize for running in public cloud or more specifically Azure
 
 ## Oracle DBMS support
 Operating system, Oracle DBMS releases and Oracle functionality supported on Azure are specifically listed in [SAP support note #2039619](https://launchpad.support.sap.com/#/notes/2039619). Essence out of that note can be summarized like: