KluthR

How many containers do you have? Sounds like the issue that the firm does not save completely when many containers are in use. Please check the last 2-3 pages to get a workaround. Will pin the post later.

Do you point the file selector to the path, holding ALL backups? Dont select a specific one!

Currently not, no. But its noted on the wishlist https://github.com/Commifreak/unraid-appdata.backup/issues/47

Currently a non-zero exit code does not stop the backup but warns you that it did so. But that would be a nice feature. 0 - success, 1 - warn but continue, 2 - warn and cancel backup (or skip container).

Exclusion paths must match the paths used in container bind mappings. For tar /mnt/cache and /mnt/user are different folders, so not being excluded.

There is a default limit of how many form fields can be sent at once to the server. It seems that LimeTech adjusted this setting a bit down? (you posted it worked in Unraid 6 and stopped working with Unraid 7). The default limit is 1000 fields. The fix sets this limit to 2000. Maybe coincidence that it stopped working with Unraid 7. I still have to update my Development server to latest Unraid to verify whats the current limit. The permanent fix would be some sort of splitting the fields, so no adjustment to Unraids PHP settings would be needed - but as aslways: My time is limited currently. I try to get back to some coding work the next few weeks. There are some issue open and some feature requests, but nothing that breaks the maun functionality.

No, still not working. However, please try this: https://forums.unraid.net/topic/137710-plugin-appdatabackup/page/62/#findComment-1491103

Sorry, no - still not working.

Link is invalid

Please perform the "debugForm" method to see if all settings are really being sent to the server: https://forums.unraid.net/topic/137710-plugin-appdatabackup/page/62/#findComment-1488731

Are other container settings being saved? How many containers do you have? whats about saving some dummy content in the post/pre scripting section? Also discarded?

Cannot find any error? Backup ran successfully?

Enable „skip backup“ in container advanced settings Submit a debug log

That makes sense.

Then theres something wrong in that path. The plugin doesnt use symlinks at all. Maybe you use symlinks there to redirect the data somewhere else?

Why are there files directly in that folder from the backup AND separate backup job folders? However, the debug log is telling me: "PHP-ERROR occured! 2 / mkdir(): No space left on device", so please check storage.

Could you post a „ls -la /mnt/user/backup“? Somehow the plugin cant create the directory there. and a „df -h“.

Maybe you are also affected by this?

The order string seems wrong, as it always talks about mariadb. Do you have 6.12.15 ot 7.0.0? If yes, those versions fixed the javascript debug console logging. Please hit F12 in Chrome or Firefox and open the tab "Console" and reload the page and try some ordering, maybe something is displayed there.

No idea. I would restart the whole system and see if the issue still persists. For me it is no issue with Appdata backup.

The image? Yes, of course. The image has nothing to do with the appdata. If you want to pin a specific image version from that tool, you have to work with image tags. Like imagegenius/zigbee2mqtt:1.2.3

Looking good. Since the restore only does data part, I would recommend: * delete container * delete the container appdata * restore (like you shown) * create container from template should fire up the backed up version.

Dont know what FolderView plugin is. Could you explain what it does?

Slighty different. @Retribution's issue happened during other states of backup. But I don’t want to rule it out.

No, not really at all. I see, that plex backup was running from 11:08:05 to 12:30:57. A "file changed as we read it" occured and the lsof (which file is open within given path) took from 12:30:57 to 12:43:55. While writing I realize, that the cotainer listing (from dockerMan) took from 05:00:05 to 09:55:21. Thats nothing special and loaded during backup initialization. Seems like Unraid had an issue.