CommServe® Deployment

The first component to be installed in a new CommCell^® environment is the CommServe^® server. Once it is installed the next step is to install MediaAgent software and detect and configure libraries. Policy configuration for storage policies, schedule policies, subclient policies and global filters should be done prior to installing any client agents. To make the agent deployment process smoother, when installing client agents, options to associate the default subclient for the agent with the policies can be selected so preconfiguring policies makes the agent deployment process smoother.

The following summarizes key points for a new CommServe server deployment:

• Commvault software must be downloaded prior to installation. To avoid any deployment delays, arrangements for the software download should be done in advance. Additionally, determine the ability to routinely download updates and upload log files from the CommServe host. If the CommServe will not have internet access, alternate methods should be discussed and documented.
• Determine the location for a local and remote Software Cache. The Software Cache is a directory where Commvault updates and software packages are stored. These can be configured during the deployment and typically help position the software to be routinely accessible throughout the organization – or prepare for a disaster.
• Verify the Hardware and System Requirements.
• Ensure the size of the environment has been assessed and there are adequate resources available for the CommServe server:
  • Based on the sizing assessment, determine if the CommServe server will be physical or virtual.
  • Determine if the CommServe server needs to be deployed in a clustered configuration for high availability.
  • Ensure the operating system meets the Commvault specifications and patched with updates prior to the installation.
  • Determine if the method of deployment requires additional considerations for Disaster Recovery. For example, configuring a 'Floating Host Name' for the CommServe server.
  • Determine if additional components such as Metrics Reporting or the Workflow engine will be installed on the CommServe server.
  • Determine the methods for accessing the CommCell^® console and/or Admin Console.
    • The consoles are installed by default along with the CommServe components.
    • IIS is required for the Web Server and Web Console and are automatically installed when IIS is enabled on the CommServe server.
• Although not always required, reboots (powering off and on) may be required to complete an installation or update. It is recommended to anticipate downtime and that the organization's change request or maintenance window process is accommodated in advance. In some cases, the organization may require the changes be implemented after hours.
• Outline the firewall and network considerations prior to any installation. Unless performing a decoupled install, all software components must communicate with the CommServe server during installation. Determine the requirements for working with the organizations firewall configuration in advance.
• Identify any monitoring, security, or anti-virus software that will be installed on the same systems as Commvault software. The installation and in many cases Commvault operations may be blocked or performance severely degraded by such software. This can be avoided by applying the appropriate exceptions or filters for the Commvault software in advance.
• Ensure any Service and Administrative accounts are preconfigured and known during the installation. The account type and permissions required are determined by the components being deployed. A thorough review of the deployment should help determine the needs.
  • For the CommServe server, an account with local Administrator privileges is required for the software installation.
  • A password for the CommCell 'admin' account is configured during the installation. This password should be a complex password and the primary administrator should always use this account when managing the environment.
• A permanent license file must be applied after the CommServe software is installed. Ensure that any pending purchase agreements are completed prior to the deployment of the Commvault software.
• Complete post installation tasks.

Download Commvault^® Software

Commvault^® offers several methods for obtaining the software installation media required for installing a CommCell^® environment. The Commvault software installation media is available for download from the Maintenance Advantage website or from the Commvault Software Cloud Services download center.

The Commvault Maintenance Advantage website or Commvault Cloud website provides the latest version of the Commvault installation media. By clicking Downloads & Packages, you can access the most current software installations and service packs or select a previous version.

There are two options to download the Commvault software:

• Resumable Download Manager– Based on the Bootstrapper download manager, this option is activated by selecting the required files from the list and then selecting Launch Download Manager at the bottom of the screen.
• Bootstrapper Direct Download– This option reduces deployment time by selecting only the required Commvault software components and download of installation media.

The installer media can also be downloaded from the Download Center on the Commvault^® software Cloud Services website.
To learn more about the Commvault's Cloud Services, go to the following link: https://cloud.commvault.com/

CommServe^® Server Installation

