Skip to content

Commit a0941dc

Browse files
dennispadiadennispadia
committed
Updated Azure shared disk - ZRS for SAP ASCS/SCS cluster
1 parent aba20d5 commit a0941dc

File tree

5 files changed

+220
-159
lines changed

5 files changed

+220
-159
lines changed

‎articles/virtual-machines/workloads/sap/media/virtual-machines-shared-sap-high-availability-guide/6007-sap-multi-sid-ascs-azure-shared-disk-sid1.png

-25.6 KB
Loading

‎articles/virtual-machines/workloads/sap/media/virtual-machines-shared-sap-high-availability-guide/6008-sap-multi-sid-ascs-azure-shared-disk-sid2.png

-28.1 KB
Loading

‎articles/virtual-machines/workloads/sap/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md

Lines changed: 83 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -21,26 +21,35 @@ ms.custom: H1Hack27Feb2017
2121
# SAP ASCS/SCS instance multi-SID high availability with Windows server failover clustering and Azure shared disk
2222

2323
> ![Windows OS][Logo_Windows] Windows
24-
>
2524
2625
This article focuses on how to move from a single ASCS/SCS installation to an SAP multi-SID configuration by installing additional SAP ASCS/SCS clustered instances into an existing Windows Server Failover Clustering (WSFC) cluster with Azure shared disk. When this process is completed, you have configured an SAP multi-SID cluster.
2726

2827
## Prerequisites and limitations
2928

30-
Currently you can use Azure Premium SSD disks as an Azure shared disk for the SAP ASCS/SCS instance.
31-
The following limitations are in place:
29+
Currently you can use Azure Premium SSD disks as an Azure shared disk for the SAP ASCS/SCS instance. The following limitations are currently in place:
3230

