Deploy Standby CommServe Server

Hi @drPhil ,

Deploying the DR CS, you have the right link: https://documentation.commvault.com/11.24/essential/106129_installing_standby_commserve_host.html

The amount of time it takes will depend on the machine you’re deploying on … In the field i’ve had some really fast installs and some really slow ones too.

For the most of the install duration, it is waiting on the Third Party packages (SQL etc) to install on the server.

Best Regards,

Michael

Hi @MichaelCapon,

thanks for the contribution. The procedure looks quite friendly and illustrative.

Just one thing I am not sure is point 13 and 22 - naming of the Standby CommServe Server.

So, let's say that my production CommServe Server host has name Commvault1.company.com. In point 13 I should specify only the name for the SQL agent of the Standby host? So, should it be different than the name of the SQL database on the main production CommServer Server?

In point 22, "Enter the CommServe client name in the Client Name field, and then enter the standby CommServe host name in the Host Name field. The Client Name 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. The Host Name is the Fully Qualified Domain Name (FQDN) of the standby CommServe host."

Just to be sure, should it be here the host name of the Production CommServer Server (in my example Commvault1.company.com? Or something different just like CommvaultStandby.company.com?

Hello, I would modify my question. When deploying CommServe Server Standby Host, what should be the hostname and client name for the Standby CommServe Server? Should be the hostname/client name the same as for the production server?

This should be different.

@drPhil , I’ll message our documentation team to clear this up!

 @drPhil , I’ll message our documentation team to clear this up!

Tagging in @Leo E  and @Jayashree as per @Seema Ghai