Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Message added by KluthR,

[Plugin] Appdata.Backup

Featured Replies

Looks like multiple containers sharing a data folder but not being grouped for start/stop.

  • Replies 2.2k
  • Views 365k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Feature freeze I have less and less time for a complete care of this plugin. You already noticed this with the fact, that announced features were not implemented yet. Another reason is, that I will mo

  • The new update is coming It been a while since the last stable update. There were some betas (never got feedback though) but I had other work to do the last weeks. I tested the major changes agai

  • 2023.08.28 should fix the docker auto update issue.

Posted Images

Suddenly just started getting the following error when running this plugin after years without issues:

Cannot create destination folder

Anyone know why this started happening and how to fix it? TIA

  • Author

Can you manually create the destination folder?

Please attach the debug log.

1 hour ago, KluthR said:

Can you manually create the destination folder?

Please attach the debug log.

I tried to create to run the following in terminal:

mkdir /mnt/user/backups/appdatabackups/ab_20251005_075421

but it said invalid argument. Actually it says invalid argument even if I just say mkdir test in the backups folder but I can create folders in any of the parent directories

ab.debug.log

Edited by rama3124

  • Author

So, not plugin related. Plugin says the same

Check space on backup share or try rebooting

Yeh you're right, not sure what was going on but a reboot fixed it. Thanks for your work on this amazing plugin!

  • 2 weeks later...

Hoping someone might have some insight on what I'm seeing.

Sometime after September 29th, I noticed that backups were no longer occurring and that the appdata backup plugin was no longer listed under installed plugins tab. I then noticed that it was under the "Plugin File install errors" tab. As instructed there, I tried removing the plugin, rebooting, and reinstalling which everything looks normal - I can even perform a manual backup. But when I reboot, the same thing happens.

Anyone know what exactly this means and what could be causing it? I so far have not been able to locate logs that reference this. I am on Unraid version 6.12.15

  • Author

Latest version? There was a small bug which caused this after a reboot. But I think I fixed it. Tested multiple times.

Yes I believe (hope) so, the latest version from Community Applications, appdata.backup-2025.09.23

I noticed that after reinstalling it was maintaining my previous settings. So I renamed /boot/config/plugins/appdata.backup, removed from plugins-error, and rebooted. I then reinstalled and had to redo my config then rebooted but the same thing happened again.

The only reference I can find so far is from /var/log/syslog but nothing that is jumping out at me
Oct 13 10:59:45 tower root: plugin: installing: appdata.backup.plg

Oct 13 10:59:45 tower root: Executing hook script: pre_plugin_checks

Oct 13 10:59:45 tower root: plugin: running: anonymous

Oct 13 10:59:45 tower root: No cleanup of old plugin archive needed!

Oct 13 10:59:45 tower root: Plugin files were not present. Fresh install

Oct 13 10:59:45 tower root: Creating plugin files directory...

Oct 13 10:59:45 tower root: plugin: checking: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz - SHA256

Oct 13 10:59:45 tower root: plugin: skipping: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz already exists

Edited by blakerw87

Update:

I installed the latest beta plugin as well concurrently with stable. Interestingly, the beta plugin has the same issue (moved to Plugin File install errors tab) but now the stable version is fine after reboot. From the System Log, I see the following, is it related to this?
Oct 13 13:24:31 tower root: Reload service php-fpm warning, no pid file found - php-fpm is not running ?
Oct 13 13:24:31 tower root: plugin: run failed: '/bin/bash' returned 1

  • Author

Thanks for the log. This seems to be the issue. Ill look into it

  • Author

@blakerw87 I updated both plugin files to show some more output. If possible try to reproduce the issue. and post the whole section of the appdata.backup plugin installation (from the system log you provided). EDIT: First open the plugin tab and hit "check for updates" so Unraid loads the latest plugin metadata file. Or reinstall the beta version.

Edited by KluthR

6 hours ago, KluthR said:

@blakerw87 I updated both plugin files to show some more output. If possible try to reproduce the issue. and post the whole section of the appdata.backup plugin installation (from the system log you provided). EDIT: First open the plugin tab and hit "check for updates" so Unraid loads the latest plugin metadata file. Or reinstall the beta version.


