zfs (zxfer) replication -- "holes" in backups?

[Jon Radel]

On 12/13/16 6:44 PM, Aleksandr Miroslav wrote:
> I'm using zxfer to replicate my ZFS snapshot to another host. Occasionally,
> for whatever reason, zxfer can't replicate a particular snapshot.

Have you considered informing us of the options you use to zxfer?

In particular, might you be using the -d and -F options, or more
precisely, failing to do so?  They're useful for keeping your snapshots
in sync between source and backup, though it's been so long since I
setup my backups that I no longer recall exactly how things break if you
leave them off.  See the examples in the man page.

I can tell you, however, that with

zxfer -vFdk -o setuid=off,compression=lz4 -T mirrors at filer.radel.com -R
zroot pool1/mirrors/stream.radel.com

I do *not* see the problem you describe and routinely have the zxfer
kicked off by cron once an hour "catch up" on multiple new snapshots
created while my backup server was not doing all it should.

-- 
--Jon Radel
jon at radel.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3890 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20161214/7ba1d32f/attachment.bin>