Unattended Installation of CommServe LiveSync Setup

Unattended installation can be used to setup multiple High Availability CommServe Host setup by recording the installation sequence once and playing it back to setup additional production and standby High Availability CommServe Host hosts.

Before You Begin

• Create a custom package using the sequence described in Creating a Custom Package.

• The custom package must be played back in a server that does not have any other Commvault packages or instances installed in it.

Procedure

Production CommServe Host

1. Copy the custom package to the server in which you plan to setup another production CommServe host.

2. Navigate to the location in which the custom package is copied, and install the package in the silent mode using the following command:

   setup.exe /silent /play install.xml
   

   You can monitor the installation from the install.log file in the %allusersprofile%\Commvault Systems\Galaxy\LogFiles folder.

   For a list of installer error codes, see Installer Error Codes.

3. Update the CommCell Administrator password as CommServe is installed using an empty password.

   For more information about updating the CommCell Administrator password, see Changing the CommCell Administrator Password.

Standby CommServe Host

1. Verify and ensure that the production CommServe host installation is successfully completed before installing the standby CommServe host.

2. Copy the custom package to the server in which you plan to setup a standby CommServe host.

3. Navigate to the location where the custom package was copied, and install the packages in the silent mode using the following command:

    
   setup.exe /silent /play install.xml /standbynode /activecshostname Production_CS_hostname

   Where:

   • <Production_CS_hostname>

     The name of the production CommServe host associated with standby in which the software is being installed. (Mandatory)

   The command can also be used with the following optional arguments for installing the SQL Client (Instance002):

   setup.exe /silent /play install.xml /standbynode /activecshostname Production_CS_hostname /failoverinstanceclientname SQL_Client_name /failoverinstancehostname IP_address /failoverinstanceusername Username to login to CS /failoverinstancepassword Password to login to CS /failoverinstanceauthcode Authcode to login to CS"

   Where:

   • /failoverinstanceclientname <SQL_Client_name>

     Option to provide a new name for the SQL client on the standby host. By default, the installer will automatically pick the available client name on the machine. (Optional)

   • /failoverinstancehostname <IP_address>

     Option to provide an IP address for the SQL Client. By default, the installer will automatically pick the available hostname for the SQL client from the machine. (Optional)

   • /failoverinstanceusername <Username to login to the CS>
     /failoverinstancepassword <Password to login to CS>

     Options to provide the credentials associated with the Administrator account on the active CommServe host. (Optional)

   • /failoverinstanceauthcode <Authcode to login to CS>

     Option to provide authcode for secure client registration. For more information on generating authcodes, see Enabling Authorization Code for a Company. (Optional)

   • /decoupledfailoverinstance

     Flag used to install the failover instance client (the instance in which the SQL Server agent and the CommServe Failover packages are installed), on both the active and standby nodes in the decoupled mode. These clients can be registered later with the CommServe, as described in Registering the Client Using the Command Line. (Optional)

   You can monitor the installation from the install.log file in the %allusersprofile%\Commvault Systems\Galaxy\LogFiles folder.

   For a list of installer error codes, see Installer Error Codes.