# Moving to redundant gateways **URL:** \ **Category:** Ignition\ **Created:** [February 27, 2020, 8:04pm UTC](https://forum.inductiveautomation.com/t/moving-to-redundant-gateways/32678 "2020-02-27T20:04:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![wpmccormick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/wpmccormick/32/13940_2.png) [@wpmccormick](https://forum.inductiveautomation.com/u/wpmccormick)\ **Post date:** [February 27, 2020, 8:04pm UTC](https://forum.inductiveautomation.com/t/moving-to-redundant-gateways/32678/1 "2020-02-27T20:04:32Z")
I’m working on an installation where there are 2 Ignition systems, both Windows, and each at different points along the road of commissioning. The first system (we’ll call it Sub-system) is mostly finished (designed, programmed, and installed by others), and is currently responsible for a vendor supplied plant sub-system. The second system, which I am responsible for (we’ll call it Plant), is somewhere between development and commissioning and is more of plant-wide system. It has been decided that these 2 systems should become redundant pairs, and I would like some guidance on implementing the setup. I am following [this](https://docs.inductiveautomation.com/display/DOC79/Setting+Up+Redundancy) as a guide. I think it makes sense for the Sub-system to be the backup; with the Plant system primary. And since I do not have a “clean” gateway for setting up the backup, I thought it might make sense to employ a virtual machine to implement the creation of the backup. These are the steps I think I should follow: 1. Backup each gateway 2. Spin-up virtual machine (Ubuntu since I have something Ignition ready, and I can quickly clone it) 3. Follow the steps in [this](https://docs.inductiveautomation.com/display/DOC79/Setting+Up+Redundancy) guide, using the VM as the backup 4. Make a backup of the VM backup 5. Restore the VM backup to the sub-system PC 6. Set IP addresses as required. I think it should be working at this point. Comments? Suggestions? Thanks! Bill ---
**Author:** ![rcrownover](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rcrownover/32/17805_2.png) [@rcrownover](https://forum.inductiveautomation.com/u/rcrownover)\ **Post date:** [February 28, 2020, 10:39pm UTC](https://forum.inductiveautomation.com/t/moving-to-redundant-gateways/32678/2 "2020-02-28T22:39:22Z")
I could be missing something here, but I'm assuming your _sub-system_ gateway has functionality that is not on your _Plant_ gateway. You would need to, at some point, restore an Ignition backup of the _Plant_ gateway to the _sub-system_ gateway and then re-add any of the _sub-system_ functionality to the _sub-system_ gateway. From reading your steps, I feel like that piece is missing, and you would end up with the _sub-system_ gateway not having the vendor's system functionality. That being said, I haven't seen an architecture in the wild where a Redundant gateway was actively used for functionality that doesn't exist on the Main gateway. Looking at the [documentation](https://docs.inductiveautomation.com/display/DOC80/Ignition+Redundancy) I don't think this is possible: > ## Configuration Synchronization > > The master node maintains the official version of the system configuration. You must make all changes to the system on the master Gateway, the backup Gateway does not allow you to edit properties. Similarly, the Designer only connects to the master node. > > When changes are made on the master, they are queued up to be sent to the backup node. When the backup connects, it retrieves these updates, or downloads a full system backup if it is too far out of date. > > If the master node has modules that aren't present on the backup, they are sent across. Both types of backup transfers, **data only** and **full** , will trigger the Gateway to perform a soft reboot. and > ## System Activity > > When a node is active, it runs fully, connecting to any configured OPC servers, and communicating with devices. When it is not active, its activity level is dictated by the settings, either **warm** or **cold**. > > - In **warm** standby, the system runs as if it were active, with the exception of logging data or writing to devices, allowing for faster fail-over. > - In **cold** standby, the system connects to all OPC servers but does not subscribe to Tag values. The Ignition OPC UA server does not communicate with any device, but third party OPC UA servers may still have device connections. This allows the system to standby without putting additional load on the devices and network. Failover takes slightly longer, as Tags must be subscribed and initialized. The issue is that, once you create a redundant pair, one of the gateways will be "inactive" and it isn't going to be able to write to devices, databases, etc.. And your designer isn't going to allow you to connect to the backup node while the master node is active. ## Edit You could get this to work if you implemented all of the functionality of the _sub-system_ on the _plant_ gateway. But then you would be running the _sub-system_ from the _plant-gateway_ during normal conditions. ---
**Author:** ![wpmccormick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/wpmccormick/32/13940_2.png) [@wpmccormick](https://forum.inductiveautomation.com/u/wpmccormick)\ **Post date:** [February 28, 2020, 11:21pm UTC](https://forum.inductiveautomation.com/t/moving-to-redundant-gateways/32678/3 "2020-02-28T23:21:48Z")
Yes, you are correct, the _sub-system_ gateway has functionality that is not on your _Plant_ the gateway. And this is sounding like something that’s not going to work. Thanks!