Cannot remove backup-settings

Hi,

The new ‘backups’ section seems to work just right, however I experience 2 problems:

  • my current backup schedule
    is configured for ‘non-data’, only settings, and I cannot change this in the GUI
  • I want to see if I can remove/add all my backup settings (to see if I can enable data to be backed up), but I cannot remove anything from the backup section expect for the encryption key.

I’m running the docker image 2025_06_0.

Thanks for observations or clues…

I think that switch is disabled for everyone

Francis,

Thanks for the response, but it is absolutely not the same for ‘everyone’.
I have access to a friends HA (same setup, docker image), were we apparently used different choices during the configuration of the setup, and there I can definitely include data in the backups.
The backup files themself are also quite large, indicating there is indeed data next to configuration only.

So, not being able to change this setting is one ‘issue’, but a bigger problem is, that there does not seem to be a way to remove my backup settings at all to simply start over again with new/other settings…

Very interesting, and would be good to see other users view here.

Strange indeed. On all my systems the first is always on, no way to change it. But I don’t have history

Thanks Francis for sharing.

So I found an ugly way to remove my settings in another thread, so I could start over again with my backup settings. For this I removed the ‘backup’ file in the .config/storage directory.

During a new setup attempt, you get this question which thus not seem to work:

No, we cannot change it ‘now’, and we cannot change it later.

I will wait for a bit and see for other people’s reaction, otherwise I will make a bug ticket.

I just confirmed that my friends backup file, really includes data. I restored his backup file on a clean test container, and very lovely the old data is included.

Now the question is how to achieve this in my own backup.

Performing a diff on the two config files, and ignoring the files present only shows this setting to be different (only showed the diff):

non-working:

{
  "version": 1,
  "minor_version": 7,
  "key": "backup",
  "data": {
    "config": {
        "include_addons": null,
 }
}

versus working

{
  "version": 1,
  "minor_version": 7,
  "key": "backup",
  "data": {
    "config": {
        "include_addons": [],
 }
}

I opened a bug ticket: