# Redundancy state change conditions?

**URL:** <https://forum.inductiveautomation.com/t/redundancy-state-change-conditions/8653>\
**Category:** Ignition\
**Created:** [July 1, 2014, 6:10pm UTC](https://forum.inductiveautomation.com/t/redundancy-state-change-conditions/8653 "2014-07-01T18:10:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [July 1, 2014, 6:10pm UTC](https://forum.inductiveautomation.com/t/redundancy-state-change-conditions/8653/1 "2014-07-01T18:10:55Z")

</div>

What are the conditions triggering the change of the BACKUP GW from warm mode to active mode  
and the MASTER GW from active to …?

Are some GW state like CPU load or particular thread activity or internal DB monitored ?

Could you shrae a statechart diagram explaining the possible state and transition ?

---

<div class="post-metadata">

**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:** [July 2, 2014, 2:48pm UTC](https://forum.inductiveautomation.com/t/redundancy-state-change-conditions/8653/2 "2014-07-02T14:48:52Z")

</div>

IIRC a backup becomes active when there is a loss of communication between the backup and the master (normally caused by the master Gateway stopping for whatever reason). When communication is re-established between the master and backup, the master sends a signal to the backup to become inactive. Starting in 7.7, you can also manually force a master to become inactive and a backup to become active (and vice versa).