Blasman Posted August 27 Share Posted August 27 If anyone is interested in any nifty ZFS features for this plugin, I created this user script that takes snapshots while the dockers are stopped by the plugin. In addition, in post-run, it can do replications as well as use the created snapshot as a source to create tarfiles and/or rsync'd folders of your appdata. This allows all your dockers to have less than a second of downtime. 1 Quote Link to comment
squabbi Posted August 28 Share Posted August 28 I tried to do a quick search of the thread, but would, or is there an option to have the archive a max file size, or be able to split it into part archives? I wanted to upload the backups via rclone to Box, but Box has a per-file size limit... I can use a different provider, but I think it would be a handy feature nonetheless! Quote Link to comment
JackTovey Posted September 2 Share Posted September 2 Howdy there folks, I was wondering if you can add in support for use alongside the docker-compose plugin? I have setup health checks and proper dependencies between services in my stack and sadly your plugin does not support this behaviour. Quote Link to comment
nerbonne Posted September 2 Share Posted September 2 @KluthR just wondering if we can add support to split archives. My plex container backup is hundreds of gb, even compressed, and I back it up remotely via rsync after the monthly backup runs. Multiple smaller files would be more ideal in case there is a network interruption. Quote Link to comment
KluthR Posted September 2 Author Share Posted September 2 I dont know yet. but - correct me if iam wrong - rsync can also continue copy on partial transferred files as well in case of am error..? Quote Link to comment
Julian-LCTT Posted September 6 Share Posted September 6 hello, i have a very annoying issue. i run this plugin to backup everything. only i have a problem when executing a docker backup that runs nextcloud. as soon as the backup instance makes a backup, no matter how (so either disabling the docker first and then making a backup or bypassing disabling the docker) makes no difference. i also see no errors in the log. so as soon as it has finished the backup my entire nextcloud docker does not work anymore, it cannot be started at all. the only solutions are then either apply an update to the nextcloud docker if it is there or perform a complete unraid server restart. only then will the nextcloud docker work again. i only have this problem with the nextcloud docker. anyone have any idea? Quote Link to comment
KluthR Posted September 6 Author Share Posted September 6 No idea. Share a debug log please. Quote Link to comment
Julian-LCTT Posted September 6 Share Posted September 6 I cant, i removed the plugin because its an critical application to do this again. Is there an way to get those logs when removed the plugin? Quote Link to comment
KluthR Posted September 6 Author Share Posted September 6 Take a look at /tmp/appdata.backup/ Quote Link to comment
Julian-LCTT Posted September 6 Share Posted September 6 Nope cant find, I can find an old backup.log [23.08.2024 03:00:01][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!! [23.08.2024 03:00:01][ℹ️][Main] Backing up from: /mnt/user/appdata, /mnt/cache/appdata [23.08.2024 03:00:01][ℹ️][Main] Backing up to: /mnt/user/BackupFTP/Appdata/ab_20240823_030001 [23.08.2024 03:00:01][ℹ️][Main] Selected containers: CloudNode-NC01, LCTT-Database, LCTT-NGINX-PROXY [23.08.2024 03:00:01][ℹ️][Main] Saving container XML files... [23.08.2024 03:00:04][ℹ️][Main] Method: Stop/Backup/Start [23.08.2024 03:00:04][ℹ️][LCTT-NGINX-PROXY] Stopping LCTT-NGINX-PROXY... done! (took 4 seconds) [23.08.2024 03:00:08][ℹ️][LCTT-NGINX-PROXY] Backing up EXTERNAL volumes, because its enabled! [23.08.2024 03:00:08][ℹ️][LCTT-NGINX-PROXY] Calculated volumes to back up: /mnt/user/appdata/LCTT-NGINX-PROXY/log, /mnt/user/appdata/LCTT-NGINX-PROXY/data, /mnt/user/appdata/LCTT-NGINX-PROXY/letsencrypt [23.08.2024 03:00:08][ℹ️][LCTT-NGINX-PROXY] Backing up LCTT-NGINX-PROXY... [23.08.2024 03:00:09][ℹ️][LCTT-NGINX-PROXY] Backup created without issues [23.08.2024 03:00:09][⚠️][LCTT-NGINX-PROXY] Skipping verification for this container because its not wanted! [23.08.2024 03:00:09][ℹ️][LCTT-NGINX-PROXY] Starting LCTT-NGINX-PROXY... (try #1) done! [23.08.2024 03:00:11][ℹ️][LCTT-Database] Stopping LCTT-Database... done! (took 4 seconds) [23.08.2024 03:00:15][ℹ️][LCTT-Database] Backing up EXTERNAL volumes, because its enabled! [23.08.2024 03:00:15][ℹ️][LCTT-Database] Calculated volumes to back up: /mnt/user/appdata/mariadb [23.08.2024 03:00:15][ℹ️][LCTT-Database] Backing up LCTT-Database... [23.08.2024 03:00:28][ℹ️][LCTT-Database] Backup created without issues [23.08.2024 03:00:28][⚠️][LCTT-Database] Skipping verification for this container because its not wanted! [23.08.2024 03:00:28][ℹ️][LCTT-Database] Starting LCTT-Database... (try #1) done! [23.08.2024 03:00:31][ℹ️][CloudNode-NC01] Stopping CloudNode-NC01... done! (took 1 seconds) [23.08.2024 03:00:32][ℹ️][CloudNode-NC01] Backing up EXTERNAL volumes, because its enabled! [23.08.2024 03:00:32][ℹ️][CloudNode-NC01] Calculated volumes to back up: /mnt/user/appdata/CloudNode-NC01/data, /mnt/user/appdata/CloudNode-NC01/html, /mnt/user/appdata/CloudNode-NC01/apps, /mnt/user/appdata/CloudNode-NC01/config [23.08.2024 03:00:32][ℹ️][CloudNode-NC01] Backing up CloudNode-NC01... [23.08.2024 03:02:27][ℹ️][CloudNode-NC01] Backup created without issues [23.08.2024 03:02:27][⚠️][CloudNode-NC01] Skipping verification for this container because its not wanted! [23.08.2024 03:02:27][ℹ️][CloudNode-NC01] Starting CloudNode-NC01... (try #1) done! [23.08.2024 03:02:30][ℹ️][Main] Backing up the flash drive. [23.08.2024 03:02:59][ℹ️][Main] Flash backup created! [23.08.2024 03:02:59][ℹ️][Main] Copying the flash backup to '/mnt/user/BackupFTP/USB/' as well... [23.08.2024 03:03:13][ℹ️][Main] Checking retention... [23.08.2024 03:03:13][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day [23.08.2024 03:03:13][ℹ️][Main] ❤️ Quote Link to comment
Julian-LCTT Posted September 6 Share Posted September 6 (edited) I retried the backup and now it works fine, im gonna run it again to see if it now works. Edited September 6 by Julian-LCTT Quote Link to comment
pfdt Posted September 8 Share Posted September 8 (edited) Hello, I always have the same problem with my backups and cannot find a solution : my containers which depends on another container (a vpn network) failed to restart. I have these containers : PIA : my vpn app (with a starting delay of 20 seconds) qbittorrent : depends on the network of PIA (--net=container:pia) sabnzbd : depends on the network of PIA (--net=container:pia) In the plugin, these 3 containers are grouped in a dedicated folder : During backup : 🟢 All the containers stop well (in the reverse order) 🟢 All the containers backup and update well 🟢 PIA restart successfully and then wait for 20 seconds 🔴 qbittorrent and sabnzbd failed to restart, even after 3 tries The stop and restart orders seem OK but I don't understand the problem. PIA only needs 5s to start, after 20s it is fully working. I have tried with a higher starting delay after PIA but the problem is the same. I've find discussions with this problem in the forum but the solution was to create a group which is already done here. Here is an extract of the log : Please can you tell me what I am doing wrong ? Edited September 8 by pfdt Quote Link to comment
KluthR Posted September 8 Author Share Posted September 8 The error says it all „No such container“ I dont know why docker thinks its not there. I would need to vuilt in more debug infos here. But for now: please do a „docker ps -a“ when this happens. Quote Link to comment
Kilrah Posted September 8 Share Posted September 8 Have you set AB to update your containers, and would by any chance one of them have been updated in parts of the logs you truncated? Quote Link to comment
peterhocking Posted September 9 Share Posted September 9 I'm using the plugin to backup the 2 Docker containers I have installed. However, when the backup runs, it also back up .bak & .xml files from Docker containers that I've tried & uninstalled. When I look in the appdata folder I can't see these files. I assume they are the configuration files from when I had these containers installed. Is there any way I can get rid of them? Quote Link to comment
Kilrah Posted September 9 Share Posted September 9 Apps->Previous Apps and remove those you don't care about anymore. The bak ones would be old and are in /boot/config/plugins/dockerMan/templates-user Quote Link to comment
KluthR Posted September 9 Author Share Posted September 9 Some thoughts for the ZFS capable version In order to do things for ZFS capable volumes a bit smarter, the script needs to know if appdata is lying on a ZFS file system. I would offer a multi selectable dropdown with all unraid shares which the user can (de-)select. This idea brought me to the idea to generally replace the "appdata sources" textfield with a select field with fixes values (coming from the share settings). Would there be any reason to not use those pre-defined share paths? With this I could simply ask Unraid which FS type is used there. If ZFS, the plugin will use snapshots to create backups. If not, the traditional way is being used. Any thoughts? A few more words to my snapshot idea: The plugin would stop all containers (in order), create the snapshot, start all containers (in reverse order) and then starting the backup from the snapshot path and finally delete the snapshot. Quote Link to comment
pfdt Posted September 9 Share Posted September 9 On 9/8/2024 at 4:40 PM, KluthR said: The error says it all „No such container“ I dont know why docker thinks its not there. I would need to vuilt in more debug infos here. But for now: please do a „docker ps -a“ when this happens. Hello KluthR, ok I will do a docker ps -a next time. But it it helps : when it happened I can easily start the stopped containers in the Unraid UI. 20 hours ago, Kilrah said: Have you set AB to update your containers, and would by any chance one of them have been updated in parts of the logs you truncated? Thank you Kilrah, I've checked and yes : PIA have been updated the last times. I've made a couple of test and discovered that no : the problem doesn't occur every time. My 2 manual backups of the day finished without any problem. So the update of the vpn container is a good lead... Quote Link to comment
JonathanM Posted September 9 Share Posted September 9 3 minutes ago, pfdt said: when it happened I can easily start the stopped containers in the Unraid UI. Probably because the Unraid container page tracks them by name, which doesn't change when updated. The actual container ID does change. Run the docker ps -a before and after an update, and compare the first value in each line. You can do docker ps -a>>/boot/list.txt which will write list.txt to the root of the flash drive if you want a more permanent copy, plus you can cut n paste to here easier. Quote Link to comment
KluthR Posted September 9 Author Share Posted September 9 2 hours ago, JonathanM said: Run the docker ps -a before and after an update, and compare the first value in each line. You can do Yea, that makes sense 2 hours ago, JonathanM said: Probably because the Unraid container page tracks them by name, which doesn't change The same way I do. I also use the exact same method to start the containers. Quote Link to comment
pfdt Posted September 9 Share Posted September 9 3 hours ago, JonathanM said: Run the docker ps -a before and after an update, and compare the first value in each line. You can do docker ps -a>>/boot/list.txt which will write list.txt to the root of the flash drive if you want a more permanent copy, plus you can cut n paste to here easier. Ok done, I let you know when it happens again Quote Link to comment
Kilrah Posted September 9 Share Posted September 9 4 hours ago, pfdt said: Thank you Kilrah, I've checked and yes : PIA have been updated the last times. That'll be it, when it gets updated it gets deleted and recreated, its ID changes, so now the container the others reference for their network is gone. Best not to do autoupdates when there are dependencies like this. Quote Link to comment
Killermaze Posted Thursday at 11:10 AM Share Posted Thursday at 11:10 AM I'm generating this error message and hoping if someone can help me regarding the plex server. It was working for one week and then this error message started popping up only on the plex service. After it generating that error message, Plex never restarts and I have to manually start the service again in docker. Thank you [12.09.2024 03:30:05][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!! [12.09.2024 03:30:06][ℹ️][Main] Backing up from: /mnt/user/appdata, /mnt/cache/appdata [12.09.2024 03:30:06][ℹ️][Main] Backing up to: /mnt/remotes/192.168.4.65_Unraid_Configuration_Backup/Unraid_Backup/AppData_backup/ab_20240912_033006 [12.09.2024 03:30:06][ℹ️][Main] Selected containers: CloudflaredTunnel, binhex-krusader, binhex-overseerr, binhex-plexpass, binhex-prowlarr, binhex-radarr, binhex-sabnzbd, binhex-sonarr [12.09.2024 03:30:06][ℹ️][Main] Saving container XML files... [12.09.2024 03:30:06][ℹ️][Main] Method: Stop/Backup/Start [12.09.2024 03:30:06][ℹ️][binhex-krusader] Stopping binhex-krusader... done! (took 17 seconds) [12.09.2024 03:30:23][ℹ️][binhex-krusader] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:30:23][ℹ️][binhex-krusader] Calculated volumes to back up: /mnt/user/appdata/binhex-krusader [12.09.2024 03:30:23][ℹ️][binhex-krusader] Backing up binhex-krusader... [12.09.2024 03:30:30][ℹ️][binhex-krusader] Backup created without issues [12.09.2024 03:30:30][ℹ️][binhex-krusader] Verifying backup... [12.09.2024 03:30:48][ℹ️][binhex-krusader] Starting binhex-krusader... (try #1) done! [12.09.2024 03:31:01][ℹ️][CloudflaredTunnel] Stopping CloudflaredTunnel... done! (took 9 seconds) [12.09.2024 03:31:10][ℹ️][CloudflaredTunnel] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:31:10][⚠️][CloudflaredTunnel] CloudflaredTunnel does not have any volume to back up! Skipping. Please consider ignoring this container. [12.09.2024 03:31:10][ℹ️][CloudflaredTunnel] Starting CloudflaredTunnel... (try #1) done! [12.09.2024 03:31:22][ℹ️][binhex-sonarr] Stopping binhex-sonarr... done! (took 9 seconds) [12.09.2024 03:31:31][ℹ️][binhex-sonarr] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:31:31][ℹ️][binhex-sonarr] Calculated volumes to back up: /mnt/user/appdata/data, /mnt/user/appdata/binhex-sonarr [12.09.2024 03:31:31][ℹ️][binhex-sonarr] Backing up binhex-sonarr... [12.09.2024 03:31:39][ℹ️][binhex-sonarr] Backup created without issues [12.09.2024 03:31:39][ℹ️][binhex-sonarr] Verifying backup... [12.09.2024 03:31:41][ℹ️][binhex-sonarr] Starting binhex-sonarr... (try #1) done! [12.09.2024 03:31:52][ℹ️][binhex-radarr] Stopping binhex-radarr... done! (took 4 seconds) [12.09.2024 03:31:56][ℹ️][binhex-radarr] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:31:56][ℹ️][binhex-radarr] Calculated volumes to back up: /mnt/user/appdata/binhex-radarr [12.09.2024 03:31:56][ℹ️][binhex-radarr] Backing up binhex-radarr... [12.09.2024 03:32:24][ℹ️][binhex-radarr] Backup created without issues [12.09.2024 03:32:24][ℹ️][binhex-radarr] Verifying backup... [12.09.2024 03:32:29][ℹ️][binhex-radarr] Starting binhex-radarr... (try #1) done! [12.09.2024 03:32:39][ℹ️][binhex-sabnzbd] Stopping binhex-sabnzbd... done! (took 10 seconds) [12.09.2024 03:32:49][ℹ️][binhex-sabnzbd] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:32:49][ℹ️][binhex-sabnzbd] Calculated volumes to back up: /mnt/user/appdata/binhex-sabnzbd [12.09.2024 03:32:49][ℹ️][binhex-sabnzbd] Backing up binhex-sabnzbd... [12.09.2024 03:32:51][ℹ️][binhex-sabnzbd] Backup created without issues [12.09.2024 03:32:51][ℹ️][binhex-sabnzbd] Verifying backup... [12.09.2024 03:32:51][ℹ️][binhex-sabnzbd] Starting binhex-sabnzbd... (try #1) done! [12.09.2024 03:33:09][ℹ️][binhex-prowlarr] Stopping binhex-prowlarr... done! (took 10 seconds) [12.09.2024 03:33:19][ℹ️][binhex-prowlarr] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:33:19][ℹ️][binhex-prowlarr] Calculated volumes to back up: /mnt/user/appdata/binhex-prowlarr [12.09.2024 03:33:19][ℹ️][binhex-prowlarr] Backing up binhex-prowlarr... [12.09.2024 03:33:20][ℹ️][binhex-prowlarr] Backup created without issues [12.09.2024 03:33:20][ℹ️][binhex-prowlarr] Verifying backup... [12.09.2024 03:33:20][ℹ️][binhex-prowlarr] Starting binhex-prowlarr... (try #1) done! [12.09.2024 03:33:32][ℹ️][binhex-overseerr] Stopping binhex-overseerr... done! (took 2 seconds) [12.09.2024 03:33:34][ℹ️][binhex-overseerr] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:33:34][ℹ️][binhex-overseerr] Calculated volumes to back up: /mnt/user/appdata/binhex-overseerr [12.09.2024 03:33:34][ℹ️][binhex-overseerr] Backing up binhex-overseerr... [12.09.2024 03:33:35][ℹ️][binhex-overseerr] Backup created without issues [12.09.2024 03:33:35][ℹ️][binhex-overseerr] Verifying backup... [12.09.2024 03:33:35][ℹ️][binhex-overseerr] Starting binhex-overseerr... (try #1) done! [12.09.2024 03:33:38][ℹ️][binhex-plexpass] Stopping binhex-plexpass... done! (took 3 seconds) [12.09.2024 03:33:41][ℹ️][binhex-plexpass] Should NOT backup external volumes, sanitizing them... [12.09.2024 03:33:41][ℹ️][binhex-plexpass] Calculated volumes to back up: /mnt/user/appdata/binhex-plexpass [12.09.2024 03:33:41][ℹ️][binhex-plexpass] Backing up binhex-plexpass... [12.09.2024 03:40:26][ℹ️][binhex-plexpass] Backup created without issues [12.09.2024 03:40:26][ℹ️][binhex-plexpass] Verifying backup... [12.09.2024 03:43:13][❌][binhex-plexpass] tar verification failed! Tar said: tar: Removing leading `/' from member names; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudAccountV2.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudAccountV2.dat: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/Privacy.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/UpdateChannels.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/Flags.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudUsersF.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudAccessV2.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudAccessV2.dat: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudUsersV2.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Cache/CloudUsersSubscriptionsV2.dat: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Crash Reports/.RateLimit.json: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Crash Reports/.RateLimit.json: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Plug-in Support/Data/com.plexapp.system/HTTPCookies: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Plug-in Support/Data/com.plexapp.system/Dict: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Plug-in Support/Data/com.plexapp.system/Dict: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Plug-in Support/Data/com.plexapp.agents.imdb/HTTPCookies: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.5: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.5: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.4: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.4: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.3: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.3: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.2: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.2: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.1: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log.1: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.system.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.5: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.5: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.4: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.4: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.3: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.3: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.2: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.2: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.1: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log.1: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.imdb.log: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.5.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.5.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.4.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.4.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.3.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.3.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.2.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.2.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.1.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.1.log: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Tuner Service.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.5.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.5.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.4.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.4.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.3.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.3.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.2.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.2.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.1.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.1.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Media Server.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.5.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.5.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.4.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.4.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.3.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.3.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.2.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.2.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.1.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.1.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.log: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Logs/Plex Crash Uploader.log: Size differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/.LocalAdminToken: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/.LocalAdminToken: Contents differ; mnt/user/appdata/binhex-plexpass/Plex Media Server/Setup Plex.html: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Preferences.xml: Mod time differs; mnt/user/appdata/binhex-plexpass/Plex Media Server/Preferences.xml: Contents differ [12.09.2024 03:43:53][ℹ️][binhex-plexpass] Starting binhex-plexpass... (try #1) Hmm - container is already started! [12.09.2024 03:43:55][ℹ️][Main] Backing up the flash drive. [12.09.2024 03:44:24][ℹ️][Main] Flash backup created! [12.09.2024 03:44:24][ℹ️][Main] Copying the flash backup to '/mnt/remotes/192.168.4.65_Unraid_Configuration_Backup/Unraid_Backup/Unraid_Flash_Drive_Backup/' as well... [12.09.2024 03:44:29][ℹ️][Main] VM meta backup enabled! Backing up... [12.09.2024 03:44:29][ℹ️][Main] Done! [12.09.2024 03:44:29][⚠️][Main] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum. [12.09.2024 03:44:29][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day Quote Link to comment
KluthR Posted Thursday at 02:54 PM Author Share Posted Thursday at 02:54 PM (edited) On 9/9/2024 at 9:50 AM, KluthR said: Some thoughts for the ZFS capable version I discarded the idea of the "dropdown". I built support for zfs detection by checking all volumes in question against their used fs type. If all are zfs, the plugin forces the zfs method. If at least one is non-zfs, the plugin uses the confugured method. The detection needs all volumes to be set to the zfs pool. That means, that the default paths (/mnt/user/appdata) are not working, because they are overlays and could target in different file systems (as I understood). So the share needs to be set to an exclusive zfs pool device for now ("Exclusive access: Yes" or let the docker volume point to a diskX path). Thoughts? Maybe I also misunderstood some things - I dont use the Array feature in any way, since Unraid supports Pool-devices. I also await the Array-less feature of Unraid to get rid of my dummy Array device Edited Thursday at 02:56 PM by KluthR Quote Link to comment
Kudagra Posted Friday at 02:47 AM Share Posted Friday at 02:47 AM If I installed the new plugin but never set a "Backup destination", will my app data still backup? If so, where? I can't find anything noting a default backup location. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.