Yeah but you'd make them "conform" to the standard layout.

For example I have a "pool2" pool, that has an "appdata_pool2" share on it in which the per-container appdata folders are, and then in appdata sources I have /mnt/pool2/appdata_pool2. Then every container's folder beneath that will be seen as internal.

Or you could just set those folders in "Include extra files/folders" at the bottom.

19 hours ago, Kilrah said:

"appdata_pool2" share on it in which the per-container appdata folders are

This popped into my head after your previous message. So if I'm understanding correctly, if the shares were named appdata_<container> then backup will allow the internal mappings?

Edited December 14, 2025Dec 14 by shiftylilbastrd
formatting

Share has to be something other than "appdata" or it would be merged with the other, and the data for said container must be a subfolder of that.

On 12/10/2024 at 8:16 AM, Fribb said:

I currently have an issue in which my backups fail because, from what I can tell, the verification of the backup of some docker containers fails. This isn't exclusive to certain containers but rather happens with a bunch of them, one day one fails, the next day everything works fine, another day some other fails. 

 

But whenever it fails, it is always the same process, here is an example:

 

First, it tries to stop the container which, for some reason, doesn't work

[10.12.2024 00:10:02][

ℹ️][plex] Stopping plex... Error while stopping container! Code: Container already started - trying 'docker stop' method [10.12.2024 00:10:02][ℹ️][plex] That _seemed_ to work.

 

then it does the backup and the TAR verification fails

[10.12.2024 00:42:59][

ℹ️][plex] Should NOT backup external volumes, sanitizing them... [10.12.2024 00:42:59][ℹ️][plex] Calculated volumes to back up: /mnt/user/appdata/plex [10.12.2024 00:42:59][ℹ️][plex] Backing up plex... [10.12.2024 01:15:30][ℹ️][plex] Backup created without issues (took 00:32:31 (hours:mins:secs)) [10.12.2024 01:15:30][ℹ️][plex] Verifying backup... [10.12.2024 01:22:46][❌][plex] tar verification failed! ... [10.12.2024 01:24:31][ℹ️][plex] Installing planned update for plex...

 

I don't know why the stopping of the container would fail since there is no error being logged.

However, it seems that the verification failed because the backup was done while the container was running. At least that is what I am guessing because the verification failed and also states "Contents differ".

 

I also tried to help the plugin out by stopping all running containers in a pre-run script but with the command listed below, it says the following log message.

#! /bin/bash
docker stop $(docker ps -a -q)

 

[10.12.2024 00:00:02][

ℹ️][Main] Executing script '/mnt/user/appdata/pre-run-backup.sh' 'pre-run' '/mnt/user/system-backup/appdata/ab_20241210_000002'... [10.12.2024 00:00:02][ℹ️][Main] Script executed! [10.12.2024 00:00:02][⚠️][Main] Script did not returned 0 (it returned 127)!

 

Which, to my knowledge, that return code 127 means that it is a "command not found". I mean the command itself runs without issues, I also have executed the script manually and it does what it is supposed to do without issues. How can the docker command not be found? Is the script executed in some way that some basic Unraid parts are not available? 

 

This whole thing raises some questions for me:

• Why is the log message "Container already started" when there is a log message of "stopping the container"?

• Apparently, the "docker stop" command never works (for me) even though it says that it "seems to work". (there is no restart=always or anything like that on the docker container). If this isn't "docker stop" that is attempted here, what is being used here to stop the containers?

• Why is a simple pre-run script with "docker stop" returning 127 instead of 0 even though I can execute it just fine manually?

 

the same error. did you find any solution?
this error happens when your file.sh has CRLF line terminators.
just do this: sed -i 's/\r$//' /your/way/to/path/file.sh

Edited December 15, 2025Dec 15 by RAMMs

