Hello,
I successfully configured (i think) borgbackupo on my omv5 virtual machine
Running borg from webinterface works fine (as far I can see).
But the cron jobs throws errors:
I get mails about failing hourly jobs.
Code
Fri Jan 17 10:05:01 CET 2020 Starting backup
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Fri Jan 17 10:05:01 CET 2020 Pruning repository
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Fri Jan 17 10:05:01 CET 2020 Starting backup
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Fri Jan 17 10:05:02 CET 2020 Pruning repository
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Fri Jan 17 10:05:02 CET 2020 Starting backup
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Fri Jan 17 10:05:02 CET 2020 Pruning repository
Repository /root/{{ ns.uri }} does not exist.
terminating with error status, rc 2
Alles anzeigen
Looking into cronjob script, it seems, that a variable isn't set correctly:
Bash
root@omv5:/etc/cron.hourly# cat /var/lib/openmediavault/borgbackup/hourly.d/borgbackup-2cd25511-2a21-407e-a6f3-97389fe1f96d
#!/bin/sh
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# Setting this, so the repo does not need to be given on the commandline:
export BORG_REPO='{{ ns.uri }}'
On my omv installation (omv4 this lines is replcaed with the correct path to the remote repo.
Bash
root@omv:~# cat /var/lib/openmediavault/borgbackup/hourly.d/borgbackup-02e22c68-6ee5-4176-981e-89ab5df63ec3
#!/bin/sh
# Setting this, so the repo does not need to be given on the commandline:
export BORG_REPO='borgbackup@servername:reponame'
soething seems to be wrong with the implementation of borg backup on omv5?
Thank you for the great omv! I'm running it since Version 2 and it's such a pleasure to use it!
Best regards
Thomas