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.

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

rear mkrescue shows "Using backup archive" message #1363

Closed
gdha opened this issue May 13, 2017 · 8 comments
Closed

rear mkrescue shows "Using backup archive" message #1363

gdha opened this issue May 13, 2017 · 8 comments

Comments

@gdha
Copy link
Member

gdha commented May 13, 2017

  • rear version (/usr/sbin/rear -V): master git
  • OS version (cat /etc/rear/os.conf or lsb_release -a): centos 7.3
  • Brief description of the issue:
    I find it rather strange when running rear mkrescue that we see the following message:
# rear -vd mkrescue
Relax-and-Recover 2.00-git201705081501 / 2017-05-08
Using log file: /var/log/rear/rear-client.log
Using backup archive '/tmp/rear.B9uTEKRZLGjnpxn/outputfs/client/backup.tar.gz'
Creating disk layout
@gdha gdha added the cleanup label May 13, 2017
@jsmeix
Copy link
Member

jsmeix commented May 15, 2017

I know it since a long time.
It is because same stuff is run for "mkbackup" and "mkrescue".
I had a look but found no time to properly clean it up.
Things are too much interwoven for a quick and clean fix.

@jsmeix
Copy link
Member

jsmeix commented May 15, 2017

The root cause is that both WORKFLOW_mkbackup
and WORKFLOW_mkrescue need to run the 'prep' stage
and the 'prep' stage contains
prep/NETFS/default/070_set_backup_archive.sh

Or in other words:
Creating the backup is implemented intermixed
with creating the rescue/recovery system
but actually creating the backup happens
usually after creating the rescue/recovery system
except for WORKFLOW_mkbackup on USB where
things are additionally intermixed in another way.

@gdha gdha self-assigned this Aug 16, 2017
@gdha
Copy link
Member Author

gdha commented Aug 16, 2017

@jsmeix Thanks Johannes for your review. I will try to fix this one later this month.

@jsmeix jsmeix added this to the ReaR v2.4 milestone Dec 1, 2017
@jsmeix
Copy link
Member

jsmeix commented Dec 1, 2017

Nothing that needs to be done for ReaR 2.3
so that I set the milestone to ReaR 2.4

@gdha gdha modified the milestones: ReaR v2.4, ReaR v2.5 May 29, 2018
@gdha
Copy link
Member Author

gdha commented May 29, 2018

moving to 2.5

@gdha
Copy link
Member Author

gdha commented Mar 1, 2019

mkbackuponly-workflow.sh:    SourceStage "prep"
mkbackup-workflow.sh:	SourceStage "prep"
mkopalpba-workflow.sh:	SourceStage "prep"
mkrescue-workflow.sh:	SourceStage "prep"

are the workflows using the prep phase

@jsmeix
Copy link
Member

jsmeix commented Mar 4, 2019

This needs a more careful analysis whether or not
usr/share/rear/output/ISO/Linux-i386/810_prepare_multiple_iso.sh
still works o.k. when the variable backuparchive is no longer set in
usr/share/rear/prep/NETFS/default/070_set_backup_archive.sh
in case of the 'mkrescue' workflow.

See
#2063 (comment)

gdha added a commit that referenced this issue Mar 5, 2019
to avoid confusing in mkrescue run we do not print using archive #1363
@jsmeix
Copy link
Member

jsmeix commented Mar 5, 2019

With
77cb3c2
and
4e03733
I added comments to
usr/share/rear/prep/NETFS/default/070_set_backup_archive.sh
and
usr/share/rear/output/ISO/Linux-i386/810_prepare_multiple_iso.sh
that describe the above described interdependency between
prep/NETFS/default/070_set_backup_archive.sh and
output/ISO/Linux-i386/810_prepare_multiple_iso.sh
that exists except for the mkrescue workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants