# Redundancy for Driver module

**URL:** <https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839>\
**Category:** Module Development\
**Created:** [March 4, 2022, 1:46pm UTC](https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839 "2022-03-04T13:46:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![e.sagnelonge](https://avatars.discourse-cdn.com/v4/letter/e/7cd45c/32.png) [@e.sagnelonge](https://forum.inductiveautomation.com/u/e.sagnelonge)\
**Post date:** [March 4, 2022, 1:46pm UTC](https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839/1 "2022-03-04T13:46:17Z")

</div>

I am currently developing a driver for ignition.  
I would like to integrate redundancy management in order to impact the state of the connected devices according to the “Standby Activity Level” (Cold/Warm).  
This behavior can be found on the Modbus TCP module of Inductive.  
On the Backup gateway (Cold) the connected devices are Disconnected.  
On the Backup gateway (Warm) the connected devices are Connected.

I have a hard time understanding how to set this up.  
Should I manage it myself according to the states issued by the RedundancyManager or, is it possible to let Ignition manage it.

Moreover I wonder about the generation of “backup” type license.  
“backup” type license only usable on a “backup” type gateway.  
Is it really up to me to manage it or is there a module configuration that would manage it automatically ?

I am interested in any information or example to implement this !

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 4, 2022, 1:50pm UTC](https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839/2 "2022-03-04T13:50:58Z")

</div>

> [@e.sagnelonge](#):
>
> I have a hard time understanding how to set this up.  
> Should I manage it myself according to the states issued by the RedundancyManager or, is it possible to let Ignition manage it.

Please see my answer here: [Redundancy in module development - #2 by brandon1](https://forum.inductiveautomation.com/t/redundancy-in-module-development/53525/2)

Someone else will have to chime in about the backup license. I never messed with that stuff in my driver.

---

<div class="post-metadata">

**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:** [March 4, 2022, 1:51pm UTC](https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839/3 "2022-03-04T13:51:37Z")

</div>

You have to manage it. I tend to use “cold” behavior even when “warm” is selected.

---

<div class="post-metadata">

**Author:** ![e.sagnelonge](https://avatars.discourse-cdn.com/v4/letter/e/7cd45c/32.png) [@e.sagnelonge](https://forum.inductiveautomation.com/u/e.sagnelonge)\
**Post date:** [March 4, 2022, 2:15pm UTC](https://forum.inductiveautomation.com/t/redundancy-for-driver-module/56839/4 "2022-03-04T14:15:48Z")

</div>

Thanks brandon1 !  
I had seen your answer before creating this post.  
I took the liberty of asking the question again because I saw no trace of RedundancyStateListener in the “Modbus Driver” module.  
What puzzles me…