my appdata Backup Plugin can`t backup my boot drive, the debug logs says:

[20.12.2025 02:06:56][❌][Main] Flash backup failed: no answer from script!

and there are no more hints whats wrong or why its not working, anyone can help me with this issue?

Manual flash backup is working?

1 minute ago, KluthR said:

Manual flash backup is working?

with manual you mean the "manual backup" button in the appdata backup plugin? no, its not working neither

2 hours ago, DaHa said:

with manual you mean the "manual backup" button in the appdata backup plugin? no, its not working neither

No. I mean the Main Dashboard -> Flash -> Flash backup button

1 hour ago, KluthR said:

No. I mean the Main Dashboard -> Flash -> Flash backup button

thx 4 the hind, the manual backup gave me the error "there is no disk space left..." I cleaned up my old backups... now its working fine again

Hi,

When I select to update containers after backup globally it not modifies the individual settings for the containers:

Update containers after backup? Yes

Update container after backup? No

Do I have to manually set all of them to Yes? How can I exclude only some of the containers from the update if not?

Thanks,

Mark

Hi, this plugin has been working flawlessly but when backing up some containers which are part of a docker-compose stack (https://github.com/akpw/mktxp-stack), I see these errors:

'mktxp_grafana_storage' does NOT exist! Please check your mappings. Skipping it for now.

'mktxp_prometheus_storage' does NOT exist! Please check your mappings. Skipping it for now.

These are the relevant logs - note that only grafana/prometheus are erroring but loki, promtail & the stack itself are fine.

[[05.01.2026 03:00:01][ℹ️][Main] Method: Stop/Backup/Start
[05.01.2026 03:33:03][ℹ️][grafana] Stopping grafana... done! (took 1 seconds)
[05.01.2026 03:33:04][❌][grafana] 'mktxp_stack_grafana_storage' does NOT exist! Please check your mappings! Skipping it for now.
[05.01.2026 03:33:06][ℹ️][grafana] Should NOT backup external volumes, sanitizing them...
[05.01.2026 03:33:06][ℹ️][grafana] Calculated volumes to back up: /mnt/cache/appdata/mktxp/grafana/provisioning/dashboards, /mnt/cache/appdata/mktxp/grafana/provisioning/datasources
[05.01.2026 03:33:06][ℹ️][grafana] Backing up grafana...
[05.01.2026 03:33:06][ℹ️][grafana] Backup created without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:33:06][ℹ️][grafana] Verifying backup...
[05.01.2026 03:33:06][ℹ️][grafana] Verification ended without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:33:06][ℹ️][grafana] Starting grafana... (try #1) done!
[05.01.2026 03:40:33][ℹ️][loki] Stopping loki... done! (took 1 seconds)
[05.01.2026 03:40:34][ℹ️][loki] Should NOT backup external volumes, sanitizing them...
[05.01.2026 03:40:34][ℹ️][loki] Calculated volumes to back up: /mnt/cache/appdata/mktxp/loki/loki-config.yml
[05.01.2026 03:40:34][ℹ️][loki] Backing up loki...
[05.01.2026 03:40:34][ℹ️][loki] Backup created without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:40:34][ℹ️][loki] Verifying backup...
[05.01.2026 03:40:34][ℹ️][loki] Verification ended without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:40:34][ℹ️][loki] Starting loki... (try #1) done!
[05.01.2026 03:40:37][ℹ️][mktxp] Stopping mktxp... done! (took 10 seconds)
[05.01.2026 03:40:47][ℹ️][mktxp] Should NOT backup external volumes, sanitizing them...
[05.01.2026 03:40:47][ℹ️][mktxp] Calculated volumes to back up: /mnt/cache/appdata/mktxp/mktxp, /mnt/cache/appdata/mktxp/cert/cert_export_homelab-ca.crt
[05.01.2026 03:40:47][ℹ️][mktxp] Backing up mktxp...
[05.01.2026 03:40:47][ℹ️][mktxp] Backup created without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:40:47][ℹ️][mktxp] Verifying backup...
[05.01.2026 03:40:47][ℹ️][mktxp] Verification ended without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:40:47][ℹ️][mktxp] Starting mktxp... (try #1) done!
[05.01.2026 03:40:55][ℹ️][prometheus] Stopping prometheus... done! (took 1 seconds)
[05.01.2026 03:40:56][❌][prometheus] 'mktxp_prometheus_storage' does NOT exist! Please check your mappings! Skipping it for now.
[05.01.2026 03:41:00][ℹ️][prometheus] Should NOT backup external volumes, sanitizing them...
[05.01.2026 03:41:00][ℹ️][prometheus] Calculated volumes to back up: /mnt/cache/appdata/mktxp/prometheus/rules, /mnt/cache/appdata/mktxp/prometheus/prometheus.yml
[05.01.2026 03:41:00][ℹ️][prometheus] Backing up prometheus...
[05.01.2026 03:41:00][ℹ️][prometheus] Backup created without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:41:00][ℹ️][prometheus] Verifying backup...
[05.01.2026 03:41:00][ℹ️][prometheus] Verification ended without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:41:00][ℹ️][prometheus] Starting prometheus... (try #1) done!
[05.01.2026 03:41:03][ℹ️][promtail] Stopping promtail... done! (took 0 seconds)
[05.01.2026 03:41:03][ℹ️][promtail] Should NOT backup external volumes, sanitizing them...
[05.01.2026 03:41:03][ℹ️][promtail] Calculated volumes to back up: /mnt/cache/appdata/promtail, /mnt/cache/appdata/mktxp/promtail/promtail-config.yml
[05.01.2026 03:41:03][ℹ️][promtail] Backing up promtail...
[05.01.2026 03:41:03][ℹ️][promtail] Backup created without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:41:03][ℹ️][promtail] Verifying backup...
[05.01.2026 03:41:03][ℹ️][promtail] Verification ended without issues (took 00:00:00 (hours:mins:secs))
[05.01.2026 03:41:03][ℹ️][promtail] Starting promtail... (try #1) done!

It says to check my mappings but I can only see how to exclude folders, not include. The included folders appear to be auto-generated. I've not really had to make any changes to the plugin previously as it's just kind of worked! Any ideas?

40 minutes ago, bigbadbud said:

It says to check my mappings but I can only see how to exclude folders, not include. The included folders appear to be auto-generated.

Then excluding them is what you want. Seems to be Docker volume names rather than folders.

Hi,

How can I configure Appdata Backup to run docker compose down, back up my stack (with some folders excluded), and then run docker compose up?

When I configure it to back up individual containers (vpn-pia, speedtest-app, stremhu-source), it breaks. I have a specific startup order, and there are also health checks defined in the Compose file, which may be causing the issue.

The only reliable approach seems to be bringing the stack down, performing the backup, and then bringing it back up.

Thank you

Use pre/post backup scripts to stop/start stacks?

17 hours ago, Kilrah said:

Use pre/post backup scripts to stop/start stacks?

I thought about that. I can also include the stacks directory using Include extra files/folders, but how do I exclude a specific directory in the same way?

Group the containers of the stack so they're all stopped together, and use excludes on each of them as required?

Edited January 6Jan 6 by Kilrah

On 9/14/2024 at 7:42 AM, KluthR said:

the backup gets created by unraid itself. I just call the method and save the result

 

bzfirmware is fixed part of the unraid system and needs to be there.

Is there any progress on this?
Backing up bzfirmware file is totally pointless as it can be downloaded from unraid website
https://docs.unraid.net/unraid-os/download_list/
File is not unique per user.

It generates a lot of unnecessary wear on usb stick and takes some sweet time on slow stick, only to copy almost 1GB of unchanged files with every single backup.

Can we have option to skip those somehow?
/boot/bzfirmware 651MB

/boot/bzimage 173MB

40 minutes ago, btTeddy said:

It generates a lot of unnecessary wear on usb stick

It's writes that do, not reads.

You can always make your own script if you want to back up only the essential stuff, for the vast majority of people it's still probably best to have a full self-contained backup they can restore without having to piecemeal stuff from the backup and official distribution.

Edited January 9Jan 9 by Kilrah

Can anyone tell me where the plugin stores the "updateContainer" value per container?

I figured it was in the container's block in /boot/config/plugins/appdata.backup/config.json but I have half as yes, half as no and there's only one "no" in my config.json with the rest as empty strings.

They're correct in the WebUI after refresh so I know they're stored somewhere.

Edited January 12Jan 12 by CS01-HS

If the containerSettings value is empty for am container, the global setting for it is inherited.

5 hours ago, KluthR said:

If the containerSettings value is empty for am container, the global setting for it is inherited.

I woke up to a several-hundred GB backup and counting.

Turns out, because of strange wrapping, when I thought I was setting "update container" in fact I was setting "save external volumes."

Makes sense now. Thanks.

Yeah, the UI is still broken for 7.3...

And Iam very sorry to say that Iam not able to fix the UI thing for now. Maybe someone can provide a PR on github

Hi all

One of my servers has just reported an error when Appdata Backup ran overnight.

The error says "Cannot create destination folder";

Any thoughts on why this is erroring and where to start looking to fix it?

Thanks

Edited January 13Jan 13 by SliMat

Says no space, so check drive utilization and the min free space setting for that share.