Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

sql-server-linux-availability-group-cluster-ubuntu.md

Latest commit

 

History

History
181 lines (121 loc) · 4.76 KB

sql-server-linux-availability-group-cluster-ubuntu.md

File metadata and controls

181 lines (121 loc) · 4.76 KB
title Configure Ubuntu Cluster for SQL Server Availability Group | Microsoft Docs
description
author MikeRayMSFT
ms.author mikeray
manager jhubbard
ms.date 02/09/2017
ms.topic article
ms.prod sql-linux
ms.technology database-engine
ms.assetid dd0d6fb9-df0a-41b9-9f22-9b558b2b2233

Configure Ubuntu Cluster for SQL Server Availability Group

Install and configure Pacemaker on each cluster node

[!INCLUDE RHEL-Configure-Pacemaker]

Install mssql-server-ha package

Create a SQL Server login for Pacemaker

[!INCLUDE SLES-Create-SQL-Login]

Open Pacemaker firewall ports

sudo ufw allow 2224/tcp
sudo ufw allow 3121/tcp
sudo ufw allow 21064/tcp
sudo ufw allow 5405/udp
		
sudo ufw allow 1433/tcp # Replace with TDS endpoint
sudo ufw allow 5022/tcp # Replace with DATA_MIRRORING endpoint
		
sudo ufw reload

Alternatively, you can just disable the firewall:

sudo ufw disable

Install Pacemaker packages

On all nodes, run the following commands:

sudo apt-get install pacemaker pcs fence-agents resource-agents

Set password for default user

Set the password for the default user that is created when installing pacemaker and corosync packages. Use the same password on all nodes. The following command sets the password.

sudo passwd hacluster

Enable and start pcsd service and Pacemaker

The following command enables and starts pcsd service and pacemaker. This allows the nodes to rejoin the cluster after reboot.

sudo systemctl enable pcsd
sudo systemctl start pcsd
sudo systemctl enable pacemaker

Create the Cluster

Run the following command on all nodes.

sudo pcs cluster destroy # On all nodes

Run the following command the primary SQL Server.

sudo pcs cluster auth nodeName1 nodeName2  -u hacluster -p <password for hacluster>
sudo pcs cluster setup --name <clusterName> <nodeName1> <nodeName2…> --force
sudo pcs cluster start --all

Disable STONITH

Run the following command to disable STONITH

sudo pcs property set stonith-enabled=false

Create availability group resource

To create the availability group resource, set properties as follows:

  • clone-max: Number of AG replicas, including primary. For example, if you have one primary and one secondary, set this to 2.
  • clone-node-max: Number of secondaries. For example, if you have one primary and one secondary, set this to 1.

The following script sets these properties.

sudo pcs resource create ag_cluster ocf:mssql:ag ag_name=ag1 \
--master meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1

Enable monitoring on master

To enable monitoring, run the following commands on one node.

sudo pcs resource op add ag_cluster monitor interval=11s timeout=60s role=Master
sudo pcs resource op add ag_cluster monitor interval=12s timeout=60s role=Slave

Create virtual IP resource

To create the virtual IP address resource, run the following command on one node. Use an available IP address from the network.

sudo pcs resource create virtualip ocf:heartbeat:IPaddr2 ip=<10.128.16.240>

Add colocation constraint

To add colocation constraint, run the following command on one node.

sudo pcs constraint colocation add virtualip ag_cluster-master INFINITY with-rsc-role=Master

Add ordering constraint

The colocation constraint has an implicit ordering constraint. It moves the virtual IP resource before it moves the availability group resource. By default the sequence of events is:

  1. User issues pcs resource move to the availability group master from node1 to node2.
  2. The virtual IP resource stops on node 1.
  3. The virtual IP resource starts on node 2.

    [!NOTE] At this point, the IP address temporarily points to node 2 while node 2 is still a pre-failover secondary.

  4. The availability group master on node 1 is demoted to slave.
  5. The availability group slave on node 2 is promoted to master.

To prevent the IP address from temporarily pointing to the node with the pre-failover secondary, add an ordering constraint.

To add an ordering constraint, run the following command on one node:

sudo pcs constraint order promote ag_cluster-master then start virtualip

Manual failover

To manually failover to cluster node2, run the following command.

sudo pcs resource move ag_cluster-master node2 --master

Next steps

Create SQL Server Availability Group