Have you ever seen this? I can’t find much info. on this…
I am seeing following in the local workstation log.nsf.
04/13/2015 08:57:02 AM FAILOVER_INFO :(CDatabaseSubprogram::TriggerDBFailback) Failback Triggered, Is MailFile = 1, Is Primary Replica = 1
04/13/2015 08:57:02 AM FAILOVER_INFO :(CDatabaseSubprogram::TriggerDBFailback) Failback Triggered, Is MailFile = 0, Is Primary Replica = 0
04/13/2015 08:57:02 AM FAILOVER_INFO :(CDatabaseSubprogram::TriggerDBFailback) Replica ID MATCH Failed !
Subject: What is Failback
When you failover to a cluster member server, we periodically check to see if the primary home mail server is back up and running This is called Failback). If it is, we then failback to the primary server. If you are seeing a lot of those messages in the log it is indicating that we are failing over for whatever reason to the cluster mate and then failing back to the primary server over and over.
The question is, ‘What is causing the failover?’
You can try the following debug:
debug_threadid=1
console_log_enabled=1
LogStatusBar=1
CLIENT_CLOCK=30
client_clock_server_format=1
CONSOLE_LOG_MAX_KBYTES=256000
Subject: Bradley - We do not have server issue so
and it appears I am only seeing this log entries on one workstation. Where do you add the debug? In the local notes.ini or one on the server? Thanks,
Subject: Check the client notes.ini
Look for DEBUGGINGWCTENABLED set to some value. You’ve turned on debugging, and in this case it is tracing failover.