We currently have a local gateway, call it Ignition 2 and another gateway hosted in MS Azure, call it Cloud. These gateways are connected via a gateway-to-gateway connection. Currently there is historical data based between these two and the users connect to the Cloud project to control the local equipment.
The plan is to add another local gateway, call it Ignition 3 as a redundant gateway to Ignition 2. The manual talks in good detail concerning the setup of the redundancy settings between two gateways.
The questions are concerning how things would behave between Ignition 3 and Cloud if Ignition 2 goes offline. Does this gateway-to-gateway connection need to be setup manually or will this be sent from Ignition 2 during the setup process? While Ignition 2 is online does the connection between Ignition 3 and the Cloud stay dormant? If Ignition 2 goes offline and Ignition 3 becomes the primary, then does it starts sending information over the gateway connection to the Cloud?
A redundant pair behave as one gateway for most purposes on a gateway network, except that each member of the pair must have its own path "out" to the other gateways. The cloud gateway that is currently pointing a remote tag provider at Ignition2 will automatically transfer that to Ignition3 when there is a failover from 2 to 3. Similarly, history transfer currently happening between Ignition2 and the cloud will automatically change to Ignition3 when Ignition3 becomes "active" in the redundant pair.
{ But note that failover is not truly "bumpless". There can be brief data loss, particularly information stuck in Store & Forward on the gateway that dies. }