# Redundancy Question: Dataset changes on backup Instance not replicating to primary **URL:** \ **Category:** Ignition\ **Tags:** redundancy\ **Created:** [April 13, 2026, 6:17pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049 "2026-04-13T18:17:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Peter.Griffin](https://avatars.discourse-cdn.com/v4/letter/p/858c86/32.png) [@Peter.Griffin](https://forum.inductiveautomation.com/u/Peter.Griffin)\ **Post date:** [April 13, 2026, 6:17pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/1 "2026-04-13T18:17:18Z")
Hello everyone, I have redundancy enabled between two Ignition instances, and I have a dataset on Instance 1. When I test redundancy by shutting down Instance 1, the dataset syncs correctly to Instance 2 without any issues. However, while running on Instance 2, I populate the dataset externally through WebDev. When I switch back to Instance 1, the data that was added while Instance 2 was active does **not** sync back to Instance 1. Is this expected behavior, or did I miss something in the configuration? Thank you! ---
**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\ **Post date:** [April 13, 2026, 7:34pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/2 "2026-04-13T19:34:56Z")
What Ignition version 8.x.x are you running? ---
**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:** [April 13, 2026, 8:53pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/3 "2026-04-13T20:53:15Z")
> [@Peter.Griffin](#): > > Is this expected behavior I don't think this is expected. But note that synchronization is not instant--it can take many seconds. It varies by module too. Tags are part of the platform--I'm not sure what the sync interval is. How long after update was it before you told the pair to fail back to the master? ---
**Author:** ![Peter.Griffin](https://avatars.discourse-cdn.com/v4/letter/p/858c86/32.png) [@Peter.Griffin](https://forum.inductiveautomation.com/u/Peter.Griffin)\ **Post date:** [April 14, 2026, 2:26pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/4 "2026-04-14T14:26:54Z")
8.1.49 ---
**Author:** ![Peter.Griffin](https://avatars.discourse-cdn.com/v4/letter/p/858c86/32.png) [@Peter.Griffin](https://forum.inductiveautomation.com/u/Peter.Griffin)\ **Post date:** [April 14, 2026, 2:27pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/5 "2026-04-14T14:27:26Z")
after about 2 to 3 mins ---
**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:** [April 14, 2026, 2:31pm UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/6 "2026-04-14T14:31:23Z")
Consider opening a support ticket. ---
**Author:** ![samee.ali](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@samee.ali](https://forum.inductiveautomation.com/u/samee.ali)\ **Post date:** [April 23, 2026, 9:19am UTC](https://forum.inductiveautomation.com/t/redundancy-question-dataset-changes-on-backup-instance-not-replicating-to-primary/115049/7 "2026-04-23T09:19:54Z")
Did you find a solution for this? I'm currently facing the same issue - when Server A comes back online, the values in Designer and external OPC clients are stale, but I had noticed that the Quick Client within the Gateway still shows the correct values.