Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect interrupted transfers for raw targets #75

Closed
digint opened this issue Mar 22, 2016 · 1 comment
Closed

Detect interrupted transfers for raw targets #75

digint opened this issue Mar 22, 2016 · 1 comment

Comments

@digint
Copy link
Owner

digint commented Mar 22, 2016

btrbk does not detect interrupted transfers of raw targets (other than filesize==0).

While btrbk is not able to check the integrity of raw targets (as there is no tool that does only checks on a send-stream without writing it into a subvolume), btrbk should at least detect interrupted transfers.

A simple way to achieve this is to write to xxx.btrfs.part, and only move it to xxx.btrfs on success. This would also allow btrfs clean to identify and delete partial transfers, as well as btrfs list backups to mark them as "incomplete".

@digint
Copy link
Owner Author

digint commented Mar 22, 2016

implemented in: 7bb1805

@digint digint closed this as completed Apr 17, 2016
digint added a commit that referenced this issue Apr 28, 2016
Version 0.23.0

Read "doc/upgrade_to_v0.23.0.md" if updating from btrbk-v0.22.0.

Please read the updated description of the "run" command in btrbk(1),
as well as the "RETENTION POLICY" section in btrbk.conf(5) for a
detailed description of the new functionality.

    man doc/btrbk.1
    man doc/btrbk.conf.5

After updating your configuration, make sure no important backups get
deleted before doing the real run and run:

    btrbk --print-schedule dryrun

ChangeLog:

  * INCOMPATIBLE CONFIGURATION:
    * Please read "doc/upgrade_to_v0.23.0.md" for details on updating
      the configuration file (/etc/btrbk/btrbk.conf).
    * Dropped "btrfs_progs_compat" option. Need btrfs-progs >= v3.18.
    * Removed "resume_missing" configuration option.
  * Create backups only if needed to satisfy retention policy.
  * Preserve FIRST backup of hour/day/week/month instead of LAST.
  * Replaced "{snapshot,target}_preserve_{daily,weekly,monthly}"
    configuration options with "{snapshot,target}_preserve_min" and
    "{snapshot,target}_preserve NNh NNd NNw NNm NNy" options.
  * Added hourly/yearly retention policies (close: #36, #69).
  * Allow regular directories for send-receive targets (close: #77).
  * Allow wildcards in subvolume section (close: #71).
  * Propagate targets defined in "volume" or "root" context to all
    "subvolume" sections (close: #78).
  * Added "archive" command (close: #79).
  * Changed output format of "origin" command, add table formats.
  * Added configuration option "rate_limit" (close: #72).
  * Added new timestamp_format "long-iso", having a timezone postfix.
  * Added "--print-schedule" command line option.
  * Detect interrupted transfers of raw targets (close: #75).
  * Always read "readonly" flag (additional call to btrfs-progs).
  * Warn on receive targets at unexpected location (instead of abort).
  * On incremental send/receive, use all snapshots sharing same
    parent_uuid as candidates for "-p <parent>" instead of only older
    snapshots. As last resort, use subvolumes in snapshot_dir matching
    btrbk file name scheme as candidates (which allows incremental
    backups after the parent vanished, e.g. after backup restore).
  * Use perl built-in Time::Local instead of Date::Calc.
  * Improvements of internal data structures.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant