Skip to main content
commvault.com commvault.com
Question

Cannot FailBack Commserver server with liveSync

  • September 15, 2025
  • 4 replies
  • 65 views
J
Byte
Forum|alt.badge.img+6

Hello,

I did failover with CommServe LiveSync. The failover was ok.

When I try to fail back to the other site, it fails, and I get an error message on the logs.

Assistant () - Executing command [C:\Program Files\Commvault\ContentStore\Base\CSRecoveryAssistant.exe].

Preparing to launch process: <C:\Program Files\Commvault\ContentStore\Base\CSRecoveryAssistant.exe>. Priority: <Normal>. Value: <32> creatio

Error: [Failed to execute command [C:\Program Files\Commvault\ContentStore\Base\CSRecoveryAssistant.exe -operation Recovery

ailure encountered while making node [commserve_xXXX] active. Rolling back operation

 

PRODUCTION FAILOVER TO NODE [commserve XXXXX] FAILED

4 replies

Erase4ndReuseMedia
Byte
Forum|alt.badge.img+14

I recommend you raise this with Support.

D
Vaulter
Forum|alt.badge.img+8

Hi ​@Jean-Paul ,

- Failback operations may fail if there is a version mismatch between the SQL Server instances hosting the CommServe Database on the primary and DR nodes.
- Ensure that the SQL Server version and build level (including cumulative updates and feature packs) are identical on both the Production and DR CommServe hosts.
- If a version discrepancy is identified, upgrade the SQL Server instance on the DR (Failback) node to match the version on the active CommServe node before initiating the failback process.
- On the target failover node, review the following log files for detailed diagnostic information: CSRecoveryAssistant.log, DatabaseUpgrade.log, cvmongod.log
- Verify that the MongoDB service is running on the target node: Open Process Manager to confirm that the MongoDB process/service is present. Examine MongoDB-related log files (CvMongod.log) for errors that may indicate issues with bringing the service online during the failback.

Regards,
Dheeraj

J
Byte
Forum|alt.badge.img+6
  • Jean-Paul
  • Author
  • Byte
  • September 25, 2025

Hello,

Thank you for your response. I’m not at the site right now to check versions. Could you please explain why the test succeeds if the SQL versions are different?

 

 

D
Vaulter
Forum|alt.badge.img+8

Hi ​@Jean-Paul ,

 

- Production failover may succeed even if the Production CommServe node is running a lower SQL Server version and the DR CommServe node is on a higher SQL version.
- However, failback from DR to the original Production node may fail, because the CommServe database that was backed up on a higher SQL version (from DR Node) cannot be restored on a lower SQL version (on Production Node).
- This SQL Server version mismatch prevents successful CVDB restore during failback, causing site replication to fail.
- In general, any mismatch between SQL Server versions will affect site replication jobs and failback operations.

- In CommServe Live Sync, site replication relies on restoring CVDB from one node to another. Therefore, always ensure that SQL Server versions are the same (or compatible) across both the Production and DR CommServe nodes to avoid replication or failback issues.

- To avoid such issues, match the SQL Server versions and patch levels between Production and DR CommServe nodes before setting up Live Sync.

 

Regards,
Dheeraj

Terms & ConditionsCookie settingsAccessibility statement