#3563 Issue closed: how to pass custom config parameter with rear command

Labels: support / question, fixed / solved / done

20pa5a1203 opened issue at 2026-02-11 06:28:

Requesting support or just a question

rear -v recover BACKUP_PROG_ARCHIVE="localhost.localdomain+2026-02-10-14-55"

Platform

Other

Output

rear -v recover BACKUP_PROG_ARCHIVE="localhost.localdomain+2026-02-10-14-55"

Additional information

Image

gdha commented at 2026-02-12 08:25:

@20pa5a1203 Can you paste your /etc/rear/local.conf file for verification?

20pa5a1203 commented at 2026-02-12 08:53:

OUTPUT=ISO
OUTPUT_URL=nfs://10.X.X.X/ReaR-backup
BACKUP=NETFS
BACKUP_URL=nfs://10.X.X.X/ReaR-backup
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash')
BACKUP_PROG_ARCHIVE="hostname+date +%Y-%m-%d-%H"
ISO_PREFIX="hostname+date +%Y-%m-%d-%H"

gdha commented at 2026-06-15 11:36:

@20pa5a1203 Did you try:
BACKUP_PROG_ARCHIVE="localhost.localdomain+2026-02-10-14-55" rear -v recover ?

20pa5a1203 commented at 2026-06-18 19:11:

I tried several approaches, but they did not work. Eventually, I identified the root cause: the backup is stored on an NFS server.

After restoring the rescue image, we need to assign an IP address to the server. Once the network is configured, the server automatically connects to the NFS server and retrieves the backup files required for data restoration.

If anyone requires the detailed recovery procedure, please let me know. I can prepare an SOP for the complete restore process.

Thanks for your reply @gdha

jsmeix commented at 2026-06-19 07:21:

@20pa5a1203
to automate special cases of network devices setup
in the rescue/recovery system you may specify
NETWORKING_PREPARATION_COMMANDS=( ... )
as needed in your /etc/rear/local.conf
see the description in usr/share/rear/conf/default.conf
e.g. for ReaR 2.9 starting at
https://github.com/rear/rear/blob/master/usr/share/rear/conf/default.conf#L3822

[Export of Github issue for rear/rear.]