-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with ReaR and Borg #2833
Comments
@ZENAdmin-Ops Do you know about our Borg backup documentation in Your above posted site.conf or local.conf looks incomplete.
or alternatively
Also without a complete "rear -D mkrescue" |
I have the following working configuration (but this doesn't use Borg) I have been able to restore this backup. But I don't want to run this daily.
Thanks for your post. I have been using a different example as my template for the integration of the Borg backup After your comments, I had a closer look at the section of the user guide which you refer to. And while I still don't have a working config as I write. I have been able to correct the error with Rear being unable to locate the Borg repository. This is definitely progress. Thanks! Sometimes you just need a fresh set of eyes to provide a different perspective. I'll do some further testing tomorrow. |
Hello, Here's my latest attempt
Failing because of the backup selection
Here is the: borg_backup.conf
The issue appears to be this statement
But the syntax looks OK to me? |
The answer appears to be to change
To this
Which seems odd, because the default.conf includes examples like the following
|
@ZENAdmin-Ops From what is see in the code it goes like this: With
that is read by
which evaluates to
which seems to let 'borg' fail with
so it seems 'borg' does not do "globbing" In contrast with
that is read by
which evaluates to
which works with 'borg'. Tertium datur:
outputs which is all files and directories in
which evaluates to
which likely also works with 'borg'. |
In default.conf use a more generic description about quoting to avoid bash pathname expansion because in case of BACKUP=BORG a quoted BACKUP_PROG_INCLUDE=( '/dir/*' ) seems to let 'borg' fail with "/dir/*: [Errno 2] No such file or directory: '*'" cf. #2833 (comment)
Via
|
Note the subtle difference:
evaluates to all files and directories in /home/ and /opt/
so a backup tool that is called as
will backup all in
but it may not backup the parent directories
(in particular owner group permissions of that parent directories) So in general it is better to keep it simple and specify
(bash pathname expansion for '/home' and '/opt' results '/home' and '/opt') |
I assume this issue is sufficiently answered so I close it. |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
2.6
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Ubuntu 22.04
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
Hyper-V VM. Gen 2
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Local USB formatted by Rear
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
N/A
Description of the issue (ideally so that others can reproduce it):
Hello,
I am posting this question on the Github issue tracker, because the rear-users list is not working at the moment.
I think that my issue is more than likely a configuration issue on my part, rather than a Rear issue.
I'm new to Rear. I currently have a working Rear backup to a local USB drive using NETFS.
I want to integrate Borg into my Rear config.
I currently have Borg backup to the local USB drive working when I use Borg directly.
The issue that I'm having is when trying to call Borg via Rear.
I've tried a number of different settings in the conf file and none have worked
Here is an extract of the error from Rear
In an ideal world, if someone can see the error in my conf file, that would be awesome.
Failing that, some troubleshooting suggestions would be appreciated.
Thank you
Vaughan
The text was updated successfully, but these errors were encountered: