Skip to content

Latest commit

 

History

History
246 lines (168 loc) · 8.56 KB

sql-server-linux-shared-disk-cluster-configure-smb.md

File metadata and controls

246 lines (168 loc) · 8.56 KB
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic ms.custom
Configure SMB Storage FCI - SQL Server on Linux
Learn to configure a failover cluster instance (FCI) using SMB storage for SQL Server on Linux.
rwestMSFT
randolphwest
vanto
01/21/2025
sql
linux
how-to
linux-related-content

Configure SMB storage failover cluster instance - SQL Server on Linux

[!INCLUDE SQL Server - Linux]

This article explains how to configure SMB storage for a failover cluster instance (FCI) on Linux.

In the non-Windows world, SMB is also referred to as a Common Internet File System (CIFS) share and implemented via Samba. In the Windows world, accessing an SMB share is done this way: \\SERVERNAME\SHARENAME. For Linux-based [!INCLUDE ssnoversion-md] installations, the SMB share must be mounted as a folder.

Important source and server information

Here are some tips and notes for successfully using SMB:

  • The SMB share can be on Windows, Linux, or even from an appliance as long as it's using SMB 3.0 or later versions. For more information on Samba and SMB 3.0, see SMB 3.0 to see if your Samba implementation is compliant with SMB 3.0.
  • The SMB share should be highly available.
  • Security must be set properly on the SMB share. Below is an example from /etc/samba/smb.conf, where SQLData is the name of the share.
[SQLData]
path=/var/smb/SQLData
read only = no
browseable = yes
guest ok = no
writeable = yes
valid users = SQLSambaUser

Instructions

  1. Choose one of the servers that will participate in the FCI configuration. It doesn't matter which one.

  2. Get information about the mssql user.

     sudo id mssql

    Note the uid, gid, and groups.

  3. Execute sudo smbclient -L //NameOrIP/ShareName -U User.

    • <NameOrIP> is the DNS name or IP address of the server hosting the SMB share.
    • <ShareName> is the name of the SMB share.

  4. For system databases, or anything stored in the default data location, follow these steps. Otherwise skip to step 5.

    1. Ensure that [!INCLUDE ssnoversion-md] is stopped on the server that you're working on.

      sudo systemctl stop mssql-server
sudo systemctl status mssql-server

    2. Switch fully to be the superuser.

      sudo -i

    3. Switch to be the mssql user.

      su mssql

    4. Create a temporary directory to store the [!INCLUDE ssnoversion-md] data and log files.

      mkdir <TempDir>
      • <TempDir> is the name of the folder. The following example creates a folder named /var/opt/mssql/tmp.
      mkdir /var/opt/mssql/tmp

    5. Copy the [!INCLUDE ssnoversion-md] data and log files to the temporary directory.

      cp /var/opt/mssql/data/* <TempDir>
      • <TempDir> is the name of the folder from the previous step.

    6. Verify that the files are in the directory.

      ls <TempDir>

      <TempDir> is the name of the folder from Step d.

    7. Delete the files from the existing [!INCLUDE ssnoversion-md] data directory.

      rm - f /var/opt/mssql/data/*

    8. Verify that the files have been deleted.

      ls /var/opt/mssql/data

    9. Type exit to switch back to the root user.

    10. Mount the SMB share in the [!INCLUDE ssnoversion-md] data folder. This example shows the syntax for connecting to a Windows Server-based SMB 3.0 share.

      Mount -t cifs //<ServerName>/<ShareName> /var/opt/mssql/data -o vers=3.0,username=<UserName>,password=<Password>,domain=<domain>,uid=<mssqlUID>,gid=<mssqlGID>,file_mode=0777,dir_mode=0777
      • <ServerName> is the name of the server with the SMB share
      • <ShareName> is the name of the share
      • <UserName> is the name of the user to access the share
      • <Password> is the password for the user
      • <domain> is the name of Active Directory
      • <mssqlUID> is the UID of the mssql user
      • <mssqlGID> is the GID of the mssql user

    11. Check to see that the mount was successful by issuing mount with no switches.

      mount

    12. Switch to the mssql user.

      su mssql

    13. Copy the files from the temporary directory /var/opt/mssql/data.

      cp /var/opt/mssql/tmp/* /var/opt/mssql/data

    14. Verify the files are there.

      ls /var/opt/mssql/data

    15. Enter exit to not be mssql.

    16. Enter exit to not be root.

    17. Start [!INCLUDE ssnoversion-md]. If everything was copied correctly and security applied correctly, [!INCLUDE ssnoversion-md] should show as started.

      sudo systemctl start mssql-server
sudo systemctl status mssql-server

    18. To test further, create a database to ensure the permissions are fine. The following example uses Transact-SQL; you can use SSMS.

      :::image type="content" source="media/sql-server-linux-shared-disk-cluster-configure-smb/10-testcreatedb.png" alt-text="Screenshot showing the creation of the test database.":::

    19. Stop [!INCLUDE ssnoversion-md] and verify it's shut down. If you're going to be adding or testing other disks, don't shut down [!INCLUDE ssnoversion-md] until those disks are added and tested.

      sudo systemctl stop mssql-server
sudo systemctl status mssql-server

    20. Only if finished, unmount the share. If not, unmount after finishing testing/adding any additional disks.

      sudo umount //<IPAddressorServerName>/<ShareName /<FolderMountedIn>
      • <IPAddressOrServerName> is the IP address or name of the SMB host
      • <ShareName> is the name of the share
      • <FolderMountedIn> is the name of the folder where SMB is mounted

  5. For things other than system databases, such as user databases or backups, follow these steps. If only using the default location, skip to Step 14.

    1. Switch to be the superuser.

      sudo -i

    2. Create a folder that will be used by [!INCLUDE ssnoversion-md].

      mkdir <FolderName>

      <FolderName> is the name of the folder. The folder's full path needs to be specified if not in the right location. The following example creates a folder named /var/opt/mssql/userdata.

      mkdir /var/opt/mssql/userdata

    3. Mount the SMB share in the [!INCLUDE ssnoversion-md] data folder. This example shows the syntax for connecting to a Samba-based SMB 3.0 share.

      Mount -t cifs //<ServerName>/<ShareName> <FolderName> -o vers=3.0,username=<UserName>,password=<Password>,uid=<mssqlUID>,gid=<mssqlGID>,file_mode=0777,dir_mode=0777
      • <ServerName> is the name of the server with the SMB share
      • <ShareName> is the name of the share
      • <FolderName> is the name of the folder created in the last step
      • <UserName> is the name of the user to access the share
      • <Password> is the password for the user
      • <mssqlUID> is the UID of the mssql user
      • <mssqlGID> is the GID of the mssql user.

    4. Check to see that the mount was successful by issuing mount with no switches.

    5. Type exit to no longer be the superuser.

    6. To test, create a database in that folder. The following example uses sqlcmd to create a database, switch context to it, verify the files exist at the OS level, and then deletes the temporary location. You can use SSMS.

    7. Unmount the share

      sudo umount //<IPAddressorServerName>/<ShareName> /<FolderMountedIn>
      • <IPAddressOrServerName> is the IP address or name of the SMB host
      • <ShareName> is the name of the share
      • <FolderMountedIn> is the name of the folder where SMB is mounted.

  6. Repeat the steps on the other node(s).

You're now ready to configure the FCI.

Related content