KluthR

Thats maybe improvable because thats not what I want users to do. It should not be always necessary, only if some important nee containers were added (which should stop in order).

It dont crash. And neither Plex does. The plugin is just unable to srop PMS. There are few known issues from users and in all cases the mentioned „docker stop“ method is working. But not in your case. are you able to stop PMS yourself?

@DennisT The order displayed is the Start oder, not the stop order. Stop is the reverse of Start. And As I see the orders seems right. the reason for the rest being always on the end: they have no order because they were created after saving the plugin settings last time. In that case the unknown containers are sorted at the end of the start and stop list. I really dont know if thats a bug or a feature because I would adjust the order if needed. And I know my containers. So: All is working as intended so far. Hit Save one time and the Transmission would stop first. _Maybe_ it would be more clear to order for stop and reverse Start instead vice versa like now.

Just built yourself a bash script with a cp command and make use of the plugin custom scripts feature. It calls your script with arguments. One of them is the current backup path. and yes: renaming a backup folder will make it permanent

@mdoherty66 Looks odd. Whats the command?

Oh, sorry: To resolve it for you, please exclude the volume in tdarr which is commonly used with the other container.

Classic. Tdarr uses volume by plex or vice versa but one of it writes to it. I really need to add such detection….

Thanks! The next update is almost ready and more to come after that. Maybe incremental backups would be nice too? 😉

This is known and already fixed in future versions. Containers get their update eight after backup before starting again.

Both are good. Just two mappings which not valid anymore. Which loglevel is set? Could be that the notification level is at warning.

It does not create new shares. It even does not create the destination folder if not yet existing. How do you created „share_backup“?

Thats not supported you could copy it with a custom script

Issue is known yes but not fixed yet. This and the no archive option are still missing but on my todo! A future beta will have it. I try to finish it asap.

No one ever told me, that the beta is not installable via CA Apps 😂 - I fixed it, so everyone who wants to test the beta can now easily install it via CA Apps (give it one hour from now on).

Which Unraid version do you have? WHich plugin (exact name, there are 3 versions) and version do you have?

To be honest: The CSRF things are Unraid things. Yes, we have a few users having this issue but I dont know why. 99% of the users dont see this issue - including me. Which browser and which extensions are installed? Is a password manager involved maybe?

A new beta is out and I want as many users as possible to test it. It has the container grouping in it and many other changes. I think some bugs are in as well 🤣 The new beta offers you to copy the prod config to it, so you dont have to reconfigure anything EXCEPT FOR THE DESTINATION PATH!!!

Thats weird. /mnt/user/backups/appdata/ is writeable but the subfolder is no creatable. Nothing I could do, something is wrong there. Please try a mkdir via terminal and report if its working

Its done when its done but I will see if I can put that in the next beta as well.

Do you have a recent flash backup? If yes, restore it on a new usb drive and boot up. This should made it. if not, reinstall unraid (same old version) on a new usb drive, install the old backup plugin and restore. you could also reinstall with latest UnraidOS and restore the things by yourself (new plugin does not read old backup archives for restore). this is how I would proceed, if anyone has better ideas, please post.

The next plugin update is making progress! Ive implemented a "Skip backup?" option per container which allows you to skip backup but includes the container for stop/starts processes. The new grouping function is not done yet but it looks like this. Please note that a container can be assigned to one group only.

No need to run or again. Just hit the button from the log tab. It should send the latest debug log if you did not rebooted yet.

Please share a debug log from a failing run.

Thats the wrong thread but: Check your destination folder…

Yep, by copying the destination folder as-is. You have to create the dockers by yourself currently. But the templates are restored as well.