Installations - FAQ

Table of Contents

Can I install an older version of the component on a Windows or a UNIX client computer?

Yes. You can install software components from older versions and use the latest version of CommServe software. See the CS0002 article or contact your Software Provider for more details.

Can I install the CommServe software using an existing SQL Server instance?

Yes. See Installing the CommServe software using an Existing SQL Server Instance for more information.

Can I configure the CommCell Administrator account to have no password?

Yes. During the installation of the SnapProtect software, you can configure the Administrator account to have no password. This configuration will skip the password check to access the CommCell Console, which disables the login window that prompts for credentials.

Having this account without a password is useful when the Administrator is the only user configured in the CommCell as you can automatically log on to the CommCell Console. However, when more CommCell users are created, the CommCell Console will start asking again for user credentials to allow access.

In a CommCell with multiple users, it is recommended that the Administrator account is configured with a password for security reasons. To change the password of your Administrator account, see Changing the User Information.

Can I install the SQL Server database files on a FAT drive?

No. A FAT drive cannot be supported as the location for the SQL database files because it does not allow a temporary sparse file to be generated when creating the database snapshot, which is required for data verification.

Can I install the SQL Express Edition in a cluster environment?

No. The SQL Express Edition cannot be installed on a cluster environment. You need to install the SQL Server Enterprise Edition to prepare your cluster setup for the CommServe installation.

Can I install the Web Console in a cluster environment?

No. The Web Console cannot be installed on a cluster environment.

For example, if you plan to install the Web Console on the CommServe computer, but the CommServe computer is configured in a cluster, then you should install the Web Console on a different computer.

Can I install SnapProtect in a language other than the one used by the operating system of the computer?

Yes. You can select a different language to install the SnapProtect software. See Installing SnapProtect in a Different Language for more information.

Can I change the user group name during subsequent agent installations on a UNIX client?

No. You cannot change the user group name during subsequent agent installations on a Unix client. The user group name is assigned during the first installation of an agent on the Unix client. The following takes place during subsequent installations:

  • For interactive installs, the installer does not ask for the user group name again.
  • For installation from the CommCell Console (remote installs), the installer asks the user to enter the user group name. However, the specified user group name will not be applied on subsequent installations.

You can change the user group name using the cvpkgchg utility available in the SnapProtect installation directory. Follow the steps to change the group ownership for SnapProtect files and directories:

  1. Ensure that no jobs are running in any SnapProtect instance.
  2. From the Command Prompt, navigate to <SnapProtect Install> directory.
  3. Enter the command ./cvpkgchg.
  4. Select option 1.
  5. Type the new group name and press Enter.
  6. Restart The SnapProtect services for all instances to change the group ownership.

Do I need to reboot the Windows client after installing DB2 Agent on the client?

Yes. We need to reboot the Windows client after installing DB2 agent on the client.

Does the space requirement vary if I install the software to a drive other than C:?

By default, the installer uses C:\%allusersprofile% as a temp location for copying the installer files, and installs the software to C: drive. When the software is installed to this default location, the amount of free drive space required for installation will be the sum of the following:

  • The amount of space required to install the software files.
  • The amount of space required in the temp location for copying the installer files.

However, when the software is installed to a drive other than C: drive, the free space required on C: drive will just be the amount of space that is required to copy the files.

How can I enable 32-bit installation from a Linux Custom Package?

Create the cvpkgadd_unlock_32 key to enable 32-bit installation from a Linux Custom Package using the following command:

touch /tmp/cvpkgadd_unlock_32

You can select a 32-bit or 64-bit installation from the menu that appears during installation. You will not see the menu if you do not create the key and the Custom Package installs 64-bit components.

How can I manually install/upgrade the Java Runtime Environment on my computer?

Open the command prompt window on your client computer, and execute the following command to verify the JRE version installed on your computer:

C:\java -version

If the version is lower than Java 7 Update 17 (JRE 1.7.0_17), uninstall and reinstall JRE using the following steps:

  1. Stop the SnapProtect services running on the client computer.
  2. Uninstall the current JRE version.
  3. Install Java 7 Update 17 (JRE 1.7.0_17) or later versions or any version of Java 8.

    Note: For Macintosh the software supports Java 7 Update 17 (JRE 1.7.0_xx) or a later version of Java 7.

  4. Start the SnapProtect Services.

How can I identify the Third-Party Application files installed with the CommServe software?

The following third-party application files are installed along with the CommServe.

<software_install_path>\Base\AutoMapper.dll

<software_install_path>\Base\Borland.Janeva.Runtime.dll

<software_install_path>\Base\Borland.Janeva.Runtime.Private.dll

<software_install_path>\Base\Borland.Janeva.Services.dll

<software_install_path>\Base\Borland.Janeva.Services.Private.dll

<software_install_path>\Base\ChilkatDotNet2.dll

