Uređivanje

Dijeli putem

SQL Server availability basics for Linux deployments

Applies to: SQL Server on Linux

Starting with SQL Server 2017 (14.x), SQL Server is supported on both Linux and Windows. Like Windows-based SQL Server deployments, SQL Server databases and instances need to be highly available under Linux.

This article covers the technical aspects of planning and deploying highly available Linux-based SQL Server instances and databases, and highlights key differences from Windows-based installations. Because either SQL Server or Linux might be new to you, this article discusses concepts that might already be familiar to you.

SQL Server availability options for Linux deployments

Besides backup and restore, the same three availability features are available on Linux as for Windows-based deployments:

On Windows, FCIs always require an underlying Windows Server failover cluster (WSFC). Depending on the deployment scenario, an AG usually requires an underlying WSFC, with the exception being the new None variant in SQL Server 2017 (14.x). A WSFC doesn't exist in Linux. Clustering implementation in Linux is discussed in Pacemaker for availability groups and failover cluster instances on Linux.

A quick Linux primer

While some Linux installations include an interface, most don't. You use the command line for nearly everything at the operating system layer. The common term for this command line in the Linux world is a shell, the most common being bash.

In Linux, you need elevated privileges to run many commands, similar to needing administrator privileges in Windows Server. You can run commands with elevated privileges in two ways:

  1. Run the command as the proper user. To change to a different user, use the su command. If you run su without a username, you enter a shell as root if you know the password.

  2. Use sudo before the command. This method is more common and more secure. Many examples in this article use sudo.

Here are some common commands. Each command has various switches and options that you can research online:

  • cd - change the directory
  • chmod - change the permissions of a file or directory
  • chown - change the ownership of a file or directory
  • ls - show the contents of a directory
  • mkdir - create a folder (directory) on a drive
  • mv - move a file from one location to another
  • ps - show all of the working processes
  • rm - delete a file locally on a server
  • rmdir - delete a folder (directory)
  • systemctl - start, stop, or enable services
  • Text editor commands. On Linux, there are various text editor options, such as vi and emacs.

Common tasks for availability configurations of SQL Server on Linux

This section covers tasks that are common to all Linux-based SQL Server deployments.

Ensure that you can copy files

Anyone administering SQL Server on Linux should be able to copy files from one server to another. This task is essential for AG configurations.

Permission problems can exist on both Linux and Windows-based installations. However, Windows users familiar with how to copy files from server to server, might not be familiar with how it's done on Linux. A common method is to use the command-line utility scp, which stands for secure copy. Behind the scenes, scp uses OpenSSH. SSH stands for secure shell. Depending on the Linux distribution, OpenSSH itself might not be installed. If it isn't, you need to install OpenSSH.

For more information on configuring OpenSSH for your Linux distribution, see:

Note

Starting in SQL Server 2025 (17.x), SUSE Linux Enterprise Server (SLES) isn't supported.

When you use scp, you must provide the credentials of the server if it isn't the source or destination. For example, the following command copies the file MyAGCert.cer to the folder specified on the other server:

scp MyAGCert.cer username@servername:/folder/subfolder

You must have permissions, and possibly ownership, of the file to copy it, so you might need to use chown before copying. Similarly, on the receiving side, the right user needs access to manipulate the file. For example, to restore that certificate file, the mssql user must be able to access it.

Samba, which is the Linux variant of server message block (SMB), can also be used to create shares accessed by UNC paths such as \\SERVERNAME\SHARE. For more information on configuring Samba, see the information at the following links for each distribution:

Note

Starting in SQL Server 2025 (17.x), SUSE Linux Enterprise Server (SLES) isn't supported.

You can also use Windows-based SMB shares. SMB shares don't need to be Linux-based, as long as the client portion of Samba is configured properly on the Linux server hosting SQL Server and the share has the right access. For customers in a mixed environment, this approach lets you use existing infrastructure for Linux-based SQL Server deployments.

The version of Samba you deploy should be SMB 3.0 compliant. When SMB support was added in SQL Server 2012 (11.x), it required all shares to support SMB 3.0. If you use Samba for the share and not Windows Server, the Samba-based share should use Samba 4.0 or later, and ideally 4.3 or later, which supports SMB 3.1.1. A good source of information on SMB and Linux is SMB3 in Samba.

Finally, using a network file system (NFS) share is an option. You can't use NFS on Windows-based deployments of SQL Server, and it can only be used for Linux-based deployments.

Configure the firewall

Similar to Windows, Linux distributions have a built-in firewall. If your organization uses an external firewall for the servers, you might be able to disable the firewalls in Linux. However, regardless of where you enable the firewall, you need to open ports. The following table lists the common ports needed for highly available SQL Server deployments on Linux.

