# Installing the Standby CommServe Host

Install the Commvault software packages on the standby CommServe host. You can also setup more than one standby CommServe hosts, if necessary.

Important

Starting Long-Term Support Release 11.40, new installations of the control plane on Windows require an additional setting to work. For instructions, see Enabling Windows Installations for Commvault.

Commvault strongly encourages you to transition to a Linux environment for Control plane components, specifically CommServe, Web Server, and Command Center. The Linux platform offers significantly better performance, enhanced stability, and superior resource efficiency when running Commvault.

## Before You Begin

- Install the Production CommServe Host.

- Verify that the prerequisites needed to setup the environment are available before setting up the CommServe LiveSync feature. For more information on the components needed to setup CommServe LiveSyncs, see Planning for the CommServe LiveSync Setup.

- Download the Commvault software installation packages. For more information on how to download the software, see Download the Commvault Software.

- Verify and ensure that Two-Factor Authentication is either disabled, or use an account without Two-Factor Authentication to install the standby CommServe host.

  Standby CommServe installation will fail if Two-Factor Authentication is enabled at the CommCell level with Time-based One-Time Password. Instance002 will install successfully, but instance001 will fail as it will try to use the same credentials which is only valid for 1 time. For more information, see the following topics:

  - Disabling Two-Factor Authentication

  - Excluding domain users from Two-Factor Authentication

## Procedure

1. Log on to the standby CommServe host as an Administrator or as a member of the Administrator group on that computer.

2. Launch the Commvault software installation package.

   The Download Manager dialog box appears.

3. Click Extract.

   The Language Selection page appears.

4. Select the language from the Please Choose a Language list, and then click the arrow to proceed.

   The Welcome page appears.

5. Select the I Agree check box, and then click the arrow to proceed.

   The Choose the Installation Type page is displayed.

6. Click Install packages on this computer, and then click the arrow to proceed.

   The Install Option page appears.

7. Select Advanced selection, and then click the arrow to proceed.

   The Select Packages page is displayed.

8. Select the following check boxes, and then click the arrow to proceed.

   - CommServe check box

   - CommServe Failover check box (Scroll through the list to locate this package.)

     Note

     The CommServe Failover package automatically installs the SQL Server agent and the CommServe Failover packages in a new instance. (No additional user intervention is needed.)

   The Select Maintenance Release page is displayed.

9. Choose the necessary option to install maintenance releases, and then click the arrow to proceed.

   Tip

   Select the same option that was selected in the production CommServe host. It is important to install the same maintenance releases for all packages in the production and standby CommServe hosts.

10. The Failover Install Option page appears.

11. Select This is a standby node, and then click the arrow to proceed.

    The Installation Path page appears.

12. Verify the path (or specify a new path) for the SQL client, and then click the arrow to proceed.

    This Installation Path is for the SQL client, as the SQL client is installed first on the standby CommServe host.

    Note

    The path should not exceed a maximum of 72 characters.

    The Installation Summary page appears.

13. Verify the list of packages, and then click the arrow to proceed.

    The software installs the binaries for setting up the SQL client. This process may take a few minutes.

    The Client Computer Information page appears.

14. Verify/modify the names and then click the arrow to proceed.

    - Client Name is the name of the SQL client that will be displayed in user interfaces like Command Center / CommCell Console.

    - Host Name is the physical name (FQDN) of the server.

    The Client Name and Host Name prompts are for the SQL client in the standby CommServe host. (This is the standalone SQL agent installed in Instance002, which is used for restoring the SQL database which was backed up from the production CommServe host. Note that this is NOT the name used by clients to connect to this CommServe host when it is active; the CommServe Client name used by clients should be provided later in Step 22, below.)

    Tip

    Choose a meaningful Client Name to clearly differentiate this client in the user interfaces like Command Center / CommCell Console. For example, you can add the word SQL to differentiate it from the CommServe client.

    The Server Information page is displayed.

