Job Types in Detail
Job Type push
Parameter |
Comment |
---|---|
|
= |
|
unique name of the job (must not change) |
|
|
|
filter specification for filesystems to be snapshotted and pushed to the sink |
|
send options, e.g. for encrypted sends |
|
|
|
Example config: config/samples/push.yml
Job Type sink
Parameter |
Comment |
---|---|
|
= |
|
unique name of the job (must not change) |
|
|
|
ZFS filesystems are received to
|
Example config: config/samples/sink.yml
Job Type pull
Parameter |
Comment |
---|---|
|
= |
|
unique name of the job (must not change) |
|
|
|
ZFS filesystems are received to
|
|
Interval at which to pull from the source job (e.g.
10m ).manual disables periodic pulling, replication then only happens on wakeup. |
|
Example config: config/samples/pull.yml
Job Type source
Parameter |
Comment |
---|---|
|
= |
|
unique name of the job (must not change) |
|
|
|
filter specification for filesystems to be snapshotted and exposed to connecting clients |
|
send options, e.g. for encrypted sends |
|
Example config: config/samples/source.yml
Local replication
If you have the need for local replication (most likely between two local storage pools), you can use the local transport type to connect a local push job to a local sink job.
Example config: config/samples/local.yml.
Job Type snap
(snapshot & prune only)
Job type that only takes snapshots and performs pruning on the local machine.
Parameter |
Comment |
---|---|
|
= |
|
unique name of the job (must not change) |
|
filter specification for filesystems to be snapshotted |
|
|
|
Example config: config/samples/snap.yml