2019-09-29 19:04:53 +02:00
.. include :: global.rst.inc
2018-10-11 17:46:26 +02:00
.. |break_config| replace :: **[CONFIG]**
2018-02-17 20:48:31 +01:00
.. |break| replace :: **[BREAK]**
2017-11-12 14:12:57 +01:00
.. |bugfix| replace :: [BUG]
2018-04-01 14:53:44 +02:00
.. |docs| replace :: [DOCS]
2018-02-17 20:48:31 +01:00
.. |feature| replace :: [FEATURE]
2019-03-19 17:43:28 +01:00
.. |mig| replace :: **[MIGRATION]**
2021-03-14 20:56:02 +01:00
.. |maint| replace :: [MAINT]
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
.. _changelog:
2017-11-12 14:12:57 +01:00
Changelog
=========
2018-10-11 17:46:26 +02:00
The changelog summarizes bugfixes that are deemed relevant for users and package maintainers.
2017-11-12 14:12:57 +01:00
Developers should consult the git commit log or GitHub issue tracker.
2022-10-25 00:42:28 +02:00
Next Release
------------
The plan for the next release is to revisit how zrepl does snapshot management.
High-level goals:
- Make it easy to decouple snapshot management (snapshotting, pruning) from replication.
- Ability to include/exclude snapshots from replication.
This is useful for aforementioned decoupling, e.g., separate snapshot prefixes for local & remote replication.
Also, it makes explicit that by default, zrepl replicates all snapshots, and that
replication has no concept of "zrepl-created snapshots", which is a common misconception.
- Use of `` zfs snapshot `` comma syntax or channel programs to take snapshots of multiple
datasets atomically.
- Provide an alternative to the `` grid `` pruning policy.
Most likely something based on hourly/daily/weekly/monthly "trains" plus a count.
- Ability to prune at the granularity of the **group** of snapshots created at a given
time, as opposed to the individual snapshots within a dataset.
Maybe this will be addressed by the alternative to the `` grid `` pruning policy,
as it will likely be more predictable.
Those changes will likely come with some breakage in the config.
However, I want to avoid breaking **use cases** that are satisfied by the current design.
There will be beta/RC releases to give users a chance to evaluate.
2023-09-08 14:54:11 +02:00
0.6.1
-----
* |feature| add metric to detect filesystems rules that don't match any local dataset (thanks, `@gmekicaxcient <https://github.com/gmekicaxcient> `_ ).
* |bugfix| `` zrepl status `` : hide progress bar once all filesystems reach terminal state (thanks, `@0x3333 <https://github.com/0x3333> `_ ).
* |bugfix| handling of tenative cursor presence if protection strategy doesn't use it (:issue: `714` ).
* |docs| address setup with two or more external disks (thanks, `@se-jaeger <https://github.com/se-jaeger> `_ ).
* |docs| document `` replication `` and `` conflict_resolution `` options (thanks, `@InsanePrawn <https://github.com/InsanePrawn> `_ ).
* |docs| docs: talks: add note on keep_bookmarks option (thanks, `@skirmess <https://github.com/skirmess> `_ ).
* |maint| dist: add openrc service file (thanks, `@gramosg <https://github.com/gramosg> `_ ).
* |maint| grafana: update dashboard to Grafana 9.3.6.
* |maint| run platform tests as part of CI.
* |maint| build: upgrade to Go 1.21 and update golangci-lint; minimum Go version for builds is now 1.20
.. NOTE ::
| zrepl is a spare-time project primarily developed by `Christian Schwarz <https://cschwarz.com> `_ .
| You can support maintenance and feature development through one of the following services:
| |Donate via Patreon| |Donate via GitHub Sponsors| |Donate via Liberapay| |Donate via PayPal|
| Note that PayPal processing fees are relatively high for small donations.
| For SEPA wire transfer and **commercial support** , please `contact Christian directly <https://cschwarz.com> `_ .
2022-10-25 00:22:32 +02:00
0.6
---
2022-01-12 16:52:58 +01:00
2022-04-12 01:26:41 +02:00
* |feature| :ref: `Schedule-based snapshotting<job-snapshotting--cron>` using `` cron `` syntax instead of an interval.
2022-10-25 00:22:32 +02:00
* |feature| Configurable initial replication policy.
When a filesystem is first replicated to a receiver, this control whether just the newest
snapshot will be replicated vs. all existing snapshots. Learn more :ref: `in the docs <conflict_resolution-initial_replication>` .
* |feature| Configurable timestamp format for snapshot names via :ref: `timestamp_format<job-snapshotting-timestamp_format>`
(Thanks, `@ydylla <https://github.com/ydylla> `_ ).
* |feature| Add `` ZREPL_DESTROY_MAX_BATCH_SIZE `` env var (default 0=unlimited)
(Thanks, `@3nprob <https://github.com/3nprob> `_ ).
* |feature| Add `` zrepl configcheck --skip-cert-check `` flag (Thanks, `@cole-h <https://github.com/cole-h> `_ ).
rework resume token validation to allow resuming from raw sends of unencrypted datasets
Before this change, resuming from an unencrypted dataset with
send.raw=true specified wouldn't work with zrepl due to overly
restrictive resume token checking.
An initial PR to fix this was made in https://github.com/zrepl/zrepl/pull/503
but it didn't address the core of the problem.
The core of the problem was that zrepl assumed that if a resume token
contained `rawok=true, compressok=true`, the resulting send would be
encrypted. But if the sender dataset was unencrypted, such a resume would
actually result in an unencrypted send.
Which could be totally legitimate but zrepl failed to recognize that.
BACKGROUND
==========
The following snippets of OpenZFS code are insightful regarding how the
various ${X}ok values in the resume token are handled:
- https://github.com/openzfs/zfs/blob/6c3c5fcfbe27d9193cd131753cc7e47ee2784621/module/zfs/dmu_send.c#L1947-L2012
- https://github.com/openzfs/zfs/blob/6c3c5fcfbe27d9193cd131753cc7e47ee2784621/module/zfs/dmu_recv.c#L877-L891
- https://github.com/openzfs/zfs/blob/6c3c5fc/lib/libzfs/libzfs_sendrecv.c#L1663-L1672
Basically, some zfs send flags make the DMU send code set some DMU send
stream featureflags, although it's not a pure mapping, i.e, which DMU
send stream flags are used depends somewhat on the dataset (e.g., is it
encrypted or not, or, does it use zstd or not).
Then, the receiver looks at some (but not all) feature flags and maps
them to ${X}ok dataset zap attributes.
These are funnelled back to the sender 1:1 through the resume_token.
And the sender turns them into lzc flags.
As an example, let's look at zfs send --raw.
if the sender requests a raw send on an unencrypted dataset, the send
stream (and hence the resume token) will not have the raw stream
featureflag set, and hence the resume token will not have the rawok
field set. Instead, it will have compressok, embedok, and depending
on whether large blocks are present in the dataset, largeblockok set.
WHAT'S ZREPL'S ROLE IN THIS?
============================
zrepl provides a virtual encrypted sendflag that is like `raw`,
but further ensures that we only send encrypted datasets.
For any other resume token stuff, it shoudn't do any checking,
because it's a futile effort to keep up with ZFS send/recv features
that are orthogonal to encryption.
CHANGES MADE IN THIS COMMIT
===========================
- Rip out a bunch of needless checking that zrepl would do during
planning. These checks were there to give better error messages,
but actually, the error messages created by the endpoint.Sender.Send
RPC upon send args validation failure are good enough.
- Add platformtests to validate all combinations of
(Unencrypted/Encrypted FS) x (send.encrypted = true | false) x (send.raw = true | false)
for cases both non-resuming and resuming send.
Additional manual testing done:
1. With zrepl 0.5, setup with unencrypted dataset, send.raw=true specified, no send.encrypted specified.
2. Observe that regular non-resuming send works, but resuming doesn't work.
3. Upgrade zrepl to this change.
4. Observe that both regular and resuming send works.
closes https://github.com/zrepl/zrepl/pull/613
2022-07-10 14:56:35 +02:00
* |bugfix| Fix resuming from interrupted replications that use `` send.raw `` on unencrypted datasets.
* The send options introduced in zrepl 0.4 allow users to specify additional zfs send flags for zrepl to use.
Before this fix, when setting `` send.raw=true `` on a job that replicates unencrypted datasets,
zrepl would not allow an interrupted replication to resume.
The reason were overly cautious checks to support the `` send.encrypted `` option.
* This bugfix removes these checks from the replication planner.
This makes `` send.encrypted `` a sender-side-only concern, much like all other `` send.* `` flags.
* However, this means that the `` zrepl status `` UI no longer indicates whether a replication step uses encrypted sends or not.
The setting is still effective though.
2022-10-25 00:22:32 +02:00
* |break| convert Prometheus metric `` zrepl_version_daemon `` to `` zrepl_start_time `` metric
2022-01-12 16:52:58 +01:00
* The metric still reports the zrepl version in a label.
But the metric *value* is now the Unix timestamp at the time the daemon was started.
The Grafana dashboard in :repomasterlink: `dist/grafana` has been updated.
2022-06-26 14:19:54 +02:00
* |bugfix| transient zrepl status error: `` Post "http://unix/status": EOF ``
2022-07-18 10:09:50 +02:00
* |bugfix| don't treat receive-side bookmarks as a replication conflict.
This facilitates chaining of replication jobs. See :issue: `490` .
2022-10-25 00:22:32 +02:00
* |bugfix| workaround for Go/gRPC problem on Illumos where zrepl would
crash when using the `` local `` transport type (:issue: `598` ).
* |bugfix| fix active child tasks panic that cold occur during replication plannig (:issue: `193abbe` )
* |bugfix| `` zrepl status `` off-by-one error in display of completed step count (:commit: `ce6701f` )
* |bugfix| Allow using day & week units for `` snapshotting.interval `` (:commit: `ffb1d89` )
* |docs| `` docs/overview `` improvements (Thanks, `@jtagcat <https://github.com/jtagcat> `_ ).
* |maint| Update to Go 1.19.
2022-06-26 14:19:54 +02:00
2021-11-10 18:49:10 +01:00
0.5
---
2021-12-18 17:19:59 +01:00
* |feature| :ref: `Bandwidth limiting <job-send-recv-options--bandwidth-limit>` (Thanks, Prominic.NET, Inc.)
* |feature| zrepl status: use a `` * `` to indicate which filesystem is currently replicating
* |feature| include daemon environment variables in zrepl status (currently only in `` --raw `` )
* |bugfix| **fix encrypt-on-receive + placeholders use case** (:issue: `504` )
* Before this fix, **plain sends** to a receiver with an encrypted `` root_fs `` **could be received unencrypted** if zrepl needed to create placeholders on the receiver.
* Existing zrepl users should :ref: `read the docs <job-recv-options--placeholder>` and check `` zfs get -r encryption,zrepl:placeholder PATH_TO_ROOTFS `` on the receiver.
* Thanks to `@mologie <https://github.com/mologie> `_ and `@razielgn <https://github.com/razielgn> `_ for reporting and testing!
* |bugfix| Rename mis-spelled :ref: `send option <job-send-options>` `` embbeded_data `` to `` embedded_data `` .
* |bugfix| zrepl status: replication step numbers should start at 1
* |bugfix| incorrect bandwidth averaging in `` zrepl status `` .
* |bugfix| FreeBSD with OpenZFS 2.0: zrepl would wait indefinitely for zfs send to exit on timeouts.
* |bugfix| fix `` strconv.ParseInt: value out of range `` bug (and use the control RPCs).
* |docs| improve description of multiple pruning rules.
* |docs| document :ref: `platform tests <usage-platform-tests>` .
* |docs| quickstart: make users aware that prune rules apply to all snapshots.
* |maint| some platformtests were broken.
* |maint| FreeBSD: release armv7 and arm64 binaries.
* |maint| apt repo: update instructions due to `` apt-key `` deprecation.
Note to all users: please read up on the following OpenZFS bugs, as you might be affected:
* `ZFS send/recv with ashift 9->12 leads to data corruption <https://github.com/openzfs/zfs/issues/12762> `_ .
* Various bugs with encrypted send/recv (`Leadership meeting notes <https://openzfs.topicbox.com/groups/developer/T24bdaa2886c6cbf5-Mc039a11c3f1507ea0664817b/december-openzfs-leadership-meeting> `_ )
Finally, I'd like to point you to the `GitHub discussion <https://github.com/zrepl/zrepl/discussions/547> `_ about which bugfixes and features should be prioritized in zrepl 0.6 and beyond!
2021-01-01 23:32:35 +01:00
0.4.0
-----
2021-03-14 20:56:02 +01:00
* |feature| support setting zfs send / recv flags in the config (send: `` -wLcepbS `` , recv: `` -ox `` ).
Config docs :ref: `here <job-send-options>` and :ref: `here <job-recv-options>` .
* |feature| parallel replication is now configurable (disabled by default, :ref: `config docs here <replication-option-concurrency>` ).
2020-03-27 20:37:17 +01:00
* |feature| New `` zrepl status `` UI:
* Interactive job selection.
* Interactively `` zrepl signal `` jobs.
* Filter filesystems in the job view by name.
* An approximation of the old UI is still included as `--mode legacy` but will be removed in a future release of zrepl.
2021-01-01 23:32:35 +01:00
2021-03-14 20:56:02 +01:00
* |bugfix| Actually use concurrency when listing zrepl abstractions & doing size estimation.
These operations were accidentally made sequential in zrepl 0.3.
* |bugfix| Job hang-up during second replication attempt.
* |bugfix| Data races conditions in the dataconn rpc stack.
* |maint| Update to protobuf v1.25 and grpc 1.35.
2021-03-14 21:13:26 +01:00
For users who skipped the 0.3.1 update: please make sure your pruning grid config is correct.
The following bugfix in 0.3.1 :issue: `caused problems for some users <400>` :
* |bugfix| pruning: `` grid `` : add all snapshots that do not match the regex to the rule's destroy list.
2020-11-01 14:19:03 +01:00
0.3.1
-----
Mostly a bugfix release for :ref: `zrepl 0.3 <release-0.3>` .
* |feature| pruning: add optional `` regex `` field to `` last_n `` rule
* |docs| pruning: `` grid `` : improve documentation and add an example
* |bugfix| pruning: `` grid `` : add all snapshots that do not match the regex to the rule's destroy list.
This brings the implementation in line with the docs.
* |bugfix| `` easyrsa `` script in docs
* |bugfix| platformtest: fix skipping encryption-only tests on systems that don't support encryption
* |bugfix| replication: report AttemptDone if no filesystems are replicated
* |feature| status + replication: warning if replication succeeeded without any filesystem being replicated
* |docs| update multi-job & multi-host setup section
* RPM Packaging
* CI infrastructure rework
* Continuous deployment of that new `stable` branch to zrepl.github.io.
.. _release-0.3:
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
0.3
---
2019-12-30 19:42:17 +01:00
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
This is a big one! Headlining features:
* **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
2020-06-01 21:21:42 +02:00
* **Encrypted Send & Recv Support** for OpenZFS native encryption,
:ref: `configurable <job-send-options>` at the job level, i.e., for all filesystems a job is responsible for.
2020-06-27 23:53:33 +02:00
* **Replication Guarantees**
Automatic use of ZFS holds and bookmarks to protect a replicated filesystem from losing synchronization between sender and receiver.
By default, zrepl guarantees that incremental replication will always be possible and interrupted steps will always be resumable.
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
2020-06-01 21:21:42 +02:00
.. TIP ::
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
2020-06-27 23:53:33 +02:00
We highly recommend studying the updated :ref: `overview section of the configuration chapter <overview-how-replication-works>` to understand how replication works.
2020-08-22 02:51:09 +02:00
.. TIP ::
Go 1.15 changed the default TLS validation policy to **require Subject Alternative Names (SAN) in certificates** .
The openssl commands we provided in the quick-start guides up to and including the zrepl 0.3 docs seem not to work properly.
If you encounter certificate validation errors regarding SAN and wish to continue to use your old certificates, start the zrepl daemon with env var `` GODEBUG=x509ignoreCN=0 `` .
Alternatively, generate new certificates with SANs (see :ref: `both options int the TLS transport docs <transport-tcp+tlsclientauth-certgen>` ).
2020-06-27 23:53:33 +02:00
Quick-start guides:
* We have added :ref: `another quick-start guide for a typical workstation use case for zrepl <quickstart-backup-to-external-disk>` .
Check it out to learn how you can use zrepl to back up your workstation's OpenZFS natively-encrypted root filesystem to an external disk.
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
2020-06-01 21:21:42 +02:00
Additional changelog:
2020-08-22 02:51:09 +02:00
* |break| Go 1.15 TLS changes mentioned above.
2020-06-01 21:21:42 +02:00
* |break| |break_config| **more restrictive job names than in prior zrepl versions**
2020-06-27 23:53:33 +02:00
Starting with this version, job names are going to be embedded into ZFS holds and bookmark names (see :ref: `this section for details <zrepl-zfs-abstractions>` ).
2020-06-01 21:21:42 +02:00
Therefore you might need to adjust your job names.
2020-06-22 12:30:42 +02:00
**Note that jobs** cannot be renamed easily **once you start using zrepl 0.3.**
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
* |break| |mig| replication cursor representation changed
2020-06-27 23:53:33 +02:00
* zrepl now manages the :ref: `replication cursor bookmark <zrepl-zfs-abstractions>` per job-filesystem tuple instead of a single replication cursor per filesystem.
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
In the future, this will permit multiple sending jobs to send from the same filesystems.
* ZFS does not allow bookmark renaming, thus we cannot migrate the old replication cursors.
* zrepl 0.3 will automatically create cursors in the new format for new replications, and warn if it still finds ones in the old format.
* Run `` zrepl migrate replication-cursor:v1-v2 `` to safely destroy old-format cursors.
The migration will ensure that only those old-format cursors are destroyed that have been superseeded by new-format cursors.
2020-06-01 21:23:03 +02:00
* |feature| New option `` listen_freebind `` (tcp, tls, prometheus listener)
2020-08-04 01:17:38 +02:00
* |feature| :issue: `341` Prometheus metric for failing replications + corresponding Grafana panel
2020-06-14 18:29:37 +02:00
* |feature| :issue: `265` transport/tcp: support for CIDR masks in client IP whitelist
2020-06-01 21:23:03 +02:00
* |feature| documented subcommand to generate `` bash `` and `` zsh `` completions
2020-06-14 18:29:37 +02:00
* |feature| :issue: `307` `` chrome://trace `` -compatible activity tracing of zrepl daemon activity
2020-06-01 21:23:03 +02:00
* |feature| logging: trace IDs for better log entry correlation with concurrent replication jobs
2020-06-14 18:29:37 +02:00
* |feature| experimental environment variable for parallel replication (see :issue: `306` )
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
* |bugfix| missing logger context vars in control connection handlers
* |bugfix| improved error messages on `` zfs send `` errors
2020-01-15 19:12:31 +01:00
* |bugfix| |docs| snapshotting: clarify sync-up behavior and warn about filesystems
2020-06-01 21:23:03 +02:00
* |bugfix| transport/ssh: do not leak zombie ssh process on connection failures
2020-01-15 19:12:31 +01:00
that will not be snapshotted until the sync-up phase is over
2020-06-01 21:23:03 +02:00
* |docs| Installation: :ref: `FreeBSD jail with iocage <installation-freebsd-jail-with-iocage>`
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold
- **Resumable Send & Recv Support**
No knobs required, automatically used where supported.
- **Hold-Protected Send & Recv**
Automatic ZFS holds to ensure that we can always resume a replication step.
- **Encrypted Send & Recv Support** for OpenZFS native encryption.
Configurable at the job level, i.e., for all filesystems a job is responsible for.
- **Receive-side hold on last received dataset**
The counterpart to the replication cursor bookmark on the send-side.
Ensures that incremental replication will always be possible between a sender and receiver.
Design Doc
----------
`replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable.
The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc).
We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc.
This might BREAK CONFIG on upgrade.
Protocol Version Bump
---------------------
This commit makes backwards-incompatible changes to the replication/pdu protobufs.
Thus, bump the version number used in the protocol handshake.
Replication Cursor Format Change
--------------------------------
The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}`
Including the GUID enables transaction-safe moving-forward of the cursor.
Including the job id enables that multiple sending jobs can send the same filesystem without interfering.
The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors.
Changes in This Commit
----------------------
- package zfs
- infrastructure for holds
- infrastructure for resume token decoding
- implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code
- ZFSSendArgs to specify a ZFS send operation
- validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`)
- RecvOptions support for `recv -s` flag
- convert a bunch of ZFS operations to be idempotent
- achieved through more differentiated error message scraping / additional pre-/post-checks
- package replication/pdu
- add field for encryption to send request messages
- add fields for resume handling to send & recv request messages
- receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into
- can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream)
- used to set `last-received-hold`
- package replication/logic
- introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender
- integrate encryption and resume token support into `Step` struct
- package endpoint
- move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go`
- step-holds + step-bookmarks
- last-received-hold
- new replication cursor + old replication cursor compat code
- adjust `endpoint/endpoint.go` handlers for
- encryption
- resumability
- new replication cursor
- last-received-hold
- client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it
- client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
* |docs| Document new replication features in the :ref: `config overview <overview-how-replication-works>` and :repomasterlink: `replication/design.md` .
* **[MAINTAINER NOTICE]** New platform tests in this version, please make sure you run them for your distro!
2020-04-18 19:09:49 +02:00
* **[MAINTAINER NOTICE]** Please add the shell completions to the zrepl packages.
2019-12-30 19:42:17 +01:00
2019-11-20 20:16:41 +01:00
0.2.1
-----
* |feature| Illumos (and Solaris) compatibility and binary builds (thanks, `MNX.io <https://mnx.io> `_ )
* |feature| 32bit binaries for Linux and FreeBSD (untested, though)
* |bugfix| better error messages in `` ssh+stdinserver `` transport
* |bugfix| systemd + `` ssh+stdinserver `` : automatically create `` /var/run/zrepl/stdinserver ``
* |bugfix| crash if Prometheus listening socket cannot be opened
* [MAINTAINER NOTICE] `` Makefile `` refactoring, see :commit: `080f2c0`
2019-09-28 17:50:07 +02:00
0.2
---
2019-06-23 12:10:52 +02:00
2019-07-26 21:12:21 +02:00
* |feature| :ref: `Pre- and Post-Snapshot Hooks <job-snapshotting-hooks>`
with built-in support for MySQL and Postgres checkpointing
2019-09-28 17:50:07 +02:00
as well as custom scripts (thanks, `@overhacked <https://github.com/overhacked> `_ !)
* |feature| Use `` zfs destroy pool/fs@snap1,snap2,... `` CLI feature if available
* |feature| Linux ARM64 Docker build support & binary builds
* |feature| `` zrepl status `` now displays snapshotting reports
* |feature| `` zrepl status --job <JOBNAME> `` filter flag
* |bugfix| i386 build
* |bugfix| early validation of host:port tuples in config
* |bugfix| `` zrepl status `` now supports `` TERM=screen `` (tmux on FreeBSD / FreeNAS)
* |bugfix| ignore *connection reset by peer* errors when shutting down connections
* |bugfix| correct error messages when receive-side pool or `` root_fs `` dataset is not imported
* |bugfix| fail fast for misconfigured local transport
* |bugfix| race condition in replication report generation would crash the daemon when running `` zrepl status ``
* |bugfix| rpc goroutine leak in `` push `` mode if zfs recv fails on the `` sink `` side
* [MAINTAINER NOTICE] Go modules for dependency management both inside and outside of GOPATH
(`` lazy.sh `` and `` Makefile `` force `` GO111MODULE=on `` )
2019-09-29 18:44:59 +02:00
* [MAINTAINER NOTICE] `` make platformtest `` target to check zrepl's ZFS abstractions (screen scraping, etc.).
These tests only work on a system with ZFS installed, and must be run as root because they create a file-backed pool for each test case.
The pool name `` zreplplatformtest `` is reserved for this use case.
Only run `` make platformtest `` on test systems, e.g. a FreeBSD VM image.
2019-06-23 12:10:52 +02:00
2019-04-06 12:36:06 +02:00
0.1.1
-----
* |bugfix| :issue: `162` :commit: `d6304f4` : fix I/O timeout errors on variable receive rate
* A significant reduction or sudden stall of the receive rate (e.g. recv pool has other I/O to do)
would cause a `` writev I/O timeout `` error after approximately ten seconds.
2018-10-13 17:35:38 +02:00
0.1
---
2018-02-17 20:48:31 +01:00
2018-10-11 17:46:26 +02:00
This release is a milestone for zrepl and required significant refactoring if not rewrites of substantial parts of the application.
It breaks both configuration and transport format, and thus requires manual intervention and updates on both sides of a replication setup.
2018-02-17 20:48:31 +01:00
2018-10-13 18:29:40 +02:00
.. DANGER ::
The changes in the pruning system for this release require you to explicitly define **keep rules** :
for any snapshot that you want to keep, at least one rule must match.
This is different from previous releases where pruning only affected snapshots with the configured snapshotting prefix.
Make sure that snapshots to be kept or ignored by zrepl are covered, e.g. by using the `` regex `` keep rule.
:ref: `Learn more in the config docs... <prune>`
2018-10-13 16:26:23 +02:00
Notes to Package Maintainers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2018-02-17 20:48:31 +01:00
2019-03-30 18:50:51 +01:00
* Notify users about config changes and migrations (see changes attributed with |break| and |mig| below)
2018-10-11 17:46:26 +02:00
* If the daemon crashes, the stack trace produced by the Go runtime and possibly diagnostic output of zrepl will be written to stderr.
This behavior is independent from the `` stdout `` outlet type.
2018-10-22 11:27:00 +02:00
Please make sure the stderr output of the daemon is captured somewhere.
2018-10-11 17:46:26 +02:00
To conserve precious stack traces, make sure that multiple service restarts do not directly discard previous stderr output.
* Make it obvious for users how to set the `` GOTRACEBACK `` environment variable to `` GOTRACEBACK=crash `` .
This functionality will cause SIGABRT on panics and can be used to capture a coredump of the panicking process.
To that extend, make sure that your package build system, your OS's coredump collection and the Go delve debugger work together.
Use your build system to package the Go program in `this tutorial on Go coredumps and the delve debugger <https://rakyll.org/coredumps/> `_ , and make sure the symbol resolution etc. work on coredumps captured from the binary produced by your build system. (Special focus on symbol stripping, etc.)
2019-03-30 18:50:51 +01:00
* Consider using the `` zrepl configcheck `` subcommand in startup scripts to abort a restart that would fail due to an invalid config.
2018-03-04 17:19:41 +01:00
2018-10-11 17:46:26 +02:00
Changes
~~~~~~~
2018-03-04 17:19:41 +01:00
2019-03-19 17:43:28 +01:00
* |break| |mig| Placeholder property representation changed
* The :ref: `placeholder property <replication-placeholder-property>` now uses `` on|off `` as values
instead of hashes of the dataset path. This permits renames of the sink filesystem without
updating all placeholder properties.
* Relevant for 0.0.X-0.1-rc* to 0.1 migrations
* Make sure your config is valid with `` zrepl configcheck ``
* Run `` zrepl migrate 0.0.X:0.1:placeholder ``
2018-10-11 17:46:26 +02:00
* |feature| :issue: `55` : Push replication (see :ref: `push job <job-push>` and :ref: `sink job <job-sink>` )
* |feature| :ref: `TCP Transport <transport-tcp>`
* |feature| :ref: `TCP + TLS client authentication transport <transport-tcp+tlsclientauth>`
2019-03-18 12:30:19 +01:00
* |feature| :issue: `111` : RPC protocol rewrite
2018-02-18 13:35:40 +01:00
2019-03-18 12:30:19 +01:00
* |break| Protocol breakage; Update and restart of all zrepl daemons is required.
* Use `gRPC <https://grpc.io/> `_ for control RPCs and a custom protocol for bulk data transfer.
* Automatic retries for network-temporary errors
2018-02-18 13:35:40 +01:00
2019-03-18 12:30:19 +01:00
* Limited to errors during replication for this release.
Addresses the common problem of ISP-forced reconnection at night, but will become
way more useful with resumable send & recv support.
Pruning errors are handled per FS, i.e., a prune RPC is attempted at least once per FS.
* |feature| Proper timeout handling for the :ref: `SSH transport <transport-ssh+stdinserver>`
* |break| Requires Go 1.11 or later.
2022-05-19 13:32:37 +02:00
2019-03-18 12:30:19 +01:00
* |break| |break_config|: mappings are no longer supported
* Receiving sides (`` pull `` and `` sink `` job) specify a single `` root_fs `` .
Received filesystems are then stored *per client* in `` ${root_fs}/${client_identity} `` .
See :ref: `job-overview` for details.
2018-02-18 13:35:40 +01:00
2018-10-11 17:46:26 +02:00
* |feature| |break| |break_config| Manual snapshotting + triggering of replication
2018-02-18 13:35:40 +01:00
2018-10-11 17:46:26 +02:00
* |feature| :issue: `69` : include manually created snapshots in replication
* |break_config| `` manual `` and `` periodic `` :ref: `snapshotting types <job-snapshotting-spec>`
2018-10-22 11:27:00 +02:00
* |feature| `` zrepl signal wakeup JOB `` subcommand to trigger replication + pruning
* |feature| `` zrepl signal reset JOB `` subcommand to abort current replication + pruning
2018-02-18 13:28:46 +01:00
2018-10-11 17:46:26 +02:00
* |feature| |break| |break_config| New pruning system
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
* The active side of a replication (pull or push) decides what to prune for both sender and receiver.
The RPC protocol is used to execute the destroy operations on the remote side.
* New pruning policies (see :ref: `configuration documentation <prune>` )
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
* The decision what snapshots shall be pruned is now made based on *keep rules*
* |feature| :issue: `68` : keep rule `` not_replicated `` prevents divergence of sender and receiver
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
* |feature| |break| Bookmark pruning is no longer necessary
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
* Per filesystem, zrepl creates a single bookmark (`` #zrepl_replication_cursor `` ) and moves it forward with the most recent successfully replicated snapshot on the receiving side.
2018-10-22 11:27:00 +02:00
* Old bookmarks created by prior versions of zrepl (named like their corresponding snapshot) must be deleted manually.
2018-10-11 17:46:26 +02:00
* |break_config| `` keep_bookmarks `` parameter of the `` grid `` keep rule has been removed
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
* |feature| `` zrepl status `` for live-updating replication progress (it's really cool!)
2019-03-18 14:53:12 +01:00
* |feature| :ref: `Snapshot- & pruning-only job type <job-snap>` (for local snapshot management)
2018-10-11 17:46:26 +02:00
* |feature| :issue: `67` : Expose `Prometheus <https://prometheus.io> `_ metrics via HTTP (:ref: `config docs <monitoring-prometheus>` )
2017-11-12 14:12:57 +01:00
2019-03-18 12:45:27 +01:00
* Compatible Grafana dashboard shipping in `` dist/grafana ``
2018-10-11 17:46:26 +02:00
* |break_config| Logging outlet types must be specified using the `` type `` instead of `` outlet `` key
* |break| :issue: `53` : CLI: `` zrepl control * `` subcommands have been made direct subcommands of `` zrepl * ``
2018-10-13 16:26:23 +02:00
* |bugfix| Goroutine leak on ssh transport connection timeouts
2018-10-11 17:46:26 +02:00
* |bugfix| :issue: `81` :issue: `77` : handle failed accepts correctly (`` source `` job)
2019-03-18 12:46:16 +01:00
* |bugfix| :issue: `100` : fix incompatibility with ZoL 0.8
* |feature| :issue: `115` : logging: configurable syslog facility
2019-03-18 12:45:27 +01:00
* |feature| Systemd unit file in `` dist/systemd ``
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
.. |lastrelease| replace :: 0.0.3
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
Previous Releases
-----------------
2017-11-12 14:12:57 +01:00
2018-10-11 17:46:26 +02:00
.. NOTE ::
Due to limitations in our documentation system, we only show the changelog since the last release and the time this documentation is built.
For the changelog of previous releases, use the version selection in the hosted version of these docs at `zrepl.github.io <https://zrepl.github.io> `_ .