CommCell Console as a Stand-Alone Application: System Requirements

The following requirements are for the CommCell Console as a Stand-Alone Application.

Operating System

Operating System

Operating System Version

Architecture

Linux

Debian

Debian 5.x and above

  • x86

  • x64

  • Compatible processors

Fedora

Fedora release 8 and above

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux 5.0 and above

  • x86

  • x64

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 10 Initial Release and above

  • x86

  • x64

  • Compatible processors

Ubuntu

Ubuntu 8.04

  • x86

  • x64

  • Compatible processors

Mac OS X

OS X El Capitan (v10.11.x)

All Macintosh-compatible processors supported

OS X Yosemite (v10.10.x)

All Macintosh-compatible processors supported

OS X Mavericks (v10.9.x)

All Macintosh-compatible processors supported

OS X Mountain Lion (v10.8.x)

All Macintosh-compatible processors supported

Windows

Windows 2016

Microsoft Windows Server 2016 Editions

All Windows-compatible processors are supported

Windows 2012

Microsoft Windows Server 2012 R2 Editions

All Windows-compatible processors are supported

Microsoft Windows Server 2012 Editions

All Windows-compatible processors are supported

Windows 2008

Microsoft Windows Server 2008 32-bit and x64 Editions

Server Core installations are not supported.

All Windows-compatible processors are supported

Windows 10

Microsoft Windows Client 10 Editions

All Windows-compatible processors are supported

Windows 8

Microsoft Windows 8 Editions

All Windows-compatible processors are supported

Windows 7

Microsoft Windows 7 32-bit and x64 Editions

All Windows-compatible processors are supported

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

All Windows-compatible processors are supported

Windows XP

Microsoft Windows XP Editions with a minimum of Service Pack 3

All Windows-compatible processors are supported

Hard Drive

  • 65 MB free disk space

  • 763 MB of temp space required for install or upgrade (where the temp folder resides)

Display

The minimum resolution required to properly display the CommCell Console is 1280x1024.

The graphical icons in the CommCell Console cannot be displayed in VGA mode. This affects the appearance of the toolbar and the CommCell tree in the CommCell Browser. Also, some table of contents is not displayed correctly.

Miscellaneous

The CommCell Console supports Internet Protocol version 6 (IPv6). See IPv6 Requirements for more information.

Service Pack Versions

The CommCell Console and the CommServe computer must have the same service pack version.

Java SE Platform

The software supports Java 11.

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.

SELinux

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create an SELinux policy module, perform the following steps as user "root":

  1. Create the following files in the /usr/share/selinux/devel directory:

    File Name

    Content of the File

    <directory>/<file_name>.te

    where:

    <directory> is /usr/share/selinux/devel

    <file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

    For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

    The content of the file should be as follows:

    policy_module(<name>,<version>)

    ##############################

    where:

    <name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

    <version> is the version of the policy module. It can be any number, such as 1.0.0.

    For Example: While creating a policy module for the backup_IDA application, you can use the following content.

    policy_module(backup_IDA,1.0.0)

    <directory>/<file_name>.fc

    where:

    <directory> is /usr/share/selinux/devel

    <file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

    For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

    The content of the file should be as follows:

    Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

    /opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

  2. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

    [root]# make backup_IDA.pp

    Compiling targeted backup_IDA module

    /usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

    /usr/bin/checkmodule: policy configuration loaded

    /usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

    Creating targeted backup_IDA.pp policy package

    rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

    [root]# semodule -i backup_IDA.pp

    [root]#

  3. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

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.

Loading...