You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
How Redundancy Works
Learn about the method of having a master Ignition and a backup Ignition for configuring Redundancy in Ignition.
Video recorded using: Ignition 7.9
Transcript(open in window)
[00:00] Redundancy in Ignition is pretty simple. Through the status section of a gateway web page, you'll notice that I already have redundancy set up, with one gateway located locally, and another on another computer. Redundancy works by having two copies of Ignition on different computers. One is the master and one is the backup. Both of them will be identical because the system will periodically take a gateway backup from the master system and restore it on to the backup gateway system. If the master system were to fail or the computer were to shut down, the system will automatically fail over to the backup system and will continue running there. All clients that are currently running will automatically switch over to the backup when a failover occurs. And there are many redundancies settings that you can alter that affect how failover occurs, and what happens to the system when the master comes back up. One important thing to note about redundancy is that the gateways don't have to be installed on the same type of system. Meaning we can have one gateway via 64 bit gateway, and another one via 32 bit gateway. Or we can have our master be a Windows machine and the backup be a Linux machine. The only thing that needs to happen for redundancy, is that the gateways need to be the same Ignition version as each other.