# Kindling - 8.3 backups

**URL:** <https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753>\
**Category:** Ignition\
**Created:** [March 30, 2026, 8:41am UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753 "2026-03-30T08:41:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [March 30, 2026, 8:41am UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/1 "2026-03-30T08:41:51Z")

</div>

Hi,

I just noticed this message in the backup explorer kindling : "8.3 Backups are not yet processed correctly" in the "statistics" section.

 ![Capture d’écran 2026-03-30 104324](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/4/749f55d4e099aa9066fb609744b5a8f464e9e5e8.png)

What does this mean? Is it an error on the integrator's part (incorrect gateway configuration, development issues)? Is it a way of indicating that Inductive didn't include everything necessary for restoration in the backup? Is it a limitation of Kindling?

Thanks.

---

<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 30, 2026, 8:51am UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/2 "2026-03-30T08:51:35Z")

</div>

> [@r.lebohec](#):
>
> Is it a limitation of Kindling?

This.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 30, 2026, 4:54pm UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/3 "2026-03-30T16:54:04Z")

</div>

To be more specific, the missing piece is that Kindling doesn't understand 8.3's file-based configuration structure. It relies on the IDB, which is not collecting updates, so on a migrated system you'll get initially accurate information that will drift from reality over time as your system accumulates 8.3 file based changes.

---

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [March 30, 2026, 5:13pm UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/4 "2026-03-30T17:13:36Z")

</div>

I deduce that beyond the current tag values ​​(if database is selected), this tool is no longer needed. For your support and diagnostic needs, what alternative do you use?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 30, 2026, 5:43pm UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/5 "2026-03-30T17:43:33Z")

</div>

Kindling's utility when viewing a gateway backup was always informational more than anything - an at-a-glance view of what the backup contains. That's still a useful feature, we just haven't implemented the "scanning"/"parsing" logic yet for 8.3. It's going to happen: [Update for maximum 8.3 compatibility · Issue #295 · inductiveautomation/kindling · GitHub](https://github.com/inductiveautomation/kindling/issues/295)

---

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [June 8, 2026, 8:58am UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/6 "2026-06-08T08:58:01Z")

</div>

Furthermore, using Kidling Tools, we observe that the backup contains all .git files located in the "config" folder of the current gateway.

Is it possible to exclude certain folders when creating the GWBK? (or is there a best practice?)

The "projects" folder structure doesn't seem to behave consistently.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 8, 2026, 3:57pm UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/7 "2026-06-08T15:57:39Z")

</div>

Any files with a leading `.` should be ignored when collecting backups.

---

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [June 9, 2026, 7:07am UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/8 "2026-06-09T07:07:47Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0f6736f96c522351b0d010f51448fb53f958ab18.png)

🤔 I am a little sceptical.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 9, 2026, 4:08pm UTC](https://forum.inductiveautomation.com/t/kindling-8-3-backups/114753/9 "2026-06-09T16:08:31Z")

</div>

Ah, `config/` goes through a different code branch and at the specific level you've got your git directory, it happens to get grabbed. I'll make a ticket.

EDIT: IGN-16538 if you want to link it to your support contact.
