Guidance Required – Promoting LiveSync DR CommServe (Azure) to Production During On-prem Decommission

Description:

We are currently planning a transition of our Commvault environment and need guidance and best practices for our scenario.

Current Setup:

• Primary CommServe (Production) hosted in a colo  data center
• LiveSync DR CommServe already configured and running in Azure (Cloud)
• Media Agents and backups are currently aligned with the colo-based production CommServe

Planned Change:

• The colo site is being decommissioned
• All workloads and servers are being migrated to Azure
• The existing DR CommServe in Azure will be promoted to Production
• Post transition, backups will be fully aligned to Azure workloads and infrastructure

Objective:

We want to:

1. Promote the Azure DR CommServe to act as the new Production CommServe
2. Reconfigure clients, Media Agents, and storage policies to align with Azure
3. Safely decommission the existing colo-based CommServe

Key Questions / Clarifications Required:

1. LiveSync Failover:
   • What is the recommended approach to promote DR CommServe to active Production?

Client Connectivity:

• Best practice for updating client communication:
  • Any tools/scripts for bulk client updates?

1. Database Consistency:
   • Any specific checks recommended before promoting DR?
2. Media Agents & Storage:
   • Considerations when switching storage from colo-based to Azure-based storage
   • Any impact on existing storage policies or deduplication databases?
3. Licensing / Configuration:
   • Any licensing or configuration implications when moving fully to Azure?
4. Best Practices:
   • Recommended sequence of steps for this migration