witten

I don't know how easy the following is to do with Unraid, but here's an example of this working: # mkdir -p /root/test/mnt # docker run -it --privileged --mount type=bind,source=/root/test,target=/test,bind-propagation=rshared --device /dev/fuse -v /root/repo:/repo b3vis/borgmatic bash f069c33ce2cc:/# borg mount /repo/repo.borg::test /test/mnt After that, the mounted archive show up within /test/mnt on the host. The main downside is you need to the run container as privileged. There might be a way to make this work with --add-cap instead, but that's beyond my Docker skills. More background here: https://stackoverflow.com/a/53632103

This may also work if you don't want to type the repository path (or you want to use a borgmatic repository label to select the respository): borgmatic break-lock The one thing to look out for when breaking a Borg lock is first make sure Borg isn't actively running! Because if it is then you'll be breaking the lock of a running process and potentially accessing the repository from multiple different processes at the same time. That's probably not what's going on here, but it's just something to look out for.

Those logs look pretty normal to me. 🤷‍♂️ Maybe increase your borgmatic verbosity in your crontab to get more details about what might be going on?

The docker-borgmatic image this is based on switched to supercronic a while back. But presumably if that introduced the changes you're seeing, you would've seen it well before now. You might consider filing a ticket describing your problem at: https://github.com/borgmatic-collective/docker-borgmatic

While Gaurhoth is correct that you can update your configuration to drop the deprecated "prefix" option with recent versions of borgmatic, the fact that "prefix" started breaking as described above was actually a bug. It has been fixed however in borgmatic 1.7.12.

"[email protected]:/mnt/disk/borg_backup/repo" would be rewritten as "ssh://[email protected]/mnt/disk/borg_backup/repo". Note both the "ssh://" and the removed ":" after the IP. Newer versions of borgmatic will show you this as part of the deprecation warning: test.yaml: Remote repository paths without ssh:// syntax are deprecated. Interpreting "[email protected]:/mnt/disk/borg_backup/repo" as "ssh://[email protected]/mnt/disk/borg_backup/repo" It doesn't have to be exactly the same, but it's good to stay within the same major version if you can. (E.g. 1.x and 1.x.) There are some exceptions to that, like there were some major changes in Borg 1.2.

The documentation on that is here! https://torsion.org/borgmatic/docs/how-to/inspect-your-backups/#logging In general, if anyone has an issue that appears to be borgmatic-specific rather than Unraid-specific, you are welcome to file it in borgmatic's issue tracker: https://torsion.org/borgmatic/#issues