Verify the prerequisites needed to setup theHigh Availability CommServe Host in a Windows environment
Note
-
Identical software must be used for setting up the production and the standby CommServe hosts. Ensure that the SQL Server version (including service packs) are identical in the both the production and standby hosts.*
-
If you want to use a standalone DR CommServe LiveSync setup as failover, uninstall the existing CommServe and all the Commvault software on the standalone DR CommServe computer, and then install the standby/passive CommServe host as failover.
-
Do not configure the Index server on the Web server which is also the CommServe server.
-
Do not use the Download Center application from the Web server that is on the CommServe server
Hardware |
You must have the necessary hardware for setting up the CommServe server on the production host and the standby hosts. Note More than one standby host is supported. For more information on the hardware specification for the CommServe server, see Hardware Specifications for the CommServe Server. |
---|---|
Operating System |
High Availability CommServe Host feature can be set up on all the operating systems supported by the CommServe server in the Windows environment:
Note High Availability CommServe Host is not supported when the CommServe server is configured with Microsoft Failover Cluster. |
License Requirements |
For information about licensing, see the Commvault Licensing Program Guide. |
Installation Packages* |
The following Commvault installation packages are required for setting up the production and standby CommServe hosts:*
|
Firewall and Network Requirements |
By default, this solution requires that all clients communicate with the CommServe server using a proxy. (By default, the SQL Clients installed in the CommServe hosts is used as the proxy.) Note A default topology, Firewall Topology created for failover clients, is created for communication between the production and standby CommServe hosts using ports 8405 and 8408. This default topology routes requests between the CommServe and the SQL instances and is created irrespective of the option selected for communication. To facilitate communication between the clients and the CommServe, verify the following conditions:
|
Client Communication with the CommServe (Optional) |
By default, the SQL client is used as a proxy to route requests and responses between the CommServe server and the clients in the CommCell, before and after a failover. If necessary, you can setup an alternate client for this purpose. For more information, see Setting Up Client Communication With the CommServe. |
* Any additional packages installed on the primary CommServe host, which includes other Commvault packages, or any third-party components, must be manually installed in the standby CommServe host. Also once the LiveSync operation is enabled, the LiveSync process will synchronize the information stored in the CommServe database from the production to the standby CommServe. For example, passwords and Additional Settings stored in the database. Any additional entities, such as third-party packages, scripts, registry keys, certificates, IIS settings, configuration files, etc. must be manually applied before or after failover as needed.