You can setup a brand new CommServe server with a CommServe LiveSync.
Step 1: Plan the CommServe LiveSync Setup
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.
Step 2: Install the Production CommServe Host
Install the Commvault software packages on the production CommServe host. For more information on installing the packages on the production CommServe host, see Installing the Production CommServe Host.
Step 3: Install the Standby CommServe Host
Install the Commvault software packages on the standby CommServe host. For more information on installing the packages on the production CommServe host, see Installing the Standby CommServe Host.
Step 4: Enable the LiveSync Operations
Enable the CommServe LiveSync feature which facilitates CommServe Recovery Using CommServe LiveSync. For more information on enabling the LiveSync operation, see Enabling CommServe LiveSync.
Step 5: Verify the Default Setup
Verify the setup from the production CommServe host to ensure that the default components are installed and configured properly. For more information, see Verifying the Default Setup.
Step 6: Verify Disaster Readiness
Perform a test failover to ensure successful production failovers. Test failovers do not affect the current jobs and activities on the production CommServe host. For more information on performing a test failover, see Verifying Disaster Readiness.
What to Do Next
Connect the Web Server and the Workflow Engine to the CommServe computer to ensure that the ODBC connection to the CommServe host is established. For more information about connecting these servers, see Configuring Connectivity to Remote Web Server and Workflow Engine Clients.
Perform a production failover to switch the CommServe server from the currently active CommServe host to a standby CommServe host. For more information on performing production failovers, see Performing Production Failovers.