Recovering From a Stuck Failback

Updated

On this page

Symptom

The failover progress does not report any new activity in the Process Manager and both the production and standby CommServe hosts are down and inaccessible.

Resolution

  1. From the active node, navigate to the following folder:

    \Program Files\Commvault\ContentStore2\Base

    Where:

    ContentStore2 corresponds to the installation folder associated with the SQL client or Instance002. If you have installed the SQL client in a different instance, navigate to the corresponding folder.

  2. Run the following command:

    GxAdmin.exe -console -failover -resetconfig <active_node_name>
  3. Check the contents of CommServeLiveSyncMonitoring.log and look for the following information:

    ResetConfigFile() - #######Received a request to reset configuration file #######

    ResetConfigFile() - Successfully reset config file for node <Active_node_name>.
  4. Increase the synchronization frequency to ensure that the live sync operation does not start during the failback operation. For more information on increasing the synchronization frequency, see Modifying the Synchronization Frequency.

  5. Perform a test failover. For more information on performing a test failover, see Performing Test Failovers.

  6. Reset the test failover. For more information on resetting the test failover, see Resetting Test Failovers.

  7. Reset the synchronization frequency to its original value. For more information on resetting the synchronization frequency, see Modifying the Synchronization Frequency.