[cisco-voip] Unity Connection 9.1 Split brain

[Heim, Dennis]

Make sure both nodes are synchronized with NTP.

Dennis Heim | Solution Architect (Collaboration)
World Wide Technology, Inc. | 314-212-1814

PS Engineering:  Innovate & Ignite.


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike
Sent: Tuesday, January 07, 2014 1:30 PM
To: 'Chris Ward (chrward)'; 'Cisco VOIP'
Subject: Re: [cisco-voip] Unity Connection 9.1 Split brain

Thanks Chris I'll open a TAC case

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Chris Ward (chrward)
Sent: Tuesday, January 07, 2014 10:02 AM
To: Mike ; 'Cisco VOIP'
Subject: Re: [cisco-voip] Unity Connection 9.1 Split brain

Call TAC and have them check.

Split brain is the recovery process and should resolve to a normal state. When the HA pair has been out of contact with each other, upon reconnecting, they enter Split Brian Recovery (SBR) mode. They are essentially doing a line by line comparison of the database and syncing information between them. If information on the Pub and Sub continues to change during this process or if communication between the pair continues to drop, SBR would either continue to run until they are in sync or SBR may need to restart.

We have seen some cases where continually interrupting SBR can result in a hung state. I would not reboot the sub until you talk to TAC and have them take a look however, so that you don't make it worse if it is still actually processing. Although 3 days does seem long for most cases, how many users and ports is this deployment?

+Chris
TME - Unity Connection and MediaSense

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike
Sent: Tuesday, January 07, 2014 9:32 AM
To: 'Cisco VOIP'
Subject: [cisco-voip] Unity Connection 9.1 Split brain

Will Split Brain auto-recover? Mines been in SB for 3 days the pub is working fine should I just reboot the sub?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140107/3895b772/attachment.html>