So I tried "check for updates" on the plugin tab but there were no updates indicated for either plugin. I then reinstalled beta version but is still showing version 2025.09.17b1. After reboot, the same issue occurs. The log file looks the same (from System log)

Oct 16 07:29:54 tower root: plugin: installing: appdata.backup.beta.plg Oct 16 07:29:54 tower root: Executing hook script: pre_plugin_checks Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: No cleanup of old plugin archive needed! Oct 16 07:29:54 tower root: Plugin files were not present. Fresh install Oct 16 07:29:54 tower root: Creating plugin files directory... Oct 16 07:29:54 tower root: plugin: checking: /boot/config/plugins/appdata.backup.beta/appdata.backup.beta-2025.09.17b1.tgz - SHA256 Oct 16 07:29:54 tower root: plugin: skipping: /boot/config/plugins/appdata.backup.beta/appdata.backup.beta-2025.09.17b1.tgz already exists Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Extracting plugin files... Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Checking cron. Oct 16 07:29:54 tower root: Checking cron succeeded! Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Applying max_input_vars fix... Oct 16 07:29:54 tower root: php-fpm is stopped Oct 16 07:29:54 tower root: Skip FPM reload: Reload... Oct 16 07:29:54 tower root: Reload service php-fpm warning, no pid file found - php-fpm is not running ? Oct 16 07:29:54 tower root: plugin: run failed: '/bin/bash' returned 1 Oct 16 07:29:54 tower root: Executing hook script: post_plugin_checks Oct 16 07:29:54 tower root: plugin: installing: appdata.backup.plg Oct 16 07:29:54 tower root: Executing hook script: pre_plugin_checks Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: No cleanup of old plugin archive needed! Oct 16 07:29:54 tower root: Plugin files were not present. Fresh install Oct 16 07:29:54 tower root: Creating plugin files directory... Oct 16 07:29:54 tower root: plugin: checking: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz - SHA256 Oct 16 07:29:54 tower root: plugin: skipping: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz already exists Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Extracting plugin files... Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Checking cron. Oct 16 07:29:54 tower root: Checking cron succeeded! Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: plugin: running: anonymous Oct 16 07:29:54 tower root: Oct 16 07:29:54 tower root: ---------------------------------------------------- Oct 16 07:29:54 tower root: appdata.backup has been installed.

FYI On unraid 7.2.0-RC2 the layout is broken.

Absolutely understandable with the new responsive UI but still broken :P

image.png

Thanks for a great plugin.

I have been troubleshooting a problem for the last few weeks and cannot figure it out. It seems similar to some other issues being posted. Basically this was working normally then a few weeks ago suddenly failed to restart certain containers:

