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

Labels: bug, fixed / solved / done

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

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

Current ReaR master code:

Summary:
Calling "rear mkbackuponly" with

OUTPUT=ISO
OUTPUT_URL=nfs://10.160.4.244/nfs
BACKUP=NETFS
BACKUP_OPTIONS="nfsvers=3,nolock"
BACKUP_URL="iso:///mybackup"

"succeeds" (i.e. exits with exit code 0) like

# usr/sbin/rear -d -D mkbackuponly
Relax-and-Recover 2.2 / Git
Using log file: /root/rear.master/var/log/rear/rear-e205.20319.log
Using backup archive '/tmp/rear.20ok0wIuc7PU2kt/tmp/isofs/mybackup/backup.tar.gz'
Creating disk layout
Using sysconfig bootloader 'grub2'
Creating tar archive '/tmp/rear.20ok0wIuc7PU2kt/tmp/isofs/mybackup/backup.tar.gz'
Preparing archive operation
Archived 25 MiB [avg 6480 KiB/sec] 
Archived 54 MiB [avg 7926 KiB/sec] 
...
Archived 2618 MiB [avg 13821 KiB/sec] 
Archived 2641 MiB [avg 13731 KiB/sec] 
OK
Archived 2641 MiB in 200 seconds [avg 13525 KiB/sec]
Saving /root/rear.master/var/log/rear/rear-e205.20319.log as /root/rear.master/var/log/rear/rear-e205.log

but no ISO is made or stored in var/lib/rear/output/
or saved at the OUTPUT_URL.

Because of the reasoning in https://github.com/rear/rear/issues/1545
and in https://github.com/rear/rear/issues/1547
only "rear mkbackup" makes sense when
the backup is configured to be in the ISO so that the
mkbackuponly workflow must be forbidden for things like

BACKUP_URL="iso:///mybackup"

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.]