Can I install an older version of Commvault on a Windows or UNIX client computer?
Yes. You can install Commvault V9 and Commvault V10 on a Windows or UNIX client computer. For more information, see Installing Clients with Deprecated Operating Systems or Applications.
Commvault Version 8 can be installed on selected UNIX operating systems and only provides backup and restore functionalities. For more information, see Installing Version 8 UNIX Clients on a Version 11 CommCell Environment.
How do I source my environment as part of a Commvault startup?
To source your environment as part of Commvault startup, you can create a file with custom environment variables. This file is which is sourced during a Commvault service restart. The system retains the custom environment file after you repair the Commvault software, or perform a feature release installation or update.
Note
You can only use the following variables in the custom environment file: set, unset, and export.
Procedure
-
Create a text file called cust_env, and apply the same permissions as the Commvault installation.
-
Enter your custom environment variables in the file. For example:
export HTTPS_PROXY=http://proxy.commvault.com:8080
export NO_PROXY=172.0.0.1,localhost,169.254.169.254
unset HTTP_PROXY
-
Copy the file to the following folder: software_installation_path/Base
-
Restart Commvault services.
What are the installation scenarios in which the installer may prompt for a reboot?
Third-party applications are installed for some Commvault packages.
The following table displays the third-party applications that might require a reboot for a specific Commvault package.
Packages |
Third-Party Applications That Might Require a Reboot |
Description |
---|---|---|
CommServe |
|
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
CommCell Console |
Microsoft .NET Framework 4.0 |
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Metrics Reporting |
Microsoft SQL Server |
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Web Server |
|
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Web Console |
Microsoft .NET Framework 4.6.2 |
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Workflow Engine |
|
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Active Directory Agent |
Active Directory Light Weight Directory Services |
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
SQLServer Agent |
|
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
Windows File System Agent |
Microsoft .NET Framework 4.6.2 |
The installation program prompts for a reboot during the installation. Reboot your computer so that the changes can take effect, and then resume the installation. |
The installation program might also prompt for a reboot in the following scenarios:
Scenarios which may lead to a computer reboot |
Description |
---|---|
If you choose to disable firewall profiles during installation. |
While performing the installation, if you select the 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 Commvaultpackages. |
If there are any pending Commvault related files that need to be renamed. |
This might happen during the installation of any of the Commvault package. |
When the Msiexec.exe utility prompts for a reboot to install MSI packages. |
This might happen during the installation of any of the Commvault package. |
When a new path is added to the environment variable. |
This might happen during the installation of the following agents:
|
When the installer runs in the Upgrade Mode. |
The following packages might require a reboot during the upgrade:
|
When the Virtual Disk Development Kit requires an upgrade. |
This might happen during the installation of the Virtual Server Agent. |
During installation of a service pack. |
The following might be required:
|