# Native database redundancy (replication / resync) in Ignition – current status, roadmap, and recommended architecture

**URL:** <https://forum.inductiveautomation.com/t/native-database-redundancy-replication-resync-in-ignition-current-status-roadmap-and-recommended-architecture/117492>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 15, 2026, 2:10am UTC](https://forum.inductiveautomation.com/t/native-database-redundancy-replication-resync-in-ignition-current-status-roadmap-and-recommended-architecture/117492 "2026-10-15T02:10:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhs](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jhs](https://forum.inductiveautomation.com/u/jhs)\
**Post date:** [October 15, 2026, 2:10am UTC](https://forum.inductiveautomation.com/t/native-database-redundancy-replication-resync-in-ignition-current-status-roadmap-and-recommended-architecture/117492/1 "2026-10-15T02:10:09Z")

</div>

Hello,

We are a system integrator in Korea building data center EPMS/BMS/DCIM systems on Ignition. Our sites run a Redundant Gateway Pair (Master/Backup), and our customers increasingly require the database layer to be redundant as well, with no data loss.

**Environment**

- Ignition version: [8.x.x]
- Database: [MS SQL Server / PostgreSQL / MySQL] [version]
- Architecture: Redundant Gateway Pair, [N] tags, history rate s
- Data stored in DB: Tag History, Alarm Journal, Audit Log, Transaction Groups, Script/Named Query writes

**Our current understanding** (please correct us if anything is wrong)

- Ignition does not natively replicate or synchronize data between databases; DB HA is expected to be handled by the RDBMS.
- Failover Datasource (STANDARD/STICKY) only reroutes queries to a secondary connection and does not resync data back to the primary after recovery.
- Tag History Splitter duplicates Tag History writes only; Transaction Groups, scripts, etc. are not covered.
- Store & Forward buffers history data while the DB is unavailable.

**Questions**

1. Is native database redundancy (replication or automatic resync between primary and secondary DBs) on the roadmap for 8.3 or later?
2. For a Redundant Gateway Pair in a mission-critical data center, what DB HA architecture does IA recommend (DB listener only / Failover Datasource / History Splitter / a combination)? Field experience would be greatly appreciated.
3. When using Failover Datasource or History Splitter, how should we handle data written only to the secondary DB during an outage (gaps or duplicates after fail-back)? Is there a recommended resync method?
4. How should non-history data (Transaction Groups, Alarm Journal, Audit Log, Script/Named Query writes) be protected in this architecture?

Thank you.

---

<div class="post-metadata">

**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\
**Post date:** [October 15, 2026, 5:35am UTC](https://forum.inductiveautomation.com/t/native-database-redundancy-replication-resync-in-ignition-current-status-roadmap-and-recommended-architecture/117492/2 "2026-10-15T05:35:30Z")

</div>

For high availability I think a better way to go is always on availability group. To Ignition it's just a single point connection but covers what you want.

---

<div class="post-metadata">

**Author:** ![jhs](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jhs](https://forum.inductiveautomation.com/u/jhs)\
**Post date:** [October 15, 2026, 5:49am UTC](https://forum.inductiveautomation.com/t/native-database-redundancy-replication-resync-in-ignition-current-status-roadmap-and-recommended-architecture/117492/3 "2026-10-15T05:49:38Z")

</div>

Thank you for your opinion.