There is. But Iam currently busy with a refactoring. I dont touch the „old“ code except for urgent changes. Please wait a bit until Iam ready. What do you want to change?

On 1/12/2023 at 4:19 PM, trurl said:

Do you perhaps have docker.img in appdata share instead of system share as is the usual setting?

 

Attach diagnostics to your NEXT post in this thread.

You were exactly right.! Thank you very much.

Docker.img was in the same folder than then dockers themselves. Moving away the image did the trick.

I moved it ant it worked flawlessly.

 

Docker vDisk location:

/mnt/disk1/system/docker/docker.img

Default appdata storage location:

/mnt/user/appdata/

52 minutes ago, KluthR said:

There is. But Iam currently busy with a refactoring. I dont touch the „old“ code except for urgent changes. Please wait a bit until Iam ready. What do you want to change?

I can wait. Mostly wanted to work on parallelization/docker restart mechanics, like what's been discussed in the thread.

I'm having issue where a few containers won't restart after the backup has finished. Can anyone assist please?



 

Jan 15 04:14:46 SERVER CA Backup/Restore: done
Jan 15 04:14:46 SERVER CA Backup/Restore: Starting binhex-plexpass... (try #1) 
Jan 15 04:14:46 SERVER CA Backup/Restore: done!
Jan 15 04:14:48 SERVER CA Backup/Restore: Starting overseerr... (try #1) 
Jan 15 04:14:48 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:14:53 SERVER CA Backup/Restore: Starting overseerr... (try #2) 
Jan 15 04:14:53 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:14:58 SERVER CA Backup/Restore: Starting overseerr... (try #3) 
Jan 15 04:14:58 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:14:58 SERVER CA Backup/Restore: Container did not started after multiple tries, skipping.
Jan 15 04:14:58 SERVER CA Backup/Restore: Waiting 10 seconds before carrying on
Jan 15 04:15:08 SERVER CA Backup/Restore: Starting tautulli... (try #1) 
Jan 15 04:15:08 SERVER kernel: docker0: port 1(veth6fe6c7c) entered blocking state
Jan 15 04:15:08 SERVER kernel: docker0: port 1(veth6fe6c7c) entered disabled state
Jan 15 04:15:08 SERVER kernel: device veth6fe6c7c entered promiscuous mode
Jan 15 04:15:08 SERVER kernel: docker0: port 1(veth6fe6c7c) entered blocking state
Jan 15 04:15:08 SERVER kernel: docker0: port 1(veth6fe6c7c) entered forwarding state
Jan 15 04:15:08 SERVER kernel: docker0: port 1(veth6fe6c7c) entered disabled state
Jan 15 04:15:09 SERVER kernel: eth0: renamed from veth75be4c7
Jan 15 04:15:09 SERVER kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6fe6c7c: link becomes ready
Jan 15 04:15:09 SERVER kernel: docker0: port 1(veth6fe6c7c) entered blocking state
Jan 15 04:15:09 SERVER kernel: docker0: port 1(veth6fe6c7c) entered forwarding state
Jan 15 04:15:09 SERVER CA Backup/Restore: done!
Jan 15 04:15:09 SERVER CA Backup/Restore: Waiting 10 seconds before carrying on
Jan 15 04:15:10 SERVER avahi-daemon[16027]: Joining mDNS multicast group on interface veth6fe6c7c.IPv6 with address fe80::101c:40ff:fec4:fe82.
Jan 15 04:15:10 SERVER avahi-daemon[16027]: New relevant interface veth6fe6c7c.IPv6 for mDNS.
Jan 15 04:15:10 SERVER avahi-daemon[16027]: Registering new address record for fe80::101c:40ff:fec4:fe82 on veth6fe6c7c.*.
Jan 15 04:15:19 SERVER CA Backup/Restore: Starting prowlarr... (try #1) 
Jan 15 04:15:19 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:24 SERVER CA Backup/Restore: Starting prowlarr... (try #2) 
Jan 15 04:15:24 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:29 SERVER CA Backup/Restore: Starting prowlarr... (try #3) 
Jan 15 04:15:29 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:29 SERVER CA Backup/Restore: Container did not started after multiple tries, skipping.
Jan 15 04:15:29 SERVER CA Backup/Restore: Waiting 10 seconds before carrying on
Jan 15 04:15:39 SERVER CA Backup/Restore: Starting radarr... (try #1) 
Jan 15 04:15:39 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:44 SERVER CA Backup/Restore: Starting radarr... (try #2) 
Jan 15 04:15:44 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:49 SERVER CA Backup/Restore: Starting radarr... (try #3) 
Jan 15 04:15:50 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:50 SERVER CA Backup/Restore: Container did not started after multiple tries, skipping.
Jan 15 04:15:52 SERVER CA Backup/Restore: Starting sonarr... (try #1) 
Jan 15 04:15:52 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:15:57 SERVER CA Backup/Restore: Starting sonarr... (try #2) 
Jan 15 04:15:57 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:16:02 SERVER CA Backup/Restore: Starting sonarr... (try #3) 
Jan 15 04:16:02 SERVER CA Backup/Restore: Error while starting container! - Code: Image can not be deleted, in use by other container(s)
Jan 15 04:16:02 SERVER CA Backup/Restore: Container did not started after multiple tries, skipping.
Jan 15 04:16:04 SERVER CA Backup/Restore: Starting homeassistant... (try #1) 
Jan 15 04:16:04 SERVER CA Backup/Restore: done!
Jan 15 04:16:04 SERVER CA Backup/Restore: Waiting 10 seconds before carrying on

 

20 minutes ago, mushtafa said:

few containers won't restart

attach diagnostics to your NEXT post in this thread

server-diagnostics-20230116-2142.zip

Been using this plugin for years, and more than once it's saved my ass. Thank you for taking this on and keeping such a great piece of work alive and progressing.

 

One question / suggestion - I have "create separate archives" set to Yes - but the plugin still stops all dockers at the start, then starts them at the end. Could it be possible to shut down a docker only when that docker appdata will be backed up instead? In other words, I don't think Plex needs to be closed if krusader is being backed up.. ?

 

Thank you!

32 minutes ago, tiwing said:

One question / suggestion - I have "create separate archives" set to Yes - but the plugin still stops all dockers at the start, then starts them at the end. Could it be possible to shut down a docker only when that docker appdata will be backed up instead? In other words, I don't think Plex needs to be closed if krusader is being backed up.. ?

Some dockers are dependent on others for many configurations

Thats one reason. The other is that the plugin has absolutely no clue which appdata folder belongs to what container (even if the naming is the same). Thats one thing I want to change in upcoming versions.

A bit busy but Iam not in hurry

Hi there! I have recently set up a second Unraid machine and would like to move some of my containers to the new machine. I found a thread on reddit that suggested that the best way to do this would be to use this plugin to create a backup, copy the back up over to the new server and then restore it.

 

The back up from the old server and restore on the new server worked flawlessly! But I don't see the containers in the Docker UI or under "previously apps" tab in community applications. I checked the appdata share via ssh and all of the folders do seem to be there.

 

Am I missing something? Did I misunderstand how this plugin or how the restore function works?

 

Thank you in advance!

30 minutes ago, SxC97 said:

Am I missing something? Did I misunderstand how this plugin or how the restore function works?

You would still need to install and configure the dockers on the new machine. The backup you moved will restore the data and app settings.

1 minute ago, wgstarks said:

You would still need to install and configure the dockers on the new machine. The backup you moved will restore the data and app settings.

Ah, I see. Thank you!

39 minutes ago, SxC97 said:

don't see the containers in the Docker UI or under "previously apps" tab

The docker templates that allow you to reinstall previous apps, and to work with installed apps in the webUI, are on the flash drive in config/plugins/dockerMan/templates-user

OK, how do I exclude more than one folder? I've got two for plex I want to exclude. If I past one folder in, it's there, but then how do I add a second?

2 minutes ago, Whaler_99 said:

how do I exclude more than one folder?

@KluthR, I have a suggestion based on the previous few posts.

 

Could you put a copy of the corresponding template xml from config/plugins/dockerMan/templates-user into the root of the archive? That way backups could be used for full disaster recovery without digging through the appropriate flash backup.

Thought exactly the same as I read the posts. Noted!

Can I setup multiple backup jobs for it at once?

22 hours ago, PlanetDyna said:

Can I setup multiple backup jobs for it at once?

What do you mean? It is intended to backup appdata, which is a single user share. It is not intended as a general purpose backup application.

 

I am getting an error when it backs up syslog which causes the whole job to fail.

 

[22.01.2023 08:43:43] Verifying Backup sonarr4K
[22.01.2023 08:43:43] Backing Up: swag
[22.01.2023 08:43:47] Verifying Backup swag
[22.01.2023 08:43:48] Backing Up: syslog-192.168.44.10.log
[22.01.2023 08:43:48] Verifying Backup syslog-192.168.44.10.log
syslog-192.168.44.10.log: Size differs
[22.01.2023 08:43:48] tar verify failed!
[22.01.2023 08:43:48] Backing Up: syslog-192.168.44.10.log.1
[22.01.2023 08:43:48] Backing Up: tailscale
[22.01.2023 08:43:48] Backing Up: tautulli

 

Syslog will update though during the backup process won't it?

If it helps, I have unpaid acting as a syslog server posting its own syslog to itself, that is so the syslog data is retained post reboot. Perhaps the logic is only expecting a single syslog file?

1 hour ago, planetwilson said:

Syslog will update though during the backup process won't it?

Seems so.

 

if you want to ignore that, set the appropriate setting.

On 1/19/2023 at 5:55 PM, trurl said:

Doesn't work at least on my system. I can excluded an entire selection, but that isn't what I want. I want to exclude my Plex cache and transcode folders only.

 

Just extend the path when filled in the textbox. You can use * as an wildcard afaik.

5 hours ago, KluthR said:

Seems so.

 

if you want to ignore that, set the appropriate setting.

Sorry which setting do you mean? Turn off verify completely?

Yes