Date: Wed, 25 Jul 2018 14:03:46 +0200 From: Jan Bramkamp <crest@rlwinm.de> To: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property Message-ID: <7631a2af-8041-4666-3cef-ebbeed31eabf@rlwinm.de> In-Reply-To: <alpine.BSF.2.00.1807222110450.28320@woozle.rinet.ru> References: <alpine.BSF.2.00.1807222110450.28320@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22.07.18 20:14, Dmitry Morozovsky wrote:
> Colleagues,
>
> still stuck in compiling stable procedure.
>
> Prerequisites:
>
> - some servers, all on ZFS, with layout such as
> machine -> unique pool name, usually 2-letters, say, hm and im
>
> - zfs layouts like
>
> hm/R/${fs}, like
> hm/R
> hm/R/usr
> hm/R/usr/local
> hm/R/var
> hm/R/home
> etc, where hm/R has property mountpoint=/ and others just inherit it
>
>
> - on servers, zfs allows for non-root user to make snapshots, hold, etc, like
>
> Local+Descendent permissions:
> group operator hold,send,snapshot
>
> - zfs send -R [-i pool@prev-snap] pool@now-snap | \
> ssh backupserver 'zfs recv tgpool/B/zfs/srvname'
>
> Problem:
>
> 0. on backup (zfs recv) server, I could not
> - overwrite mountpoint property (and I'd better avoid it)
> - add canmount=off, especially for child filesets, as it's not inherited (which
> could be preferred behaviour)
>
> 1. after backup server reboot, if special manual tweaks did not have place,
> filesets from backup images overwrite backup filesets, render it unuseable
>
> Any hints?
>
> Or did I missed something trivial?
You missed the normal non-replication streams. Those contain only the
dataset and not its properties. You can use those to backup the dataset
and a wrapper script to deal with the dataset's properties. The zxfer
script does all that for you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7631a2af-8041-4666-3cef-ebbeed31eabf>