System Requirements - CommServe

Enterprise Version Express Version  

The following requirements are for the Enterprise version of the CommServe:

Operating System



Windows 2012

Microsoft Windows Server 2012 Editions

See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information.

Dual 1 GHz minimum required

Windows 2008

Microsoft Windows Server 2008 R2 Editions

Dual 1 GHz minimum required

Microsoft Windows Server 2008 32-bit and x64 Editions*

*Core and Web Server Editions not supported

Dual 1 GHz minimum required

Windows 2003

Microsoft Windows Server 2003 32-bit and x64 Editions* with a minimum of Service Pack 2

*Web Server Editions not supported

Dual 1 GHz minimum required

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.

Hard Drive

2.1 GB of local disk space for the CommServe software, including database and log file growth, and the Microsoft SQL Server application and database. (The SQL software is embedded in the CommServe software installation.)

500 MB of temp space on the drive on which the Operating System and temp directory resides. (This space is used for temporary files copied during the installation or upgrade of the Microsoft SQL Server and CommServe software).

1.5 GB of permanently available disk space on a local or mapped network drive for CommServe Disaster Recovery. (CommServe Disaster Recovery is a feature that secures the metadata of the CommServe.)

In time, you may need to provide additional space (several GB) to allow for growth in the CommServe metadata. The size of the metadata depends on the number of computers in the CommCell and the quantity of data stored.


16 GB RAM minimum required

To achieve higher scalability, it is recommended to deploy the CommServe on a physical server with 32 GB memory and Solid-state-disk (SSD). Refer to CommCell Scalability Guide for additional details.

Database Engine

Simpana includes a license for Microsoft SQL Server 2008 (Enterprise Edition). Microsoft SQL Server 2008 database instance with Service Pack 1 will be automatically installed while installing the CommServe. Later SQL Server service packs and updates must be installed manually. We recommend to maintain the SQL Server up-to-date with any important updates released by Microsoft.

Microsoft SQL Server 2008 R2 Editions and SQL Server 2012 (SP1) are also supported. If using SQL Server 2012, it is required that you install the Cumulative Update Package 3 and review the recommendations listed in Considerations for SQL Server 2012.

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.

In a clustered environment, Microsoft SQL Server 2008 (Enterprise Edition) with the appropriate service pack must be installed and clustered prior to installing the CommServe software. The CommServe software automatically uses the default or the named instance created during the SQL installation.

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.

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

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 20%

Service Accounts

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).

Hardware Validation for CommServe Database

The CommServe database needs to be on a fast disk for optimal backup performance. Before setting up the CommServe, the storage volumes must be validated for high performance. This can be done using IO meter tool which measures the IOPs (Input Output Operations per second). For more information, see IOPs for CommServe Database Volumes.


DVD-ROM drive

Network Interface Card


Internet Explorer

Microsoft Internet Explorer (IE) version 8.0, 9.0

Java Support

The software supports Java 7 or higher*.

  Java 7 versions are supported with Simpana Service Pack 8 or higher. Previous service pack versions do not fully support this version.

If a JRE version 1.7.0_17 or higher is available, the software will use the existing JRE software.

If a JRE version lower than 1.7.0_17 is available, or no JRE version is available at all, you will be prompted to install JRE version 1.7.0_17

*The Backup Time selection in the Advanced Options area of the Find dialog box is not compatible with Java 7 or higher.

CommServe Database on CIFS

The CommServe's SQL database is not supported on a CIFS share.

Recommendation for Using Virtual Machines


  • Allocate multiple virtual CPUs to a virtual machine, if the anticipated SQL Server workload can take advantage of all the virtual CPUs.
  • Memory page sharing and memory ballooning must be enabled on the virtual machine.


SQL Data files and log files must reside on different disks (different VMFS). It is recommended to place the log files on RAID 1+0 or RAID 1 disks.


Make sure to use the VMXNET virtual network adapter and separate virtual switches, each connected to its own physical network adapter.

Notes on CommServe Installation

The CommServe is a resource intensive application and should be installed on a dedicated server. Therefore, it is recommended that the CommServe not be installed on a computer running other applications, such as Microsoft Exchange Server, an Oracle database, etc. Additionally, CommServe installed on virtual machines generally perform at about 60% capacity compared to physical machines with similar configurations.

The software should not be installed on a compressed drive.

The Enterprise version of the CommServe is not supported on Microsoft Windows Small Business Server platforms. If you wish to install the CommServe on Microsoft Windows Small Business Server platform, you must install the Express version of the CommServe. See the System Requirements for the Express version of the CommServe for more information.

The computer on which the software is installed must have a static IP address. The software does not support Dynamic Host Configuration Protocol (DHCP).

Installing on a VMware Environment

If installing the CommServe on a VMware virtual machine, consider the following recommendations for optimal performance:

  • The ESX Server hosting the virtual machine should be vSphere (4.0) or above.
  • Disable vMotion for the virtual machine and the storage.
  • The virtual machine on which the CommServe will be installed should have:
    • Minimum 2 64-bit vCPUs
    • Minimum 16 GB RAM
    • A Windows Server 2008 x64 Edition operating system
    • All VMware tools and utilities installed
  • Minimum bandwidth of 1 Gbps for data transfer.
  • The CommServe's SQL database should be configured on shared storage (such as a SAN or FAST disk).

Installing on a Hyper-V Environment

If installing the CommServe on a Hyper-V virtual machine, consider the following recommendations for optimal performance:

  • Hyper-V Server 2008 R2 with Service Pack 1 (or higher) should be used to host the virtual machine.
  • The virtual machine on which the CommServe will be installed should have:
    • Minimum 4 64-bit vCPUs
    • Minimum 16 GB RAM
    • A Windows Server 2008 x64 Edition operating system
    • All Hyper-V Integration tools installed using the latest versions
  • A fast and dedicated storage as well as network interfaces for optimal performance of the CommServe SQL database.

Notes on Combined Installations

You will often install more than one module (For example, CommServe, MediaAgent, Client) on a single computer so that it can perform two or more functions. For example, you may want to back up the file system of a MediaAgent; hence, you would install both the MediaAgent and client software on that computer.

When you combine two or more functions on a single computer, the storage resources required to support the software for that computer are not essentially cumulative. This is because modules 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.


Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable