KluthR

Im wondering as well no, no encryption planned. You could use post-run scripts to build something own

Do not backup /mnt/user/system when the docker image is there.

The restore needs more love, yes, but I never wanted it to create containers. Users should check the template first. A restore under existing system does not need a container creation. And a new system maybe needs a template review, so a container creation is also not needed. in the case the nee system is 1:1 set up like a new one, there could be a container creation, yes.

Restore does not create docker containers. It restores the xml. Create the desired docker from „create container“ and select the right template. Check paths and create it.

That message is something I never understood. The debug log states that nothing uses the file. I dont know how it can shrink. Maybe some tar expert here?

The snapshot can be made, yes, but a backup from a running database as example seems not a good thing to me. This can work in restore cases but it feels wrong. Maybe database engine dependent? Idk

@Infosucher Yes

Yes, you need to. You have to stop them, move every data folder, edit the container config and run them again. Except you want this for new containers only. However, the warning you get, is telling me that you are just done doing so? Because it seems to use the new path but you did not entered it as „allowed appdata sources“. or maybe you did changed the setting but the containers. Would lead to the same message. Whats your migration state?

Thats also my plan. I check native ways without sanoid but incremental zfs snapshots are my goal for the next update.

Because online snapshots are not consistent. There will be imcremental zfs snapshots in future but the recommendation to stop the services for the snapshot will still be there.

Is the plex volume in use by another container?

It only copies over the xml metadata. Not the whole libvirt things.

Sounds like file system error. Check filesystem I dont remember but is there a advanced config option to skip container backup?

Smells like temporary issue on githubs end. Try again later.

Did you read the debug log upload confirm dialog? However, it seems to be a bug. All of your nextcloudaio members should be ignored. So the group is left empty. I bet I did not catch this state. It seems the backup script skips some group magic and keeps nextcloudaio as a container name. remove the group when you not plan to backup any member. The bug will get fixed when Iam back from my holidays. Put plex and tautulli in one group. They share volumes with each other. There should also a warning in the container settings secrion.

Share debug log

No problem 😁

I dont see any issue. The timestamps are correct (+10 seconds)??

Update to latest.

Just what I thought.

Just now.

The debug log contains all infos needed. the backup stops logging at the part where extra files should back up. Either the backup script crashes or its still running? No, when running, no sharing possible afaik. And just by checking the code block for this task reveals the bug. Its a typo. Ill try to fix it today.

Please share a debug log from a recent run.

Not sure. The messages means, that something played with the files. Maybe the debug log shows what was accessing it?

Where? if you specified the share path (/mnt/user/appdata) and the final path as „extra backup files“ path, it should work DO NOT add the final path to the sources list.