note on Mv3 IOPS with cached disks

Author: msjuergent

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

@@ -384,8 +384,6 @@ Oracle Data Guard is supported for high availability and disaster recovery purpo
 
 Disaster Recovery aspects for Oracle databases in Azure are presented in the article [<u>Disaster recovery for an Oracle Database 12c database in an Azure environment</u>](/azure/virtual-machines/workloads/oracle/oracle-disaster-recovery).
 
-Another good Oracle whitepaper [Setting up Oracle 12c Data Guard for SAP Customers](https://www.sap.com/documents/2016/12/a67bac51-9a7c-0010-82c7-eda71af511fa.html)
-
 ## Huge Pages & Large Oracle SGA Configurations
 
 VLDB SAP on Oracle on Azure deployments apply SGA sizes in excess of 3TB. Modern versions of Oracle handle large SGA sizes well and significantly reduce IO. Review the AWR report and increase the SGA size to reduce read IO. 

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

@@ -6,13 +6,13 @@ manager: patfilot
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 10/34/2024
+ms.date: 10/14/2024
 ms.author: juergent
 ms.custom: H1Hack27Feb2017, linux-related-content
 ---
 # SAP ASE Azure Virtual Machines DBMS deployment for SAP workload
 
-In this document, covers several different areas to consider when deploying SAP ASE in Azure IaaS. As a precondition to this document, you should have read the document [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) and other guides in the [SAP workload on Azure documentation](./get-started.md). This document covers SAP ASE running on Linux and on Windows Operating Systems. The minimum supported release on Azure is SAP ASE 16.0.02 (Release 16 Support Pack 2). It's recommended to deploy the latest version of SAP and the latest Patch Level.  As a minimum SAP ASE 16.0.03.07 (Release 16 Support Pack 3 Patch Level 7) is recommended.  The most recent version of SAP can be found in [Targeted ASE 16.0 Release Schedule and CR list Information](https://wiki.scn.sap.com/wiki/display/SYBASE/Targeted+ASE+16.0+Release+Schedule+and+CR+list+Information).
+In this document, covers several different areas to consider when deploying SAP ASE in Azure IaaS. As a precondition to this document, you read the document [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) and other guides in the [SAP workload on Azure documentation](./get-started.md). This document covers SAP ASE running on Linux and on Windows Operating Systems. The minimum supported release on Azure is SAP ASE 16.0.02 (Release 16 Support Pack 2). It's recommended to deploy the latest version of SAP with the most recent Patch Level.  As a minimum SAP ASE 16.0.03.07 (Release 16 Support Pack 3 Patch Level 7) is recommended.  The most recent version of SAP can be found in [Targeted ASE 16.0 Release Schedule and CR list Information](https://wiki.scn.sap.com/wiki/display/SYBASE/Targeted+ASE+16.0+Release+Schedule+and+CR+list+Information).
 
 Additional information about release support with SAP applications or installation media location are found, besides in the SAP Product Availability Matrix in these locations:
 
@@ -24,17 +24,17 @@ Additional information about release support with SAP applications or installati
 Remark: Throughout documentation within and outside the SAP world, the name of the product is referenced as Sybase ASE or SAP ASE or in some cases both. In order to stay consistent, we use the name **SAP ASE** in this documentation.
 
 ## Operating system support
-The SAP Product Availability Matrix contains the supported Operating System and SAP Kernel combinations for each SAP application.  Linux distributions SLES 12.x, SLES 15.x, RHEL 7.x and RHEL 8.x are fully supported. Oracle Linux as operating system for SAP ASE isn't supported.  It's recommended to use the most recent Linux releases available. Windows customers should use Windows Server 2016 or Windows Server 2019 releases.  Older releases of Windows such as Windows 2012 are technically supported but the latest Windows version is always recommended.
+The SAP Product Availability Matrix contains the supported Operating System and SAP Kernel combinations for each SAP application.  Linux distributions SLES 12.x, SLES 15.x, RHEL 7.x, and RHEL 8.x are fully supported. Oracle Linux as operating system for SAP ASE isn't supported.  It's recommended to use the most recent Linux releases available. Windows customers should use Windows Server 2016 or Windows Server 2019 releases.  Older releases of Windows such as Windows 2012 are technically supported but the latest Windows version is always recommended.
 
 
 ## Specifics to SAP ASE on Windows
 Starting with Microsoft Azure, you can migrate your existing SAP ASE applications to Azure Virtual Machines. SAP ASE in an Azure Virtual Machine enables you to reduce the total cost of ownership of deployment, management, and maintenance of enterprise breadth applications by easily migrating these applications to Microsoft Azure. With SAP ASE in an Azure Virtual Machine, administrators and developers can still use the same development and administration tools that are available on-premises.
 
-Microsoft Azure offers numerous different virtual machine types that allow you to run smallest SAP systems and landscapes up to large SAP systems and landscapes with thousands of users. SAP sizing SAPS numbers of the different SAP certified VM SKUs is provided in [SAP support note #1928533](https://launchpad.support.sap.com/#/notes/1928533).
+Microsoft Azure offers numerous different virtual machine types that allow you to run smallest SAP systems and landscapes up to large SAP systems and landscapes with thousands of users. SAP sizing SAPS numbers of the different SAP certified Virtual Machine (VM) SKUs is provided in [SAP support note #1928533](https://launchpad.support.sap.com/#/notes/1928533).
 
 Documentation to install SAP ASE on Windows can be found in the [SAP ASE Installation Guide for Windows](https://help.sap.com/viewer/36031975851a4f82b1022a9df877280b/16.0.3.7/en-US/a660d3f1bc2b101487cbdbf10069c3ac.html)
 
-Lock Pages in Memory is a setting that will prevent the SAP ASE database buffer from being paged out.  This setting is useful for large busy systems with a high memory demand. Contact BC-DB-SYB for more information. 
+Lock Pages in Memory is a setting that is preventing the SAP ASE database buffer from being paged out.  This setting is useful for large busy systems with a high memory demand. Contact BC-DB-SYB for more information. 
 
 
 ## Linux operating system specific settings
@@ -43,7 +43,7 @@ Linux Huge Pages should be enabled by default and can be verified with command
 
 `cat /proc/meminfo` 
 
-The page size is typically 2048 KB. For details see the article [Huge Pages on Linux](https://help.sap.com/viewer/ecbccd52e7024feaa12f4e780b43bc3b/16.0.3.7/en-US/a703d580bc2b10149695f7d838203fad.html) 
+The page size is typically 2,048 KB. For details see the article [Huge Pages on Linux](https://help.sap.com/viewer/ecbccd52e7024feaa12f4e780b43bc3b/16.0.3.7/en-US/a703d580bc2b10149695f7d838203fad.html) 
 
 
 ## Recommendations on VM and disk structure for SAP ASE deployments
@@ -62,17 +62,17 @@ Separate disks are recommended for Data devices and Log Devices.  The system dat
 ![Storage configuration for SAP ASE](./media/dbms-guide-sap-ase/sap-ase-disk-structure.png)
 
 ### File systems, stripe size & IO balancing 
-SAP ASE writes data sequentially into disk storage devices unless configured otherwise. This means an empty SAP ASE database with four devices will write data into the first device only.  The other disk devices will only be written to when the first device is full.  The amount of READ and WRITE IO to each SAP ASE device is likely to be different. To balance disk IO across all available Azure disks, either Windows Storage Spaces or Linux LVM2 needs to be used. On Linux, it's recommended to use XFS file system to format the disks. The LVM stripe size should be tested with a performance test. 128 KB stripe size is a good starting point. On Windows, the NTFS Allocation Unit Size (AUS) should be tested. 64 KB can be used as a starting value. 
+SAP ASE writes data sequentially into disk storage devices unless configured otherwise. This means an empty SAP ASE database with four devices wwrites data into the first device only.  The other disk devices are only written into when the first device is full.  The amount of READ and WRITE IO to each SAP ASE device is likely to be different. To balance disk IO across all available Azure disks, either Windows Storage Spaces or Linux LVM2 needs to be used. On Linux, it's recommended to use XFS file system to format the disks. The LVM stripe size should be tested with a performance test. 128 KB stripe size is a good starting point. On Windows, the NTFS Allocation Unit Size (AUS) should be tested. 64 KB can be used as a starting value. 
 
 It's recommended to configure Automatic Database Expansion as described in the article [Configuring Automatic Database Space Expansion in SAP Adaptive Server Enterprise](https://blogs.sap.com/2014/07/09/configuring-automatic-database-space-expansion-in-sap-adaptive-server-enterprise/)  and [SAP support note #1815695](https://launchpad.support.sap.com/#/notes/1815695). 
 
-### Sample SAP ASE on Azure virtual machine, disk and file system configurations 
+### Sample SAP ASE on Azure virtual machine, disk, and file system configurations 
 The templates below show sample configurations for both Linux and Windows. Before confirming the virtual machine and disk configuration, ensure that the network and storage bandwidth quotas of the individual VM are sufficient to meet the business requirement. Also keep in mind that different Azure VM types have different maximum numbers of disks that can be attached to the VM. For example, a E4s_v3 VM  has a limit 48 MB/sec storage IO throughput. If the storage throughput required by database backup activity demands more than 48 MB/sec then a larger VM type with more storage bandwidth throughput is unavoidable. When configuring Azure storage, you also need to keep in mind that especially with [Azure Premium storage](/azure/virtual-machines/premium-storage-performance) the throughput, and IOPS per GB of capacity do change. See more on this topic in the article [What disk types are available in Azure?](/azure/virtual-machines/disks-types). The quotas for specific Azure VM types are documented in the article [Memory optimized virtual machine sizes](/azure/virtual-machines/sizes-memory) and articles linked to it. 
 
 > [!NOTE]
 >  If a DBMS system is being moved from on-premises to Azure, it's recommended to perform monitoring on the VM and assess the CPU, memory, IOPS and storage throughput. Compare the peak values observed with the VM quota limits documented in the articles mentioned above
 
-The examples given below are for illustrative purposes and can be modified based on individual needs. Due to the design of SAP ASE, the number of data devices isn't as critical as with other databases. The number of data devices detailed in this document is a guide only. The configurations suggested should be treated as what they're. They are starting points for you. But they are configurations that are going to need some fine-tuning to your workload and cost efficiencies.
+The examples given below are for illustrative purposes and can be modified based on individual needs. Due to the design of SAP ASE, the number of data devices isn't as critical as with other databases. The number of data devices detailed in this document is a guide only. The configurations suggested should be treated as what they're. They're starting points for you. But they're configurations that are going to need some fine-tuning to your workload and cost efficiencies.
 
 An example of a configuration for a little SAP ASE DB Server with a database size between 50 GB – 250 GB could look like
 
@@ -210,7 +210,7 @@ The HADR Users Guide details the setup and configuration of a two-node SAP ASE 
 There are two supported High Availability configurations for SAP ASE on Azure:
 
 - HA Aware with Fault Manager - The SAP Kernel is an “HA Aware” application and knows about the primary and secondary SAP ASE servers. There are no close integrations between the SAP ASE “HA Aware“ solution and Azure, the Azure Internal load balancer isn't used.  The solution is documented in the [SAP ASE HADR Users Guide](https://help.sap.com/viewer/efe56ad3cad0467d837c8ff1ac6ba75c/16.0.3.7/en-US/a6645e28bc2b1014b54b8815a64b87ba.html)
-- Floating IP with Fault Manager – This solution can be used for SAP Business Suite and non-SAP Business Suite applications.  This solution utilizes the Azure ILB and the SAP ASE database engine provides a Probe Port.  The Fault Manager will call SAPHostAgent to start or stop a secondary Floating IP on the ASE hosts.  This solution is documented in [SAP note #3086679 - SYB: Fault Manager: floating IP address on Microsoft Azure](https://launchpad.support.sap.com/#/notes/3086679)
+- Floating IP with Fault Manager – This solution can be used for SAP Business Suite and non-SAP Business Suite applications.  This solution utilizes the Azure ILB and the SAP ASE database engine provides a Probe Port.  The Fault Manager calls the SAPHostAgent to start or stop a secondary Floating IP on the ASE hosts.  This solution is documented in [SAP note #3086679 - SYB: Fault Manager: floating IP address on Microsoft Azure](https://launchpad.support.sap.com/#/notes/3086679)
 
 
 > [!NOTE]
@@ -228,13 +228,13 @@ SAP Software provisioning Manager (SWPM) is giving an option to encrypt the data
 - [SAP support note #2593925](https://launchpad.support.sap.com/#/notes/2593925) 
 
 > [!NOTE]
-> If a SAP ASE database is encrypted then Backup Dump Compression will not work. See also [SAP support note #2680905](https://launchpad.support.sap.com/#/notes/2680905) 
+> If a SAP ASE database is encrypted then Backup Dump Compression is not working. See also [SAP support note #2680905](https://launchpad.support.sap.com/#/notes/2680905) 
 
 ## SAP ASE on Azure deployment checklist
 
 - Deploy SAP ASE 16.0.03.07 or higher
 - Update to latest version and patches of FaultManager and SAPHostAgent
-- Deploy on latest certified OS available such as Windows 2019, SLES 15 or RHEL 8 
+- Deploy on latest certified OS available such as Windows 2019, SLES 15, or RHEL 8 
 - Use SAP Certified VMs – high memory Azure VM SKUs such as Es_v3 or for x-large systems M-Series VM SKUs are recommended
 - Match the disk IOPS and total VM aggregate throughput quota of the VM with the disk design.  Deploy sufficient number of disks
 - Aggregate disks using Windows Storage Spaces or Linux LVM2 with correct stripe size and file system
@@ -258,7 +258,7 @@ As with on-premises systems several steps are required to enable all SAP NetWeav
 > 
 > 
 
-and the links generated in transaction DBACockpit look similar to:
+And the links generated in transaction DBACockpit look similar to:
 
 > https:\//\<fullyqualifiedhostname>:44300/sap/bc/webdynpro/sap/dba_cockpit
 > 
@@ -310,7 +310,7 @@ The starting page for [SAP ASE 16.0.03.07 Documentation](https://help.sap.com/vi
 - SAP ASE Learning Journey - Administration & Monitoring
 - SAP ASE Learning Journey - Installation & Upgrade
 
-are helpful. Another useful document is [SAP Applications on SAP Adaptive Server Enterprise Best Practices for Migration and Runtime](https://assets.cdn.sap.com/sapcom/docs/2016/06/26450353-767c-0010-82c7-eda71af511fa.pdf).
+Are helpful. Another useful document is [SAP Applications on SAP Adaptive Server Enterprise Best Practices for Migration and Runtime](https://assets.cdn.sap.com/sapcom/docs/2016/06/26450353-767c-0010-82c7-eda71af511fa.pdf).
 
 Other helpful SAP support notes are: