-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by witten
-
-
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.
- 1
- 1
-
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?
-
3 hours ago, darkside40 said:
Was something recently changed in this Image?
Using it for over a year but in the past couple of weeks it seems that the cron runs quite random. Normally it should rum at 18:00 every day, but now it sometimes simply runs the script when the server comes from sleep etc.
Anyone also experienced this?
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.
-
On 2/25/2023 at 2:20 PM, kilonde said:
I am confused how to update my repo path in the configuration to avoid this error:
Remote repository paths without ssh:// syntax are deprecated.
My repo configuration is like this:
[email protected]:/mnt/disk/borg_backup/repo
and the ssh command looks like this:
ssh_command: ssh -i /root/.ssh/Pi
"[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"
On 2/25/2023 at 2:20 PM, kilonde said:Also, is it advised to keep the same version of borg on client and the server?
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.
- 1
-
On 4/20/2022 at 4:10 AM, donbruno said:
another question, where I can find the log files for borgmatic?
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
[Support] borgmatic
in Docker Containers
Posted
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