Lines Matching full:be
85 The output can be redirected to a file or to a different system
94 non-deduplicated stream will be generated.
102 The incremental source may be specified as with the
148 must also be specified.
156 to be excluded from the send stream.
157 The root dataset may not be excluded.
177 Datasets that are sent with this flag may not be
211 then the data will be decompressed before sending so it can be split into
218 The new compression property will be set for future data.
224 This allows backups to be taken even if encryption keys are not currently
226 The backup may then be received on an untrusted machine since that machine will
232 property will be defaulted to
235 For unencrypted datasets, this flag will be equivalent to
238 be sent unencrypted and may be re-encrypted with a different encryption key on
246 that the holds be applied to the dataset on the receiving system.
254 The incremental source can be specified as the last component of the snapshot
260 and it is assumed to be from the same file system as the incremental target.
262 If the destination is a clone, the source may be the origin snapshot, which must
278 flags to determine what data will be sent.
279 In this case, the verbose output will be written to standard output
299 This flag can only be used in conjunction with
304 The same report can be requested by sending
312 You will be able to receive your streams on future versions of ZFS.
321 Generate a send stream, which may be of a filesystem, and may be incremental
323 If the destination is a filesystem or volume, the pool must be read-only, or the
324 filesystem must not be mounted.
326 snapshot name will be
332 non-deduplicated stream will be generated.
367 then the data will be decompressed before sending so it can be split into
371 This allows backups to be taken even if encryption keys are not currently
373 The backup may then be received on an untrusted machine since that machine will
379 property will be defaulted to
382 For unencrypted datasets, this flag will be equivalent to
385 be sent unencrypted and may be re-encrypted with a different encryption key on
404 Datasets that are sent with this flag may not be received as an encrypted
416 The incremental source must be an earlier snapshot in the destination's history.
417 It will commonly be an earlier snapshot in the destination's file system, in
418 which case it can be specified as the last component of the name
426 If the incremental target is a clone, the incremental source can be the origin
438 flags to determine what data will be sent.
439 In this case, the verbose output will be written to standard output
446 The same report can be requested by sending
468 The resulting send stream is said to be redacted with respect to the snapshots
475 This feature can be used to allow clones of a filesystem to be made available on
476 a remote system, in the case where their parent need not (or needs to not) be
480 can be used to replicate the secured data without replicating the original
486 parent, that block will not be sent; but if one or more snapshots have not
488 that block will be sent.
489 Note that only user data will be redacted.
493 Due to the nature of redaction, a redacted dataset can only be used in the
500 blocks that were redacted in the parent are guaranteed to be present in the
502 This use case will produce a normal snapshot, which can be used just like other
510 (redacting with respect to additional snapshots causes less data to be redacted
520 necessary to fill in any redacted data, should it be needed, because the sending
547 raw sends and redacted sends cannot be combined at this time.
598 failure), the redaction can be resumed by rerunning the same command.
607 can be created that stores a list of blocks containing sensitive information.
618 A redacted dataset cannot be mounted by default, since it is incomplete.
619 It can be used to receive other send streams.
620 In this way datasets can be used for data backup and replication,
630 command with a parent snapshot, a bookmark to be created, and a number of
632 These redaction snapshots must be descendants of the parent snapshot,
644 the original parent to the redaction snapshots can then also be received on
645 the target system, and this will produce a complete snapshot that can be used
648 can also be done by sending from the redaction bookmark, rather than the
664 it must all be sent and received together.
679 The parent can then be sent, redacted, to the target
681 Finally, incremental sends from the parent snapshot to each of the clones can be
684 ones on the source, and are ready to be used, while the parent snapshot on the