Merge pull request #232212 from msjuergent/pv2

add storage block size

Author: prmerger-automator[bot]

articles/sap/workloads/dbms-guide-sapase.md

@@ -214,7 +214,7 @@ There are two supported High Availability configurations for SAP ASE on Azure:
 
 
 > [!NOTE]
-> The failover times and other characteristics of either HA Aware or Floating IP solutions are similar.  When deciding between these two solutions customers should perform their own testing and evaluation including factors such as planned and unplanned failover times and other operational procedures.  
+> The failover times and other characteristics of either HA Aware or Floating IP solutions are similar.  When deciding between these two solutions customers should perform their own testing and evaluation including factors such as planned and unplanned failover times and other operational procedures. High Availability Clusters based on Pacemaker are **NOT** supported at this point in time on Azure. 
 
 ### Third node for disaster recovery
 Beyond using SAP ASE Always-On for local high availability, you might want to extend the configuration to an asynchronously replicated node in another Azure region. For more information, see [Installation Procedure for Sybase 16. 3 Patch Level 3 Always-on + DR on Suse 12.3](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/installation-procedure-for-sybase-16-3-patch-level-3-always-on/ba-p/368199).

articles/sap/workloads/get-started.md

@@ -14,7 +14,7 @@ ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 03/01/2023
+ms.date: 03/27/2023
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -65,6 +65,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- March 26, 2023: Adding recommended block storage size in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)
 - March 1, 2023: Change in [HA for SAP HANA on Azure VMs on RHEL](./sap-hana-high-availability-rhel.md) to add configuration for cluster default properties
 - February 21, 2023: Correct link to HANA hardware directory in [SAP HANA infrastructure configurations and operations on Azure](./hana-vm-operations.md) and fixed a bug in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)
 - February 17, 2023: Add support and Sentinel sections, few other minor updates in [RISE with SAP integration](rise-integration.md)

articles/sap/workloads/hana-vm-premium-ssd-v2.md

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure
-ms.date: 12/14/2022
+ms.date: 03/27/2023
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 ---
@@ -58,6 +58,9 @@ When you look up the price list for Azure managed disks, then it becomes apparen
 
 Since we don't want to define which direction you should go, we're leaving the decision to you on whether to take the single disk approach or to take the multiple disk approach. Though keep in mind that the single disk approach can hit its limitations with the 1,200MB/sec throughput. There might be a point where you need to stretch /hana/data across multiple volumes. also keep in mind that the capabilities of Azure VMs in providing storage throughput are going to grow over time. And that HANA savepoints are extremely critical and demand high throughput for the **/hana/data** volume
 
+> [!IMPORTANT]
+> You have the possibility to define the block size of Azure Premium SSD v2 as 512 Bytes or 4096 Bytes. All the tests conducted and the certification as storage for SAP HANA were done with a block size of 4096 Bytes. Therefore, you should make sure that this is the block size of choice when you deploy disks. This block size is different than stripe sizes that you need to define when using a logical volume manager.
+
 **Recommendation: The recommended configurations with Azure premium storage for production scenarios look like:**
 
 Configuration for SAP **/hana/data** volume: