10 hours ago, Kilrah said:

You must select the "backup-2" folder, NOT the individual backup. Next step will list the available backups to restore from.

OMG yes, did not see that it expanded below 🙈

It works. Just not sure what to pick after, do I restore backup config? And click all templates and containers? 

 

Edit: Got it working, thank you for the help all, saved me tons of hours of work

Edited January 11, 20251 yr by Tyk

1 hour ago, Kilrah said:

Current Win11 supports it natively

🤢🤮  Not going to install spyware11 but i will check out the 7z fork and try to figure out what was the bloat.

Edited January 10, 20251 yr by miicar

On 1/10/2025 at 10:19 AM, Kilrah said:

 

 

Do you have Update containers after backup enabled?

 

 

It’s currently set to no.

Just tried to update the plugin and got the error:
Couldn't create socket: [2] No such file or directoryChecking cron succeeded!

I've been busy recently and my server has been running fine so I haven't looked at it in weeks. This is possibly a new error, or it could have been going on for a while.

Just had a power blip and everything shut down (I really need to get a UPS).
When I fired it up I figured I might as well update my plugins manually (usually everything updates as part of appdata backup)

10 hours ago, daithi said:

usually everything updates as part of appdata backup

Appdata Backup is not updating plugins at all. It just updates docker containers, if enabled.

 

the above error message comes from Unraids install routine. Never seen it before. Did the update succeeded? I would try another reboot and check the log during boot.

On 1/10/2025 at 11:12 AM, KluthR said:

External volume backups? Whats the source paths configured?

So after a long long time, the super bloated plex backup shows that it did indeed backup my whole media collection for some reason!  I have no idea why, as the setting in the backup app are only set to "appdata" and nothing else!  Also, when i manually did the backup (a couple days after the auto one ran), non of the media files were backed up; it only backed up the appdata folder, as expected!  So, i continue to be confused!  I didn't check the krusader backup that was bloated as well, but i'm going to assume something similar has happened there!

Maybe a bug where it looks at the folders the docker containers are pointing to and backs those up too?  

Edited January 12, 20251 yr by miicar

Please upload a debug log from a faulty backup run.

11 minutes ago, KluthR said:

Please upload a debug log from a faulty backup run.

the problem is, i have rebooted the server a number of times since that faulty/bloated backup run.  I did upload the debug log (b43ce314-661f-4de5-874d-9e24bba9a28b) after i ran the manual backup, but i doubt that will be much help, as it seemed to run properly.

Hello,

 

I'm encountering the same tar verification failure on every container, e.g.:

 

[13.01.2025 11:12:09][ℹ️][Main] Starting backup for containers
[13.01.2025 11:12:09][ℹ️][stack-readarr-audio-1] Backing up EXTERNAL volumes, because its enabled!
[13.01.2025 11:12:09][ℹ️][stack-readarr-audio-1] Calculated volumes to back up: /etc/localtime, /mnt/user/data, /mnt/unraid/appdata/readarr-audio
[13.01.2025 11:12:09][ℹ️][stack-readarr-audio-1] Backing up stack-readarr-audio-1...
[13.01.2025 11:12:10][ℹ️][stack-readarr-audio-1] Backup created without issues (took 00:00:01 (hours:mins:secs))
[13.01.2025 11:12:10][ℹ️][stack-readarr-audio-1] Verifying backup...
[13.01.2025 11:12:10][❌][stack-readarr-audio-1] tar verification failed! Tar said: tar: Removing leading `/' from member names; tar: etc/localtime: Warning: Cannot readlink: No such file or directory; tar: /mnt/user/data: Not found in archive; tar: Exiting with failure status due to previous errors

 

It's failing on the global exclusions: /etc/localtime, /mnt/user/data

 

Debug log id: 2fd12486-8792-4f99-b350-1f4770ee2700

Since updating to 7.0, i'm now getting an error every backup saying "shared" does NOT exist.

 

Well it doesn't because I don't use the template folders and have them set for others in the settings. Everything works as expected, and has for many years, except now this is popping up even though its not set in the settings to look for it.

 

Bug or otherwise?

15 minutes ago, Brandonb1987 said:

Since updating to 7.0, i'm now getting an error every backup saying "shared" does NOT exist.

What "shared"? Only one that's common is "binhex-shared" that is a common Docker volume that's been added to binhex containers some time ago and needs to be excluded.

Edited January 14, 20251 yr by Kilrah

11 minutes ago, Kilrah said:

and needs to be excluded.

I would love to know how to do this?

47 minutes ago, wgstarks said:

I would love to know how to do this?

Just add it to exclusions?

 

52 minutes ago, Kilrah said:

Just add it to exclusions?

 

Thx. Thought that was for files.

It actually is. But comparing the path „binhex-shared“ (which is a named volume and not a path) matches against the entry in this field, so its being ignored.

Thank you for this great plugin! 🙏

 

I have the classic problem discussed numerous times in this thread: "X does not have any volume to back up!"

I thought that I had set the plugin up correctly to back up from /mnt/user/appdata and /mnt/cache/appdata.

 

However, my container volume mappings are /config <-> /mnt/dockers/appdata/<container_name> where "dockers" is the NVMe drive that the appdata lives on. Adding /mnt/dockers/appdata to the appdata sources in the settings fixed the issue.

 

Now I am confused. If I go to Shares -> appdata, it leads me to /mnt/user/appdata where I see all the appdata and I also see that the location is "dockers".

 

1. I am not very tech savvy, could someone explain why I needed to add /mnt/dockers/appdata to the appdata sources in the settings?
2. Have I set up the appdata structures in a not-so-smart way?

 

Log with the error (I have more containers than shown here):

 

[14.01.2025 20:02:06][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!! :D
[14.01.2025 20:02:06][ℹ️][Main] Backing up from: /mnt/user/appdata, /mnt/cache/appdata
[14.01.2025 20:02:06][ℹ️][Main] Backing up to: /mnt/user/backups/appdata/ab_20250114_200206
[14.01.2025 20:02:06][ℹ️][Main] Selected containers: prowlarr, qbittorrent, radarr
[14.01.2025 20:02:06][ℹ️][Main] Saving container XML files...
[14.01.2025 20:02:06][ℹ️][Main] Method: Stop all container before continuing.
[14.01.2025 20:02:06][ℹ️][radarr] No stopping needed for radarr: Not started!
[14.01.2025 20:02:06][ℹ️][qbittorrent] No stopping needed for qbittorrent: Not started!
[14.01.2025 20:02:06][ℹ️][Main] Starting backup for containers
[14.01.2025 20:02:06][ℹ️][radarr] Should NOT backup external volumes, sanitizing them...
[14.01.2025 20:02:06][⚠️][radarr] radarr does not have any volume to back up! Skipping. Please consider ignoring this container.
[14.01.2025 20:02:06][ℹ️][qbittorrent] Should NOT backup external volumes, sanitizing them...
[14.01.2025 20:02:06][⚠️][qbittorrent] qbittorrent does not have any volume to back up! Skipping. Please consider ignoring this container.
[14.01.2025 20:02:06][ℹ️][Main] Set containers to previous state
[14.01.2025 20:02:06][ℹ️][qbittorrent] Starting qbittorrent is being ignored, because it was not started before (or should not be started).
[14.01.2025 20:02:06][ℹ️][radarr] Starting radarr is being ignored, because it was not started before (or should not be started).
[14.01.2025 20:02:06][ℹ️][Main] Backing up the flash drive.
[14.01.2025 20:02:26][ℹ️][Main] Flash backup created!
[14.01.2025 20:02:26][ℹ️][Main] Copying the flash backup to '/mnt/user/backups/flash_drive/' as well...
[14.01.2025 20:02:26][ℹ️][Main] VM meta backup enabled! Backing up...
[14.01.2025 20:02:26][ℹ️][Main] Done!
[14.01.2025 20:02:26][ℹ️][Main] Checking retention...
[14.01.2025 20:02:26][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day ;)
[14.01.2025 20:02:26][ℹ️][Main] ❤️

 

Edited January 14, 20251 yr by Di4rnu

My guess is that /mnt/dockers/appdata/ isn't either one of these paths:

 

[Main] Backing up from: /mnt/user/appdata, /mnt/cache/appdata

1 hour ago, Di4rnu said:

Now I am confused. If I go to Shares -> appdata, it leads me to /mnt/user/appdata where I see all the appdata and I also see that the location is "dockers".

 

1. I am not very tech savvy, could someone explain why I needed to add /mnt/dockers/appdata to the appdata sources in the settings?
2. Have I set up the appdata structures in a not-so-smart way?

You're supposed to map containers to /mnt/user/appdata and configure the appdata share to reside on the "dockers" pool. 

43 minutes ago, Kilrah said:

You're supposed to map containers to /mnt/user/appdata and configure the appdata share to reside on the "dockers" pool. 

Thank you! I had a feeling that I had configured something the wrong way.

Not sure what happened or when it happened but just realised I had 434GB of appdata backups. Looks like will need to look at how to set this up again. 

Is it right that it doesnt need to backup plex appdata folder? It was suggesting I exclude it but I might have misunderstood?

I think we need a rough backup size estimation/simulation after config change 😅

 

19 minutes ago, bally12345 said:

Is it right that it doesnt need to backup plex appdata folder?

Just the metadata/cover things. The important things like database should be included.

user needs assistance with unsigned disk plugin and a remote share mount while using the app data plugin:
 

 

Update containers after backup? is YES

But no container is updated. Where can I check what's wrong? No error in the log...

Are you sure the containers have an update?

Think so. Unraid/Docker Screen: apply update with 'blue cloud' for several docker containers. Manual update is possible with such containers.

log:
[20.01.2025 13:33:50][ℹ️][Main] Auto-Update for 'luckyBackup' is enabled and update is available! Schedule update after backup...
in the log there are the backups, then they are all started but no update after backup 😞
 

backup type: Stop all container, backup, start all
 

Edited January 20, 20251 yr by peter j