[21.10.2025 08:06:57][ℹ️][radarr] Starting radarr... (try #3) Container 'radarr' did not started! - Code: No such container
[21.10.2025 08:06:57][][radarr] Container 'radarr' did not started after multiple tries, skipping. More infos in debug log

Full debug log attached.

It seems to be the containers that have their network routed through GlutenVPN that are having issues restarting. I have tried multiple iterations of changing the backup type / order / grouping and it doesn't seem to have solved it. This current iteration / log I have "Stop, backup, start for each container" backup type with GlutenVPN in a "First" group to make sure it was up first. But no luck. I have tried about every other variation I can think too.

The backup seems to complete successfully however I am left with most of my docker containers stopped. In addition, I cannot even use the Unraid Docker GUI to "Start All". I have to reboot or at least restart Docker itself to get all the containers working again.

This has been particularly challenging to troubleshoot is that I cannot reproduce the problem with a manual backup. It seems to only happen with the scheduled (currently weekly, Tuesday at 8am) backups.

appdata backup debug log.txt

23 hours ago, JTVUS said:

GlutenVPN in a "First" group to make sure it was up first.

You're supposed to put all the containers that depend on it in the same group, so they all get stopped with gluetun last, then processed, then gluetun started first and the others next, then it moves on to the next group. Having gluetun alone in a group achieves nothing.

2 hours ago, Kilrah said:

You're supposed to put all the containers that depend on it in the same group, so they all get stopped with gluetun last, then processed, then gluetun started first and the others next, then it moves on to the next group. Having gluetun alone in a group achieves nothing.

Thanks! I think I have tried iterations of that setup including the "stop all containers, backup, start all" backup type. However, I have now created an explicit "VPN" group and just tried a manual backup that worked. Though, manual backups normally work and the errors seem to crop up more with the regular scheduled backups. I have adjusted the scheduled backups to be daily for now and will report back tomorrow.

20 hours ago, JTVUS said:

Thanks! I think I have tried iterations of that setup including the "stop all containers, backup, start all" backup type. However, I have now created an explicit "VPN" group and just tried a manual backup that worked. Though, manual backups normally work and the errors seem to crop up more with the regular scheduled backups. I have adjusted the scheduled backups to be daily for now and will report back tomorrow.

That seemed to work for the regular backup this morning too! Thanks again!

  • Author
On 10/16/2025 at 2:56 PM, KluthR said:

The log revealed the issue. I create a fix asap.

@blakerw87 I added another fix to the plugin. Please hit "Search for updates" It will find no updates, but the Metadata for the plugin gets updated. Try a reboot then, it should work now.

Which Unraid-Version do you have?

6 hours ago, KluthR said:

@blakerw87 I added another fix to the plugin. Please hit "Search for updates" It will find no updates, but the Metadata for the plugin gets updated. Try a reboot then, it should work now.

Which Unraid-Version do you have?

Unfortunately it looks like this is still occurring for me, I'll provide System Log output below. I am running Unraid version 6.12.15

Oct 24 07:56:20 tower root: plugin: installing: appdata.backup.plg Oct 24 07:56:20 tower root: Executing hook script: pre_plugin_checks Oct 24 07:56:20 tower root: plugin: running: anonymous Oct 24 07:56:20 tower root: No cleanup of old plugin archive needed! Oct 24 07:56:20 tower root: Plugin files were not present. Fresh install Oct 24 07:56:20 tower root: Creating plugin files directory... Oct 24 07:56:20 tower root: plugin: checking: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz - SHA256 Oct 24 07:56:20 tower root: plugin: skipping: /boot/config/plugins/appdata.backup/appdata.backup-2025.09.23.tgz already exists Oct 24 07:56:20 tower root: plugin: running: anonymous Oct 24 07:56:20 tower root: Extracting plugin files... Oct 24 07:56:20 tower root: plugin: running: anonymous Oct 24 07:56:20 tower root: Checking cron. Oct 24 07:56:21 tower root: Checking cron succeeded! Oct 24 07:56:21 tower root: plugin: running: anonymous Oct 24 07:56:21 tower root: Applying max_input_vars fix... Oct 24 07:56:21 tower root: Skip FPM reload: Reload... Oct 24 07:56:21 tower root: Reload service php-fpm warning, no pid file found - php-fpm is not running ? Oct 24 07:56:21 tower root: plugin: run failed: '/bin/bash' returned 1 Oct 24 07:56:21 tower root: Executing hook script: post_plugin_checks

  • Author

Please enclose those log lines within a „code“ (</>) block. However, Ill check again later.

On 10/13/2025 at 11:26 AM, blakerw87 said:

Hoping someone might have some insight on what I'm seeing.

Sometime after September 29th, I noticed that backups were no longer occurring and that the appdata backup plugin was no longer listed under installed plugins tab. I then noticed that it was under the "Plugin File install errors" tab. As instructed there, I tried removing the plugin, rebooting, and reinstalling which everything looks normal - I can even perform a manual backup. But when I reboot, the same thing happens.

Anyone know what exactly this means and what could be causing it? I so far have not been able to locate logs that reference this. I am on Unraid version 6.12.15

this is also happening to me on 6.12.5

On 10/23/2025 at 9:01 AM, JTVUS said:

That seemed to work for the regular backup this morning too! Thanks again!

Welp, I spoke to fast. The regular weekly backup failed with the same error this morning. Log attached. This has been frustrating to troubleshoot because I am not reliably able to reproduce the problem. I try a fix and works in the short term but then it fails at the regular weekly backup.

backup log 20251028.txt

Do you have a delay set after gluetun start on the Docker page? If not set a minute or so. Gluetun's probably not ready and connected instantly.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.