2018-05-17 14:16:46.251048154 Including rescue/NSR/default/470_safe_filesystems.sh

[nirmal21s]

OS Version :Red Hat Enterprise Linux Server release 7.5 (Maipo)
REAR rpm used : rear-2.3-1.el7.x86_64.rpm
Networker client : lgtoclnt-8.2.4.7-1.x86_64

local.conf :

NRSERVER=xxxxxxx
NSR_CLIENT_MODE=
OUTPUT=ISO
ISO_PREFIX="rear-nsr-$HOSTNAME"
BACKUP=NSR
OUTPUT_URL=file:///tmp
# Static IP (no DHCP!)
USE_DHCLIENT=
USE_STATIC_NETWORKING="y"
# NTP
TIMESYNC=NTP

Error :

[VIP root@ts2otafe303: /usr/share/rear/rescue/NSR/default]$ rear -v mkrescue
Relax-and-Recover 2.3 / 2017-12-20
Using log file: /var/log/rear/rear-txxxxx.log
Creating disk layout
Using guessed bootloader 'GRUB'
No Networker ISO Backups found.
Creating root filesystem layout
Adding net.ifnames=1 to KERNEL_CMDLINE
Adding biosdevname=0 to KERNEL_CMDLINE
ERROR: The savefs command could not retrieve the "save sets" from this client
Aborting due to an error, check /var/log/rear/rear-txxx.log for details
Terminated

[hpannenb]

@nirmal21s In case You are not allowed or not the admin of the networker server please use NSR_CLIENT_MODE=yes . Otherwise ReaR will fail to find the proper "save set" on the networker server (but I am not a networker expert!). Just in case it still does not work it would be valuable to provide the extract of the log file where the error occurs.

[nirmal21s]

This time i installed the latest snapshot dump :
VIP root@ts2otafe303: /etc/rear]$ rear dump
Relax-and-Recover 2.3-git.0.e4eb0e1.unknown / 2018-05-14

This time also nsr_path was empty.
mkrescue output attached

mkrescue.txt

Site.conf:

NRSERVER=
NSR_CLIENT_MODE=yes
OUTPUT=ISO
ISO_PREFIX="rear-nsr-$HOSTNAME"
BACKUP=NSR
OUTPUT_URL=file:///isorear/rear
export TMPDIR=/isorear/temprear
#
# Static IP (no DHCP!)
USE_STATIC_NETWORKING="y"
# NTP
TIMESYNC=NTP

[nirmal21s]

Hello Holger,

Any parameter needs to be changed on Backup server ,with respect to NSR_CLIENT_MODE ?
Still the "savefs -p -s <NSRSERVER" command is not executing in 470_safe_filesystems.sh.
But when i run this command on client its showing the output.

[hpannenb]

@nirmal21s: ReaR behaves as per design here: In the NSR_CLIENT_MODE the NSR_PATH is not gathered and not required. The data recovery for the to be recovered server has to be initiated on the networker server side at a later stage of the recovery process. Once the rescue image has been booted ReaR will prepare the to be recovered server during the "rear recover" process and a prompt is shown to trigger the data recovery at a later stage (see 400_restore_with_nsr.sh).

[nirmal21s]

Thanks Holger!
I will do the testing and confirm you the status.

Again thanks for your help.