SQL Server Deployment for High Availability - SAP NetWeaver on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

SQL Server Deployment for High Availability

  1. Deploy the SAP NetWeaver ASCS instance. For instructions, see the SAP NetWeaver on Amazon Deployment and Operations Guide for Windows .

  2. Create two EC2 instances for Microsoft SQL server, one in each Availability Zone. See the Windows EC2 instances deployment section for steps.

  3. Assign two secondary IP addresses to each instance from the same subnet CIDR in which they are installed:

    1. Use one address for Windows Server Failover Cluster (WSFC).

    2. Use the second address for the Availability Group listener.

      You can assign IP addresses through the Amazon Web Services Management Console, Amazon Command Line Interface (Amazon CLI), or Amazon Tools for Windows PowerShell. For detailed working instructions, see Multiple IP Addresses.

      For example, in the screenshot that follows, is the primary private IP address of the EC2 instance. It has been allocated two secondary private addresses: and

                  Locate the private IP addresses for your EC2 instances.
  4. Domain join EC2 instances created in Step 1. If you are using Amazon Managed Microsoft AD, see Amazon Directory Service documentation for detailed steps.

  5. Log in to the EC2 instance as admin, open PowerShell, and execute the following command to install the Windows Failover Clustering feature.

    Install-WindowsFeature -Name Failover-Clustering -restart -IncludeAllSubFeature

    This command may force your EC2 instance to restart. Make sure you execute the command on both EC2 instances.

  6. Log in as domain admin into one of the EC2 instance and execute the following command to create the Windows Server Failover Cluster. Make sure to replace the placeholders before executing the command.

    New-Cluster -Name <ClusterName> -Node <Node1>,<Node2> -NoStorage

    For example:

    New-Cluster -Name SAPSQLCluster -Node primarysql,secondarysql -NoStorage
  7. Install SQL Server on both EC2 instances. For instructions, see the SAP installation guide.

    Install the database instance on the primary node. Follow SAP installation guide to install Database instance on primary node. Make sure you perform domain installations and choose Domain of Current User or Different Domain as appropriate during parameter selection.

              The domain model parameter.
  8. Create operating system users on secondary instance.

    1. Start sapinst, and in the Available Options pane, navigate to Generic Options > MS SQL Server > Preparations > Operating System Users and Groups.


      The navigation path can vary depending on the version of SWPM you are using.

    2. Create users and groups for this instance, as appropriate.


      You do not need to create users on the primary instance because the database instance was installed on the primary node operating system.

              The Operating System Users and Groups option.
  9. Install SAP Host agent on secondary instance with SWPM.

  10. Create a SQL Server Always On availability group. See the Microsoft documentation for SQL Always On availability group installation instructions.

  11. Adjust the SAP profile files for parameters per the following example. Make sure to replace the <availabilitygroup listener> placeholder with appropriate the value for your setup. For details, refer to SAP Note 1772688 - SQL Server Always On and SAP applications.

    dbs/mss/server = <availabilitygroup listener>;MultiSubnetFailover=yes

    SAPDBHOST = <availabilitygroup listener>

  12. Perform failover and failback of SQL Server to validate it is working correctly.

  13. Continue with installation of primary application server (PAS) and additional application server (AAS) following the instructions in SAP installation guides.