# Potentially unexpected redundancy behavior?

**URL:** <https://forum.inductiveautomation.com/t/potentially-unexpected-redundancy-behavior/110218>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [August 27, 2025, 6:03pm UTC](https://forum.inductiveautomation.com/t/potentially-unexpected-redundancy-behavior/110218 "2025-08-27T18:03:22Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [August 27, 2025, 6:03pm UTC](https://forum.inductiveautomation.com/t/potentially-unexpected-redundancy-behavior/110218/1 "2025-08-27T18:03:23Z")

</div>

Using 8.1.25.

I have two servers in redundancy that host a vision application. Had unexpected behavior last time they had to patch the primary server so just wanted to clarify a few things.

When I manually failover, it lasts until I fail things back over and I see on the status page the status change from Backup to Master or vice versa.

1. However when server 1 was given a hard reset to run its updates without being failed over first - on server 2 the status page never changed so it didn’t seem clear that server 2 took over although vision users did increase and the instance of the applicaiton I had seemed to fail over ok. Normal to not see the status change in this event?

2. Also, when server 1 came back online, it resumed status as the master which I was not expecting - is this expected behavior?

3. A general question to people who do use it, does the redundancy not work nicely with the master getting a hard shut off, I know its better to gracefully failover when you can but has anyone experienced issues from unexpected failovers?

---

<div class="post-metadata">

**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\
**Post date:** [August 27, 2025, 7:26pm UTC](https://forum.inductiveautomation.com/t/potentially-unexpected-redundancy-behavior/110218/2 "2025-08-27T19:26:52Z")

</div>

1. This could be related to the Backup Node Settings (if Ping Max Missed is a high value and/or the Ping Timeout is high).
2. This depends on the Master Node Settings (Automatic or Manual).
3. I specifically recall issues between 8.1.18-8.1.24 with a redundant install I was working on. 8.1.25 introduced a proper fixed that allowed redundant pairs to be on different versions for the sake of upgrading. Since, then I’ve not any issues like that.

8.1.25 snippet:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/d/adee78d75e1d206dc536e960a354c387d533079a.png)