Solved

trying to enable livesync on prod stuck

  • 15 March 2021
  • 8 replies
  • 659 views

Userlevel 4
Badge +14

I try to enable livesync ont the prod customer commserve.

 In the control panel\Commserve LiveSync, I have selected the checkbox to Enable Livesync.

The name the  instance002 on each commserve is ok

I have selected the default CommServeDR, in connectivity I have chosen  Use Existing Configuration and leave all by default.

after 5 mn the Console is stuck. “Commserve Livesync datasaving in progress ...”

When I verify naming in the process manager, I notice that the client name of each Instance002 contains _NODE at the end, but on the console the name is ok.  Do you know why it appears ?

Thanks !

 

when I go to process manager of each commserve I have :

PROD

Client name   commserve
Client Hostname    csprod.mycustomer.com
Instance Name    Instance001
CommServe Hostname    csprod.mycustomer.com
CommServe Name   commserve


Client name         csprod-SQL_NODE
Client Hostname    csprod.mycustomer.com
Instance Name       Instance002
CommServe Hostname csprod.mycustomer.com
CommServe Name     commserve

STANDBY

Client name       commserve
Client Hostname    csdr.mycustomer.com
Instance Name      Instance001
CommServe Hostname csprod.mycustomer.com
CommServe Name     commserve

 

Client name        csdr-SQL_NODE
Client Hostname    csdr.mycustomer.com
Instance Name      Instance002
CommServe Hostname csprod.mycustomer.com
CommServe Name     commserve

icon

Best answer by Bloopa 17 March 2021, 15:03

View original

8 replies

Userlevel 4
Badge +14

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 [csdr-SQL] to check if it is running
4536  1c10  03/15 18:10:22 ### CMonitor::SendCheckAliveReq() - Successfully checked if the remote node [csdr-SQL] is alive
4536  1c10  03/15 18:10:23 ### CMonitor::StopAndDisableServicesOnPassiveNode() - Stopping and disabling services on passive node [csdr-SQL] if running
4536  1c10  03/15 18:10:23 ### CMonitor::SendStopAndDisableServicesOnPassiveNodeReq() - Sending the request to node [csdr-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 [csdr-SQL]
4536  1c10  03/15 18:10:28 ### cvhb::CvHeartBeatPrivate::refreshConfiguration(522) - Focus ClientName is not set [].
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 [Instance001] on node [csprod-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 [Instance001] on node [csprod-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 [524289]

 

 

Userlevel 4
Badge +14

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.

Userlevel 7
Badge +23

@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

 

Userlevel 4
Badge +14

Hi @Mike Struening ,

Sure here they are attached. Thanks !

 

Userlevel 4
Badge +14

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 !

Userlevel 7
Badge +23

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

Glad all is working!

Userlevel 4
Badge +14

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

11.20.3 > 11.20.40

 

Userlevel 7
Badge +23

Thanks for the detail!!!!

Reply