Replication and automatic snapshots redesign
Description
Attachments
duplicates
SmartDraw Connector
Katalon Manual Tests (BETA)
Link goals
Activity

george hartzell June 18, 2019 at 3:51 PM
Thank's for the followup. I'll look forward to it!

Vladimir Vinogradenko June 18, 2019 at 8:06 AM
unfortunately the feature to avoid replicating properties (all or only selected) will only be available in FreeNAS 12.0. Right now zettarepl in alpha stage and (most likely) more important things are broken. However, this feature in zettarepl itself will most likely be available much earlier from github/pip/BSD ports and you'll be able to install it standalone.

george hartzell June 10, 2019 at 6:19 PM
I ended up here after stumbling on zettarepl in the FreeNAS GitHub org and filing an issue asking about its status. Apologies if I'm in the wrong place.
I'm interested in pull-replicating a remote FreeBSD 12 system (bog-standard ZFS install, plus a few extra filesystems) onto one of my FreeNAS systems and/but am particularly concerned that remote filesystems that have dangerous mountpoints (e.g. zroot/usr, which has mountpoint=/usr) not end up mounted in inappropriate places on my FreeNAS box.
Reading through the source (e.g. [here, where zfs_recv is defined](https://github.com/freenas/zettarepl/blob/master/zettarepl/transport/zfscli/__init__.py#L49-L50), it seems as if you don't have a way to filter things when they're received.
Is zettarepl protecting against this somehow? Is it out of scope (the zettarepl tagline does mention "cross-platform") or a TODO?

Achim Staebler May 25, 2019 at 9:58 AM
I believe I encountered a similar situation, opened an issue for it here: https://jira.ixsystems.com/browse/NAS-101892. I also see the console spammed with this but more importantly the mount point for the datasets "disappear"/turn empty.

This ticket gathers all tasks needed for the new replication/autosnap engine.