As per the documentation "zelta backup: A robust replication tool with safe defaults, designed for creating consistent and reliable read-only replicas."
if i perform "zelta backup -n system pool_18a/system "
I get "zfs send -P -Lcpwn 'system@system_root-20220224-014059' | zfs receive -v -o readonly=on 'pool_18a/system'"
etc
Notice that my backup of my root (system) dataset is about to mount straight over my existing root dataset.
The " -ux mountpoint " is missing (one guess as to how I noticed this)
To set this I needed to set the environment variable RECEIVE_FLAGS_TOP="-ux mountpoint -o readonly=on"
This is supposed to be the default. RECEIVE_FLAGS seems to be ignored and RECEIVE_FLAGS_TOP is undocumented.
Setting RECEIVE_FLAGS_TOP in zelta.env is ignored, so it has to be set as an environment variable.
I feel that somewhere along the line, what the author is using compared with this version, are out of sync. Some sort of revision number on each file would probably help.
As per the documentation "zelta backup: A robust replication tool with safe defaults, designed for creating consistent and reliable read-only replicas."
if i perform "zelta backup -n system pool_18a/system "
I get "zfs send -P -Lcpwn 'system@system_root-20220224-014059' | zfs receive -v -o readonly=on 'pool_18a/system'"
etc
Notice that my backup of my root (system) dataset is about to mount straight over my existing root dataset.
The " -ux mountpoint " is missing (one guess as to how I noticed this)
To set this I needed to set the environment variable RECEIVE_FLAGS_TOP="-ux mountpoint -o readonly=on"
This is supposed to be the default. RECEIVE_FLAGS seems to be ignored and RECEIVE_FLAGS_TOP is undocumented.
Setting RECEIVE_FLAGS_TOP in zelta.env is ignored, so it has to be set as an environment variable.
I feel that somewhere along the line, what the author is using compared with this version, are out of sync. Some sort of revision number on each file would probably help.