Hi,
Our plan is to have a redundant pair of batch executives. For now, the plan is that the campaign manager would run on one of them. Most of our recipes will be started by a Pas-X MES sysytem.
In your opinion, is there usually a need to have two campaign managers for redundancy? If yes, how would you do it?
The other question is whether there is a way to ensure redundancy in the batch historian. The data coming from there could be critical as it needs to be forwarded to MES and our historian so we wold not like to have any downtime.
Thanks,
Istvan
Istvan,
redundancy on the Batch historian has been viewed as less critical because the typical data sources, the .EVT from Batch Executive and the SQL or MDB Alarm Chronicle Events, are essentially buffered for a pretty substantial period of time in their native data source locations, typically. I've seen batch historians off line for weeks come back without losing any data because the .EVT and chronicle still have all the missed data. The historian simply picks up where it left off.
You can have multiple batch historians fed from the same souces, then have your MES aggregate the data from both, and/or build a temporary table in the query in which a 'distinct' statement will only get 1 copy of all records.
Campaign manager redundancy, just like batch executive redundancy is an available supported option in v11.3.