Cisco Bug: CSCtb62868 - Some messages left on secondary after SBR may not be delivered
May 28, 2010
- Cisco Unity Connection
Known Affected Releases
Symptom: After a network outage that caused the secondary server of a Cisco Unity Connection cluster to become primary and start delivering messages, once the network is restored and the split-brain recovery process finishes, messages that were in the process of being delivered (on the secondary) but had not completed may not be delivered. Conditions: This only applies to a Cisco Unity Connection cluster with messages left on the secondary server during an outage (in which the primary and secondary servers cannot communicate). As part of the split-brain recovery processes, messages that are in the delivery queue are copied over to the primary server (so that they can be delivered when the MTA service is started up again on the primary). However the MTA service only checks the message queue folder as it initializes. If the files have not yet completed copying when the MTA service starts, they will not be delivered. This may typically happen when the system is under substantial load (lots of messages left) during the outage.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases