CommServe Server: System Requirements
The following requirements are for the CommServe server.
Use the latest version of the operating system software listed in the Operating System table. Commvault software fully supports the latest version of an operating system until the vendor ends support. Newer versions of Commvault software might not install on operating systems for which vendor support has ended. For information about the Microsoft support lifecycle, go to the Microsoft Support website, Microsoft Support Lifecycle. For support lifecycle information for other operating systems, contact the appropriate software vendor.
Microsoft Windows Server 2019 Editions
Microsoft Windows Server 2016 Editions
*See Considerations for Microsoft Windows Server 2016 for more information.
Microsoft Windows Server 2012 Editions
*See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x for more information.
Microsoft Windows Server 2012 R2 Editions
*See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x for more information.
Cluster - Support
The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.
For information on supported cluster types, see Clustering - Support.
All Windows-compatible processors are supported.
The hardware requirements for CommServe installed on either physical or virtual machines is explained in Hardware Specifications for CommServe.
- The software installation requires 10 GB of disk space on the operating system drive. 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.
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 2019 Enterprise, Standard, and Express Editions
Microsoft SQL Server 2019 Enterprise, Standard, and Express editions are supported. Microsoft SQL Server must be manually installed. 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, go to the Microsoft website, Editions and supported features of Microsoft SQL Server.
Microsoft SQL Server 2017 Enterprise, Standard, and Express Editions
Microsoft SQL Server 2017 Enterprise, Standard, and Express editions are supported. Microsoft SQL Server must be manually installed. 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, go to the Microsoft website, Editions and supported features of Microsoft SQL Server.
Microsoft SQL Server 2016 Standard Edition
Microsoft SQL Server 2016 Standard edition is automatically installed during the installation of the CommServe software. 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 scalability (such as CPU, socket, and memory limits), performance, and other features supported by the standard edition, go to the Microsoft website, Features Supported by the Editions of SQL Server 2016.
If you set up the CommServe in a virtual environment and use Microsoft SQL Server 2016, set the socket count to four and the core count to 24.
Microsoft SQL Server 2016 Express Edition
Microsoft SQL Server 2016 Express edition is automatically installed during the installation of Commvault solutions packages, such as the Virtual Server Protection package. For information about the solutions packages, see Commvault Data Protection Solutions - Deployment.
The maximum database size for Microsoft SQL Server 2016 Express edition is 10 gigabytes. If your Express edition database approaches the 10 gigabyte limit, a critical event will appear in the Event Viewer. To increase the size of the database, you can upgrade to Microsoft SQL Server 2016 Standard edition. For information about upgrading your database, see Upgrading Microsoft SQL Server Express to Microsoft SQL Server 2016 Standard Edition.
Microsoft SQL Server 2014 Standard Edition
Microsoft SQL Server 2014 Standard edition is supported and must be manually installed. For information about scalability (such as CPU, socket, and memory limits), performance, and other features supported by the standard edition, go to the Microsoft website, Features Supported by the Editions of SQL Server 2014.
If you set up the CommServe in a virtual environment and use Microsoft SQL Server 2014, set the socket count to four and the core count to four.
Microsoft SQL Server 2012 Enterprise Edition
Microsoft SQL Server 2012 Enterprise edition with Service Pack 2 (SP2) and Cumulative Update 4 (CU4) is also supported. If you plan to use SQL Server 2012, review important recommendations listed in Considerations for SQL Server 2012.
Recommended SQL Server Settings
The database instance used by the software requires specific SQL server settings. 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.
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
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 MB 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%.
Note: To preallocate tempdb space or disable the autogrowth option in an Enterprise environment, allocate atleast 30GB space for tempdb. Monitor and track the usage of tempdb periodically to ensure that the tempdb usage is less than 20GB. If the tempdb size is nearing 20GB, contact the software vendor to investigate the reason for tempdb growth.
For Service Accounts, use the same Local System account for each service and enable auto-start for SQL services.
On clustered environments, use an account with administrator privileges (such as, a member of the Administrator local group of the computer or domain).
CommServe Database on CIFS
The CommServe SQL database is not supported on a CIFS share.
Microsoft Internet Explorer (IE) version 11.0
Microsoft .NET Framework 4.6 is required and is automatically installed.
Internet Information Services IIS
By default, the Web Server and Web Console packages are installed with the CommServe. To install this software, IIS must be enabled on the CommServe computer and meet the following requirements:
- Microsoft Internet Information Services (IIS) Manager version 10.0 (on Windows 2016 only)
- Microsoft Internet Information Services (IIS) Manager version 8.0 or 8.5 (on Windows 2012 only)
Microsoft Internet Information Services (IIS) Manager version 7.5
By default, the Commvault software uses the name of the server computer (where the CommServe component is being installed) as the CommServe name. During the installation of the CommServe component, the software also allows you to specify a different CommServe name.
Note: The CommServe name cannot be "CommCell". If you change the CommServe name during installation, do not change it to "CommCell".
Java SE Platform
The software supports Java 11.
The Java version is installed automatically during the installation of this software. If you already have a system installed Java version, the software will install another instance of the supported Java version in the software installation path.
Note: Manually upgrading the Java version installed by the software is not supported. We always update the Java version with the latest security updates, so that the components using Java are free from any vulnerabilities reported by the open source community.
Microsoft Visual C++ Redistributable 2017 is Automatically Installed
Starting in Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed. If a computer does not have the latest Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime.
The following Windows updates must be installed to prevent the installation failure:
Updates are not required on latest Windows operating system versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, as these versions come with the Universal C Runtime already installed.
Notes on Combined Installations
Installing more than one Commvault package on a single computer is a common practice. For example, if the computer has an Exchange and an Oracle database, you will install the Exchange Database Agent and the Oracle Agent to protect the data from both databases.
When you combine multiple functions on a single computer, the storage resources required to support the software for that computer are not essentially cumulative. This is because Commvault packages share some of the same software. As a result, combined installations require about 30 MB less disk space than installations where the software resides on separate computers.
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.
Last modified: 6/16/2020 7:51:35 PM