# Server(s) redundancy - Cluster/Failover/High Availability/Compellent **URL:** \ **Category:** Ignition\ **Tags:** ignition79, ignition80, database\ **Created:** [January 21, 2020, 1:38pm UTC](https://forum.inductiveautomation.com/t/server-s-redundancy-cluster-failover-high-availability-compellent/31464 "2020-01-21T13:38:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [January 21, 2020, 2:02pm UTC](https://forum.inductiveautomation.com/t/server-s-redundancy-cluster-failover-high-availability-compellent/31464/3 "2020-01-21T14:02:59Z")
That describes the kind of infrastructure needed when deploying a clustered database product (all the major commercial products have such). You will need a clustered DB product in your spec. Ignition would indeed make a connection to a single database. All of the HA functionality would be invisible to Ignition. In such a setup, consider having the most critical data buffered in the PLCs, and transferred from PLC FIFO to DB with store-and-forward disabled. This was discussed recently: > [@PLC data logging and Ignition synchronization](http://forum.inductiveautomation.com/t/plc-data-logging-and-ignition-synchronization/31362): > > I have lately came across an requirement that showed up in several tenders and left me a bit baffled. It can be summed up something like this: basic setup, several PLCs on a network connected to the SCADA server (since I’d be building a system with Ignition, this is Ignition GW) for simplicity, suppose Ignition GW is a standalone version, with DB installed on the same machine in normal operation, data from the PLC is polled and using tag historian stored stored in DB BUT: in case that GW goes … --- _[View the full topic](https://forum.inductiveautomation.com/t/server-s-redundancy-cluster-failover-high-availability-compellent/31464)._