Verify that your environment meets the system requirements to configure Azure SQL database backups using a backup gateway.
Commvault Software
- Verify that the SQL Server Agent is installed on the access node.
Azure Cloud
-
Verify that the following ports are open on the backup gateway that has access to the Azure cloud:
-
443 to management.azure.com
-
1433 to *.database.windows.net
-
-
If you are using an Azure storage account for staging and not the DaCFX method, use the storage location to stage the database bacpac file for processing export and import operations. The bacpac file is deleted from the storage account after the export/import operation completes.
Operating System
Important
Use the most recent version of the operating system that is listed. The Commvault Cloud software fully supports the most recent version of an operating system, until the vendor ends support. More recent versions of the Commvault Cloud software might not install on operating systems that are not supported by the vendor anymore. For information about the support lifecycle of an operating system, contact the vendor.
Linux
For information about SQL Server on Linux, see Microsoft guidelines for SQL Server on Linux on the Microsoft website.
Important
The following operating systems are supported only for the following versions of Microsoft SQL Server. Microsoft has a known issue on Microsoft SQL server 2017 cumulative updates 19 and 20.
-
Microsoft SQL Server 2017 cumulative update 18 or lower
-
Microsoft SQL Server 2017 cumulative update 21 and higher
-
Microsoft SQL Server 2019 cumulative update 5 and higher
-
Microsoft SQL Server 2022
|
Operating System |
Applies to SQL Server Version |
|---|---|
|
Red Hat Enterprise Linux 8.0 to 8.6 |
SQL Server 2022, SQL Server 2019, SQL Server 2017 |
|
Red Hat Enterprise Linux 7.7 to 7.9 |
SQL Server 2019, SQL Server 2017 |
|
SUSE Enterprise Linux Server v15 SP1 - SP4 |
SQL Server 2022, SQL Server 2019 |
|
SUSE Enterprise Linux Server v12 SP3 - SP5 |
SQL Server 2019, SQL Server 2017 |
|
Ubuntu 20.04 LTS |
SQL Server 2022, SQL Server 2019 |
|
Ubuntu 18.04 |
SQL Server 2019, SQL Server 2017 |
|
Ubuntu 16.04 |
SQL Server 2019, SQL Server 2017 |
Windows
|
Operating system |
Processor architecture |
|---|---|
|
Microsoft Windows Server 2025 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2022 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2019 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2016 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2012 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2012 R2 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows 10 |
All Windows-compatible processors are supported |
|
Microsoft Windows 7 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2008 R2 Editions |
All Windows-compatible processors are supported |
SQL Server Authentication
Azure SQL DB allows the following types of user accounts for data protection.
-
Azure SQL Server Admin account: Server administrator of the Azure SQL instance.
-
Microsoft Entra Admin: Administrator account to centrally manage identity and access for your Azure SQL database.
-
Database user: Database level account that is used to configure minimal permissions for data protection operations. This authentication type will require the following minimum permissions:
Server-Level Roles
Database-Level Roles
None
- db_ owner on database that is being backed up
- dbmanager on master database
This role is required because the restore operation needs to create the database if it does not exist.
The configuration requires the database level account to be a user of the master database. This is required to allow the software to perform discovery and gather metadata information for the databases being protected. Commvault recommends that you create a SQL login for the database level account and associate the user of the master database and other databases with the SQL login. This approach is preferred when the user must access multiple databases, while keeping the passwords synchronized.
Supported TLS Version
The software supports database protection operations on TLS version 1.2.