Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"rear mkrescue" useless/dangerous in case of backup on ISO #1547

Closed
jsmeix opened this issue Oct 26, 2017 · 2 comments · Fixed by #1549
Closed

"rear mkrescue" useless/dangerous in case of backup on ISO #1547

jsmeix opened this issue Oct 26, 2017 · 2 comments · Fixed by #1549
Assignees
@jsmeix
Labels
bug The code does not do what it is meant to do fixed / solved / done
Milestone
ReaR v2.3

Comments

@jsmeix
Copy link
Member

jsmeix commented Oct 26, 2017

This is a follow-up of #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 jsmeix added the bug The code does not do what it is meant to do label Oct 26, 2017
@jsmeix jsmeix added this to the ReaR v2.3 milestone Oct 26, 2017
@jsmeix jsmeix self-assigned this Oct 26, 2017
This was referenced Oct 26, 2017
Closed
Merged
jsmeix added a commit that referenced this issue Oct 26, 2017
@jsmeix
Merge pull request #1549 from jsmeix/forbid_mkrescue_and_mkbackuponly…
0d11982 
…_for_iso_backup_scheme_issues_1547_and1548

Forbid mkrescue and mkbackuponly for BACKUP_URL="iso:///..."
because they do not make sense when the backup
is configured to be in the ISO,
see #1545
and #1547
and #1548
Require BACKUP_URL for BACKUP=NETFS and
document that in default.conf and in the man page
see #1532 (comment)
and subsequent comments.
@jsmeix
Copy link
Member Author

jsmeix commented Oct 26, 2017

With #1549 merged
this issue should be fixed.

@jsmeix jsmeix mentioned this issue Dec 1, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsmeix jsmeix

Labels
bug The code does not do what it is meant to do fixed / solved / done
Projects
None yet
Milestone
ReaR v2.3
Development

Successfully merging a pull request may close this issue.

Forbid mkrescue and mkbackuponly for BACKUP_URL="iso:///..." jsmeix/rear
2 participants
@jsmeix and others