rm -r znapzend/
git clone https://github.com/oetiker/znapzend.git znapzend && cd znapzend/
apt-get install perl unzip autoconf carton
./bootstrap.sh
./configure --prefix=/opt/znapzend-master
make
make install
rm /usr/local/bin/znapzend*
for x in /opt/znapzend-master/bin/*; do ln -s $x /usr/local/bin; done
ln -f
takes care of removing older ones if present, and a GNU ln -r
can make relative symlinks that are more meaningful when you juggle many alternate roots and do not want to reference the current OS you are running (most linux systems/scripts do not know the difference... solaris had that for decades, e.g. a file server hosting roots for diskless NFS workstations, so it is sort of a built-in habit)
ln
such as in Solaris does not have the -r
so explicit ../
have to be prepended
znapzend --runonce=pool/data/set
only requesting one data set with a schedule
znapzend list -r pool | grep 'key chars from heading' | awk '{print $4}'
iirc) run once one by one.
--autoCreation
, but znapzend doesn't seem to be handling the case where the filesystem can't be mounted after creation cleanly: I get […]
cannot open 'thirtythree/backups/sosiego/mail': dataset does not exist
filesystem successfully created, but it may only be mounted by root
cannot open 'thirtythree/backups/sosiego/mail': dataset does not exist
ERROR: cannot create dataSet thirtythree/backups/sosiego/mail
zfs set org.znapzend:enabled=off pool/backeduptree/childnotbackedup
should be it