Skip to main content
commvault.com commvault.com
Question

Commserve LiveSync issue

  • July 25, 2025
  • 3 replies
  • 178 views
A
Forum|alt.badge.img+1

Hi,

I configured Livesync betweeen two commserve servers. They connect to the same network without firewall enable. I run “Test Failover” test and all good without problems. Then “Mantenance Failover” all test are ok, without problem. But, when try “Maintenance Failback” the test failed.

This are the steps:

07/25/2025 11:45:24    Checking node [StandbySQL] is reachable...
07/25/2025 11:45:24    Sending the request to make node [StandbySQL] passive...
07/25/2025 11:45:11    Stopping and disabling all the services...    Done
07/25/2025 11:45:51    Update firewall settings...    Done
07/25/2025 11:46:15    Sending the request to make node [ActiveSQL] active...
07/25/2025 11:46:15    Update firewall settings...    Done
07/25/2025 11:46:15    Disabling read only CommServe mode if enabled...    Done
07/25/2025 11:46:15    Update remote cache client...    Done
07/25/2025 11:46:15    Running MongoDB repair utility...    Done
07/25/2025 11:46:25    Enabling and starting all core services...    Done
07/25/2025 11:46:48    Enabling and starting all the services...    Done
07/25/2025 11:47:00    Updating live sync schedule with new active node...    Failed
07/25/2025 11:47:13    Rolling back the operation...
07/25/2025 11:47:13    Sending the request to make node [ActiveSQL] passive...
07/25/2025 11:47:26    Stopping and disabling all the services...    Done
07/25/2025 11:48:02    Update firewall settings...    Done
07/25/2025 11:48:02    Sending the maintenance failover request to node [StandbySQL]...
07/25/2025 11:47:39    Restoring database(s) with recovery option...    Done
07/25/2025 11:47:39    Executing recovery tool in readOnlyProduction mode...    Done
07/25/2025 11:49:33    Enabling read only CommServe mode...    Done
07/25/2025 11:49:33    Doing name change if required...    Done
07/25/2025 11:49:33    Kill all active jobs...    Done
07/25/2025 11:49:33    Update firewall settings...    Done
07/25/2025 11:49:34    Running MongoDB repair utility...    Done
07/25/2025 11:49:54    Enabling and starting all the services...    Done
07/25/2025 11:50:52    Update active node information in the config file...    Done
07/25/2025 11:51:12    Successfully rolled back the operation
Failed to perform Maintenance Failback operation, please check CommServeLiveSync.log for more details

 

CommServeLiveSync.log:

[general]
# keepalive_interval=300
# tunnel_init_interval=5
# force_incoming_ssl=0
# bind_open_ports_only=0
# lockdown=1
# allowed_tppms=3389

[incoming]
# tunnel_ports=8403
# data_ports=8600-8620

[outgoing]

[http-proxy]
# host=proxy.domain.com
# port=8000

[vpnclient]

 

07/25 09:21:25 ### CCSFailoverUtils::reloadFwConfig() - Failed to reload FwConfig, check appMgrSrv.log for more details. Error code [150995030], error [[ClientSessionWrapper::connectToCS] Error connecting to svc [AppManager network access] on CS. [0xE8090068:{CCvNetwork::Attach_RemoteService(1770)} + {CCvNetwork::Attach_RemoteServiceInternal(1725)} + {CCvNetwork::Attach_RemotePort(1439)} + {CCvNetwork::GetConnection(3314)} + {CSessionConnectionSocket::GetConnection(215)} + {CSessionConnectionSocket::ParseLastError(174)/EventMessage.0x09000068.9:104.(There is no incoming network connection from remote machine [cs1.test.local]. Please check if the remote machine is able to connect to the current machine using cvping tool on tunnel port)}]]

 

I don’t understand why they can’t connect if the firewall in both servers CV are disabled and the sql server are installed in the same commserve server.

 

Thanks for the comments.

    3 replies

    P
    Vaulter
    Forum|alt.badge.img+12
    • PradeepVaulter
    • Vaulter
    • July 26, 2025

    Hi ​@Arti ,

    The above logs are from the present active machine. However, we may need logs from the DR machine as well. For now request to follow below POA and let us know the results.

     

    • Navigate to the install directory on the standby server:

      C:\Program Files\Commvault\ContentStore\Base

    • Take a backup of the following files before making any changes:

      • FwConfig

      • FwConfig.local

    • Open the FwConfig file using a text editor (e.g., Notepad).

    • Scroll to the end of the file and check for the presence of the following lines: 

    • If found, remove these lines completely.

    • Save the file and close the editor.

    clear acl clnt=xxxxxx dst=@self@ ports=@svcports@
     

    1. Log in to the Production Server.
    2. Verify if any replication or transaction log (T-Log) backups are currently running.
    3. Allow these jobs to complete before proceeding.
    4. Wait for the replication process to complete.
    5. Ensure all pending updates are fully synced with the standby server.
    6. Open the Failover Process Manager and verify that it shows the correct "Last Sync Time" to confirm replication is up to date.
    7. Once verified, initiate the Maintenance Failover.
    J
    Vaulter
    Forum|alt.badge.img+12
    • JavierVaulter
    • Vaulter
    • July 27, 2025

    Hi Arti,

     

    As Predeep is suggesting, we will need to check the logs on the current Passive Node to understand why the schedules cannot be updated accordingly.

     

    I wouldn’t adventure to say what might be going wrong without checking the logs first, it may be a good idea to open a case with support to review this

    A
    Forum|alt.badge.img+1
    • Arti
    • Author
    • July 28, 2025

    Hello,

    Thanks for take time to response Pradeep and Javier. Unfortunately, the lines erased not fix the problem. I attachs logs files for passive node

    Thanks in advance!

    2 Attachments
    Terms & ConditionsCookie settingsAccessibility statement