I’d like some advice on deployment.
Currently I have a mission critical setup that is running one project that has several department specific areas to it. (mining business)
The mission critical setup is based in our mill with both servers being located close to each other. This is useful as we can take one down for maintenance and all the clients continue to function as they should.
One of the departments (water treatment) is based in another building about 1/2 hour drive from the mill, they use Ignition in conjunction with some other HMIs to control the plant that they are based at, as well as several facilities in and around the mill.
The problem is if the fiber link goes down between the other building and the mill, they would have to rely on local HMI (i.e. panelviews) to control the plant until we could shift one of the mission critical servers down there for them to run Ignition off. (Or install a panel edition in that building, this would prevent use of the Database functionality though). Shifting one of the mission critical servers would mean SCADA outages everytime we needed to do maintenance if the fiber link is down.
I would like for the same project to remain accessible on both sides of the link if it breaks down and would appreciate your thoughts on the best way to do this. I’m guessing the answer may lie in retargeting of some sort.
When the system is working they should be able to view alarms from all facilities on one screen as well as trends from these different facilities which I am not sure how to do with retargeting.
The user manual says Ignition supports two node redundancy, can this be expanded to three?