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: docs/linux/sql-server-linux-availability-group-ha-hpe.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,8 @@ This tutorial explains how to configure SQL Server Always On availability group
17
17
Refer to [HPE Serviceguard Clusters](https://h20195.www2.hpe.com/v2/GetPDF.aspx/c04154488.pdf) for an overview of the HPE Serviceguard clusters.
18
18
19
19
> [!NOTE]
20
-
> Microsoft supports data movement, the availability group, and the SQL Server components. Contact HPE for support related to the documentation HPE Serviceguard cluster and quorum management.
20
+
> Microsoft supports data movement, the availability group, and the SQL Server components. Contact HPE for support related to the documentation of HPE Serviceguard cluster and quorum management.
21
+
21
22
This tutorial consists of the following tasks:
22
23
23
24
> [!div class="checklist"]
@@ -47,10 +48,6 @@ This tutorial consists of the following tasks:
47
48
48
49
## Install SQL Server
49
50
50
-
Install SQL Server on all the three VMs that are going to be part of the Availability Group (AG).
51
-
52
-
### SLES & support SQL OS link
53
-
54
51
On all the three VMs, please follow one of the below steps based on the Linux distribution that you choose for this tutorial, to install SQL Server and tools.
55
52
56
53
### RHEL
@@ -80,8 +77,8 @@ To install Serviceguard, use the `cminstaller` method. Specific instructions are
80
77
Serviceguard cluster and Serviceguard Quorum server
81
78
82
79
*[Install Serviceguard for Linux on two nodes](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Install_serviceguard_using_cminstaller). Refer to the section **Install_serviceguard_using_cminstaller**.
83
-
*[Install Serviceguard quorum server on the third node](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Install_QS_from_the_ISO). Please refer to the section "Install_QS_from_the_ISO".
84
80
*[Install Serviceguard quorum server on the third node](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Install_QS_from_the_ISO). Refer to the section **Install_QS_from_the_ISO**.
81
+
85
82
After you complete the installation of the HPE Serviceguard cluster, you can enable cluster management portal on TCP port 5522 on the primary replica node. The steps below add a rule to the firewall to allow 5522, the command below is for a RHEL distribution, you need to run similar commands for other distributions:
86
83
87
84
```console
@@ -95,8 +92,8 @@ sudo firewall-cmd --reload
95
92
Follow the instructions below to configure and create the HPE Serviceguard cluster. In this step we will also be configuring the quorum server.
96
93
97
94
1.[Configure the Serviceguard quorum server on the third node](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Configure_QS). Refer to the **Configure_QS** section.
98
-
2.[Configure and create Serviceguard cluster on the other two nodes](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Configure_and_create_cluster). Please refer to the "Configure_and_create_Cluster" section.
99
95
2.[Configure and create Serviceguard cluster on the other two nodes](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Configure_and_create_cluster). Refer to the **Configure_and_create_Cluster** section.
96
+
100
97
## Create the availability group and add a sample database
101
98
102
99
In this step, create an availability group with two (or more) synchronous replicas and a configuration only replica, which provides data protection and may also provide high availability. The following diagram represents this architecture:
@@ -295,8 +292,8 @@ For the automatic failover test, you can go ahead and bring down the primary rep
295
292
1. The cluster manager promotes one of the secondary replicas in the availability group to primary.
296
293
2. The failed primary replica automatically joins the cluster after it is back up. The cluster manager promotes it to secondary replica.
297
294
298
-
For HPE Servicguard, refer to the section [**Testing the setup for failover readiness**](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Test_the_setup_preparedness)
295
+
For HPE Serviceguard, refer to the section [**Testing the setup for failover readiness**](https://support.hpe.com/hpesc/public/docDisplay?docId=a00107699en_us#Test_the_setup_preparedness)
299
296
300
297
## Next steps
301
298
302
-
Learn more about Always On [Always On Availability Groups on Linux](sql-server-linux-availability-group-overview.md).
299
+
Learn more about Always On [Availability Groups on Linux](https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-availability-group-overview?view=sql-server-ver15)
0 commit comments