# How don't lose the config tree in roll-back?

**URL:** <https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962>\
**Category:** Legato Application Framework\
**Created:** [January 23, 2020, 11:33am UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962 "2020-01-23T11:33:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Riegosalz](https://avatars.discourse-cdn.com/v4/letter/r/f1d935/32.png) [@Riegosalz](https://forum.legato.io/u/Riegosalz)\
**Post date:** [January 23, 2020, 11:33am UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/1 "2020-01-23T11:33:35Z")

</div>

Is there any possibility to do a config tree that it don’t erase the rollback?  
thanks

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [March 19, 2020, 10:52am UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/2 "2020-03-19T10:52:27Z")

</div>

@Riegosalz, With the roll-back, you come back to the basic Image.

If you need to keep some custom change, you need to build this basic image (.spk) as is explained here: [Legato framework seems to factory reset itself - #7 by karlkuhn](https://forum.legato.io/t/legato-framework-seems-to-factory-reset-itself/4085/7)

---

<div class="post-metadata">

**Author:** ![Riegosalz](https://avatars.discourse-cdn.com/v4/letter/r/f1d935/32.png) [@Riegosalz](https://forum.legato.io/u/Riegosalz)\
**Post date:** [March 19, 2020, 11:25am UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/3 "2020-03-19T11:25:44Z")

</div>

Hello mehdiALL1,  
I need keep the client cnf. And this can change every day (alarm points, telephone numbers, etc). Ours clients change its remotly. If a roll-back happen and this is erased, the device isn’t util  
regards

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [March 19, 2020, 1:22pm UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/4 "2020-03-19T13:22:25Z")

</div>

@Riegosalz, I know, but the rollback mechanism doesn’t trigger automatically … it’s happening just when customer do something wrong and prevents legato to work properly

---

<div class="post-metadata">

**Author:** ![Riegosalz](https://avatars.discourse-cdn.com/v4/letter/r/f1d935/32.png) [@Riegosalz](https://forum.legato.io/u/Riegosalz)\
**Post date:** [March 20, 2020, 6:01am UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/5 "2020-03-20T06:01:10Z")

</div>

Hello,  
Yes I know. But this happens more than I want. Low batteries, power off and unknown reasons. If the configuration tree was not in the legato folder, only a reboot would be seen.  
Regards

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [August 12, 2020, 2:02pm UTC](https://forum.legato.io/t/how-dont-lose-the-config-tree-in-roll-back/4962/6 "2020-08-12T14:02:13Z")

</div>

@Riegosalz, I think that Legato it’s based on that. But you can for example, put **faultAction: restart** (adef file) in all your apps to specifies the Supervisor action (reboot) when process terminates with a non-zero exit code or because of an un-caught signal (e.g., SIGSEGV, SIGBUS, SIGKILL). at least you minimize the chances of triggering the roll-back