# Planning For LiveSync in a Linux Environment

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 an existing standalone DR CommServe to set up CSLiveSync for failover, uninstall the existing CommServe and all the Commvault software on the standalone DR CommServe computer, and then install the CSLiveSync 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.

- When CommServe LiveSync is configured in the CommCell environment, and the passphrase is initially exported to the CommServe client, you must instead export the passphrase to the SQL clients on all nodes. Exporting the passphrase to each SQL client ensures that the passphrase is consistently available across all nodes in the LiveSync setup. This step is critical to avoid configuration issues during failover or synchronization operations.

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 | CommServe Server No special licenses are required for setting up the CommServe server. SQL Server Agent You must have two Microsoft SQL Server agent licenses, one for the production CommServe host and the other for the standby CommServe host. For more information on CommCell license categories, see License Administration.
Installation Packages* | The following Commvault installation packages are required for setting up the production and standby CommServe hosts: CommServe Server Additional packages are installed by default during the CommServe installation. For more information, see the Additional Packages Installed with the CommServe section in Preinstallation Checklist for the CommServe Server in a Linux Environment. Create a dedicated, non deduplicated storage policy for the LiveSync operation. Create the storage policy using a MediaAgent available in the standby site. CommServe Failover The SQL Server agent and the CommServe Failover package are automatically installed in a new instance. (No additional user intervention is needed.)
Firewall and Network Requirements | To facilitate communication between the clients and the CommServe, verify the following conditions: Both the active host and the passive CommServe hosts can reach the tunnel ports that are associated with the SQL clients in both the active host and the passive CommServe hosts. If the SQL clients are used as the proxy, verify that all the clients in the CommCell environment can communicate with the tunnel port and hostname of the SQL clients in both the active host and the passive CommServe hosts. If a dedicated proxy is already set up and available in your environment, use this dedicated proxy to communicate with the CommServe server. Note A dedicated proxy is recommended in environments with a large number of clients. (5000 or more approximately.) If there is a firewall between a remote Linux Web Server and/or Workflow Engine, you must update your configurations to allow communication between the components. For more information, see Firewall Configurations for the Web Server - Linux. See Also: Network TCP Port Requirements.

* 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.

×

Loading...