'Sync Now' not working on new Standby Commserve

Last post 03-05-2019, 10:17 AM by Leo E. 7 replies.
Sort Posts: Previous Next
  • 'Sync Now' not working on new Standby Commserve
    Posted: 12-13-2018, 7:28 PM

    I'm new to Commvault.  Following these instructions to set up a Standby Commserve:

    http://documentation.commvault.com/commvault/v11_sp6/article?p=features/disaster_recovery/c_cs_failover_build_with_dns.htm

    I thought I had it all set up:

    • On both hosts, Commserve is on Instance001, SQL Agent/Failover on Instance002
    • Using a pre-existing separate Media Agent
    • SQL Server is using the Full recovery model
    • Successfully backed up prod SQL DB/restored to standby SQL DB using new subclient/storage policy just before sync attempt
     
    But all I get is the following text in CvFailover.Log when I hit 'Sync Now'.  What am I missing?
     
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:__init__] - ---------Starting CvFailoverCommserv process---------
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:__init__] - Command line arguments received are [['cvfailovercommserv.exe', '--synchronize', '1', '-cn', 'PROD_COMMSERVE_Failover', '-vm', 'Instance002']]
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:__init__] - CvFailover process currently running with pid 14772
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:__init__] - My node:(PROD_COMMSERVE.mydomain.com). My Id:[1]
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:checkActiveNode] - IsLocal:False
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:isTestFailoverInProgress] - Failed to read registry key 'TestFailOverClient'. Error:[The system cannot find the file specified]
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:checkActiveNode] - Couldn't find the mangledHostname key for client: PROD_COMMSERVE_Failover.Error:[No option 'node1.mangledHostname' in section: 'CvFailover Configuration']
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:checkActiveNode] - Couldn't find the mangledHostname key for client: STANDBY_COMMSERVE_Failover.Error:[No option 'node2.mangledHostname' in section: 'CvFailover Configuration']
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:checkActiveNode] - Local clientname:[PROD_COMMSERVE_Failover] Remote clientname:[STANDBY_COMMSERVE_Failover].
    30436  422c  12/13 16:12:05  [CvFailoverCommserv:checkActiveNode] - Client (PROD_COMMSERVE_Failover) Status (True) Node No(1) ActiveNode (1) ServiceStatus (0) TestFailover (0)
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:checkActiveNode] - Client (STANDBY_COMMSERVE_Failover) Status (True) Node No(2) ActiveNode (1) ServiceStatus (0) TestFailover (0)
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:checkActiveNode] - Fetched status from both the nodes successfully.
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:checkActiveNode] - Both nodes are euther up or dowm.
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:checkActiveNode] - Node (PROD_COMMSERVE.mydomain.com) is ACTIVE. Node (STANDBY_COMMSERVE_Failover) is PASSIVE accroding to the values in the registry
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:__init__] - This node is ACTIVE
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:__init__] - Current active node:[1], MyId:[1].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:__init__] - Failover is configured without witness servers, CVFailover will run in basic mode.
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:__init__] - Instance: [Instance002] Commserver Instance: [Instance001]
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:__init__] - Sending email alert is disabled by configuration.
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:reloadSyncValuesFromRegistry] - Last FullSyncTime [11/16/2018 18:12:55].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:reloadSyncValuesFromRegistry] - Last DiffSyncTime [11/16/2018 18:12:55].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:reloadSyncValuesFromRegistry] - Last IncSyncTime [11/16/2018 18:12:55].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:reloadSyncValuesFromRegistry] - Last NoSyncEmailAlertSentTime [12/31/1969 16:00:00].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:reloadSyncValuesFromRegistry] - Allowed duration without a synchronization: [6 hours].
    30436  422c  12/13 16:12:07  [CvFailoverCommserv:__init__] - Starting a synchronization operation
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Synchronize() isFull[False]. isDifferential[False]
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Failed to read node1.installDirectory from config file. Error:[No option 'node1.installDirectory' in section: 'CvFailover Configuration']
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Commvault temp directory of the restore destination client: [D:\Program Files\Commvault\ContentStore_Failover\Temp]
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Synchronization thread is starting a backup and restore sequence
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - SQL Restore will close all open DB Connections
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - SQL Restore will close all open DB Connections
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Running an Incremental Backup:'"D:\Program Files\Commvault\ContentStore_Failover\Base\..\CvFailover\log_backup.cmd" DNS_ALIAS.mydomain.com 35396d35356e8a6e058c7c32580fd9fcc5ebe43bc683cb3a9eb71ce16442ba62e2582ab50431e820b488a0002a27cbf041b07f10c48b3edeaf954c7407dfbd397f8a754b1eb8a404da6380404b4f77cdf00da421ba53c92de329f0aefddcad5474306fe8b09792772bef53793c4f011090897f7a9639319a1d185bf012f7175477d540d6f1d04fb9737da88c49abc0d084a7ef3551d7fa1f340ca815b135bd8e9312e60eeb56036337f1bfd45dbf6f63ce35239bcc57bf57583e45d7a701702db83718486724db12d1ab310e1c000ffd40f0f87163b0a4453a9b5464dde4e87df6e530b9f9e6fa42891b318d0c5f72e9d2a8d87ebd175c09246560a8e29c203a7 C:\Windows\TEMP\output_log_backup_cvfailover_2018_12_14_16_12_07 C:\Windows\TEMP\log_backup_cvfailover_2018_12_14_16_12_07 -c PROD_COMMSERVE_Failover -i DNS_ALIAS\Commvault -s CvFailoverLogShipping'
    30436  422c  12/13 16:12:07  [CvFailoverCommserv.SynchronizationHelper:executeCommand] - "D:\Program Files\Commvault\ContentStore_Failover\Base\..\CvFailover\log_backup.cmd" DNS_ALIAS.mydomain.com 35396d35356e8a6e058c7c32580fd9fcc5ebe43bc683cb3a9eb71ce16442ba62e2582ab50431e820b488a0002a27cbf041b07f10c48b3edeaf954c7407dfbd397f8a754b1eb8a404da6380404b4f77cdf00da421ba53c92de329f0aefddcad5474306fe8b09792772bef53793c4f011090897f7a9639319a1d185bf012f7175477d540d6f1d04fb9737da88c49abc0d084a7ef3551d7fa1f340ca815b135bd8e9312e60eeb56036337f1bfd45dbf6f63ce35239bcc57bf57583e45d7a701702db83718486724db12d1ab310e1c000ffd40f0f87163b0a4453a9b5464dde4e87df6e530b9f9e6fa42891b318d0c5f72e9d2a8d87ebd175c09246560a8e29c203a7 C:\Windows\TEMP\output_log_backup_cvfailover_2018_12_14_16_12_07 C:\Windows\TEMP\log_backup_cvfailover_2018_12_14_16_12_07 -c PROD_COMMSERVE_Failover -i DNS_ALIAS\Commvault -s CvFailoverLogShipping
    30436  422c  12/13 16:12:09  [CvFailoverCommserv.SynchronizationHelper:executeCommand] - Command Incremental Backup executed with return code: 2 Error string: execute: Error 0x911: Failed to process request due to invalid entity information.Invalid instanceId for instanceName[DNS_ALIAS\Commvault].Invalid backupsetId for backupsetName[defaultBackupSet].Invalid subclientId for subclientName[CvFailoverLogShipping].Failed to get job details.
    30436  422c  12/13 16:12:09  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Failed to read the file : C:\Windows\TEMP\output_log_backup_cvfailover_2018_12_14_16_12_07
    30436  422c  12/13 16:12:09  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Backup failed with error code 2
    30436  422c  12/13 16:12:09  [CvFailover.Email:sendMail] - Sending email is disabled by configuration.
    30436  422c  12/13 16:12:09  [CvFailover.Email:sendMail] - Email with subject [Alert: Synchronization operation failed Type: Disaster Recovery] is not sent.
    30436  422c  12/13 16:12:09  [CvFailoverCommserv:__init__] - Failed to synchronize the nodes
    30436  422c  12/13 16:12:09  [CvFailover.Email:sendMail] - Sending email is disabled by configuration.
    30436  422c  12/13 16:12:09  [CvFailover.Email:sendMail] - Email with subject [Alert: Synchronization operation failed Type: Disaster Recovery] is not sent.
    30436  422c  12/13 16:12:09  [CvFailoverCommserv:__init__] - ---------CvFailoverCommserv process is exiting. RetCode:[0].---------
  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 12-26-2018, 4:27 PM

    Were you able to get this working? If not, are we still using a floating hostname?

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 01-09-2019, 8:46 PM

    It's still not working because I'm at a loss for how to troubleshoot it.  Yes, still using a floating hostname -- though I haven't even attempted a failover, since it doesn't appear to be synchronizing.

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 01-10-2019, 2:03 PM

    It may be beneficial to open a support ticket if posisble, to have an engineer review the steps and ensure a proper failover configuration.

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 01-10-2019, 2:12 PM

    Yeah, I'll do that. Thanks.

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 01-10-2019, 3:27 PM

    Hi Sheree,

    Can you please check the SQL Server Instance name on Advance Tab of Config GUI of Production Host.

    30436  422c  12/13 16:12:09  [CvFailoverCommserv.SynchronizationHelper:executeCommand] - Command Incremental Backup executed with return code: 2 Error string: execute: Error 0x911: Failed to process request due to invalid entity information.Invalid instanceId for instanceName[DNS_ALIAS\Commvault].Invalid backupsetId for backupsetName[defaultBackupSet].Invalid subclientId for subclientName[CvFailoverLogShipping].Failed to get job details.
    30436  422c  12/13 16:12:09  [CvFailoverCommserv.SynchronizationHelper:synchronize] - Failed to read the file : C:\Windows\TEMP\output_log_backup_cvfailover_2018_12_14_16_12_07

    Is there any future service pack upgrade plans?

    Thanks

    Anirudh

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 03-04-2019, 10:28 PM

    Hi Andiruh,

    I replaced the text in the log copy/paste.  DNS_ALIAS represents the 'floating' hostname. We just updated from SP12 to SP14 a couple days ago.

    When I engaged Support regarding this issue, they indicated that CvFailover is deprecated and that I should use LiveSync.

  • Re: 'Sync Now' not working on new Standby Commserve
    Posted: 03-05-2019, 10:17 AM

    Hi Sheree:

    LiveSync is the latest and recommended solution for standby DR solution. It is very easy to configure.

    See doc link here for http://documentation.commvault.com/commvault/v11_sp14/article?p=102843.htm.

    Please reach out to support if you need further help and they can escalate to enigneering if need be.

    We will work with you until this issue if fully resolved.

    Thanks.

    Leo

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 © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy