Install the Commvault software packages on the production CommServe host.
Log on to the production CommServe host as root.
Download the Commvault software installation packages from the Commvault Store.
Navigate to the folder, or mount point, containing the software installation packages and run the following command.
./cvpkgaddThe OEM Selection screen appears.
Select Commvault (or the appropriate OEM) and then click Next.
The Welcome to Commvault Installer screen appears.
Click Next.
The Install Task screen appears.
Select Install packages on this machine and then click Next.
The Install Option screen appears.
Select Advanced Selection and then click Next.
The Interface Selection screen may appear, when multiple interfaces (NICs) are available in the server.
Select the interface to perform the installation and then click Next.
The Package Selection screen appears.
Select the CommServe package and then click the Next button on the right-side of the dialog box.
Select the CommServe Failover package.
Note
The CommServe Failover package automatically installs the SQL Server agent and the CommServe Failover packages in a separate instance. (No additional user intervention is needed.)
OPTIONAL: Select any additional packages that you may want to install on the CommServe server.
Click Next.
The Failover Install Option screen appears.
Select This is an active node and then click Next.
The Install Directory screen appears.
Verify the installation directory (or specify a new directory) and then click Next.
Note
If you choose another directory, make sure that you have root privileges and read access to 'Others' on that directory. The /opt directory has 755 (-rwxr-xr-x) permissions by default.
The Commvault Database Setup Recommended Settings screen appears.
Verify the settings, and then click Next.
If you unselect an option, you will need to provide a new name or directory for the respective option.
Note
If you choose another directory, make sure that you have root privileges and read access to 'Others' on that directory. The /opt directory has 755 (-rwxr-xr-x) permissions by default.
The Summary screen appears.
Verify the summary, and then click Next.
The software copies the binaries and installs the packages for the CommServe server on Instance001 and the progress will be displayed. This process may take a few minutes.
The Commvault ID screen appears.
Type a User Name, Email and Password for the admin account, and then click Next.
Note down the credentials. You will need this to install the SQL Client, standby CommServe host , and to login to the user-interface.
The software copies the binaries and installs the SQL database for the CommServe server on Instance001 and the progress will be displayed. This process may take a few minutes.
The Installation Status screen appears.
Click Finish to complete the CommServe server (or Instance001) installation.
Complete the following steps to setup the SQL client (or Instance002).
The Welcome to Commvault Installer screen appears.
Click Next.
The Interface Selection will be displayed, with the available interfaces (NICs) in the server.
Select the interface to perform the installation and then click Next.
The Install Directory screen appears.
Verify the installation directory (or specify a new directory) and then click Next.
Note
If you choose another directory, make sure that you have root privileges and read access to 'Others' on that directory. The /opt directory has 755 (-rwxr-xr-x) permissions by default.
The Log Directory screen appears.
Verify the log directory (or specify a new directory) and then click Next.
Note
If you choose another directory, make sure that you have root privileges and read access to 'Others' on that directory. The /opt directory has 755 (-rwxr-xr-x) permissions by default.
The Unix Group Assignments screen appears.
Select one of the following options:
Select Yes to assign full access permissions to both the group and other users, and then click Next. (Proceed to the next step.)
Select No to setup separate permissions for group users and other users, and then click Next.
The Permission Details screen appears.
Select the necessary permissions for group users and other users, and then click Next.
The Client Host Information screen appears.
Verify the hostname for the production CommServe host, and then click Next.
The Client Information screen appears.
Verify the client name for the SQL client in the production CommServe host, and then click Next.
This is the standalone SQL agent installed in Instance002 which will be used for backing up the SQL database from the production CommServe host.
Tip
Choose a meaningful hostname to clearly differentiate this SQL client in the user interfaces like Command Center / CommCell Console. If necessary modify the Client name to make it easily recognizable.
The CVD/Network Port screen appears.
Verify the network port (or specify a new port) for the SQL client and then click Next.
The Summary screen appears.
Verify the summary, and then click Next.
The software copies the binaries and installs the packages for the SQL client (Instance002) and the progress will be displayed. This process may take a few minutes.
The Server Information screen appears.
Type the hostname of the CommServe server (Instance001), and then click Next.
The Configure HTTP Proxy screen appears.
Select one of the following options:
Select No if there are no HTTP proxy server to connect to the CommServe server, and then click Next. (Proceed to the next step.)
Select Yes, if the SQL client must connect to the CommServe server through a HTTP server, and then click Next.
The Setting HTTP Proxy Configuration screen appears.
Enter the following information and then click Next.
Type the hostname or the IP address for the HTTP proxy server.
Type the port number that must be used to communicate with the proxy server.
The Server Authentication screen appears.
Type the Username and Password associated with the admin account that was added in the Commvault ID screen (above) and then click Next.
The Installation Status screen appears.
Click Finish.
All the services will be installed and started on both the instances. You can view the services as follows:
