# Ignition Reduncancy when Database Connection Failed

**URL:** <https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219>\
**Category:** Ignition\
**Tags:** redundancy, database\
**Created:** [September 15, 2023, 2:53pm UTC](https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219 "2023-09-15T14:53:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fraser\_Mossman](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@Fraser\_Mossman](https://forum.inductiveautomation.com/u/Fraser_Mossman)\
**Post date:** [September 15, 2023, 2:53pm UTC](https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219/1 "2023-09-15T14:53:40Z")

</div>

Hi,

We as an Integrator are new to using Ignition and would like to know if anyone has experience with our redundancy scenario.

We have 2 servers set up as a redundant pair each with a PostgrSQL database running. If the connection to the database failes on the master gateway - we would like the backup to take over and become active.

Is there somewhere to configure this setting?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 15, 2023, 3:09pm UTC](https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219/2 "2023-09-15T15:09:23Z")

</div>

No, nothing like this exists.

I suggest you handle database redundancy external to Ignition. Host the database on its own server(s), using your database of choice's replication/redundancy mechanism. It should appear and be configured as a single connection to Ignition.

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [September 15, 2023, 3:34pm UTC](https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219/3 "2023-09-15T15:34:46Z")

</div>

This is how a customer of ours does it with SQL Servers and a Availability Group. They create one "listener port" that Ignition connects to, so we only have one db connection to it, but behind that connection port, they have a redundant pair of database servers that failover as needed.

---

<div class="post-metadata">

**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:** [September 15, 2023, 4:12pm UTC](https://forum.inductiveautomation.com/t/ignition-reduncancy-when-database-connection-failed/79219/4 "2023-09-15T16:12:48Z")

</div>

If you wish to follow Kevin's advice, and don't want to pay EnterpriseDB to set it up for you, look at PostgreSQL's [Replication Manager](https://www.repmgr.org/) and [Backup and Recovery Manager](https://pgbarman.org/index.html) tools.

PostgreSQL can do replication natively, but it doesn't have built-in tools to manage failover. Theoretically, you could script it all yourself with HAProxy or something similar, but repmgr and barman are well-known and supportable tools.

(EnterpriseDB offers support for PostgreSQL and these tools. EDB is the largest employer of contributors to these projects, IIRC.)