Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: SAP ASCS/SCS instance multi-SID high availability with Windows Server Failover Clustering and file share on Azure description: Multi-SID high availability for SAP ASCS/SCS instances with Windows Server Failover Clustering and file share on Azure author: rdeltcheva manager: juergent ms.assetid: cbf18abe-41cb-44f7-bdec-966f32c89325 ms.service: sap-on-azure ms.subservice: sap-vm-workloads ms.topic: article ms.tgt_pltfrm: vm-windows ms.date: 12/16/2022 ms.author: juergent ms.custom: - H1Hack27Feb2017 - sfi-image-nochange # Customer intent: As a SAP system administrator, I want to configure a multi-SID high availability setup for SAP ASCS/SCS instances using Windows Failover Clustering and Azure file shares, so that I can ensure operational resilience and redundancy for my SAP deployment. --- # SAP ASCS/SCS instance multi-SID high availability with Windows Server Failover Clustering and file share on Azure > ![Windows OS][Logo_Windows] Windows > You can manage multiple virtual IP addresses by using an [Azure internal load balancer][load-balancer-multivip-overview]. If you have an SAP deployment, you can use an internal load balancer to create a Windows cluster configuration for SAP Central Services (ASCS/SCS) instances. 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 **file share**. When this process is completed, you have configured an SAP multi-SID cluster. > [!NOTE] > > This feature is available only in the Azure Resource Manager deployment model. > >There is a limit on the number of private front-end IPs for each Azure internal load balancer. > >The maximum number of SAP ASCS/SCS instances in one WSFC cluster is equal to the maximum number of private front-end IPs for each Azure internal load balancer. > > The configuration introduced in this documentation is not yet supported to be used for [Azure Availability Zones](../../reliability/availability-zones-overview.md) > For more information about load-balancer limits, see the "Private front-end IP per load balancer" section in [Networking limits: Azure Resource Manager][networking-limits-azure-resource-manager]. Also consider using the [Azure Standard Load Balancer SKU](../../load-balancer/load-balancer-standard-availability-zones.md) instead of the basic SKU of the Azure load balancer. ## Prerequisites You have already configured a WSFC cluster to use for one SAP ASCS/SCS instance by using **file share**, as shown in this diagram. ![Figure 1: An SAP ASCS/SCS instance and SOFS deployed in two clusters][sap-ha-guide-figure-8007] _**Figure 1:** An SAP ASCS/SCS instance and SOFS deployed in two clusters_ > [!IMPORTANT] > The setup must meet the following conditions: > * The SAP ASCS/SCS instances must share the same WSFC cluster. > * Different SAP Global Hosts file shares belonging to different SAP SIDs must share the same SOFS cluster. > * The SAP ASCS/SCS instances and the SOFS shares must not be combined in the same cluster. > * Each database management system (DBMS) SID must have its own dedicated WSFC cluster. > * SAP application servers that belong to one SAP system SID must have their own dedicated VMs. > * A mix of Enqueue Replication Server 1 and Enqueue Replication Server 2 in the same cluster is not supported. ## SAP ASCS/SCS multi-SID architecture with file share The goal is to install multiple SAP Advanced Business Application Programming (ASCS) or SAP Java (SCS) clustered instances in the same WSFC cluster, as illustrated here: ![Figure 2: SAP multi-SID configuration in two clusters][sap-ha-guide-figure-8008] _**Figure 2:** SAP multi-SID configuration in two clusters_ The installation of an additional **SAP \<SID2>** system is identical to the installation of one \<SID> system. Two additional preparation steps are required on the ASCS/SCS cluster as well as on the file share SOFS cluster. ## Prepare the infrastructure for an SAP multi-SID scenario ### Prepare the infrastructure on the domain controller Create the domain group **\<Domain>\SAP_\<SID2>_GlobalAdmin**, for example, with \<SID2> = PR2. The domain group name is \<Domain>\SAP_PR2_GlobalAdmin. ### Prepare the infrastructure on the ASCS/SCS cluster You must prepare the infrastructure on the existing ASCS/SCS cluster for a second SAP \<SID>: * Create a virtual host name for the clustered SAP ASCS/SCS instance on the DNS server. * Add an IP address to an existing Azure internal load balancer by using PowerShell. These steps are described in [Infrastructure preparation for an SAP multi-SID scenario][sap-ascs-ha-multi-sid-wsfc-shared-disk-infrast-prepare]. ### Prepare the infrastructure on an SOFS cluster by using the existing SAP Global Host You can reuse the existing \<SAPGlobalHost> and Volume1 of the first SAP \<SID1> system. ![Figure 3: Multi-SID SOFS is the same as the SAP Global Host name][sap-ha-guide-figure-8014] _**Figure 3:** Multi-SID SOFS is the same as the SAP Global Host name_ > [!IMPORTANT] >For the second **SAP \<SID2>** system, the same Volume1 and the same **\<SAPGlobalHost>** network name are used. >Because you have already set **SAPMNT** as the share name for various SAP systems, to reuse the **\<SAPGlobalHost>** network name, you must use the same **Volume1**. > >The file path for the \<SID2> global host is >C:\ClusterStorage\\**Volume1**\usr\sap\<SID2>\SYS\. > For the \<SID2> system, you must prepare the SAP Global Host ..\SYS\.. folder on the SOFS cluster. To prepare the SAP Global Host for the \<SID2> instance, execute the following PowerShell script: ```powershell ################## # SAP multi-SID ################## $SAPSID2 = "PR2" $DomainName2 = "SAPCLUSTER" $SAPSIDGlobalAdminGroupName2 = "$DomainName2\SAP_" + $SAPSID2 + "_GlobalAdmin" # SAP ASCS/SCS cluster nodes $ASCSCluster2Node1 = "ja1-ascs-0" $ASCSCluster2Node2 = "ja1-ascs-1" # Define the SAP ASCS/SCS cluster node computer objects $ASCSCluster2ObjectNode1 = "$DomainName2\$ASCSCluster2Node1$" $ASCSCluster2ObjectNode2 = "$DomainName2\$ASCSCluster2Node2$" # Create usr\sap\.. folders on CSV $SAPGlobalFolder2 = "C:\ClusterStorage\Volume1\usr\sap\$SAPSID2\SYS" New-Item -Path $SAPGlobalFolder2 -ItemType Directory # Add permissions for the SAP SID2 system Grant-SmbShareAccess -Name sapmnt -AccountName $SAPSIDGlobalAdminGroupName2, $ASCSCluster2ObjectNode1, $ASCSCluster2ObjectNode2 -AccessRight Full -Force $UsrSAPFolder = "C:\ClusterStorage\Volume1\usr\sap\" # Set file and folder security $Acl = Get-Acl $UsrSAPFolder # Add the security object of the SAP_<sid>_GlobalAdmin group $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($SAPSIDGlobalAdminGroupName2,"FullControl", 'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Add the security object of the clusternode1$ computer object $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($ASCSCluster2ObjectNode1,"FullControl",'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Add the security object of the clusternode2$ computer object $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($ASCSCluster2ObjectNode2,"FullControl",'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Set security Set-Acl $UsrSAPFolder $Acl -Verbose ``` ### Prepare the infrastructure on the SOFS cluster by using a different SAP Global Host You can configure the second SOFS (for example, the second SOFS cluster role with **\<SAPGlobalHost2>** and a different **Volume2** for the second **\<SID2>**). ![Figure 4: Multi-SID SOFS is the same as the SAP GLOBAL host name 2][sap-ha-guide-figure-8015] _**Figure 4:** Multi-SID SOFS is the same as SAP GLOBAL host name 2_ To create the second SOFS role with \<SAPGlobalHost2>, execute this PowerShell script: ```powershell # Create SOFS with SAP Global Host Name 2 $SAPGlobalHostName = "sapglobal2" Add-ClusterScaleOutFileServerRole -Name $SAPGlobalHostName ``` Create the second **Volume2**. Execute this PowerShell script: ```powershell New-Volume -StoragePoolFriendlyName S2D* -FriendlyName SAPPR2 -FileSystem CSVFS_ReFS -Size 5GB -ResiliencySettingName Mirror ``` ![Figure 5: Second Volume2 in Failover Cluster Manager][sap-ha-guide-figure-8016] _**Figure 5:** Second Volume2 in Failover Cluster Manager_ Create an SAP Global folder for the second \<SID2>, and set file security. Execute this PowerShell script: ```powershell # Create a folder for <SID2> on a second Volume2 and set file security $SAPSID = "PR2" $DomainName = "SAPCLUSTER" $SAPSIDGlobalAdminGroupName = "$DomainName\SAP_" + $SAPSID + "_GlobalAdmin" # SAP ASCS/SCS cluster nodes $ASCSClusterNode1 = "ascs-1" $ASCSClusterNode2 = "ascs-2" # Define SAP ASCS/SCS cluster node computer objects $ASCSClusterObjectNode1 = "$DomainName\$ASCSClusterNode1$" $ASCSClusterObjectNode2 = "$DomainName\$ASCSClusterNode2$" # Create usr\sap\.. folders on CSV $SAPGlobalFolder = "C:\ClusterStorage\Volume2\usr\sap\$SAPSID\SYS" New-Item -Path $SAPGlobalFOlder -ItemType Directory $UsrSAPFolder = "C:\ClusterStorage\Volume2\usr\sap\" # Set file and folder security $Acl = Get-Acl $UsrSAPFolder # Add the file security object of the SAP_<sid>_GlobalAdmin group $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($SAPSIDGlobalAdminGroupName,"FullControl", 'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Add the security object of the clusternode1$ computer object $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($ASCSClusterObjectNode1,"FullControl",'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Add the security object of the clusternode2$ computer object $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($ASCSClusterObjectNode2,"FullControl",'ContainerInherit,ObjectInherit', 'None', 'Allow') $Acl.SetAccessRule($Ar) # Set security Set-Acl $UsrSAPFolder $Acl -Verbose ``` To create a SAPMNT file share on Volume2 with the *\<SAPGlobalHost2>* host name for the second SAP \<SID2>, start the **Add File Share** wizard in Failover Cluster Manager. Right-click the **saoglobal2** SOFS cluster group, and then select **Add File Share**. ![Figure 6: Start the "Add File Share" wizard][sap-ha-guide-figure-8017] _**Figure 6:** Start "Add File Share" wizard_ <br> ![Figure 7: "Select SMB Share – Quick"][sap-ha-guide-figure-8018] _**Figure 7:** Select "SMB Share – Quick"_ <br> ![Figure 8: Select "sapglobalhost2" and specify path on Volume2][sap-ha-guide-figure-8019] _**Figure 8:** Select "sapglobalhost2" and specify path on Volume2_ <br> ![Figure 9: Set file share name to "sapmnt"][sap-ha-guide-figure-8020] _**Figure 9:** Set file share name to "sapmnt"_ <br> ![Figure 10: Disable all settings][sap-ha-guide-figure-8021] _**Figure 10:** Disable all settings_ <br> Assign *Full control* permissions to files and sapmnt share for: * The **SAP_\<SID>_GlobalAdmin** domain user group * Computer object of ASCS/SCS cluster nodes **ascs-1$** and **ascs-2$** ![Figure 11: Assign Full control permissions to user group and computer accounts][sap-ha-guide-figure-8022] _**Figure 11:** Assign "Full control" to user group and computer accounts_ <br> ![Figure 12: Select "Create"][sap-ha-guide-figure-8023] _**Figure 12:** Select "Create"_ <br> ![Figure 13: The second sapmnt bound to sapglobal2 host and Volume2 is created][sap-ha-guide-figure-8024] _**Figure 13:** The second sapmnt bound to sapglobal2 host and Volume2 is created_ <br> ## Install SAP NetWeaver multi-SID ### Install SAP \<SID2> ASCS/SCS and ERS instances Follow the same installation and configuration steps as described earlier for one SAP \<SID>. ### Install DBMS and SAP application servers Install DBMS and SAP application Servers as described earlier. ## Next steps * [Install an ASCS/SCS instance on a failover cluster with no shared disks][sap-official-ha-file-share-document]: Official SAP guidelines for an HA file share * [Storage spaces direct in Windows Server 2016][s2d-in-win-2016] * [Scale-out file server for application data overview][sofs-overview] * [What's new in storage in Windows Server 2016][new-in-win-2016-storage] [1928533]:https://launchpad.support.sap.com/#/notes/1928533 [1999351]:https://launchpad.support.sap.com/#/notes/1999351 [2015553]:https://launchpad.support.sap.com/#/notes/2015553 [2178632]:https://launchpad.support.sap.com/#/notes/2178632 [2243692]:https://launchpad.support.sap.com/#/notes/2243692 [1869038]:https://launchpad.support.sap.com/#/notes/1869038 [2287140]:https://launchpad.support.sap.com/#/notes/2287140 [2492395]:https://launchpad.support.sap.com/#/notes/2492395 [s2d-in-win-2016]:/windows-server/storage/storage-spaces/storage-spaces-direct-overview [sofs-overview]:https://technet.microsoft.com/library/hh831349(v=ws.11).aspx [new-in-win-2016-storage]:/windows-server/storage/whats-new-in-storage [sap-installation-guides]:http://service.sap.com/instguides [networking-limits-azure-resource-manager]:../../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits [azure-resource-manager/management/azure-subscription-service-limits]:../../azure-resource-manager/management/azure-subscription-service-limits.md [azure-resource-manager/management/azure-subscription-service-limits-subscription]:../../azure-resource-manager/management/azure-subscription-service-limits.md [load-balancer-multivip-overview]:../../load-balancer/load-balancer-multivip-overview.md [dbms-guide]:../../virtual-machines-windows-sap-dbms-guide-general.md [deployment-guide]:deployment-guide.md [dr-guide-classic]:https://go.microsoft.com/fwlink/?LinkID=521971 [getting-started]:get-started.md [planning-guide]:planning-guide.md [planning-guide-11]:planning-guide.md [planning-guide-2.1]:planning-guide.md#1625df66-4cc6-4d60-9202-de8a0b77f803 [planning-guide-2.2]:planning-guide.md#f5b3b18c-302c-4bd8-9ab2-c388f1ab3d10 [planning-guide-microsoft-azure-networking]:planning-guide.md#61678387-8868-435d-9f8c-450b2424f5bd [planning-guide-storage-microsoft-azure-storage-and-data-disks]:planning-guide.md#a72afa26-4bf4-4a25-8cf7-855d6032157f [sap-ha-guide-2]:#42b8f600-7ba3-4606-b8a5-53c4f026da08 [sap-ha-guide-4]:#8ecf3ba0-67c0-4495-9c14-feec1a2255b7 [sap-ha-guide-8]:#78092dbe-165b-454c-92f5-4972bdbef9bf [sap-ha-guide-8.1]:#c87a8d3f-b1dc-4d2f-b23c-da4b72977489 [sap-ha-guide-8.9]:#fe0bd8b5-2b43-45e3-8295-80bee5415716 [sap-ha-guide-8.11]:#661035b2-4d0f-4d31-86f8-dc0a50d78158 [sap-ha-guide-8.12]:#0d67f090-7928-43e0-8772-5ccbf8f59aab [sap-ha-guide-8.12.1]:#5eecb071-c703-4ccc-ba6d-fe9c6ded9d79 [sap-ha-guide-8.12.3]:#5c8e5482-841e-45e1-a89d-a05c0907c868 [sap-ha-guide-8.12.3.1]:#1c2788c3-3648-4e82-9e0d-e058e475e2a3 [sap-ha-guide-8.12.3.2]:#dd41d5a2-8083-415b-9878-839652812102 [sap-ha-guide-8.12.3.3]:#d9c1fc8e-8710-4dff-bec2-1f535db7b006 [sap-ha-guide-9]:#a06f0b49-8a7a-42bf-8b0d-c12026c5746b [sap-ha-guide-9.1]:#31c6bd4f-51df-4057-9fdf-3fcbc619c170 [sap-ha-guide-9.1.1]:#a97ad604-9094-44fe-a364-f89cb39bf097 [sap-ascs-ha-multi-sid-wsfc-shared-disk]:sap-ascs-ha-multi-sid-wsfc-shared-disk.md [sap-ascs-ha-multi-sid-wsfc-shared-disk-infrast-prepare]:sap-ascs-ha-multi-sid-wsfc-shared-disk.md#25e358f8-92e5-4e8d-a1e5-df7580a39cb0 [Logo_Linux]:media/virtual-machines-shared-sap-shared/Linux.png [Logo_Windows]:media/virtual-machines-shared-sap-shared/Windows.png [sap-ha-guide-figure-1000]:./media/virtual-machines-shared-sap-high-availability-guide/1000-wsfc-for-sap-ascs-on-azure.png [sap-ha-guide-figure-1001]:./media/virtual-machines-shared-sap-high-availability-guide/1001-wsfc-on-azure-ilb.png [sap-ha-guide-figure-1002]:./media/virtual-machines-shared-sap-high-availability-guide/1002-wsfc-sios-on-azure-ilb.png [sap-ha-guide-figure-2000]:./media/virtual-machines-shared-sap-high-availability-guide/2000-wsfc-sap-as-ha-on-azure.png [sap-ha-guide-figure-2001]:./media/virtual-machines-shared-sap-high-availability-guide/2001-wsfc-sap-ascs-ha-on-azure.png [sap-ha-guide-figure-2003]:./media/virtual-machines-shared-sap-high-availability-guide/2003-wsfc-sap-dbms-ha-on-azure.png [sap-ha-guide-figure-2004]:./media/virtual-machines-shared-sap-high-availability-guide/2004-wsfc-sap-ha-e2e-archit-template1-on-azure.png [sap-ha-guide-figure-2005]:./media/virtual-machines-shared-sap-high-availability-guide/2005-wsfc-sap-ha-e2e-arch-template2-on-azure.png [sap-ha-guide-figure-3000]:./media/virtual-machines-shared-sap-high-availability-guide/3000-template-parameters-sap-ha-arm-on-azure.png [sap-ha-guide-figure-3001]:./media/virtual-machines-shared-sap-high-availability-guide/3001-configuring-dns-servers-for-Azure-vnet.png [sap-ha-guide-figure-3002]:./media/virtual-machines-shared-sap-high-availability-guide/3002-configuring-static-IP-address-for-network-card-of-each-vm.png [sap-ha-guide-figure-3003]:./media/virtual-machines-shared-sap-high-availability-guide/3003-setup-static-ip-address-ilb-for-ascs-instance.png [sap-ha-guide-figure-3004]:./media/virtual-machines-shared-sap-high-availability-guide/3004-default-ascs-scs-ilb-balancing-rules-for-azure-ilb.png [sap-ha-guide-figure-3005]:./media/virtual-machines-shared-sap-high-availability-guide/3005-changing-ascs-scs-default-ilb-rules-for-azure-ilb.png [sap-ha-guide-figure-3006]:./media/virtual-machines-shared-sap-high-availability-guide/3006-adding-vm-to-domain.png [sap-ha-guide-figure-3007]:./media/virtual-machines-shared-sap-high-availability-guide/3007-config-wsfc-1.png [sap-ha-guide-figure-3008]:./media/virtual-machines-shared-sap-high-availability-guide/3008-config-wsfc-2.png [sap-ha-guide-figure-3009]:./media/virtual-machines-shared-sap-high-availability-guide/3009-config-wsfc-3.png [sap-ha-guide-figure-3010]:./media/virtual-machines-shared-sap-high-availability-guide/3010-config-wsfc-4.png [sap-ha-guide-figure-3011]:./media/virtual-machines-shared-sap-high-availability-guide/3011-config-wsfc-5.png [sap-ha-guide-figure-3012]:./media/virtual-machines-shared-sap-high-availability-guide/3012-config-wsfc-6.png [sap-ha-guide-figure-3013]:./media/virtual-machines-shared-sap-high-availability-guide/3013-config-wsfc-7.png [sap-ha-guide-figure-3014]:./media/virtual-machines-shared-sap-high-availability-guide/3014-config-wsfc-8.png [sap-ha-guide-figure-3015]:./media/virtual-machines-shared-sap-high-availability-guide/3015-config-wsfc-9.png [sap-ha-guide-figure-3016]:./media/virtual-machines-shared-sap-high-availability-guide/3016-config-wsfc-10.png [sap-ha-guide-figure-3017]:./media/virtual-machines-shared-sap-high-availability-guide/3017-config-wsfc-11.png [sap-ha-guide-figure-3018]:./media/virtual-machines-shared-sap-high-availability-guide/3018-config-wsfc-12.png [sap-ha-guide-figure-3019]:./media/virtual-machines-shared-sap-high-availability-guide/3019-assign-permissions-on-share-for-cluster-name-object.png [sap-ha-guide-figure-3020]:./media/virtual-machines-shared-sap-high-availability-guide/3020-change-object-type-include-computer-objects.png [sap-ha-guide-figure-3021]:./media/virtual-machines-shared-sap-high-availability-guide/3021-check-box-for-computer-objects.png [sap-ha-guide-figure-3022]:./media/virtual-machines-shared-sap-high-availability-guide/3022-set-security-attributes-for-cluster-name-object-on-file-share-quorum.png [sap-ha-guide-figure-3023]:./media/virtual-machines-shared-sap-high-availability-guide/3023-call-configure-cluster-quorum-setting-wizard.png [sap-ha-guide-figure-3024]:./media/virtual-machines-shared-sap-high-availability-guide/3024-selection-screen-different-quorum-configurations.png [sap-ha-guide-figure-3025]:./media/virtual-machines-shared-sap-high-availability-guide/3025-selection-screen-file-share-witness.png [sap-ha-guide-figure-3026]:./media/virtual-machines-shared-sap-high-availability-guide/3026-define-file-share-location-for-witness-share.png [sap-ha-guide-figure-3027]:./media/virtual-machines-shared-sap-high-availability-guide/3027-successful-reconfiguration-cluster-file-share-witness.png [sap-ha-guide-figure-3028]:./media/virtual-machines-shared-sap-high-availability-guide/3028-install-dot-net-framework-35.png [sap-ha-guide-figure-3029]:./media/virtual-machines-shared-sap-high-availability-guide/3029-install-dot-net-framework-35-progress.png [sap-ha-guide-figure-3030]:./media/virtual-machines-shared-sap-high-availability-guide/3030-sios-installer.png [sap-ha-guide-figure-3031]:./media/virtual-machines-shared-sap-high-availability-guide/3031-first-screen-sios-data-keeper-installation.png [sap-ha-guide-figure-3032]:./media/virtual-machines-shared-sap-high-availability-guide/3032-data-keeper-informs-service-be-disabled.png [sap-ha-guide-figure-3033]:./media/virtual-machines-shared-sap-high-availability-guide/3033-user-selection-sios-data-keeper.png [sap-ha-guide-figure-3034]:./media/virtual-machines-shared-sap-high-availability-guide/3034-domain-user-sios-data-keeper.png [sap-ha-guide-figure-3035]:./media/virtual-machines-shared-sap-high-availability-guide/3035-provide-sios-data-keeper-license.png [sap-ha-guide-figure-3036]:./media/virtual-machines-shared-sap-high-availability-guide/3036-data-keeper-management-config-tool.png [sap-ha-guide-figure-3037]:./media/virtual-machines-shared-sap-high-availability-guide/3037-tcp-ip-address-first-node-data-keeper.png [sap-ha-guide-figure-3038]:./media/virtual-machines-shared-sap-high-availability-guide/3038-create-replication-sios-job.png [sap-ha-guide-figure-3039]:./media/virtual-machines-shared-sap-high-availability-guide/3039-define-sios-replication-job-name.png [sap-ha-guide-figure-3040]:./media/virtual-machines-shared-sap-high-availability-guide/3040-define-sios-source-node.png [sap-ha-guide-figure-3041]:./media/virtual-machines-shared-sap-high-availability-guide/3041-define-sios-target-node.png [sap-ha-guide-figure-3042]:./media/virtual-machines-shared-sap-high-availability-guide/3042-define-sios-synchronous-replication.png [sap-ha-guide-figure-3043]:./media/virtual-machines-shared-sap-high-availability-guide/3043-enable-sios-replicated-volume-as-cluster-volume.png [sap-ha-guide-figure-3044]:./media/virtual-machines-shared-sap-high-availability-guide/3044-data-keeper-synchronous-mirroring-for-SAP-gui.png [sap-ha-guide-figure-3045]:./media/virtual-machines-shared-sap-high-availability-guide/3045-replicated-disk-by-data-keeper-in-wsfc.png [sap-ha-guide-figure-3046]:./media/virtual-machines-shared-sap-high-availability-guide/3046-dns-entry-sap-ascs-virtual-name-ip.png [sap-ha-guide-figure-3047]:./media/virtual-machines-shared-sap-high-availability-guide/3047-dns-manager.png [sap-ha-guide-figure-3048]:./media/virtual-machines-shared-sap-high-availability-guide/3048-default-cluster-probe-port.png [sap-ha-guide-figure-3049]:./media/virtual-machines-shared-sap-high-availability-guide/3049-cluster-probe-port-after.png [sap-ha-guide-figure-3050]:./media/virtual-machines-shared-sap-high-availability-guide/3050-service-type-ers-delayed-automatic.png [sap-ha-guide-figure-5000]:./media/virtual-machines-shared-sap-high-availability-guide/5000-wsfc-sap-sid-node-a.png [sap-ha-guide-figure-5001]:./media/virtual-machines-shared-sap-high-availability-guide/5001-sios-replicating-local-volume.png [sap-ha-guide-figure-5002]:./media/virtual-machines-shared-sap-high-availability-guide/5002-wsfc-sap-sid-node-b.png [sap-ha-guide-figure-5003]:./media/virtual-machines-shared-sap-high-availability-guide/5003-sios-replicating-local-volume-b-to-a.png [sap-ha-guide-figure-6001]:media/virtual-machines-shared-sap-high-availability-guide/6001-sap-multi-sid-ascs-scs-sid1.png [sap-ha-guide-figure-6002]:media/virtual-machines-shared-sap-high-availability-guide/6002-sap-multi-sid-ascs-scs.png [sap-ha-guide-figure-6003]:media/virtual-machines-shared-sap-high-availability-guide/6003-sap-multi-sid-full-landscape.png [sap-ha-guide-figure-6004]:media/virtual-machines-shared-sap-high-availability-guide/6004-sap-multi-sid-dns.png [sap-ha-guide-figure-6005]:media/virtual-machines-shared-sap-high-availability-guide/6005-sap-multi-sid-azure-portal.png [sap-ha-guide-figure-6006]:media/virtual-machines-shared-sap-high-availability-guide/6006-sap-multi-sid-sios-replication.png [sap-ha-guide-figure-8001]:./media/virtual-machines-shared-sap-high-availability-guide/8001.png [sap-ha-guide-figure-8002]:./media/virtual-machines-shared-sap-high-availability-guide/8002.png [sap-ha-guide-figure-8003]:./media/virtual-machines-shared-sap-high-availability-guide/8003.png [sap-ha-guide-figure-8004]:./media/virtual-machines-shared-sap-high-availability-guide/8004.png [sap-ha-guide-figure-8005]:./media/virtual-machines-shared-sap-high-availability-guide/8005.png [sap-ha-guide-figure-8006]:./media/virtual-machines-shared-sap-high-availability-guide/8006.png [sap-ha-guide-figure-8007]:./media/virtual-machines-shared-sap-high-availability-guide/8007.png [sap-ha-guide-figure-8008]:./media/virtual-machines-shared-sap-high-availability-guide/8008.png [sap-ha-guide-figure-8009]:./media/virtual-machines-shared-sap-high-availability-guide/8009.png [sap-ha-guide-figure-8010]:./media/virtual-machines-shared-sap-high-availability-guide/8010.png [sap-ha-guide-figure-8011]:./media/virtual-machines-shared-sap-high-availability-guide/8011.png [sap-ha-guide-figure-8012]:./media/virtual-machines-shared-sap-high-availability-guide/8012.png [sap-ha-guide-figure-8013]:./media/virtual-machines-shared-sap-high-availability-guide/8013.png [sap-ha-guide-figure-8014]:./media/virtual-machines-shared-sap-high-availability-guide/8014.png [sap-ha-guide-figure-8015]:./media/virtual-machines-shared-sap-high-availability-guide/8015.png [sap-ha-guide-figure-8016]:./media/virtual-machines-shared-sap-high-availability-guide/8016.png [sap-ha-guide-figure-8017]:./media/virtual-machines-shared-sap-high-availability-guide/8017.png [sap-ha-guide-figure-8018]:./media/virtual-machines-shared-sap-high-availability-guide/8018.png [sap-ha-guide-figure-8019]:./media/virtual-machines-shared-sap-high-availability-guide/8019.png [sap-ha-guide-figure-8020]:./media/virtual-machines-shared-sap-high-availability-guide/8020.png [sap-ha-guide-figure-8021]:./media/virtual-machines-shared-sap-high-availability-guide/8021.png [sap-ha-guide-figure-8022]:./media/virtual-machines-shared-sap-high-availability-guide/8022.png [sap-ha-guide-figure-8023]:./media/virtual-machines-shared-sap-high-availability-guide/8023.png [sap-ha-guide-figure-8024]:./media/virtual-machines-shared-sap-high-availability-guide/8024.png [sap-ha-guide-figure-8025]:./media/virtual-machines-shared-sap-high-availability-guide/8025.png [sap-templates-3-tier-multisid-xscs-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-xscs%2Fazuredeploy.json [sap-templates-3-tier-multisid-xscs-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fapplication-workloads%2Fsap%2Fsap-3-tier-marketplace-image-multi-sid-xscs-md%2Fazuredeploy.json [sap-templates-3-tier-multisid-db-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-db%2Fazuredeploy.json [sap-templates-3-tier-multisid-db-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fapplication-workloads%2Fsap%2Fsap-3-tier-marketplace-image-multi-sid-db-md%2Fazuredeploy.json [sap-templates-3-tier-multisid-apps-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-apps%2Fazuredeploy.json [sap-templates-3-tier-multisid-apps-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fapplication-workloads%2Fsap%2Fsap-3-tier-marketplace-image-multi-sid-apps-md%2Fazuredeploy.json [virtual-machines-azure-resource-manager-architecture-benefits-arm]:../../azure-resource-manager/management/overview.md#the-benefits-of-using-resource-manager [virtual-machines-manage-availability]:../../virtual-machines/availability.md