The Batch Event Collector for Redundant Batch Servers don't synchronize.
I don't know exactly when the problem was generated, it was after consecutive power failures due to a UPS problem or after a hard disc failure and replacement of a new disk with a HDD Image in it.
Any of the redundant batch servers work fine as primary, but the secondary never gets to synchronize, in fact in the attempt for synchronize it puts down the only Batch Event Collector working and the operator loses conectivity.
The temporary solution has been to turn off one of the redundant servers or disable one of the Batch Event Collector Service Provider just to keep everything working.
System ABB 800xA Ver 4.1
Redundant Batch Servers
Batch Management Version 4.1 Rollup 4
Thank you in advance.
Voted best answer
In 800xA 5.1 version, I have seen in redundant Batch server system, Primary batch server related Event collector service remains in service state and Secondary batch server related Event Collector remains in synchronizing state and shows red status in service structure which is works as designed.
Secondary event collector will come in service when primary batch server is down as switchover in Batch server redundancy is not bumpless, there is a time period mentioned in system guide for which batch services will be down during switchover.
I hope this will help you.
As per 5.1 batch Operation document -:3BUA000145-510_D_en_System_800xA_Batch_Management_5.1_Operation
The other service provider (Event Collector Service, Batch) represents the state of
the event collector service that is the source of batch events for propagation through
the 800xA core system. The batch server node that is running the primary batch
services is the exclusive provider of batch events through the 800xA core system.
The Event Collector Service for the batch node running as primary service provider
is reported as Service. The Event Collector Service for the batch node running as
secondary service provider is reported as Synchronizing. This represents the
normal and expected operational state of this service provider because batch events can only be sourced from a single node (the primary). The batch node running as secondary is synchronized with the batch node running as primary. In the event of a batch primary to secondary transfer event, the batch secondary will assume
operations as primary and begin serving batch events to the 800xA core system.
Hope it will solve you confusion.