#1445 Issue closed: Unable restore server from successful rear backup

Labels: support / question, fixed / solved / done

sameergithub5 opened issue at 2017-08-15 16:23:

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): Realx-and-Recover 2.00/ Git
  • OS version (cat /etc/rear/os.conf or lsb_release -a):LSB package is not installed
  • rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
OUTPUT=ISO
OUTPUT_URL=nfs://192.168.211.128/shared
BACKUP=NETFS
BACKUP_URL=nfs://192.168.211.128/shared

  • Are you using legacy BIOS or UEFI boot?
    legacy BIOS

  • Brief description of the issue:
    Unable to recover 7.2 centos says mount failed

  • Work-around, if any:
    NO

vm error

gozora commented at 2017-08-16 07:15:

Hi @sameergithub5,

Maybe you could share rear-qa.log with us?
If you try to mount fileystem manually, like:

mkdir /tmp/test && \
mount -v -t nfs 192.168.211.128:/shared /tmp/test

what does the output say?

V.

sameergithub5 commented at 2017-08-16 08:05:

This is the output with nfsver4.

[root@qa ~]# mkdir /tmp/test && \

mount -v -t nfs 192.168.211.128:/shared /tmp/test
mount.nfs: timeout set for Wed Aug 16 18:36:06 2017
mount.nfs: trying text-based options 'vers=4,addr=192.168.211.128,clientaddr=192.168.211.130'
[root@qa ~]# cd /tmp/test/
[root@qa test]# ll
total 760
drwxr-x--- 2 nfsnobody nfsnobody 106 Aug 16 03:29 qa
drwxr-xr-x 7 root root 4096 Jan 20 2017 rear-master
-rw-r--r-- 1 root root 772599 Mar 4 14:03 rear-master.zip
[root@qa test]# df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 13G 4.5G 8.5G 35% /
devtmpfs 903M 0 903M 0% /dev
tmpfs 913M 0 913M 0% /dev/shm
tmpfs 913M 8.6M 904M 1% /run
tmpfs 913M 0 913M 0% /sys/fs/cgroup
/dev/sda1 497M 125M 373M 26% /boot
tmpfs 183M 0 183M 0% /run/user/0
192.168.211.128:/shared 28G 5.3G 23G 20% /tmp/test
[root@qa test]#

gozora commented at 2017-08-16 08:13:

Hmm, no reason for ReaR return error on mount as it is visible from you screenshot.
Can you please run rear -d -D recover and provide us logfile from failed session? (/var/log/rear/rear-qa.log)

sameergithub5 commented at 2017-08-16 13:00:

[root@qa sbin]# ./rear -v -d -D mkbackup
Relax-and-Recover 2.00 / Git
Using log file: /tmp/rear-master/var/log/rear/rear-qa.log
Using backup archive '/tmp/rear.Bn5U8Z0wIODQI9L/outputfs/qa/backup.tar.gz'
Creating disk layout
Creating root filesystem layout
Copying logfile /tmp/rear-master/var/log/rear/rear-qa.log into initramfs as '/tmp/rear-qa-partial-2017-08-16T05:08:30+0530.log'
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
Making ISO image
Wrote ISO image: /tmp/rear-master/var/lib/rear/output/rear-qa.iso (109M)
Copying resulting files to nfs location
Saving /tmp/rear-master/var/log/rear/rear-qa.log as rear-qa.log to nfs location
Creating tar archive '/tmp/rear.Bn5U8Z0wIODQI9L/outputfs/qa/backup.tar.gz'
Archived 495 MiB [avg 5898 KiB/sec] OK
Archived 495 MiB in 87 seconds [avg 5830 KiB/sec]
You should also rm -Rf /tmp/rear.Bn5U8Z0wIODQI9L

=============================================
Kindly find attached
/tmp/rear-master/var/log/rear/rear-qa.log file for backup happened.
so that u can spot any error in backup which is causing incorrect restoration.

Restoration:
I have attached screenshot of rear -d -D recover.
restore time error

I am not able to find file /var/log/rear/rear-qa.log

gozora commented at 2017-08-16 13:08:

Your rear mkbackup looks to be working fine so I don't need logs from this session.

What you need to do to locate rear-qa.log from rear recover is following:

  1. Boot your ReaR rescue/recover system from ISO file
  2. Run rear -d -D recover
  3. Your log file is created in /var/log/rear/ directory, so you need to download it and post it to Github ...

V.

gozora commented at 2017-08-16 13:11:

@sameergithub5 for the case you don't know it yet, you can login to ReaR rescue/recovery system using SSH (c.f. default.conf).

sameergithub5 commented at 2017-08-16 13:37:

last restore log Kindly see attached /var/log/rear/rear-qa.log

schabrolles commented at 2017-08-16 13:38:

@sameergithub5, just before starting a ReaR recovery, could you please run the following command:

  • ip a
  • route -n
    May be your network configuration is not correctly set....

sameergithub5 commented at 2017-08-16 15:55:

Kindly find attached screenshot
ip route details

gozora commented at 2017-08-16 16:01:

@schabrolles was right, your network interface is not configured. You are probably trying to restore your OS to other then original server.
All you need to do is configure your NIC:
ip address add <IP>/<NETMASK_PREFIX> dev eno16777736 and run rear recover

V.

schabrolles commented at 2017-08-16 16:25:

I think #1349 should solved this one (ReaR 2.1)
@sameergithub5 could you test ReaR 2.1 ?

sameergithub5 commented at 2017-08-17 11:21:

Where can i find the link for downloading this bug fix version.

schabrolles commented at 2017-08-17 11:55:

@sameergithub5
you can try to get it from here : https://github.com/rear/rear/releases/tag/2.2

sameergithub5 commented at 2017-08-17 12:45:

Hello Guyz,
I have downloaded 2.2 git rear version but story remains the same.
server still not reachable

Please see attached screenshot.
2 2 rear error

sameergithub5 commented at 2017-08-17 12:52:

I manually tried to configured but still no luck
configure network

gozora commented at 2017-08-17 13:07:

Are you sure your network address mask is 255.255.255.255 ?

gozora commented at 2017-08-17 13:12:

My best guess is that following could work much better ip a add 192.168.211.130/24 dev eno16777736

gdha commented at 2017-08-18 07:32:

@sameergithub5 Do not forget your hypervisor virtual network - are you in the same VLAN?

jsmeix commented at 2017-08-21 12:57:

To set up networking manually in the ReaR recovery system
one can use NETWORKING_PREPARATION_COMMANDS,
see usr/share/rear/conf/default.conf

sameergithub5 commented at 2017-08-21 13:06:

@gozora u nailed it. It was network mistake nothing to blame rear on this occasion.

This is great you guyz will encourage us to stick with this.

gdha commented at 2017-08-21 14:19:

@sameergithub5 Great that your problem has been fixed. So, this issue can be closed then?

sameergithub5 commented at 2017-08-21 17:06:

Yes absolutely . thanks 4 it

On 21-Aug-2017 7:49 PM, "gdha" notifications@github.com wrote:

@sameergithub5 https://github.com/sameergithub5 Great that your problem
has been fixed. So, this issue can be closed then?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rear/rear/issues/1445#issuecomment-323754311, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AUru8_e6q2E-8X50pRvjk4HDwWC0Sxeyks5saZHXgaJpZM4O3zSV
.

[Export of Github issue for rear/rear.]