Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/spelling/expect.txt
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ buildpackage
Bzip
canmount
CBuilder
ccache
cdn
cfg
cgi
Expand Down
12 changes: 11 additions & 1 deletion bin/znapzendzetup
Original file line number Diff line number Diff line change
Expand Up @@ -658,7 +658,7 @@ and where 'command' and its unique options is one of the following:

=head1 DESCRIPTION

Use znapzendsetup to configure your backup tasks. The cli is modled after
Use znapzendsetup to configure your backup tasks. The cli is modeled after
the zfs commandline.

After modifying the configuration, send a HUP signal to your znapzend daemon
Expand Down Expand Up @@ -748,6 +748,16 @@ a different pool) or remote.
When adding multiple B<DST> entries, each will get labeled for later
identification, optionally you can specify your own label.

By default, you can enable the backup schedule for a particular dataset,
however it is often more useful to enable B<--recursive> mode to cover
any child datasets (including those that appear later). To exclude some
sub-trees from backup, you can set B<enabled=off> on those descendant
datasets (technically, a recursive snapshot will be made for the parent,
and then those for excluded datasets removed before sending increments
to the destination). For example, this can be useful to recursively
backup all home directories starting from B<rpool/export/home> and then
avoid backing up locations like a certain user's B<.ccache> directory.

=over

=item B<--tsformat>=I<limited-strftime-format>
Expand Down
Loading