Skip to content

Commit 043d5ba

Browse files
committed
add sector size
1 parent bab8ada commit 043d5ba

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/sap/workloads/get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ In the SAP workload documentation space, you can find the following areas:
6565

6666
## Change Log
6767

68-
- 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)
68+
- March 26, 2023: Adding recommended sector size in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)
6969
- 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
7070
- 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)
7171
- 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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ When you look up the price list for Azure managed disks, then it becomes apparen
5959
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
6060

6161
> [!IMPORTANT]
62-
> 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.
62+
> You have the possibility to define the sector 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 sector size of choice when you deploy disks. This sector size is different than stripe sizes that you need to define when using a logical volume manager.
6363
6464
**Recommendation: The recommended configurations with Azure premium storage for production scenarios look like:**
6565

0 commit comments

Comments
 (0)