#1547 Issue closed: "rear mkrescue" useless/dangerous in case of backup on ISO¶

Labels: bug, fixed / solved / done

jsmeix opened issue at 2017-10-26 08:32:¶

This is a follow-up of https://github.com/rear/rear/issues/1545

Current ReaR master code:

Summary:
When I do a backup on the ISO via "rear mkbackup"
then recovery via "rear recover" works.
But "rear mkrescue" with

BACKUP_URL="iso:///mybackup"

is useless and even dangerous because such an ISO can
never work later for "rear recover" because a non-working
backup URL is stored in that recovery system.

Doing "rear recover" with such a "rear mkrescue" ISO fails with

RESCUE e205:~ # rear -d -D recover
...
ERROR: Backup archive 'backup.tar.gz' not found.
Aborting due to an error, check /var/log/rear/rear-e205.log for details

In case of "rear mkrescue" there is no backup in the ISO
so that such an ISO is useless because it can never work
unless the backup is actually in the ISO.

Therefore backup in the ISO via something like

BACKUP_URL="iso:///mybackup"

conflicts with "rear mkrescue" so that the mkrescue workflow
must be forbidden when the backup is configured to be in the ISO.

jsmeix commented at 2017-10-26 11:59:¶

With https://github.com/rear/rear/pull/1549 merged
this issue should be fixed.

---

[Export of Github issue for rear/rear.]