#2383 Issue closed: [Question] How to add lftp to rescue image when using duplicity?

Labels: support / question, fixed / solved / done

vigri opened issue at 2020-04-30 11:32:

  • ReaR version ("/usr/sbin/rear -V"): 2.5 / git

  • OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): Debian 10

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

BACKUP=DUPLICITY
DUPLY_PROFILE="test"
OUTPUT=ISO
OUTPUT_URL=ftp://.....

  • Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): Virtual Machine

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x64

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): GRUB

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): local disk

  • Description of the issue (ideally so that others can reproduce it): /

  • Workaround, if any: none

Hello,
I've created a backup in combination with duplicity/duply. The backup is stored on a remote ftp server.

When I boot the recovery image I select "automatic recover". After some time rear tells me to manually recovery my files using duplicity.

After entering duply /root/.duply/test I get the error message: LFTP not found. Please install LFTP

Question
How can I make lftp inside the boot image available? Is there a way to install it (apt-get / yum .. isn't working) or can it be copied to the image during its creation?

Thanks and best regards

gdha commented at 2020-04-30 11:51:

@vigri I can think of 2 points to add to your /etc/rear/local.conf file:

  • COPY_AS_IS=( "${COPY_AS_IS[@]}" /root/root.gpgkey )
  • PROGS=( "${PROGS[@]}" lftp )
    Also, check the rear logfile to see whether above files were not already added?

vigri commented at 2020-04-30 13:29:

Exactly what I was looking for.

Thank you @gdha .

[Export of Github issue for rear/rear.]