When deploying Commvault^® software, it is important to note that every environment is different relative to the available infrastructure, technology, budget, culture and requirements of the organization. Whether performing a new installation, an upgrade, or expanding an existing environment, a good amount of planning should take place prior to installing Commvault software. The more emphasis put into planning, the more likely the deployment will go smoothly.

Gathering Information

Proper documentation of the CommCell components being installed is essential for a smooth deployment. The following chart provides a sample of the information that must be obtained for the CommServe deployment. Having this information in advance will not only help the deployment go quicker – it can help bring any shortcomings to the surface, such as a lacking resource. Furthermore, it can aid in verifying site readiness and serve as a template for post deployment documentation.

Chart showing critical information for the CommServe server installation

CommServe^® Server Installation Overview

The following steps are used to install the CommServe server:

1. From the download location, launch Setup.exe.
2. Select Accept on the license agreement screen.
3. Choose Install Packages on this computer.
4. In the Select Platforms window, select CommServe and CommCell console. Additional components such as the MediaAgent component can also be selected.
5. The installation folder path is set by default to the operating system install drive, Program Files folder. The default location can be changed to a different location by clicking the Browse button and selecting the desired location.
6. After the destination folder is selected, the summary of install options selected is displayed for confirmation.
7. Review the install options and click Install to proceed with the installation. The CommServe^® server installation now installs the Microsoft .NET Framework 4.0 and Microsoft Visual C++ redistributable packages for the selected platforms.

Configure CommServe^® Database Settings

During the installation, the location for the CommServe database engine and database files must be selected. This location should follow the recommendations provided on Commvault's documentation site. The database must be located on a dedicated volume. A new CommServe database is created for new installations. The software also sets the SA password for the CommServe database. The password can be changed after the installation. Although not needed for day to day administration, it may be needed during troubleshooting or Disaster Recovery procedures.
The installation wizard also offers the opportunity to import an existing database. This function is useful when performing a hardware refresh, or when rebuilding a CommServe server in a disaster scenario. When selecting the 'Use an Existing Database' option, browse to the location of the database export, and select the correct database. If there is an SA password mismatch, you must supply the customer defined password.

When configuring the CommServe Database, the following occurs during installation:

1. The Microsoft SQL Server administrator password is set.
2. The option for the database files folder path is shown during the SQL instance installation.
3. A new CommServe database can be created or an existing database can be used. An existing database in the form of a CommServe database dump or export is used when:
   1. Installing the CommServe^® server in an existing CommCell^® environment when performing a server upgrade.
   2. Rebuilding a CommServe^® server in a disaster scenario.

When selecting the 'Use an Existing Database' option, browse to the location of the database export, and select the correct database.

Configure Basic Console Options

Administrator Account

During the installation, an administrator account must be created. This account is used to log into the CommCell console which is the primary user interface for configuration and administration tasks. The account cannot be deleted. A strong password should be used and be safely stored in the organization's secure password management system. After the installation, at least one other administrative account should be created for daily use. This is critical in disaster situations to rebuild and login to the environment to implement additional DR procedures. Other administrators and users can use Active Directory (AD) for logging in.

Even if Active Directory integration is used to authenticate users, it is strongly recommended to have at least two administrators with local administrative accounts for DR purposes.

Software Cache Options

During the installation, the software packages and updates are copied to local disk. This is called a Software Cache or CommServe Cache and can be leveraged to "push" Client Agent software and updates to other servers in the environment. These settings can later be changed.

Cluster Setup Options

If the CommServe server is being installed in a cluster, log into the active node with an Administrative account and then run Setup.exe from the installation media. The Cluster Setup Install Option page is displayed during the installation. After completing the selections on the active node, it may be necessary to log into the remaining cluster nodes and repeat the installation process. The installation will apply the missing components to the cluster node.

Addressing Installation Issues

To assist in troubleshooting installation errors, check the following log:
%allusersprofile%\Commvault Systems\Galaxy\LogFiles\Install.log. If the error occurs after the summary page, check the installation logs in the Software_Installation_Directory\Log Files directory.

%TEMP% also contains installation log files.