on this log file “CommserveLiveSyncMonitoring”

here is the error message that I’ve found

4536  1c10  03/15 18:10:22 ### CCommserveFailoverConfig::GetCurrentTestNodeName() - Fetching current test node name
4536  1c10  03/15 18:10:22 ### CMonitor::CheckAlive() - Checking if the node csdr-SQL] is alive
4536  1c10  03/15 18:10:22 ### CMonitor::SendCheckAliveReq() - Sending the request to node ecsdr-SQL] to check if it is running
4536  1c10  03/15 18:10:22 ### CMonitor::SendCheckAliveReq() - Successfully checked if the remote node ecsdr-SQL] is alive
4536  1c10  03/15 18:10:23 ### CMonitor::StopAndDisableServicesOnPassiveNode() - Stopping and disabling services on passive node ocsdr-SQL] if running
4536  1c10  03/15 18:10:23 ### CMonitor::SendStopAndDisableServicesOnPassiveNodeReq() - Sending the request to node ecsdr-SQL] to stop and disable services if running
4536  1c10  03/15 18:10:28 ### CMonitor::SendStopAndDisableServicesOnPassiveNodeReq() - Successfully stopped and disabled services on the node ecsdr-SQL]
4536  1c10  03/15 18:10:28 ### cvhb::CvHeartBeatPrivate::refreshConfiguration(522) - Focus ClientName is not set C].
4536  1c10  03/15 18:10:28 ### CCommserveFailoverConfig::GetCurrentActiveNodeName() - Fetching current active node name
4536  1324  03/15 18:11:07 ### CommServeFailoverHandler() - CommServeFailoverHandler invoked via Client csdr.centreapi.com
4536  1324  03/15 18:11:07 ### CCommServeFailover::IdentifyAndGetCommServeInstance() - CommServe instance is eInstance001] on node ccsprod-SQL]
4536  1324  03/15 18:11:07 ### CommServeFailoverHandler() - Received request to check this node is alive
4536  1324  03/15 18:11:08 ### CommServeFailoverHandler() - CommServeFailoverHandler invoked via Client csdr.centreapi.com
4536  1324  03/15 18:11:08 ### CCommServeFailover::IdentifyAndGetCommServeInstance() - CommServe instance is nInstance001] on node icsprod-SQL]
4536  1324  03/15 18:11:08 ### CommServeFailoverHandler() - Received request to refresh schedule
4536  1324  03/15 18:11:08 ### CCommServeFailover::RefreshFailoverSchedule() - Refreshing failover schedule
4536  1324  03/15 18:11:08 ### CCommServeFailover::RefreshFailoverSchedule() - Failed to configure CommServe LiveSync schedule policy. Error code v524289]

Also, after the livesync job is activated, I noticed that in the subclient created by default under the SQL instance 002 for the PROD commserve the storage Policy is missing. Normally it should be populated automatically when livesync is enabled.

I will open a commvault ticket tomorrow morning.

@Bloopa , hopefully we can get you some answers before then so you don’t need to open a case :-)

Can you please share the "CommServeFailover.xml" file from the active and the passive nodes?

Location will be the <Installation path>\Commvault\ContentStore2\iDataAgent\JobResults

Hi @Mike Struening ,

Sure here they are attached. Thanks !

Hello Team,

I have resolved the issue with my Commvault PS guy that work on the same project.

We have  update the two commserves. And now all is fine.

Thanks to all for your help !

@Bloopa , when you say update the two Commserves, do you mean you updated the Maintenance Release?

Glad all is working!

@Mike Struening Yes we pushed the last maintenance release on commserves, and Media agents. ! 

11.20.3 > 11.20.40

Thanks for the detail!!!!