laur

> ~/.ssh # ls -al You don't have any keys in ~/.ssh/ Either generate them, or mount /boot/config/ssh/ or /root/.ssh (ie wherever on host you have the keys) to container's /root/.ssh Note in the parent post example you can see the example expects key to be found at ~/.ssh/id_rsa: storage: ssh_command: ssh -i /root/.ssh/id_rsa <-- keyfile for ssh Yet your dir listing above shows there's no key to be found.

> This docker can be used with the Unraid rclone plugin if you wish to mirror your repo to a supported cloud service. Note this goes against borg recommendation. > Files cache set to use "mtime,size" - Very important as unRAID does not have persistent inode values That's a great point! Will amend my setup. Why did you change the default 'ctime' to 'mtime' though?

find -L "/root/.ssh" \( -type f -o -type d \) -exec chmod 'u=rwX,g=,o=' -- '{}' \+ (this will guarantee the dirs will get the executable bit set)

Borgmatic supports hooks, so you could likely use those to interact with docker. I wrote alternative solution to borgmatic with less dependencies that addresses this. Although borgmatic absolutely is a nice tool to work with.

So I suppose following files/dirs should be backed up (someone please correct me if this looks wrong): - /boot (you likely want to back /boot up in its entirety anyway) - /var/lib/docker/unraid-autostart - /var/local/emhttp/plugins/dynamix.docker.manager/docker.json actually no need for this - /boot/config/plugins/dockerMan/userprefs.cfg also reflects which containers are currently deployed; still docker.json explicitly defines which template is used for given container, so you might want to include it anyway.

Example crontab entry for backing up your appdata, libvirt, quemu & /boot, while excluding some directories (note this backup doesn't involve database at all): 13 05 * * * /backup.sh -p unraid -E '/appdata/EmbyServer/transcoding-temp,/appdata/docker-registry/registry,/appdata/gitea,/appdata/borg-mysql-backup/.borg,/appdata/mariadb/databases,/appdata/redis' -H 2rd63c32-a988-478a-b86b-6fdef8e381ab /appdata /libvirt /qemu /usb-boot Another example backing up Gitea appdata & database, while switching off its container for the duration of backup (note /appdata/gitea dir was excluded from the other backup job above): 33 05 * * * /backup.sh -p gitea-downtime -d gitea -c Gitea -H bee237e8-3b1a-98a2-9ca5-d752er5e42a /appdata/gitea ^ ^ ^ ^ ^ borg archive prefix db to backup container to turn off healthcheck ID directory to include More detailed examples in Readme.

Application: borg-mysql-backup Docker Hub: https://hub.docker.com/r/layr/borg-mysql-backup Github: https://github.com/laur89/docker-borg-mysql-backup Templates' repo: https://github.com/laur89/unraid-templates Usage/configuration documentation in github Readme. Note it's advisable to track the borg1 tag instead of latest; when borg releases new major version (v2), it's likely to conflict with repositories created with borg v1. Why use this image? It's best suited for backup needs where mysql/mariadb databases and other files-directories need to be backed up. It also offers possibility to shut down specific docker containers for the duration of the backup to ensure data parity. Eg with Gitea, you might want to back up both its /appdata directory and database, and switch off Gitea container for the backup. Additionally, as it uses borg as the underlying backup tool, you can choose between number of reasonably priced offsite storage options out there supporting borg, rsync.net & borgbase being the main ones. Before choosing this solution, please also consider other similar options out there, some of which are listed at the bottom of the Readme. There's also this dockerised Borgmatic template:

Edit: so this is what I've pieced together so far: Docker templates: /boot/config/plugins/dockerMan/templates-user/ container order: /boot/config/plugins/dockerMan/userprefs.cfg containers currently in use/deployed: /var/local/emhttp/plugins/dynamix.docker.manager/docker.json (actually this is also shown by userprefs.cfg) auto-startup with startup delay: /var/lib/docker/unraid-autostart Pre-edit post follows: The docker templates are located in /boot/config/plugins/dockerMan/templates-user/ and container data in /mnt/cache/appdata/; what about the current state of containers used, ie the composition - which containers are actually in use? This question asks something similar, but doesn't quite answer the question. Grepping suggests this file reflects the current state of play: /var/local/emhttp/plugins/dynamix.docker.manager/docker.json So is it a valid file to back up (and later use on recovered system)? Looks like the entire /var/local/emhttp/plugins/dynamix.docker.manager/ directory could be backed up, as it also contains the images/ directory. Container order appears to be in /boot/config/plugins/dockerMan/userprefs.cfg Where would the container startup delay be stored at though, as the files above define no container startup info we set in the UI.