Skip to main content
commvault.com commvault.com
Solved

What is the Role "Test node" as seen on the Standby node?

  • February 21, 2025
  • 4 replies
  • 36 views
downhill
Byte
Forum|alt.badge.img+9

Seem to be on the struggle bus as of late with LiveSync. I’ve reinstalled the failover packages a few times but when I run CvFailover -OpType GetFailoverConfig my standby role doesn’t show up as “Stand by Node” it is “Test node”. I’ve tried disabling and re-enabling LiveSync, etc. Nothing in the LiveSync logs that I can see show why this is. Any ideas would be appreciated.

Uninstalling and reinstalling is sort of a pain due to certs and CA bundle monkeying around and I can find no references to Test Node in any documentation pertaining to the Stand By.

thanks

Best answer by Damian Andre

It sounds like it could be a state entry in the database which is why the reinstall isn't resolving the issue. There are a couple of cleanup scripts that support can provide:

CleanupStaleFailoverAssoc.sqle
RemoveFailoverInstanceClientProp.sqle

View original
Did this answer your question?

4 replies

Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Damian AndreVaulter
  • Vaulter
  • 1287 replies
  • Answer
  • February 26, 2025

It sounds like it could be a state entry in the database which is why the reinstall isn't resolving the issue. There are a couple of cleanup scripts that support can provide:

CleanupStaleFailoverAssoc.sqle
RemoveFailoverInstanceClientProp.sqle

downhill
Byte
Forum|alt.badge.img+9
  • downhill
  • Author
  • Byte
  • 65 replies
  • February 28, 2025

Yeah, it was stale entries alright. However, after cleaning all that up and reinstalling everything, setting up LiveSync works, and it shows as a Stand By Node, and it syncs no problem, yet the Status is “ “ meaning nothing there. The primary is online. What is the trigger to make it appear “online” like it should?

thanks

downhill
Byte
Forum|alt.badge.img+9
  • downhill
  • Author
  • Byte
  • 65 replies
  • February 28, 2025

hrm, well, er, so - now I think I know: Clean install, seems good:

Stand By Node                                  2025/02/28 15:48:08.000000

Do a “test” failover and voila - it turns into a test node. Is this by design?

  Test Node                                  2025/02/28 16:30:10.000000

 

sbhatia
Vaulter
Forum|alt.badge.img+3
  • sbhatiaVaulter
  • Vaulter
  • 17 replies
  • March 4, 2025

Hello, 

Yes this is expected as a test failover is done but a test failback needs to be done to correct it automatically. 

You can use the below commands in future but make sure to perform the test failback operation as well. 

For Test failover 

./CvFailover -OpType Failover -FailoverType Test -TargetNode StandbySQLClient

for test Failback

./CvFailover -OpType Failover -FailoverType TestFailback -TargetNode TestNodeSQLClient

https://documentation.commvault.com/2024e/expert/verifying_disaster_readiness_using_test_failover.html
 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings