Skip to main content

Hi Team,

Currently our commserve is configured on Vcenter Virtual Machine. We are planning to configure the commserve in high availability.

Please suggest which is best way to configure the commserve in high availability. 

1.Microsoft Cluster

2.commserver Livesync

3.Any other option?  

 

Version: 11.24.103

Hi @Thava_91,

 

Good day!

We can configure Commserver in a Windows failover cluster or as a Commserver Livesync environment as well depending on your requirement. 

But we would recommend you to plan for Commserver Live sync environment(As everything is managed by CV itself) and please find the below documentation for more information.

https://documentation.commvault.com/2022e/essential/104697_commserve_livesync_for_high_availability_disaster_recovery.html

 

Kindly let us know if you have any other concerns.

 

Thanks,
Naresh G

 

 


Hi @Thava_91,

 

Good day!

We can configure Commserver in a Windows failover cluster or as a Commserver Livesync environment as well depending on your requirement. 

But we would recommend you to plan for Commserver Live sync environment(As everything is managed by CV itself) and please find the below documentation for more information.

https://documentation.commvault.com/2022e/essential/104697_commserve_livesync_for_high_availability_disaster_recovery.html

 

Kindly let us know if you have any other concerns.

 

Thanks,
Naresh G

 

 

Thanks for the suggestions. i have a one more doubt, the current commserve is VM , so can we configure the standby Commserve as VM ?



Windows Clustering adds quite a bit of unnecessary complexity, IMHO.  I would recommend going with CommServe LiveSync for an easier to manage configuration.

Sure, the standby CS can be a VM assuming it meets the HW specs.  My suggestion would be running it on separate infrastructure, though.  You don’t want a hypervisor outage to take down both of the CommServes, as that would defeat the point of having CS replication.

Thanks,
Scott
 


We use WSFC for many years already and we love it! We have been responsible for an environment of a customer that was configured with CommServe Live Sync and we ran into a few issues and because it doesn't deliver RPO 0 we therefor decided to stick to WSFC. Once you have it running it really doesn't increase operations I would even say that it is easier to maintain. 


@Scott Moseman as @Onno van den Berg pointed out the complexity and (at the time) instability introduced when using commserve livesync in our opinion highly outweigh any other solutions including WSFC.

 

In our experience a feature release upgrade in a CommServe Livesync situation took 4+ hours each time, whereas our WSFC solution runs production again in 1 hour.

 

Only thing to point out here is that we do not use shared storage for our WSFC setup and rely on native SQL options in the product, which allows us to run the CommServe HA in the public cloud without shared storage aswell.

 

We talked about our solution versus what Commvault provides ‘out-of-the-box’ and in all honesty do not understand their push for livesync in stead of using native solutions (WSFC, SQL AG).

 

Anyway, officially currently the only HA solutions provided for Commvault are: CommServe Livesync OR WSFC with shared storage.


Reply