Skip to content

Commit b752660

Browse files
Merge pull request #312801 from MicrosoftDocs/main
Auto Publish – main to live - 2026-03-07 23:00 UTC
2 parents 025fa99 + 3787371 commit b752660

5 files changed

Lines changed: 16 additions & 7 deletions

articles/sap/workloads/high-availability-guide-suse-nfs.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ manager: juergent
77
ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
10+
1011
ms.date: 02/02/2026
12+
1113
ms.author: radeltch
1214
ms.custom:
1315
- linux-related-content
@@ -83,7 +85,10 @@ The NFS server uses a dedicated virtual hostname and virtual IP addresses for ev
8385
* Probe port 61001 for NW2
8486

8587
## Set up a highly available NFS server
86-
In the following sections, you'll learn how to set up a highly available NFS server on SUSE Linux Enterprise Server.
88+
89+
90+
Use the following steps to deploy and configure a highly available NFS infrastructure for SAP workloads on SLES. Complete each subsection in order, because later steps depend on resources created in earlier steps.
91+
8792
### Deploy Linux manually via Azure portal
8893

8994
This document assumes that you've already deployed a resource group, [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md), and subnet.
@@ -394,6 +399,8 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
394399

395400
### Configure Cluster Framework
396401

402+
After you complete the DRBD and NFS base configuration, add Pacemaker resources for each SAP system and define the required ordering and colocation constraints.
403+
397404
1. **[1]** Add the NFS drbd devices for SAP system NW1 to the cluster configuration
398405

399406
> [!IMPORTANT]

articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
1010
ms.tgt_pltfrm: vm-windows
11-
ms.date: 12/16/2022
11+
ms.date: 03/07/2026
1212
ms.author: juergent
1313
ms.custom:
1414
- H1Hack27Feb2017

articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ There are two options for shared disks in a Windows failover cluster in Azure:
102102
- Use [Azure shared disks](/azure/virtual-machines/disks-shared) to attach Azure Managed Disks to multiple VMs simultaneously.
103103
- Use [SIOS DataKeeper Cluster Edition](https://us.sios.com/products/sios-datakeeper/) to create a mirrored storage that simulates cluster shared storage.
104104

105-
When you're selecting the technology for shared disks, keep in mind the following considerations about Azure shared disks for SAP workloads:
105+
When you select a technology for shared disks, keep in mind the following considerations about Azure shared disks for SAP workloads:
106106

107107
- Use of Azure shared disks with [Azure Premium SSD](/azure/virtual-machines/disks-types#premium-ssds) disks is supported for SAP deployment in availability sets and availability zones.
108108
- [Ultra Disks](/azure/virtual-machines/disks-types#ultra-disks) and [Azure Standard SSDs](/azure/virtual-machines/disks-types#standard-ssds) are not supported as Azure shared disks for SAP workloads.
@@ -121,7 +121,9 @@ You can implement SAP ASCS/SCS HA with [Azure shared disks](/azure/virtual-machi
121121

122122
#### Prerequisites and limitations
123123

124-
Currently, you can use Azure Premium SSDs as Azure shared disks for the SAP ASCS/SCS instance. The following limitations are currently in place:
124+
125+
You can use Azure Premium SSD disks as Azure shared disks for the SAP ASCS/SCS instance. Consider the following limitations:
126+
125127

126128
- [Ultra Disks](/azure/virtual-machines/disks-types#ultra-disks) and [Standard SSDs](/azure/virtual-machines/disks-types#standard-ssds) are not supported as Azure shared disks for SAP workloads.
127129
- [Azure Shared disks](/azure/virtual-machines/disks-shared) with [Premium SSDs](/azure/virtual-machines/disks-types#premium-ssds) are supported for SAP deployment in availability sets and availability zones.
@@ -133,7 +135,7 @@ Currently, you can use Azure Premium SSDs as Azure shared disks for the SAP ASCS
133135
- If you're using PPGs for an SAP system deployed in a region, all virtual machines that share a disk must be part of the same PPG.
134136
- If you're using PPGs for an SAP system deployed across zones, as described in [Proximity placement groups with zonal deployments](proximity-placement-scenarios.md#proximity-placement-groups-with-zonal-deployments), you can attach `Premium_ZRS` storage to virtual machines that share a disk.
135137

136-
For more information, review the [Limitations](/azure/virtual-machines/disks-shared#limitations) section of the documentation for Azure shared disks.
138+
For more information, see the [Limitations](/azure/virtual-machines/disks-shared#limitations) section of the documentation for Azure shared disks.
137139

138140
#### Important considerations for Premium SSD shared disks
139141

articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
1010
ms.tgt_pltfrm: vm-windows
11-
ms.date: 12/16/2022
11+
ms.date: 03/07/2026
1212
ms.author: radeltch
1313
ms.custom: H1Hack27Feb2017
1414
# Customer intent: As a cloud architect, I want to prepare Azure infrastructure for SAP high availability using Windows failover clustering and file shares, so that I can ensure robust performance and reliability for SAP ASCS/SCS instances.

articles/virtual-network/ip-services/public-ip-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ In order to upgrade a public IP, it must not be associated with any resource. Fo
6161
Upgrading a public IP resource retains the IP address.
6262

6363
>[!IMPORTANT]
64-
>In most cases, Public IPs upgraded from Basic to Standard SKU continue to have no [availability zones](/azure/reliability/availability-zones-overview?toc=%2fazure%2fvirtual-network%2ftoc.json). This means they can't be associated with an Azure resource that is either zone-redundant or tied to a prespecified zone in regions where this is offered. (In rare cases where the Basic Public IP has a specific zone assigned, it retains this zone when upgraded to Standard.)
64+
>In most cases, Public IPs upgraded from Basic to Standard SKU become zone-redundant [availability zones](/azure/reliability/availability-zones-overview?toc=%2fazure%2fvirtual-network%2ftoc.json). Note these upgraded IPs will [not show multiple zones in their properties](public-ip-addresses.md#availability-zone), but they are zone-redundant. (In rare cases where the Basic Public IP has a specific zone assigned, it retains this zone when upgraded to Standard.)
6565
6666
> [!NOTE]
6767
> If you have multiple basic SKU public IP addresses attached to a virtual machine, it may be easier to use our [upgrade script](public-ip-upgrade-vm.md).

0 commit comments

Comments
 (0)