--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/childnotbackedupshould be it
Does anyone have an example of a service manifest XML file for OpenIndiana/Illumos?
You can use Manifold to quickly create smf manifest https://code.google.com/archive/p/manifold/
question: I ran into the situation that I can't create new snapshots, not enough space on the volume. I can fix that obviously but what I'm surprised about is that znapzend logs that but then still seems to continue. I see among others:
# zfs snapshot -r zones/74e519c8-0010-41fb-846b-9301f5587797-disk0@2021-05-18-102226 cannot create snapshot 'zones/74e519c8-0010-41fb-846b-9301f5587797-disk0@2021-05-18-102226': out of space no snapshots were created # zfs list -H -o name -t snapshot zones/74e519c8-0010-41fb-846b-9301f5587797-disk0@2021-05-18-102226 cannot open 'zones/74e519c8-0010-41fb-846b-9301f5587797-disk0@2021-05-18-102226': dataset does not exist [2021-05-18 10:22:27.66667]  [warn] taking snapshot on zones/74e519c8-0010-41fb-846b-9301f5587797-disk0 failed: ERROR: cannot create snapshot zones/74e519c8-0010-41fb-846b-9301f5587797-disk0@2021-05-18-102226 at /opt/tools/lib/ZnapZend/ZFS.pm line 272.
so right now it still does a
zfs recv on the remote system but I guess that will fail at one point
When I run znapzend with noaction:
Can there be a problem that at first, subvol-165-disk-0 snapshot is created and then recursive snapshot fails, because it already exists?