15. Select / enter the following information:

    - Type the Fully Qualified Domain Name (FQDN) of the production CommServe host.

      This is the name that you noted while installing the production CommServe host.

    - Select the CommServe will connect to this computer to finish registration later option if the CommServe computer must initiate communications with the client.

      For more information about configuring direct connections from the CommServe computer, see Configuring Direct Connections from the CommServe Computer to the Client.

    - Select Post Quantum Cryptography (PQC) mode enabled on Commserve if PQC is enabled on the CommServe server. PQC encrypts and decrypts data to protect it from attacks by quantum computers.

      Note

      - Post-quantum cryptography can be configured only at the CommCell level.

      - For information about enabling PQC, see Enabling Post Quantum Cryptography.

    Click the arrow to proceed.

    The Server Authentication page appears.

16. Select an authentication method for accessing the production CommServe host, and then click the arrow to proceed.

    The software installs the binaries for setting up the SQL client. This process may take a few minutes.

    Note

    This completes the SQL Client installation and the following prompts are displayed for installing the standby CommServe client.

    The Select Maintenance Release page is displayed.

17. Choose the necessary option to install maintenance release on the CommServe client, and then click the arrow to proceed.

    Note

    Select the same option that was selected in the SQL client in step 8. It is important to install the same maintenance releases for all packages in the both the instances..

    The Installation Path page appears.

18. Verify the path (or specify a new the path) for the standby CommServe server, and then click the arrow to proceed.

    Important

    Note that this Installation Path is for the CommServe server.

    The Index Cache Path page is displayed.

19. Verify the index cache path (or specify a new path), and then click the arrow to proceed.

    The Database Engine Installation Path page is displayed.

20. Verify the database engine installation path (or specify a new path) and then click the arrow to proceed. (This is the path for installing Microsoft SQL Server.)

    The CommServe Database Installation Path page appears.

21. Verify the CommServe database installation path (or specify a new path) and then click the arrow to proceed. (This is the path for storing the CommServe server databases.)

    The Disaster Recovery Path page appears.

22. Select Use Network Path or Use Local Path, enter the path in Disaster Recovery Backup Files Path, and then click the arrow to proceed.

    The Client Computer Information page appears.

23. Verify/modify the names and then click the arrow to proceed.

    - Client Name is the name of the CommServe client that will be displayed in user interfaces like Command Center / CommCell Console.

    - Host Name is the physical name (FQDN) of the server.

    The Client Name and Host Name prompts are for the CommServe client in the standby CommServe host. (This is the CommServe client installed in Instance001. Note that this is the name used by clients to connect to this CommServe when it is active.)

    Tip

    Choose a meaningful Client Name to clearly differentiate this client in the user interfaces like Command Center / CommCell Console. For example, you can add the words Standby or passive to differentiate it from the production CommServe client.

    The software creates the databases and services. This process may take a few minutes.

    A message similar to the following appears:

24. Click Finish to complete the installation.

Note

- To troubleshoot errors that occur before the installation summary page, check the %allusersprofile%\Commvault Systems\Galaxy\LogFiles\Install.log file.

If the error occurs after the summary page, check the installation logs in the software_installation_directory\Log Files folder.

## What to Do Next

- If a passphrase key management server is configured in the CommCell environment and the passphrase is exported to the CommServe client, then you must export the passphrase to the SQL clients of all nodes instead of exporting to CommServe client. The export of the passphrase to all clients ensures that the passphrase is available on all the nodes.

- If an AWS Key Management Service (KMS) Server or a Key Management Interoperability Protocol (KMIP) server is configured in the CommCell environment, then you must copy the certificates to all the nodes under the same path.

- Enable the CommServe LiveSync feature which facilitates CommServe Recovery Using CommServe LiveSync. For more information on enabling the LiveSync operation, see Enabling CommServe LiveSync.

## Additional Notes

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