You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/workloads/high-availability-guide-suse-nfs.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,9 @@ manager: juergent
7
7
ms.service: sap-on-azure
8
8
ms.subservice: sap-vm-workloads
9
9
ms.topic: article
10
+
10
11
ms.date: 02/02/2026
12
+
11
13
ms.author: radeltch
12
14
ms.custom:
13
15
- linux-related-content
@@ -83,7 +85,10 @@ The NFS server uses a dedicated virtual hostname and virtual IP addresses for ev
83
85
* Probe port 61001 for NW2
84
86
85
87
## 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
+
87
92
### Deploy Linux manually via Azure portal
88
93
89
94
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,
394
399
395
400
### Configure Cluster Framework
396
401
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
+
397
404
1. **[1]** Add the NFS drbd devices for SAP system NW1 to the cluster configuration
Copy file name to clipboardExpand all lines: articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ There are two options for shared disks in a Windows failover cluster in Azure:
102
102
- Use [Azure shared disks](/azure/virtual-machines/disks-shared) to attach Azure Managed Disks to multiple VMs simultaneously.
103
103
- Use [SIOS DataKeeper Cluster Edition](https://us.sios.com/products/sios-datakeeper/) to create a mirrored storage that simulates cluster shared storage.
104
104
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:
106
106
107
107
- 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.
108
108
-[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
121
121
122
122
#### Prerequisites and limitations
123
123
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
+
125
127
126
128
-[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.
127
129
-[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
133
135
- 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.
134
136
- 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.
135
137
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.
137
139
138
140
#### Important considerations for Premium SSD shared disks
Copy file name to clipboardExpand all lines: articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: sap-on-azure
8
8
ms.subservice: sap-vm-workloads
9
9
ms.topic: article
10
10
ms.tgt_pltfrm: vm-windows
11
-
ms.date: 12/16/2022
11
+
ms.date: 03/07/2026
12
12
ms.author: radeltch
13
13
ms.custom: H1Hack27Feb2017
14
14
# 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.
Copy file name to clipboardExpand all lines: articles/virtual-network/ip-services/public-ip-upgrade.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ In order to upgrade a public IP, it must not be associated with any resource. Fo
61
61
Upgrading a public IP resource retains the IP address.
62
62
63
63
>[!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.)
65
65
66
66
> [!NOTE]
67
67
> 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