[rear-users] rear-users post from thomas.gosteli at post.ch requires approval

thomas.gosteli at post.ch thomas.gosteli at post.ch
Tue Apr 26 10:23:11 CEST 2016


Hi Gratien,
Sorry I forgot to mention that I’m already using the options “nfsvers=3, nolock” as well as “rsize=32768,wsize=32768”. I’m also using the same options on some RHEL 7.2,6.7 and SLES 11 SP4 systems and there everything works flawlessly. Here the output from journalctl:

[cid:image001.png at 01D19FA3.97632D80]

For me it seems that this is some sort of problem from the rear rescue image. When I try to mount the NFS Share manually (mount –o nolock hddzf2:/data/col1/zf2_nfs_fallback_linux/v000ra /mnt) this works just fine. So maybe rear is not using the nolock option?

Config :

OUTPUT="ISO"
OUTPUT_URL="http://fqdn.domain.ch/rear/"
BACKUP="NETFS"
BACKUP_URL="nfs://hddzf2.fqdn.domain.ch/data/col1/zf2_nfs_fallback_linux/v000ra"
BACKUP_OPTIONS="nfsvers=3,hard,rsize=32768,wsize=32768,nolock"
BACKUP_PROG_COMPRESS_OPTIONS=""
BACKUP_PROG_COMPRESS_SUFFIX=""
BACKUP_PROG_OPTIONS="${BACKUP_PROG_OPTIONS[@]} --one-file-system"
BACKUP_PROG_EXCLUDE=( "${BACKUP_PROG_EXCLUDE[@]}" '/data*' '/appl/*' '/mnt/*' '/logs/*' '/nsr/*'  )
POST_RECOVERY_SCRIPT="reboot"

Thomas

Von: rear-users-bounces at lists.relax-and-recover.org [mailto:rear-users-bounces at lists.relax-and-recover.org] Im Auftrag von Gratien D'haese
Gesendet: Dienstag, 26. April 2016 09:56
An: rear-users at lists.relax-and-recover.org
Betreff: Re: [rear-users] rear-users post from thomas.gosteli at post.ch requires approval


Try to use BACKUP_OPTIONS="nfsvers=3,nolock" in /etc/rear/local.conf to avoid using rpc.statd daemon.

However, it would have been nice to know why the rpcstatd daemon did not start? Any clues?

regards,

Gratien

On Mon, 25 Apr 2016 15:02:45 +0200, rear-users-owner at lists.relax-and-recover.org<mailto:rear-users-owner at lists.relax-and-recover.org> wrote:
Hi there,
I’m currently experiencing some problems with restoring Debian 8.{2,3} machines. Rear is unable to start rpc.statd when recovering, see screenshots below:
Any idea how to fix this issue?
Thanks for every help – Regards Thomas

[cid:image002.png at 01D19FA3.97632D80]


[cid:image003.png at 01D19FA3.97632D80]

[cid:image004.png at 01D19FA3.97632D80]


--

Gratien D'haese
IT3 Consultants bvba
Vennestraat 15, B-2560 Nijlen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20160426/9f394699/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 65347 bytes
Desc: image001.png
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20160426/9f394699/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 17762 bytes
Desc: image002.png
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20160426/9f394699/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 56703 bytes
Desc: image003.png
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20160426/9f394699/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 21118 bytes
Desc: image004.png
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20160426/9f394699/attachment-0007.png>


More information about the rear-users mailing list