# Setting Up MySQL on a Backup Gateway

**URL:** <https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986>\
**Category:** Ignition\
**Created:** [September 25, 2025, 6:35pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986 "2025-09-25T18:35:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keith\_Magill](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@Keith\_Magill](https://forum.inductiveautomation.com/u/Keith_Magill)\
**Post date:** [September 25, 2025, 6:35pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986/1 "2025-09-25T18:35:52Z")

</div>

Has anyone come across any documentation specific to the installation and configuration of a MySQL database on a Backup Gateway?

The Ignition Gateway is very straight forward but I would like to insure that historical data is not lost if the main gateway crashes…

Not sure how to approach the MySQL database side of things..

---

<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 25, 2025, 6:52pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986/2 "2025-09-25T18:52:12Z")

</div>

Ignition redundancy does not understand master/backup database instances (and databases should never be installed on the same server as Ignition in production environments). You are expected to set up high availability database clustering **outside** your Ignition servers, using DB native technologies, such that both master and backup gateways can point to the **DB cluster** with a single URL.

---

<div class="post-metadata">

**Author:** ![Keith\_Magill](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@Keith\_Magill](https://forum.inductiveautomation.com/u/Keith_Magill)\
**Post date:** [September 25, 2025, 6:54pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986/3 "2025-09-25T18:54:56Z")

</div>

Ah. So I should “move” the MySQL to a third machine and have them both point to the same instance?

---

<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 25, 2025, 6:58pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986/4 "2025-09-25T18:58:29Z")

</div>

Yes. And if you need a redundant DB, it has to be done internal to your DB brand. Often done with HAproxy or similar load balancers that track which real DB is "master" behind the proxy. Some solutions use floating IP addresses the move to the live "master". There are multi-master options in some environments, but Ignition isn't really equipped to handle that.

---

<div class="post-metadata">

**Author:** ![Keith\_Magill](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@Keith\_Magill](https://forum.inductiveautomation.com/u/Keith_Magill)\
**Post date:** [September 25, 2025, 7:00pm UTC](https://forum.inductiveautomation.com/t/setting-up-mysql-on-a-backup-gateway/110986/5 "2025-09-25T19:00:18Z")

</div>

I will check with site IT. I think just a scheduled back-up of the database should be sufficient.

Thanks as always.