Commserve Failover

Last post 10-12-2017, 10:50 AM by anirudh kambhatla. 3 replies.
Sort Posts: Previous Next
  • Commserve Failover
    Posted: 10-11-2017, 11:18 AM

    Anyone with experience of using the Commserve failover?

    Testing it out and have run into a few anomalies.

    Using the Failover monitor to execute a test failover, suceeds, am able to perform restores from the standby DR Commserve.

    When failing back, the operation on the standby DR suceeds but the operation on the primary Commserve fails.

    It won't stop me logging into the Commserve but the Media Agent I have included in the test client computer group now shows as offline as well as the direct attached library despite all services running.

    Looking more closely at the services on the Media Agent it points to the standby DR physical host name, so updating the Commserve name (which is floating) makes no difference.

    Any suggestions or experiences/results similar to this?

    Version 11 sp9

  • Re: Commserve Failover
    Posted: 10-11-2017, 11:45 AM

    Looks like name change operation on Test Failover clients failed during Test Failback operation.

    Can you please check cvfailover.logs on Active host. Can you please escalate the issue to us, with logs.

     

    Thanks

    Anirudh

  • Re: Commserve Failover
    Posted: 10-11-2017, 1:13 PM

    thanks for the reply. This is from the cvfailover.log on the active node.

    5300	1c54	10/12 01:56:18	### INFO	[CvFailoverCommserv:__init__@93] - ---------Starting CvFailoverCommserv process---------
    5300 1c54 10/12 01:56:18 ### INFO [CvFailoverCommserv:__init__@94] - Command line arguments received are ['C:\\Program Files\\Commvault\\ContentStore2\\CvFailover\\cvfailovercommserv.exe', '--testFailback', 'True', '--startFromCVD', 'True', '-cn', 'cmvcs02_sqldrp', '-vm', 'Instance002']
    5300 1c54 10/12 01:56:18 ### INFO [CvFailoverCommserv:__init__@122] - CvFailover process currently running with pid 6464
    5300 1c54 10/12 01:56:18 ### INFO [CvFailoverCommserv:checkAndCreateKeys@728] - Registry Key 'CvFailoverNodeNo' was found to be updated, do nothing
    5300 1c54 10/12 01:56:18 ### INFO [CvFailoverCommserv:getActiveCachedValue@749] - Getting active node value from the registry
    5300 1c54 10/12 01:56:18 ### ERROR [CvFailoverCommserv:doTestFailback@1057] - Testfailover is not in progress.Cannot proceed
    5300 1c54 10/12 01:56:18 ### INFO [CvFailoverCommserv:__init__@273] - ---------CvFailoverCommserv process is exiting---------
    7236 14a0 10/12 01:58:59 ### INFO [CvFailoverCommserv:__init__@93] - ---------Starting CvFailoverCommserv process---------
    7236 14a0 10/12 01:58:59 ### INFO [CvFailoverCommserv:__init__@94] - Command line arguments received are ['cvfailovercommserv.exe', '--synchronize', '2', '-cn', 'cmvcs02_sqldrp', '-vm', 'Instance002']
    7236 14a0 10/12 01:59:00 ### INFO [CvFailoverCommserv:__init__@122] - CvFailover process currently running with pid 6464
    7236 14a0 10/12 01:59:00 ### INFO [CvFailoverCommserv:checkAndCreateKeys@728] - Registry Key 'CvFailoverNodeNo' was found to be updated, do nothing
    7236 14a0 10/12 01:59:00 ### INFO [CvFailoverCommserv:getActiveCachedValue@749] - Getting active node value from the registry
    7236 14a0 10/12 01:59:00 ### ERROR [CvFailoverCommserv.SynchronizationHelper:synchronize@206] - Failed to get the Commvault temp directory of the restore destination client: cmvcs01_sqldr_a. Defaulting to C:\windows\temp.
    7236 14a0 10/12 01:59:01 ### INFO [CvFailoverCommserv.SynchronizationHelper:synchronize@244] - Synchronization thread is starting backup and restore sequence
    7236 14a0 10/12 01:59:01 ### INFO [CvFailoverCommserv.SynchronizationHelper:synchronize@301] - SQl Restore will close all open DB Connections
    7236 14a0 10/12 01:59:01 ### INFO [CvFailoverCommserv.SynchronizationHelper:synchronize@325] - SQl Restore will close all open DB Connections
    7236 14a0 10/12 01:59:01 ### INFO [CvFailoverCommserv.SynchronizationHelper:synchronize@342] - Incremental Backup command to be run:'"C:\Program Files\Commvault\ContentStore2\Base\..\CvFailover\log_backup.cmd" cmvcommserve.company.com 34bfc6a2e0a1f2757ffcc570d8283e5133dd33134e5ca3da8a139805dd172edb3fad7c1a9ffc37d80058e11a80e620bbb4c073dcd16e08d7c09f7999b1255d8bd8c45524f221d8da357a6dd1b3a582076ac93e0996508a3b02eb209453685a180825a919580f1a83e9ffd2826425a4a673449067bcffb27089136718b5166b94ba8f011abf4686ba2204286dee3745c22597a9e208d1642fd789fc4eec20bd8537b67c63460c6bb5232f9b4a529fec2450ec90ecf9809f8399481da69195b2aec85e83208d890d08dfe603431b1ef149339cd52842c5e4202678201cc6f995c1a2d9afed8dc9b90772e91477b92ebe780155f96677f88187daf1d1259cf7873004d11f3cbb57eab69a8a1583f7649d769 C:\Windows\TEMP\output_log_backup_cvfailover_2017_10_13_01_59_00 C:\Windows\TEMP\log_backup_cvfailover_2017_10_13_01_59_00 -c cmvcs02_sqldrp -i cmvcs02\Commvault -s CvFailoverLogShipping'
    7236 14a0 10/12 01:59:01 ### INFO [CvFailoverCommserv.SynchronizationHelper:executeCommand@496] - "C:\Program Files\Commvault\ContentStore2\Base\..\CvFailover\log_backup.cmd" cmvcommserve.company.com 34bfc6a2e0a1f2757ffcc570d8283e5133dd33134e5ca3da8a139805dd172edb3fad7c1a9ffc37d80058e11a80e620bbb4c073dcd16e08d7c09f7999b1255d8bd8c45524f221d8da357a6dd1b3a582076ac93e0996508a3b02eb209453685a180825a919580f1a83e9ffd2826425a4a673449067bcffb27089136718b5166b94ba8f011abf4686ba2204286dee3745c22597a9e208d1642fd789fc4eec20bd8537b67c63460c6bb5232f9b4a529fec2450ec90ecf9809f8399481da69195b2aec85e83208d890d08dfe603431b1ef149339cd52842c5e4202678201cc6f995c1a2d9afed8dc9b90772e91477b92ebe780155f96677f88187daf1d1259cf7873004d11f3cbb57eab69a8a1583f7649d769 C:\Windows\TEMP\output_log_backup_cvfailover_2017_10_13_01_59_00 C:\Windows\TEMP\log_backup_cvfailover_2017_10_13_01_59_00 -c cmvcs02_sqldrp -i cmvcs02\Commvault -s CvFailoverLogShipping
     
    Interestingly full failover rather than Test works. 
  • Re: Commserve Failover
    Posted: 10-12-2017, 10:50 AM

    Hi,

    We create a lock file when Test Failover operation is in progress. In this case lock file went missing.

    5300    1c54    10/12 01:56:18            ### ERROR   [CvFailoverCommserv:doTestFailback@1057] - Testfailover is not in progress.Cannot proceed

     

    Can you please escalate the issue with logs from all 4 Instances. [2CS Instances + 2 CVFailover Instances]

     

    Thanks

    Anirudh

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2017 Commvault | All Rights Reserved. | Legal | Privacy Policy