Solverz

My friend, read what the warnings say 😅. The syntax you are using in the config files is deprecated and may not work in future versions. Solution: read the borgmatic docs and use the new syntax.

grep for the borg process so you do not have to look through all the lines manually. ps -aux | grep borg

Borgbackup, backs up to a repo. You can choose what you want to be backed up to this repo. So what what do you need to use rsnapshot for that borgbackup is not doing already.

So you have two repos, each on a separate external hard drive? Got that. Not sure what you mean on the rest? What do you mean here?

Please just say what you exactly want to do without using prolonged sentences and fancy words. Your post is like a riddle that we'd need to break down to understand what you are talking about.

/mnt/borg makes sense in normal distros but for unraid, it is best to put it in /mnt/disks/borg

The compaction feature has been out since Borg 1.2+, so if you only now aware of this, I would definitely recommend reading through the borgmatic and borg documentation as quite a few new features and changes have been added which may trigger you to change your method using borgmatic. For example, the syntax you use to specify remote repos and the consistency checks scheduling.

No worries! Yeah healthchecks is my favourite out of the options definitely and bonus it can be self hosted ☺ Oh BTW, I correct the cron schedule expression syntax, there was an extra few spaces I noticed. So it should be like the below: 0 6 * * 3

0 1,13 * * * borgmatic prune create -v 1 --stats 2>&1 0 6 * * 3 borgmatic check -v 1 2>&1 Hope that helps!

FYI, if anyones backups are failing since the latest update to this container 2 days ago, please see below: The borgmatic binary is no longer at /usr/bin/borgmatic it is now in /usr/local/bin/borgmatic. Of course, this this will only affect you if you are specifiying the full path to the borgmatic binary in your cronjob. /usr/local/bin is actually and to no surpise in the PATH env so you do not need to actually specifiy the full path to borgmatic and you can instead just put write "borgmatic" and if this path ever changes in the future you should not be affected.

As I like to say, "it depends". There are advantages and disadvantages to both, for instance, UD devices can be removed and installed adhoc where a pool cannot and unraid will complain if it goes "missing" Pools allow you to have redundancy, UD devices do not from the gui (as far as I am aware, please correct me if otherwise) UD can mount network shares etc and not just local media, pools is for local media only. Etc etc etc, just way up the pros and cons and see what suits your situation and setup the best and use that. ☺

No problem! It was probably set to read only in the template by default so that the container can only read data from your mapped directory and not modify or delete it or its contents, security hardening.

The error says read only file system, so the file system you are restoring too is read only. Have you checked the directory permissions or the docker path mapping? Are these read only or read/write?

Does the "compose pull" button, just issue the command docker compose pull or is there some way for it to also issue docker compose build? For locally created images?

Personally, I use borg by itself to backup everything including docker containers. As long as you use borgmatics database backup tool for the containers that have a supported database, it should be fine. ☺