-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syncoid - failed to send because child dataset with syncoid:no-sync=true
has no snapshots
#951
Comments
@luispabon yes you are doing something wrong :-) With the zfs send "-R" option you instructed zfs to do the recursive replication instead of syncoid. So all excludes which syncoid would handle have no effect:
You can use they "-X" option for zfs send to exclude datasets in an -R stream:
|
Thank you @phreaker0. How can I specify that as syncoid send options though? The following upsets syncoid:
|
@luispabon seems there is missing support for X with argument, you can temporarily patch syncoid to support it right away: Line 2178 in 826d4d1
replace that line with "if ($char eq 'o' || $char eq 'x' || $char eq 'X') { " |
Cheers. Looks like there's already a PR open for it: |
I have the following set of datasets for libvirt VMs:
The
zroot/vms/storage-pool-ephemeral
is where I place VMs to try out and I don't want them to be snapshotted or backed up. So:syncoid:no-sync=true
When I try to send the
zroot/vms
to my remote backup server I get the following:Seems counter intuitive that the dataset is explicitly excluded from sync's on syncoid yet syncoid expects datasets to be there. Perhaps I'm doing something wrong?
The text was updated successfully, but these errors were encountered: