diff options
Diffstat (limited to 'man/man8/zfs-send.8')
| -rw-r--r-- | man/man8/zfs-send.8 | 23 |
1 files changed, 15 insertions, 8 deletions
diff --git a/man/man8/zfs-send.8 b/man/man8/zfs-send.8 index b033e15a1..83f4e81da 100644 --- a/man/man8/zfs-send.8 +++ b/man/man8/zfs-send.8 @@ -215,7 +215,8 @@ compress on the receiver, unless you specify .Fl o Sy compress Ns = Em off . .It Fl w , -raw For encrypted datasets, send data exactly as it exists on disk. -This allows backups to be taken even if encryption keys are not currently loaded. +This allows backups to be taken even if encryption keys are not currently +loaded. The backup may then be received on an untrusted machine since that machine will not have the encryption keys to read the protected data or alter it without being detected. @@ -286,7 +287,8 @@ when using this flag. Allows sending a replication stream even when there are snapshots missing in the hierarchy. When a snapshot is missing, instead of throwing an error and aborting the send, -a warning is printed to the standard error stream and the dataset to which it belongs +a warning is printed to the standard error stream and the dataset to which it +belongs and its descendents are skipped. This flag can only be used in conjunction with .Fl R . @@ -354,7 +356,8 @@ then the data will be decompressed before sending so it can be split into smaller block sizes. .It Fl w , -raw For encrypted datasets, send data exactly as it exists on disk. -This allows backups to be taken even if encryption keys are not currently loaded. +This allows backups to be taken even if encryption keys are not currently +loaded. The backup may then be received on an untrusted machine since that machine will not have the encryption keys to read the protected data or alter it without being detected. @@ -386,7 +389,8 @@ If the .Sy lz4_compress feature is active on the sending system, then the receiving system must have that feature enabled as well. -Datasets that are sent with this flag may not be received as an encrypted dataset, +Datasets that are sent with this flag may not be received as an encrypted +dataset, since encrypted datasets cannot use the .Sy embedded_data feature. @@ -445,7 +449,7 @@ included in the redaction list contained in the bookmark specified by the flag. The resulting send stream is said to be redacted with respect to the snapshots the bookmark specified by the -.Fl -redact No flag was created with. +.Fl -redact No flag was created with . The bookmark must have been created by running .Nm zfs Cm redact on the snapshot being sent. @@ -629,7 +633,8 @@ snapshots themselves. In order to make the purpose of the feature more clear, an example is provided. Consider a zfs filesystem containing four files. These files represent information for an online shopping service. -One file contains a list of usernames and passwords, another contains purchase histories, +One file contains a list of usernames and passwords, another contains purchase +histories, a third contains click tracking data, and a fourth contains user preferences. The owner of this data wants to make it available for their development teams to test against, and their market research teams to do analysis on. @@ -641,7 +646,8 @@ However, because all of this data is stored in one ZFS filesystem, it must all be sent and received together. In addition, the owner of the data wants to take advantage of features like compression, checksumming, and -snapshots, so they do want to continue to use ZFS to store and transmit their data. +snapshots, so they do want to continue to use ZFS to store and transmit their +data. Redaction can help them do so. First, they would make two clones of a snapshot of the data on the source. In one clone, they create the setup they want their market research team to see; @@ -654,7 +660,8 @@ They would then create a redaction bookmark on the parent snapshot, using snapshots on the two clones as redaction snapshots. The parent can then be sent, redacted, to the target server where the research and development teams have access. -Finally, incremental sends from the parent snapshot to each of the clones can be sent +Finally, incremental sends from the parent snapshot to each of the clones can be +sent to and received on the target server; these snapshots are identical to the ones on the source, and are ready to be used, while the parent snapshot on the target contains none of the username and password data present on the source, |