Thanks for reply, No, the passphrase is not the aktual one.
I have running 4 backup jobs running on different servers, with different borgmatic versions. The Passphrase is the right on. Your…
you are right, it was the wrong SSH Key path in the config.yaml. For a while I changed the key, and I have forgotten to change the path.
Thanks for helping!
Bernd
all backup jobs are running as root
I removed the ssh key path from the config.yaml:
storage: # Point to your private key # ssh_command: ssh -i /volume1/borgbackup/id_synology
…
If I make a direct connect to the storage box with "ssh -p 23 u123456@u123456.your-storagebox.de", that works without passphrase. So it couldn't come from SSH, the SSH key works without probleme.…
Î tried once more with borg prune -v --list --keep-daily=7 ssh://u2988....., and that was working. Now it works automatically.
Thanks
I put keep_within: 2m in the config.yaml:
without the "prune" action. See borgmatic documentation for details.
retention: # Keep all archives within this time interval. keep_within…
Hi witten,
now I had time to working back on my mailcow borgmatic backup. I had removed all the entries in the config.yaml file:
location:
source_directories:
- /mnt/source
…
yes, both files are the same. I put the file in the docker container on the position shown in this description: https://docs.mailcow.email/de/third_party/borgmatic/third_party-borgmatic/. After…