33-
- [Azure Ultra disk](../../disks-types.md#ultra-disk) is not supported as Azure Shared Disk for SAP workloads. Currently it is not possible to place Azure VMs, using Azure Ultra Disk in Availability Set
34-
- [Azure Shared disk](../../disks-shared.md) with Premium SSD disks is only supported with VMs in Availability Set. It is not supported in Availability Zones deployment.
31+
- [Azure Ultra disk](../../disks-types.md#ultra-disk) and [Standard SSD disks](../../disks-types.md#standard-ssd) are not supported as Azure Shared Disk for SAP workloads.
32+
- [Azure Shared disk](../../disks-shared.md) with [Premium SSD disks](../../disks-types#premium-ssd) is supported for SAP deployment in availability set and availability zones.
33+
- Azure shared disk with Premium SSD disks comes with two storage SKUs.
34+
- Locally-redundant storage (LRS) for premium shared disk (skuName - Premium_LRS) is supported with deployment in availability set.
35+
- Zone-redundant storage (ZRS) for premium shared disk (skuName - Premium_ZRS) is supported with deployment in availability zones.
3536
- Azure shared disk value [maxShares](../../disks-shared-enable.md?tabs=azure-cli#disk-sizes) determines how many cluster nodes can use the shared disk. Typically for SAP ASCS/SCS instance you will configure two nodes in Windows Failover Cluster, therefore the value for `maxShares` must be set to two.
36-
- All SAP ASCS/SCS cluster VMs must be deployed in the same [Azure proximity placement group](../../windows/proximity-placement-groups.md).
37-
Although you can deploy Windows cluster VMs in Availability Set with Azure shared disk without PPG, PPG will ensure close physical proximity of Azure shared disks and the cluster VMs, therefore achieving lower latency between the VMs and the storage layer.
37+
- When using [Azure proximity placement group](../../windows/proximity-placement-groups.md) for SAP system, all virtual machines sharing a disk must be part of the same PPG.
3838

39-
For further details on limitations for Azure shared disk, review carefully the [Limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
39+
For further details on limitations for Azure shared disk, please review very carefully the [limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
4040

41-
> [!IMPORTANT]
42-
> When deploying SAP ASCS/SCS Windows Failover cluster with Azure shared disk, be aware that your deployment will be operating with a single shared disk in one storage cluster.
43-
> Your SAP ASCS/SCS instance will be impacted, in case of issues with the storage cluster, where the Azure shared disk is deployed.
41+
#### Important consideration for Premium shared disk
42+
43+
Following are some of the important points to consider with respect to Azure Premium shared disk:
44+
45+
- LRS for Premium shared disk
46+
- SAP deployment with LRS for premium shared disk will be operating with a single Azure shared disk on one storage cluster. Your SAP ASCS/SCS instance would be impacted, in case of issues with the storage cluster, where the Azure shared disk is deployed.
47+
48+
- ZRS for Premium shared disk
49+
- Write latency for ZRS is higher than that of LRS due to cross zonal copy of data.
50+
- The distance between availability zones in different region varies and with that ZRS disk latency across availability zones as well. [Benchmark your disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-benchmarks) to identify the latency of ZRS disk in your region.
51+
- ZRS for Premium shared disk synchronously replicates data across three availability zones in the region. In case of any issue in one of the storage cluster, your SAP ASCS/SCS will continue to run as storage failover is transparent to the application layer.
52+
- Review the the [limitations](../../disks-redundancy.md#limitations) section of ZRS for managed disks for more details.
4453

4554
> [!IMPORTANT]
4655
> The setup must meet the following conditions:
@@ -96,15 +105,33 @@ We'll install a new SAP SID **PR2**, in addition to the **existing clustered** S
96105

97106
### Host names and IP addresses
98107

99-
| Host name role | Host name | Static IP address | Availability set | Proximity placement group |
100-
| --- | --- | --- |---| ---|
101-
| 1st cluster node ASCS/SCS cluster |pr1-ascs-10 |10.0.0.4 |pr1-ascs-avset |PR1PPG |
102-
| 2nd cluster node ASCS/SCS cluster |pr1-ascs-11 |10.0.0.5 |pr1-ascs-avset |PR1PPG |
103-
| Cluster Network Name | pr1clust |10.0.0.42(**only** for Win 2016 cluster) | n/a | n/a |
104-
| **SID1** ASCS cluster network name | pr1-ascscl |10.0.0.43 | n/a | n/a |
105-
| **SID1** ERS cluster network name (**only** for ERS2) | pr1-erscl |10.0.0.44 | n/a | n/a |
106-
| **SID2** ASCS cluster network name | pr2-ascscl |10.0.0.45 | n/a | n/a |
107-
| **SID2** ERS cluster network name (**only** for ERS2) | pr1-erscl |10.0.0.46 | n/a | n/a |
108+
Based on the your deployment type, the host names and the IP addresses of the scenario would be like:
109+
110+
**SAP deployment in Azure availability set**
111+
112+
| Host name role | Host name | Static IP address | Availability set | Disk SkuName |
113+
| ----------------------------------------------------- | ----------- | ---------------------------------------- | ---------------- | ------------ |
114+
| 1st cluster node ASCS/SCS cluster | pr1-ascs-10 | 10.0.0.4 | pr1-ascs-avset | Premium_LRS |
115+
| 2nd cluster node ASCS/SCS cluster | pr1-ascs-11 | 10.0.0.5 | pr1-ascs-avset | |
116+
| Cluster Network Name | pr1clust | 10.0.0.42(**only** for Win 2016 cluster) | n/a | |
117+
| **SID1** ASCS cluster network name | pr1-ascscl | 10.0.0.43 | n/a | |
118+
| **SID1** ERS cluster network name (**only** for ERS2) | pr1-erscl | 10.0.0.44 | n/a | |
119+
| **SID2** ASCS cluster network name | pr2-ascscl | 10.0.0.45 | n/a | |
120+
| **SID2** ERS cluster network name (**only** for ERS2) | pr1-erscl | 10.0.0.46 | n/a | |
121+
122+
**SAP deployment in Azure availability zones**
123+
124+
| Host name role | Host name | Static IP address | Availability zone | Disk SkuName |
125+
| ----------------------------------------------------- | ----------- | ---------------------------------------- | ----------------- | ------------ |
126+
| 1st cluster node ASCS/SCS cluster | pr1-ascs-10 | 10.0.0.4 | AZ01 | Premium_ZRS |
127+
| 2nd cluster node ASCS/SCS cluster | pr1-ascs-11 | 10.0.0.5 | AZ02 | |
128+
| Cluster Network Name | pr1clust | 10.0.0.42(**only** for Win 2016 cluster) | n/a | |
129+
| **SID1** ASCS cluster network name | pr1-ascscl | 10.0.0.43 | n/a | |
130+
| **SID2** ERS cluster network name (**only** for ERS2) | pr1-erscl | 10.0.0.44 | n/a | |
131+
| **SID2** ASCS cluster network name | pr2-ascscl | 10.0.0.45 | n/a | |
132+
| **SID2** ERS cluster network name (**only** for ERS2) | pr1-erscl | 10.0.0.46 | n/a | |
133+
134+
The steps mentioned in the document remains same for both deployment type. But if your cluster is running in availability set, you need to deploy LRS for Azure premium shared disk (Premium_LRS) and if it is running in availability zone deploy ZRS for Azure premium shared disk (Premium_ZRS).
108135

109136
### Create Azure internal load balancer
110137

@@ -166,33 +193,42 @@ As Enqueue Replication Server 2 (ERS2) is also clustered, ERS2 virtual IP addres
166193
Run this command on one of the cluster nodes. You will need to adjust the values for your resource group, Azure region, SAPSID, and so on.
167194

168195
```powershell
169-
$ResourceGroupName = "MyResourceGroup"
170-
$location = "MyRegion"
171-
$SAPSID = "PR2"
172-
$DiskSizeInGB = 512
173-
$DiskName = "$($SAPSID)ASCSSharedDisk"
174-
$NumberOfWindowsClusterNodes = 2
175-
$diskConfig = New-AzDiskConfig -Location $location -SkuName Premium_LRS -CreateOption Empty -DiskSizeGB $DiskSizeInGB -MaxSharesCount $NumberOfWindowsClusterNodes
196+
$ResourceGroupName = "MyResourceGroup"
197+
$location = "MyRegion"
198+
$SAPSID = "PR2"
199+
$DiskSizeInGB = 512
200+
$DiskName = "$($SAPSID)ASCSSharedDisk"
201+
$NumberOfWindowsClusterNodes = 2
202+
203+
# For SAP deployment in availability set, use below storage SkuName
204+
$SkuName = "Premium_LRS"
205+
# For SAP deployment in availability zone, use below storage SkuName
206+
$SkuName = "Premium_ZRS"
207+
208+
$diskConfig = New-AzDiskConfig -Location $location -SkuName $SkuName -CreateOption Empty -DiskSizeGB $DiskSizeInGB -MaxSharesCount $NumberOfWindowsClusterNodes
176209
177-
$dataDisk = New-AzDisk -ResourceGroupName $ResourceGroupName -DiskName $DiskName -Disk $diskConfig
178-
##################################
179-
## Attach the disk to cluster VMs
180-
##################################
181-
# ASCS Cluster VM1
182-
$ASCSClusterVM1 = "pr1-ascs-10"
183-
# ASCS Cluster VM2
184-
$ASCSClusterVM2 = "pr1-ascs-11"
185-
# next free LUN number
186-
$LUNNumber = 1
187-
# Add the Azure Shared Disk to Cluster Node 1
188-
$vm = Get-AzVM -ResourceGroupName $ResourceGroupName -Name $ASCSClusterVM1
189-
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun $LUNNumber
190-
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroupName -Verbose
191-
# Add the Azure Shared Disk to Cluster Node 2
192-
$vm = Get-AzVM -ResourceGroupName $ResourceGroupName -Name $ASCSClusterVM2
193-
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun $LUNNumber
194-
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroupName -Verbose
195-
```
210+
$dataDisk = New-AzDisk -ResourceGroupName $ResourceGroupName -DiskName $DiskName -Disk $diskConfig
211+
##################################
212+
## Attach the disk to cluster VMs
213+
##################################
214+
# ASCS Cluster VM1
215+
$ASCSClusterVM1 = "pr1-ascs-10"
216+
# ASCS Cluster VM2
217+
$ASCSClusterVM2 = "pr1-ascs-11"
218+
# next free LUN number
219+
$LUNNumber = 1
220+
221+
# Add the Azure Shared Disk to Cluster Node 1
222+
$vm = Get-AzVM -ResourceGroupName $ResourceGroupName -Name $ASCSClusterVM1
223+
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun $LUNNumber
224+
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroupName -Verbose
225+
226+
# Add the Azure Shared Disk to Cluster Node 2
227+
$vm = Get-AzVM -ResourceGroupName $ResourceGroupName -Name $ASCSClusterVM2
228+
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun $LUNNumber
229+
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroupName -Verbose
230+
```
231+
196232
### Format the shared disk with PowerShell
197233
1. Get the disk number. Run the PowerShell commands on one of the cluster nodes:
198234

@@ -235,7 +271,7 @@ Run this command on one of the cluster nodes. You will need to adjust the values
235271

236272
4. Register the disk in the cluster.
237273
```powershell
238-
# Add the disk to cluster
274+
# Add the disk to cluster
239275
Get-ClusterAvailableDisk -All | Add-ClusterDisk
240276
# Example output
241277
# Name State OwnerGroup ResourceType

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

Lines changed: 25 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -125,11 +125,11 @@ There are two options for shared disk in a windows failover cluster in Azure:
125125
When selecting the technology for for shared disk, keep in mind the following considerations:
126126

127127
**Azure shared disk for SAP workloads**
128-
- Allows you to attach Azure managed disk to multiple VMs simultaneously without the need for additional software to maintain and operate
129-
- You will be operating with a single Azure shared disk on one storage cluster. That has an impacts on the reliability of your SAP solution.
130-
- Currently the only supported deployment is with Azure shared Premium disk in Availability set. Azure Shared Disk is not supported in zonal deployment.
131-
- Make sure to provision Azure Premium disk with a minimum disk size as specified in [Premium SSD ranges](../../disks-shared.md#disk-sizes) to be able to attach to the required number of VMs simultaneously (typically 2 for SAP ASCS Windows Failover cluster ).
132-
- Azure shared Ultra disk is not supported for SAP workloads, as it doesn't support deployment in Availability set or zonal deployment.
128+
129+
- Allows you to attach Azure managed disk to multiple VMs simultaneously without the need for additional software to maintain and operate.
130+
- [Azure shared disk](../../disks-shared.md) with [Premium SSD](../../disks-types.md#premium-ssd) disks is supported for SAP deployment in availability set and availability zones.
131+
- [Azure Ultra disk](../../disks-types.md#ultra-disk) and [Azure Standard disks](../../disks-types.md#standard-ssd) is not supported as Azure shared disk for SAP workloads.
132+
- Make sure to provision Azure Premium disk with a minimum disk size as specified in [Premium SSD ranges](../../disks-shared.md#disk-sizes) to be able to attach to the required number of VMs simultaneously (typically 2 for SAP ASCS Windows Failover cluster ).
133133

134134
**SIOS**
135135
- The SIOS solution provides real-time synchronous data replication between two disks
@@ -143,19 +143,30 @@ Microsoft is offering [Azure shared disks](../../disks-shared.md), which can be
143143

144144
#### Prerequisites and limitations
145145

146-
Currently you can use Azure Premium SSD disks as an Azure shared disk for the SAP ASCS/SCS instance.
147-
The following limitations are currently in place:
146+
Currently you can use Azure Premium SSD disks as an Azure shared disk for the SAP ASCS/SCS instance. The following limitations are currently in place:
148147

149-
- [Azure Ultra disk](../../disks-types.md#ultra-disk) is not supported as Azure Shared Disk for SAP workloads. Currently it is not possible to place Azure VMs, using Azure Ultra Disk in Availability Set
150-
- [Azure Shared disk](../../disks-shared.md) with Premium SSD disks is only supported with VMs in Availability Set. It is not supported in Availability Zones deployment.
148+
- [Azure Ultra disk](../../disks-types.md#ultra-disk) and [Standard SSD disks](../../disks-types.md#standard-ssd) is not supported as Azure Shared Disk for SAP workloads.
149+
- [Azure Shared disk](../../disks-shared.md) with [Premium SSD disks](../../disks-types#premium-ssd) is supported for SAP deployment in availability set and availability zones.
150+
- Azure shared disk with Premium SSD disks comes with two storage SKUs.
151+
- Locally-redundant storage (LRS) for premium shared disk (skuName - Premium_LRS) is supported with deployment in Azure availability set.
152+
- Zone-redundant storage (ZRS) for premium shared disk (skuName - Premium_ZRS) is supported with deployment in Azure availability zones.
151153
- Azure shared disk value [maxShares](../../disks-shared-enable.md?tabs=azure-cli#disk-sizes) determines how many cluster nodes can use the shared disk. Typically for SAP ASCS/SCS instance you will configure two nodes in Windows Failover Cluster, therefore the value for `maxShares` must be set to two.
152-
- All SAP ASCS/SCS cluster VMs must be deployed in the same [Azure proximity placement group](../../windows/proximity-placement-groups.md).
153-
Although, you can deploy Windows cluster VMs in Availability Set with Azure shared disk without PPG, PPG will ensure close physical proximity of Azure shared disks and the cluster VMs, therefore achieving lower latency between the VMs and the storage layer.
154+
- When using [Azure proximity placement group](../../windows/proximity-placement-groups.md) for SAP system, all virtual machines sharing a disk must be part of the same PPG.
154155

155-
For further details on limitations for Azure shared disk, please review very carefully the [Limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
156+
For further details on limitations for Azure shared disk, please review very carefully the [limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
156157

157-
> [!IMPORTANT]
158-
> When deploying SAP ASCS/SCS Windows Failover cluster with Azure shared disk, be aware that your deployment will be operating with a single shared disk in one storage cluster. Your SAP ASCS/SCS instance would be impacted, in case of issues with the storage cluster, where the Azure shared disk is deployed.
158+
#### Important consideration for Premium shared disk
159+
160+
Following are some of the important points to consider with respect to Azure Premium shared disk:
161+
162+
- LRS for Premium shared disk
163+
- SAP deployment with LRS for Premium shared disk will be operating with a single Azure shared disk on one storage cluster. Your SAP ASCS/SCS instance would be impacted, in case of issues with the storage cluster, where the Azure shared disk is deployed.
164+
165+
- ZRS for Premium shared disk
166+
- Write latency for ZRS is higher than that of LRS due to cross zonal copy of data.
167+
- The distance between availability zones in different region varies and with that ZRS disk latency across availability zones as well. [Benchmark your disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-benchmarks) to identify the latency of ZRS disk in your region.
168+
- ZRS for Premium shared disk synchronously replicates data across three availability zones in the region. In case of any issue in one of the storage cluster, your SAP ASCS/SCS will continue to run as storage failover is transparent to the application layer.
169+
- Review the the [limitations](../../disks-redundancy.md#limitations) section of ZRS for managed disks for more details.
159170

160171
> [!TIP]
161172
> Review the [SAP Netweaver on Azure planning guide](./planning-guide.md) and the [Azure Storage guide for SAP workloads](./planning-guide-storage.md) for important considerations, when planning your SAP deployment.

0 commit comments

Comments
 (0)