Overview
This post demonstrate the steps to create an AlwaysOn Availability Group (AG) with one replica on a Windows server and the other replica on a Linux server. This configuration is cross-platform because the replicas are on different operating systems. This configuration can be used for migration from one platform to the other or disaster recovery (DR). This configuration does not support high-availability because there is no cluster solution to manage a cross-platform configuration.
The configuration used in this demo consists Linux servers running CentOS 7 – a free, enterprise-class, community-supported distribution based on Red Hat Enterprise Linux (RHEL). CentOS distribution is based on RHEL, the instructions for installing and configuring SQL Server on Linux RHEL apply to CentOS 7.
Scenario
In this post, we will learn how to deploy SQL Server Always On Availability Groups (Cross Platform) without a Pacemaker (Linux cluster resource manager). This is not designed to be a high availability solution, but rather for scale-out readable secondary replicas. In this scenario, two servers are on different operating systems. A Windows Server 2016 named SQL-Windows hosts the primary replica. A Linux server named SQL-Linux host the secondary replica.
High-level overview of the process involved in installing and configuring SQL Server 2019 Always On Availability Groups (Cross Platform).
- Install and configure SQL Server 2019 on both the nodes.
- Create the SQL Server 2019 Always On Availability Group.
- Test and verify both the ways to fail over the primary replica.
Refer the link below to configure SQL Server Always On Availability Group on Windows and Linux (Cross Platform)
Note: Perform these steps in order.
Note: Perform these steps in order.
No comments:
Post a Comment