Verify the prerequisites needed to setup theCommServe LiveSync in a Linux 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.
Operating System |
CommServe LiveSync feature can be set up on all the operating systems supported by the CommServe server on Linux. For more information on the supported operating systems, see System Requirements for the CommServe Server (Linux) |
---|---|
License Requirements |
|
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.) To facilitate communication between the clients and the CommServe, verify the following conditions:
|
* 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.