# Gateway Redundancy Providers System Events (Remote needs to do full pull) **URL:** \ **Category:** Ignition\ **Tags:** redundancy\ **Created:** [December 11, 2023, 7:26am UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959 "2023-12-11T07:26:38Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 28, 2024, 10:57pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/10 "2024-02-28T22:57:29Z")
See this recent topic: > [@Architecture for Distributed Control Center](https://forum.inductiveautomation.com/t/architecture-for-distributed-control-center/85104/9): > > Ignition redundancy is both latency sensitive and subject to split brain syndrome. If the comms goes down between sites, both servers will end up active and therefore numerous properties start to diverge. So let me amend my answer to: Ignition redundant servers must be installed on a common LAN with a robust network layout (preferably multi-path, like RTSP), such that any loss of comms also results in loss of comms to all clients and all devices and all databases. (Trunk port for multiple VL… --- _[View the full topic](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959)._