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
How to avoid the copy of ISO (rescue +data) under /var/lib/rear/output ? #1281
Comments
My version is Relax-and-Recover 2.00 / Git OS_VENDOR=RedHatEnterpriseServer |
@jfucanada For some background information you may have a look at Accordingly you cannot avoid the local ISO because |
@jfucanada I think the solution you are looking for is described in issue #802 |
@gdha I assumed @jfucanada likes to avoid If @jfucanada only likes to change the default directory With ISO_DIR I could only specify a local directory ISO_DIR="/tmp/myISOdir" but I failed to specify a remote place for the ISO Even manually mounting e.g. a NFS share 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 # 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 mkdir -p "$ISO_DIR" |
Mainly for my own information ... there is a reason why the output workflow is before the backup workflow and that is OBDR (however, is anyone still using that?) |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
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=
The text was updated successfully, but these errors were encountered: