Skip to main content
Solved

Commvault CommServe DR Setup and Licensing Requirements

  • Nov 15, 2026 12:33 PM UTC
  • 1 reply
  • 12 views

Forum|alt.badge.img+3

Hi Team,

We currently have a standalone Commvault CommServe server running with a capacity-based licensing model.

As part of our DR planning, we are evaluating the possibility of setting up a Disaster Recovery (DR) site for the CommServe server to ensure business continuity in case of a primary site failure.

We would like to understand the recommended approach and the associated licensing requirements.

Could you please clarify the following?

  1. Do we require any additional Commvault licenses to set up a DR CommServe server?

  2. Can we achieve this using the CommServe LiveSync feature, or is a Windows Failover Cluster configuration required?

  3. Would setting up a cluster be sufficient, or do we need a separate CommServe DR server at the secondary site?

  4. Are there any additional licensing or infrastructure prerequisites for implementing CommServe DR?

  5. What is the recommended architecture and configuration procedure for setting up CommServe DR?

Our objective is to establish a reliable CommServe DR solution while minimizing additional licensing and infrastructure costs.

We would appreciate your technical recommendations and guidance on the prerequisites, architecture and licensing implications.

Best answer by Pradeep

Hi ​@Mentee ,
 

CommServe Live Sync is the recommended and supported method for DR/high availability. CommServe Live Sync does NOT require Windows Failover Cluster configurations. 
 

  • Licensing: No additional Commvault licenses are required for the DR CommServe or LiveSync itself, but you do need a Microsoft SQL Server Agent license for each CommServe host (production and standby).
  • Infrastructure: You must have:
    • Identical OS and SQL Server versions on both production and DR CommServe hosts.
    • A dedicated MediaAgent and non-deduplicated storage for LiveSync replication.
    • Proper network connectivity between production and DR sites (including required ports).

Refer document below for more details

https://documentation.commvault.com/11.46/commcell-console/planning_for_commserve_livesync_in_windows_environment.html

https://documentation.commvault.com/11.46/commcell-console/preinstallation_checklist_for_high_availability_computing.html

https://documentation.commvault.com/11.46/commcell-console/commserve_livesync_for_high_availability_disaster_recovery.html

View original

1 reply

Forum|alt.badge.img+17
  • Vaulter
  • Answer
  • Nov 16, 2026 5:23 AM UTC

Hi ​@Mentee ,
 

CommServe Live Sync is the recommended and supported method for DR/high availability. CommServe Live Sync does NOT require Windows Failover Cluster configurations. 
 

  • Licensing: No additional Commvault licenses are required for the DR CommServe or LiveSync itself, but you do need a Microsoft SQL Server Agent license for each CommServe host (production and standby).
  • Infrastructure: You must have:
    • Identical OS and SQL Server versions on both production and DR CommServe hosts.
    • A dedicated MediaAgent and non-deduplicated storage for LiveSync replication.
    • Proper network connectivity between production and DR sites (including required ports).

Refer document below for more details

https://documentation.commvault.com/11.46/commcell-console/planning_for_commserve_livesync_in_windows_environment.html

https://documentation.commvault.com/11.46/commcell-console/preinstallation_checklist_for_high_availability_computing.html

https://documentation.commvault.com/11.46/commcell-console/commserve_livesync_for_high_availability_disaster_recovery.html