# Linux - upgrading redundant pair servers **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [September 18, 2024, 3:37pm UTC](https://forum.inductiveautomation.com/t/linux-upgrading-redundant-pair-servers/96137 "2024-09-18T15:37:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\ **Post date:** [September 18, 2024, 3:37pm UTC](https://forum.inductiveautomation.com/t/linux-upgrading-redundant-pair-servers/96137/1 "2024-09-18T15:37:17Z")
I've now upgraded my redundant pair servers 3-4x, each time following the User Manual's upgrade instructions. Yet, even if I follow the steps in section, "Upgrading a Redundant Pair" to a T, I always seem to have a blip somewhere. The steps specify forcing a fail over to the Backup server and then upgrading the Primary server first. The steps have me believe that there should not be any disruption to the live system due to the Backup taking over _until I allow the Primary to take over again._ Yet, each time the Primary starts following the upgrade, it immediately tries to take over and the live system gets caught in limbo. Am I missing something? I guess I'm just looking for some feedback and experiences from others because it seems the Manual's instructions are missing something. Thanks! ---
**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\ **Post date:** [September 18, 2024, 6:47pm UTC](https://forum.inductiveautomation.com/t/linux-upgrading-redundant-pair-servers/96137/2 "2024-09-18T18:47:05Z")
Under the gateway Redundancy config settings, there is a setting called "Recovery Mode". If you change this setting to Manual, the backup gateway will remain active after the primary gateway starts and they reconnect. When you are ready for the primary gateway to take over again, you have to navigate to the gateway Redundancy status page and click the "Force Failover" button. ---
**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\ **Post date:** [September 18, 2024, 7:13pm UTC](https://forum.inductiveautomation.com/t/linux-upgrading-redundant-pair-servers/96137/3 "2024-09-18T19:13:51Z")
Thank you for the feedback. I have noted that setting and will make sure I use it during my next upgrade. ---
**Author:** ![Shawn\_Rieger1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/shawn_rieger1/32/57040_2.png) [@Shawn\_Rieger1](https://forum.inductiveautomation.com/u/Shawn_Rieger1)\ **Post date:** [November 26, 2024, 4:27am UTC](https://forum.inductiveautomation.com/t/linux-upgrading-redundant-pair-servers/96137/4 "2024-11-26T04:27:44Z")
Does this negate the need for the "Startup Connection Allowance" setting/steps outlined in the manual for redundant pair upgrades? > **Step 4** : Adjust the **Startup Connection Allowance** setting to a large number. This will allow the Master to sit in the undecided state and not become active after being upgraded. Note the original value so you can reset it at the end of this process > **Step 10** : Change the **Startup Connection Allowance** setting to 0