<software_install_path>\Base\ctreedbs.dll

<software_install_path>\Base\ctreestd_trans.dll

<software_install_path>\Base\CVChunkLister.exe

<software_install_path>\Base\CVctreestd.dll

<software_install_path>\Base\CvMsoIrmProtector.dll

<software_install_path>\Base\CvSMTPMgr.dll

<software_install_path>\Base\CvSnapLSI.dll

<software_install_path>\Base\CVSQLite3.dll

<software_install_path>\Base\DLLOA64.DLL

<software_install_path>\Base\DSAPIDotNet.dll

<software_install_path>\Base\DSModelDotNet.dll

<software_install_path>\Base\eql_psapi.dll

<software_install_path>\Base\Esp-Searchapi.dll

<software_install_path>\Base\FPCore.dll

<software_install_path>\Base\FPLibrary.dll

<software_install_path>\Base\FPOS64.dll

<software_install_path>\Base\FPParser.dll

<software_install_path>\Base\FPStreams.dll

<software_install_path>\Base\FPUtils.dll

<software_install_path>\Base\FPXML.dll

<software_install_path>\Base\HTMLConverter.dll

<software_install_path>\Base\HtmlConverterX.exe

<software_install_path>\Base\ICSharpCode.SharpZipLib.dll

<software_install_path>\Base\Interop.GENEVTINFLib.dll

<software_install_path>\Base\Libeay32.dll

<software_install_path>\Base\MonadCmdLetSrvr.dll

<software_install_path>\Base\MSVCR71.dll

<software_install_path>\Base\NTAPAdmin.dll

<software_install_path>\Base\ONCRPC.dll

<software_install_path>\Base\PAI_module.dll

<software_install_path>\Base\pcre.dll

<software_install_path>\Base\pcrecpp.dll

<software_install_path>\Base\pegclient.dll

<software_install_path>\Base\pegcommon.dll

<software_install_path>\Base\pegslp_client.dll

<software_install_path>\Base\PLink.exe

<software_install_path>\Base\SnapCleanup.exe

<software_install_path>\Base\SSLeay32.dll

<software_install_path>\Base\stlport.5.0.dll

<software_install_path>\Base\unzip.exe

<software_install_path>\Base\Xalan-C_1_10.dll

<software_install_path>\Base\XalanMessages_1_10.dll

<software_install_path>\Base\xerces-c_2_6.dll

<software_install_path>\Base\xerces-c_2_7.dll

<software_install_path>\Base\zip.exe

<software_install_path>\Base\zlib1.dll

<software_install_path>\Base32\ErrorMonitor.exe

<software_install_path>\Base32\msvcr71.dll

<software_install_path>\Base32\python25.dll

C:\Windows\system32\DRIVERS\RsFx0103.sys

These files are not signed and will not have complete file version information in the file's Properties dialog box.

For example:

<software install path>\Base\AutoMapper.dll does not have a valid Company name and Product Name properties.

However, note that having incomplete file version information on these files does not affect the performance of the software.

How does SnapProtect handle the SQL Enterprise License during the CommServe Installation?

Commvault Systems, Inc. has an ISV-R royalty contract with Microsoft, allowing the SnapProtect software to be bundled with a full copy of the SQL Server Enterprise Edition. CommVault Systems, Inc. reports the license usage (per country) every month to Microsoft.

How does installation from the CommCell Console work?

Install Software from the CommCell Console works in conjunction with Custom Packages and Multi-Cache features, where WAN bandwidth can be drastically reduced during remote site installations.

Once the installation job starts, the CommServe pushes the required software packages to the selected computers sequentially. Once the CommServe receives notification from the client computer that the software package has been successfully delivered to the computer, it pushes the software packages to the next computer, and so on. In the meantime, the silent installation automatically begins for a computer once the packages are successfully delivered.

For comprehensive information on Custom Package support, see Support.

What are the different SnapProtect  components that are included in various install packages?

The following table outlines the features that are included in different install packages:

Component/Agent type License Consumption Features/Agents included
CommServe No license is consumed. All of the core CommServe components that can perform basic operations, for example, schedules, alerts, and reports.
Operations Manager No license is consumed.
  • VM Life Cycle Management
  • Virtualize Me
  • External Data Connector
  • Global Repository Cell
  • CommCell Migration
MediaAgent MediaAgent license is consumed. Includes the File System agent without advanced functionality. It can only function with  'Restore only' client capability.
File System Agent The File System agent is the combination of the File System Core and File System components.

Licenses are consumed by the File System Core component as follows:

  • If installed on a server computer, the 'Server File System' license is consumed. If installed on a laptop/desktop computer, the 'Laptop and Desktop" license is consumed.
  • The licenses are consumed when you explicitly select the agent during installation. If automatically selected, the agent is installed without consuming the license.
