Kilrah

AFAIK CA takes any xml in the repo whatever the folder, you kept your old ones in a "deprecated" folder so they might still be found first and supersede the intended one, they should be outright deleted if not valid anymore. You can add a tag to deprecate a template but I'm not sure how that works if it refers to the same repo as an active one.

It is offered in the USB creator.

When opening AB settings it probes the backup destination for some reason (spins my destination disks up if they were spun down) so if the destination is on an unavailable remote it's not surprising it hangs.

Yeah, use official or LSIO, AIO is really poorly suited for use on Unraid.

This thing causes massive network spikes every time it refreshes even when nothing has changed And on my main system manages the incredible feat of freezing not only the browser (chrome) for about 3 seconds each time it does so (see below, I'm scroling continuously, the stops are due to it) but the entire OS (win11), can't switch windows and the mouse gets sluggish whenever the dashboard page is open. Also why a tiny font instead of the same as everything in the UI? Enregistrement 2026-03-14 205030.mp4

The "enable tailscale" toggle is a hack that won't work with all containers, depends how they're made. Should use a sidecar container/TSDProxy.

Maybe post your notification settings

Are the notifications actually showing in the unraid ui?

Use the group feature in the plugin, click on them in AB settings

A file changed while the backup ran. Immich usually doesn't run alone so make sure to put it into a group along with all its companion containers. / anything else that might touch the folder.

Then click "show advanced options" and set it to ignore errors.

You have excluded the only folder that would have been backed up, so of course there's nothing left. If you don't want to backup that container set Skip to Yes.

Looks like you're trying to update an A record with an ipv6 address... I've don't know anything about v6, see container doc/issues?

The good thing with Unraid is for stuff like this you can just reboot and it'll be all cleaned up :D

Hardware too old to support VT-d passthrough

You just posted a massive wall of text that's completely off-topic given OP's subsequent clarification.

I don't know how your stuff got messed up but I don't think it's from this plugin, everything fine here.

Need to check the backup settings for that container that it backs up the paths you want. Also besides the main "file storage/sync" function of Nextcloud the apps will often NOT have their data in folders but stored in the database. So it's crucial to back that up too.

Where is the compose file located? Why should it be executable?

Looks like you haven't set up / formatted the storage yet so of course there's nothing to store that onto.

path1 is by default set to read-only, if that is OK i.e. you're only going to modify the right side/path2 then just ignore that warning. If you want write access to both edit the access mode in the template.

Hopefully with a good warranty, check and use it if you can. Helium sensors are known to be prone to false warnings but the bad sectors are not great.

Just shows everything storage. That used to be the only/main thing before Docker/VM etc was added. Ranting's pretty pointless, and most people are happy with it. If you wanted to give useful input maybe mention what you'd expect to see there? Intuitive/unintuitive is subjective, likely what you would find intuitive would be unintuitive for others, nothing can ever fully satisfy everyone.

They're just showing the available keyboard shortcuts, Ctrl/Cmd-K opens a search box and ? opens the "help and support" pane you can also reach in the left drawer... Obviously not anything essential so pretty normal to have them muted in a corner.

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#using-mover-to-empty-an-array-disk