output ?¶

Labels: support / question, fixed / solved / done

jfucanada opened issue at 2017-04-05 22:03:¶

Relax-and-Recover (ReaR) Issue Template¶

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

rear version (/usr/sbin/rear -V):
OS version (cat /etc/rear/os.conf or lsb_release -a):
rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
Are you using legacy BIOS or UEFI boot?
Brief description of the issue:
Work-around, if any:

My local.conf is as below.

OUTPUT=ISO
OUTPUT_URL=null
BACKUP=NETFS
BACKUP_URL=iso:///mondo
SSH_ROOT_PASSWORD="redhat"
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/mondo' '/var/tmp' '/var/crash')
#NETFS_KEEP_OLD_BACKUP_COPY=

jfucanada commented at 2017-04-05 22:37:¶

My version is Relax-and-Recover 2.00 / Git

OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=6

jsmeix commented at 2017-04-06 08:00:¶

@jfucanada
perhaps you misunderstand what OUTPUT_URL=null
actually does?

For some background information you may have a look at
https://github.com/rear/rear/issues/734
and also see the other issues mentioned therein.

Accordingly you cannot avoid the local ISO because
currently there is no support in ReaR that ReaR
creates its ISO directly on a remote location.
You can only avoid that the locally generated ISO
gets afterwards copied to a remote location.

gdha commented at 2017-04-06 08:32:¶

@jfucanada I think the solution you are looking for is described in issue #802

jsmeix commented at 2017-04-07 13:23:¶

@gdha
I do not know what exactly @jfucanada is asking for.

I assumed @jfucanada likes to avoid
that the ISO exists in a local directory
(which is by default /var/lib/rear/output).

If @jfucanada only likes to change the default directory
where the local ISO gets stored, ISO_DIR helps.

With ISO_DIR I could only specify a local directory
where the ISO is created like

ISO_DIR="/tmp/myISOdir"

but I failed to specify a remote place for the ISO
(i.e. so that one never has the ISO locally).

Even manually mounting e.g. a NFS share
using ISO_DIR as mountpoint like

ISO_DIR="/tmp/nfsISOdir"
PRE_BACKUP_SCRIPT="mkdir -v -p $ISO_DIR ; mount -v -t nfs -o $OUTPUT_OPTIONS 10.160.4.244:/nfs/$HOSTNAME $ISO_DIR"
POST_BACKUP_SCRIPT="umount $ISO_DIR"

does not work
because backup/default/990_post_backup_script.sh
that umounts the NFS share from ISO_DIR
is run before output/ISO/Linux-i386/800_create_isofs.sh
that creates the ISO - now in the local ISO_DIR
so that one gets in the end still a local ISO:

# ls -lh /tmp/nfsISOdir/rear-e205.iso
-rw------- 1 root root 1.3G Apr  7 15:08 /tmp/nfsISOdir/rear-e205.iso

In local.conf I even tried things like

export TMPDIR="/tmp/myReaRtmpdir"
ISO_DIR="$TMPDIR/rear.*/myISOdir"

and

ISO_DIR=nfs://10.160.4.244/nfs/$HOSTNAME

but that did not work - as expected when looking briefly
at the code about ISO_DIR which basically does

mkdir -p "$ISO_DIR"

jsmeix commented at 2017-04-11 09:43:¶

Mainly for my own information
why the 'output' stage is usually before the 'backup' stage see
https://github.com/rear/rear/issues/1283#issuecomment-293205009
(excerpt):

... there is a reason why the output workflow
is before the backup workflow and that is OBDR
(however, is anyone still using that?)

[Export of Github issue for rear/rear.]

#1281 Issue closed: How to avoid the copy of ISO (rescue +data) under /var/lib/rear/output ?¶