Verify that your Linux environment meets the system requirements for the CommServe server.
Operating System
|
Operating system |
Processor architecture |
|---|---|
|
Red Hat Enterprise Linux 8.2 through Linux 8.10 |
x64 |
|
Red Hat Enterprise Linux 7.7 through Linux 7.9 |
x64 |
Processor
All Linux x64 compatible processors are supported.
Hardware Specifications
The hardware requirements for the CommServe server, installed on either physical or virtual machines, is explained in Hardware Specifications for CommServe.
Note
-
The software installation requires 10 GB of disk space on the operating system drive (path: /). This space is used for temporary files copied during the installation or upgrade of the CommServe and Microsoft SQL Server software.
-
For hard drive requirements details of other components (such as the Deduplication Mode), see the corresponding system requirements pages.
Disk Partitioning
A dedicated 100 GB disk/volume (preferably SSD) is recommended for the following partitions/logical volumes on a Linux CommServe computer:
Note
The following partitions/logical volumes support EXT4 and XFS as file system types, though XFS is recommended.
-
Linux operating system (path: /)
-
Commvault application (binaries) (path: /opt)
-
Commvault databases
-
Temp database
-
Software cache and Commvault log files
Database Engine
The Microsoft SQL Server application that is installed on the computer must be dedicated to support the software and cannot be shared by other applications.
|
Microsoft SQL Server Build |
Supported Editions |
Default with Fresh CommServe Software |
Certified Service Pack/ Cumulative Update |
Supported Feature |
Notes |
|---|---|---|---|---|---|
|
Microsoft SQL Server 2022 |
Standard |
Cumulative Update 16 Cumulative Update 15 + GDR |
Microsoft SQL Server 2022 is not installed during a fresh CommServe server installation. You can only upgrade an existing SQL server standard installation on the CommServe server to Microsoft SQL Server 2022. For upgrade instructions, see Supported version and edition upgrades (SQL Server 2022). |
||
|
Microsoft SQL Server 2019 |
Enterprise, Standard, and Express Editions |
Standard edition only with Commvault Platform Release 2023 and more recent releases. |
Cumulative Update 29 Cumulative Update 29 + GDR |
Later SQL Server service packs and updates must be installed manually. You must update the SQL Server with any important updates released by Microsoft. For information about pre-installing Microsoft SQL Server, see Pre-Installing the Microsoft SQL Server Software on a Non-Cluster Environment.
For information about scalability (such as CPU, socket, and memory limits), performance, and other supported features, see "Editions and supported features of Microsoft SQL Server" on the Microsoft website.
Note
-
The name of the computer that is trying to install the SQL Server package must be 15 characters or less. For more information, see "Common issues" in the Microsoft article Troubleshoot SQL Server on Linux.
-
The minimum version of unixODBC required is 2.3.4.
-
Microsoft SQL Server is automatically installed with Commvault. If MS SQL Server is already installed on the computer, the installation wizard skips the MS SQL Server installation. Note that Commvault Systems, Inc. has an ISV-R royalty contract with Microsoft, allowing a full copy of MS SQL Server Standard Edition to be bundled with Commvault. Commvault Systems, Inc. reports the license usage (per country) every month to Microsoft.
-
When Microsoft SQL Server 2019 Enterprise, Standard and Express editions are installed with Commvault, the following packages are installed (required):
-
MS SQL Server: mssql-server-15.0.4123.1-5.x86_64.rpm
-
MS Tools: mssql-tools-17.7.1.1-1.x86_64.rpm
-
MS ODBC: msodbcsql17-17.10.4.1-1.x86_64.rpm
-
UNIX ODBC:
-
unixODBC-2.3.7-1.rh.x86_64.rpm
-
unixODBC-devel-2.3.7-1.rh.x86_64.rpm
-
-
Other Required Software
The following software is required for the CommServe server:
-
compat-openssl10
-
cpp
-
cyrus-sasl
-
gc
-
gcc
-
gdb
-
gdb-headless
-
glibc-devel
-
glibc-headers
-
guile
-
isl
-
kernel-headers
-
krb5-libs
-
libatomic
-
libatomic_ops
-
libbabeltrace
-
libcurl
-
libicu
-
libipt
-
libmpc
-
libtool-ltdl
-
libxcrypt-devel
-
net-tools
-
openssl
-
openssl-libs
-
python3-pip
-
python36
-
xz-libs
-
zlib
Recommended SQL Server Settings
The database instance used by the software requires specific SQL server settings.
Note
For information about SQL Server on Linux, see Microsoft guidelines for SQL Server on Linux on the Microsoft website.
Using the SQL Management Studio, verify the SQL properties listed below.
SQL Memory Size
Access the server properties and navigate to the Memory page. The maximum server memory should be 50% of the physical memory available in the computer on which the software is installed.
Server Collation
Run the sp_helpsort system stored procedure, and verify that the server default collation has the following properties:
-
Character Set is 1252/ISO (default)
-
Sort Order is Dictionary order, and case is Insensitive
-
Unicode Collation includes General Unicode, case Insensitive, width Insensitive
-
SQL Server collation is SQL_Latin1_General_CP1_CI_AS
Temp Database Properties
Navigate to the tempdb database (under the Databases | System Databases node), and access its properties to verify the following:
-
The tempdb database has at least 100 GB of disk space. Depending on the components that you decide to install later, additional space may needed.
-
Click the Files page to check the autogrowth properties of the database files. The Enable Autogrowth option must be selected, and the file growth should be set to 10%.
For more information about the CommServe Server hardware requirements, see Hardware Specifications for the CommServe Server.
Note
-
For SQL Server 2019, the license is limited to 4 sockets or 24 cores, whichever is less.
-
For the SQL Server scheduler, use NUMAs for distributing or scheduling the SPID load.
-
For VMs that have more than 4 sockets, SQL Server uses only the first 4 sockets. This configuration is considered to be a bad configuration.
-
Each VM socket must have its own NUMA association for SQL Server Schedulers and for CPUs that have more than 4 sockets per NUMA.
-
SQL Server VMs must have matching, dedicated physical CPUs on the VM Host. For the best performance, the VMs must not be shared.
-
For a SQL Server VM used in the CommServe environment, I/O per second (IOPS) must be at least 150.
Miscellaneous
Java SE Platform
Java is installed automatically during the installation of this software. If you already have a system-installed Java version, the software installs another instance of the supported Java version in the software installation path.
All Commvault binaries (JAR files) are signed by SHA-256 Digest. To verify that the downloaded JAR files from Java webstart/netx.jar are not modified, use SHA 256.
Note
Commvault always updates the Java version with the most recent security updates, so that the components using Java do not have any vulnerabilities that are reported by the open source community. To manually upgrade the Java Runtime Environment (JRE) for the Commvault software, see KB article 57019.
Content Indexing and Compliance Search for File Systems
Content indexing and Compliance Search for file systems is supported on Windows Web Servers and access nodes.
Disclaimer
Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.