@witten - For feedback, I can confirm the 1.9.1 works as intended, thank you!
Fixed in borgmatic 1.9.1, just released!
Halo I'm experiencing this issue too.
this my docker compose
services: borgmatic: container_name:…
This is my current compose file (which I realise I didn't post originally (derp))
#############
##Borgmatic##
#############
borgmatic:
image: modem7/borgmatic-docker
…
Seems to be reliable currently (will need to check at 5am when the server backs up).
In my ssh config file, I seem to already have:
Host *
ServerAliveInterval 300
❯ docker exec -it Borgmatic /bin/bash
fc4881062a50:/# borg info --json ssh://jv7q0jm5@jv7q0jm5.repo.borgbase.com/./repo
{
"cache": {
"path": "/root/.cache/borg/f08b941…
Oh thank god - I thought I screwed something up (usually the case), especially as two other VMs (albeit with one repo attached rather than multiple) were working!
Thanks for the quick response…
I recreated the repo, and no issues so far.
Looks like it may have just been a weird issue, but I'll keep an eye.
Thanks!
I'll give "borg delete --cache-only repo" a bit later and see what happens!
Thanks!
Another repair did the trick.
Sorry for lack of comms!
@s1shed - you've given me a great idea.
hooks:
before_backup:
- echo "Starting a backup job."
- docker exec GrafanaDB influxd backup -portable…
Yupper!
My crappy script so far is as follows:
#Backup Varken Database
docker exec GrafanaDB influxd backup -since 2021-01-01T00:00:00Z -database varken /dbbackup/varken.bak
#Backup…