File System Core:
  • Base component which establishes the connections between the client and the CommServe database.
  • Provides the capability to perform laptop backups and restores.
  • Provides recursive scan functionality (for UNIX).

File System:

  • Provides all backup and restore capabilities. For example:
    • SnapProtect backups
    • Office Communication Server backups
    • Optimized Scan (for UNIX)
  • Provides the required data to generate Discovery and File Level Analytics reports.
  • Required for 1-Touch and Simpana OnePass archiving operations.
Database Agents

License is consumed for the respective database agent.

Provides the capability to perform backup and recovery operations of the database objects.

What are the installation scenarios in which the installer may prompt for a reboot?

If the software package that you are installing involves the installation of any of the third-party applications listed in the below table, then the installer may prompt for a reboot so that the changes can take effect:

Third-Party applications Associated Software Packages Description
Microsoft ASP.NET

AJAX Extensions Package

Web Server Reboot is prompted during the installation process as the third-party applications require a reboot.

Reboot your computer so that the changes can take effect, and then resume the installation.

SQL Server CommServe

Web Server

Metrics Reporting

Workflow

Reboot is prompted during the installation process as the third-party application requires a reboot.

Reboot your computer so that the changes can take effect, and then resume the installation.

Active Directory Light Weight Directory Services Active Directory iDataAgent Reboot is prompted during the installation process as the third-party application requires a reboot.

Reboot your computer so that the changes can take effect, and then resume the installation.

.Net 4.0 File System iDataAgent

Web Console

CommCell Console

Reboot is prompted during the installation process as the third-party application requires a reboot.

Reboot your computer so that the changes can take effect, and then resume the installation.

.Net 3.5 Workflow Engine

CommServe

Exchange Offline Mining Tool

Compliance Search

Web Server

MSSQL Server iDataAgent

Reboot is prompted during the installation process as the third-party application requires a reboot.

Reboot your computer so that the changes can take effect, and then resume the installation.

SQL 2005 Native Client package MSSQL Server iDataAgent Installer may prompt for a reboot either in the middle or at the end of the installation process.

Reboot your computer so that the changes can take effect.

MSXML package MSSQL Server iDataAgent Installer may prompt for a reboot either in the middle of the installation or at the end of the installation.

Reboot your computer so that the changes can take effect.

SQL XMO Package MSSQL Server iDataAgent Installer may prompt for a reboot during the installation.

Reboot your computer so that the changes can take effect.

SQL 2005 Backward Compatibility Package SRMSQL Agent Installer may prompt for a reboot during the installation.

Reboot your computer so that the changes can take effect

In addition to the scenarios mentioned above, the installer may prompt for a reboot in the following conditions:

Conditions which may lead to a computer reboot Description
If you choose to disable Firewall profiles during installation. While performing the installation, if you select  'Yes, disable Windows Firewall for all profiles' option in the Firewall Configuration screen, then your computer will prompt for a reboot.

This applies to all SnapProtect components.

If there are any pending SnapProtect  related files that need to be renamed. This may happen during the installation of any of the SnapProtect components.
When the Msiexec.exe utility prompts for a reboot to install certain MSI packages successfully. This may happen during the installation of any of the SnapProtect components.
When a new path is added to the Environment variable. This may happen during the installation of the following components:
  • Sybase iDataAgent
  • DB2 iDataAgent
  • Oracle iDataAgent
  • SAP for Oracle iDataAgent
  • Test Automation
When the installer runs in the Upgrade Mode When the installer upgrades the following components:
  • File Share Archiver Client
  • Driver for File Archiver
  • Driver for Continuous Data Replicator
When the Virtual Disk Development Kit is required to be upgraded This may happen during the installation of the Virtual Server iDataAgent.
While installing the SnapProtect Agents  

How much free disk space is required to install the software?

By default, the installer uses C:\ %allusersprofile% for temp location, and installs the software to C: drive.
When the software is installed to this default location, the amount of free space required for installation will be the sum of the following:

  • The amount of space required to install the files.
  • The amount of Space required in the temp location to complete the installation.

However, when the software is installed to a directory other than C: drive, the space required will just be the amount of space that is required to copy the files.

What is the install behavior when we try to install more than one instance on the client computer?

The following table outlines the installation behavior when you try to install more than one instance on a client computer.

Instance and Ports Install Behavior
When the existing instance on the client computer is not using the default port number selected during the current installation. The current instance will be installed with the next available port numbers .
When the existing instance on the client computer is not using the port numbers specified during the current installation The current instance will be installed with the specified port numbers
When the existing instance on the client computer is already using the default port numbers selected during the current installation. The current instance will be installed with the next available ports.
When the existing instance on the client computer is already using the port numbers selected during the current installation. The current installation will be successful only if you specify the same CommServe name that is being used by the existing instance; else, the installation will not succeed.

See Multi-Instancing to learn about the install behavior for push installs.