#2264 Issue closed: CDM: Needs method to perform unattended recovery

Labels: enhancement, no-issue-activity

DamaniN opened issue at 2019-10-25 04:14:

Relax-and-Recover (ReaR) Issue Template

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

2.6 - dev

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

All

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

N/A

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

All

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

All

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

All

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

All

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

Automatic recovery does not work with the Rubrik CDM integration. Users must use the manual recovery option and answer various questions. Automatic recovery will launch but leaves the user at the rear> prompt.

ReaR should automatically recover the latest backup from the original cluster using the fileset used to back up with ReaR.

  • Workaround, if any:

None

  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

None

DamaniN commented at 2019-10-25 04:14:

Assign this issue to me. I am working on a fix.

jsmeix commented at 2019-10-25 07:56:

@DamaniN
thank you for your continuous usability improvements of BACKUP=CDM.
I appreciate ReaR usability improvements very much.

With 'ReaR usability' I do not mean that ReaR should "just work"
even for arbitrary unexperienced end-users,
cf. "Inappropriate expectations" in
https://en.opensuse.org/SDB:Disaster_Recovery

With 'ReaR usability' I mean for example things like

Do not "simply abort" but let the user retry if possible

for example as in https://github.com/rear/rear/issues/2253
and (even more important) things like

Try hard to care about possible errors

and

It should be possible to run ReaR unattended

in https://github.com/rear/rear/wiki/Coding-Style

github-actions commented at 2020-06-29 01:37:

Stale issue message

[Export of Github issue for rear/rear.]