Port Number Type Description
111 TCP/UDP NFS - rpcbind/sunrpc
135 TCP Samba (if used) - Endpoint Mapper
137 UDP Samba (if used) - NetBIOS Name Service
138 UDP Samba (if used) - NetBIOS Datagram
139 TCP Samba (if used) - NetBIOS Session
445 TCP Samba (if used) - SMB over TCP
1433 TCP SQL Server - default port; if desired, can change with mssql-conf set network.tcpport <portnumber>
2049 TCP, UDP NFS (if used)
2224 TCP Pacemaker - used by pcsd
3121 TCP Pacemaker - Required if there are Pacemaker Remote nodes
3260 TCP iSCSI Initiator (if used) - Can be altered in /etc/iscsi/iscsid.config (RHEL), but should match port of iSCSI Target
5022 TCP SQL Server - default port used for an AG endpoint; can be changed when creating the endpoint
5403 TCP Pacemaker
5404 UDP Pacemaker - Required by Corosync if using multicast UDP
5405 UDP Pacemaker - Required by Corosync
21064 TCP Pacemaker - Required by resources using DLM
Variable TCP AG endpoint port; default is 5022
Variable TCP NFS - port for LOCKD_TCPPORT (found in /etc/sysconfig/nfs on RHEL)
Variable UDP NFS - port for LOCKD_UDPPORT (found in /etc/sysconfig/nfs on RHEL)
Variable TCP/UDP NFS - port for MOUNTD_PORT (found in /etc/sysconfig/nfs on RHEL)
Variable TCP/UDP NFS - port for STATD_PORT (found in /etc/sysconfig/nfs on RHEL)

For other ports that Samba uses, see Samba Port Usage.

Conversely, you can add the name of the service under Linux as an exception instead of the port. For example, use high-availability for Pacemaker. Refer to your distribution for the appropriate names. On RHEL, for example, the command to add in Pacemaker is:

sudo firewall-cmd --permanent --add-service=high-availability

Firewall documentation

Note

Starting in SQL Server 2025 (17.x), SUSE Linux Enterprise Server (SLES) isn't supported.

Install SQL Server packages for availability

On a Windows-based SQL Server installation, some components are installed even in a basic engine install, while others aren't. Under Linux, only the SQL Server engine is installed as part of the installation process. Everything else is optional. For highly available SQL Server instances under Linux, two packages should be installed with SQL Server:

  • SQL Server Agent (mssql-server-agent)
  • the high availability (HA) package (mssql-server-ha)

While SQL Server Agent is technically optional, it's the default scheduler for SQL Server jobs, and is required by log shipping, so installation is recommended.

On SQL Server 2017 (14.x) with CU 4 and later versions, SQL Server Agent is included in the Database Engine package, but you still need to enable it. On Windows-based installations, SQL Server Agent isn't optional.

Note

SQL Server Agent is the built-in job scheduler for SQL Server. It's used to schedule tasks such as backups and routine maintenance. On Windows, SQL Server Agent runs as a separate service. On Linux, it runs in the context of SQL Server itself.

When you configure AGs or FCIs on a Windows-based configuration, they're cluster-aware. Cluster awareness means that SQL Server has specific resource DLLs that a WSFC knows about (sqagtres.dll and sqsrvres.dll for FCIs, hadrres.dll for AGs) and are used by the WSFC to ensure that the SQL Server clustered functionality is up, running, and functioning properly.

Because clustering is external not only to SQL Server but Linux itself, Microsoft had to code the equivalent of a resource DLL for Linux-based AG and FCI deployments. This resource is the mssql-server-ha package, also known as the SQL Server resource agent for Pacemaker. To install the mssql-server-ha package, see Deploy a Pacemaker cluster for SQL Server on Linux.

On Linux, Full-Text Search (mssql-server-fts) and Integration Services (mssql-server-is) are optional SQL Server packages, and aren't required for an FCI or AG.

SQL Server high availability and disaster recovery partners

To provide high availability and disaster recovery for your SQL Server services, choose from a wide variety of industry-leading tools. This section highlights Microsoft partner companies with high availability and disaster recovery solutions supporting SQL Server.

Partner Description
DH2i DxEnterprise is an availability management solution for Windows, Linux, and container environments. It supports high availability, reduces planned and unplanned downtime, and simplifies the management of physical and logical resources.

- Deploy availability groups with DH2i DxEnterprise on Kubernetes
- Tutorial: Set up a three node Always On availability group with DH2i DxEnterprise
HPE Serviceguard HPE SGLX offers context-sensitive monitoring and recovery options for Failover Cluster Instance and Always On Availability Groups. Maximize uptime with HPE SGLX without compromising data integrity and performance.

- Tutorial: Set up a three node Always On availability group with HPE Serviceguard for Linux.
Pacemaker Pacemaker is an open source high-availability cluster resource manager. With Corosync, an open source group communication system, Pacemaker can detect component failures and orchestrate necessary failover procedures to minimize interruptions to applications.

- Pacemaker for availability groups and failover cluster instances on Linux
- Deploy a Pacemaker cluster for SQL Server on Linux

Related content

  • Last updated on