octoleo/restic
2
2
Fork 0
mirror of https://github.com/octoleo/restic.git synced 2024-12-23 19:38:57 +00:00
Code Issues Releases Wiki Activity
c6fd13425b
restic/CHANGELOG.md
Gurjeet Singh 34a6a24544 Use S3's proper product name, Amazon S3 
Per Amazon's product page [1], S3 is officially called "Amazon S3". The
restic project uses the phrase "AWS S3" in some places. This patch
corrects the product name.

[1]:https://aws.amazon.com/s3/
2021-11-13 22:21:06 +01:00

141 KiB
Raw Blame History

Changelog for restic 0.12.1 (2021-08-03)

The following sections list the changes in restic 0.12.1 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #2742: Improve error handling for rclone and REST backend over HTTP2
  • Fix #3111: Fix terminal output redirection for PowerShell
  • Fix #3214: Treat an empty password as a fatal error for repository init
  • Fix #3267: copy failed to copy snapshots in rare cases
  • Fix #3184: backup --quiet no longer prints status information
  • Fix #3296: Fix crash of check --read-data-subset=x% run for an empty repository
  • Fix #3302: Fix fdopendir: not a directory error for local backend
  • Fix #3334: Print created new cache message only on a terminal
  • Fix #3380: Fix crash of backup --exclude='**'
  • Fix #3305: Fix possibly missing backup summary of JSON output in case of error
  • Fix #3439: Correctly handle download errors during restore
  • Chg #3247: Empty files now have size of 0 in ls --json output
  • Enh #2780: Add release binaries for s390x architecture on Linux
  • Enh #3293: Add --repository-file2 option to init and copy command
  • Enh #3312: Add auto-completion support for fish
  • Enh #3336: SFTP backend now checks for disk space
  • Enh #3377: Add release binaries for Apple Silicon
  • Enh #3414: Add --keep-within-hourly option to restic forget
  • Enh #3456: Support filtering and specifying untagged snapshots
  • Enh #3167: Allow specifying limit of snapshots list
  • Enh #3426: Optimize read performance of mount command
  • Enh #3427: find --pack fallback to index if data file is missing

Details

Changelog for restic 0.12.0 (2021-02-14)

The following sections list the changes in restic 0.12.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1681: Make mount not create missing mount point directory
  • Fix #1800: Ignore no data available filesystem error during backup
  • Fix #2563: Report the correct owner of directories in FUSE mounts
  • Fix #2688: Make backup and tag commands separate tags by comma
  • Fix #2739: Make the cat command respect the --no-lock option
  • Fix #3087: The --use-fs-snapshot option now works on windows/386
  • Fix #3100: Do not require gs bucket permissions when running init
  • Fix #3111: Correctly detect output redirection for backup command on Windows
  • Fix #3151: Don't create invalid snapshots when backup is interrupted
  • Fix #3166: Improve error handling in the restore command
  • Fix #3232: Correct statistics for overlapping targets
  • Fix #3014: Fix sporadic stream reset between rclone and restic
  • Fix #3152: Do not hang until foregrounded when completed in background
  • Fix #3249: Improve error handling in gs backend
  • Chg #3095: Deleting files on Google Drive now moves them to the trash
  • Enh #2186: Allow specifying percentage in check --read-data-subset
  • Enh #2453: Report permanent/fatal backend errors earlier
  • Enh #2528: Add Alibaba/Aliyun OSS support in the s3 backend
  • Enh #2706: Configurable progress reports for non-interactive terminals
  • Enh #2944: Add backup options --files-from-{verbatim,raw}
  • Enh #3083: Allow usage of deprecated S3 ListObjects API
  • Enh #3147: Support additional environment variables for Swift authentication
  • Enh #3191: Add release binaries for MIPS architectures
  • Enh #909: Back up mountpoints as empty directories
  • Enh #3250: Add several more error checks
  • Enh #2718: Improve prune performance and make it more customizable
  • Enh #2495: Add option to let backup trust mtime without checking ctime
  • Enh #2941: Speed up the repacking step of the prune command
  • Enh #3006: Speed up the rebuild-index command
  • Enh #3048: Add more checks for index and pack files in the check command
  • Enh #2433: Make the dump command support zip format
  • Enh #3099: Reduce memory usage of check command
  • Enh #3106: Parallelize scan of snapshot content in copy and prune
  • Enh #3130: Parallelize reading of locks and snapshots
  • Enh #3254: Enable HTTP/2 for backend connections

Details

  • Bugfix #1681: Make mount not create missing mount point directory

    When specifying a non-existent directory as mount point for the mount command, restic used to create the specified directory automatically.

    This has now changed such that restic instead gives an error when the specified directory for the mount point does not exist.

    https://github.com/restic/restic/issues/1681 https://github.com/restic/restic/pull/3008

  • Bugfix #1800: Ignore no data available filesystem error during backup

    Restic was unable to backup files on some filesystems, for example certain configurations of CIFS on Linux which return a no data available error when reading extended attributes. These errors are now ignored.

    https://github.com/restic/restic/issues/1800 https://github.com/restic/restic/pull/3034

  • Bugfix #2563: Report the correct owner of directories in FUSE mounts

    Restic 0.10.0 changed the FUSE mount to always report the current user as the owner of directories within the FUSE mount, which is incorrect.

    This is now changed back to reporting the correct owner of a directory.

    https://github.com/restic/restic/issues/2563 https://github.com/restic/restic/pull/3141

  • Bugfix #2688: Make backup and tag commands separate tags by comma

    Running restic backup --tag foo,bar previously created snapshots with one single tag containing a comma (foo,bar) instead of two tags (foo, bar).

    Similarly, the tag command's --set, --add and --remove options would treat foo,bar as one tag instead of two tags. This was inconsistent with other commands and often unexpected when one intended foo,bar to mean two tags.

    To be consistent in all commands, restic now interprets foo,bar to mean two separate tags (foo and bar) instead of one tag (foo,bar) everywhere, including in the backup and tag commands.

    NOTE: This change might result in unexpected behavior in cases where you use the forget command and filter on tags like foo,bar. Snapshots previously backed up with --tag foo,bar will still not match that filter, but snapshots saved from now on will match that filter.

    To replace foo,bar tags with foo and bar tags in old snapshots, you can first generate a list of the relevant snapshots using a command like:

    Restic snapshots --json --quiet | jq '.[] | select(contains({tags: ["foo,bar"]})) | .id'

    And then use restic tag --set foo --set bar snapshotID [...] to set the new tags. Please adjust the commands to include real tag names and any additional tags, as well as the list of snapshots to process.

    https://github.com/restic/restic/issues/2688 https://github.com/restic/restic/pull/2690 https://github.com/restic/restic/pull/3197

  • Bugfix #2739: Make the cat command respect the --no-lock option

    The cat command would not respect the --no-lock flag. This is now fixed.

    https://github.com/restic/restic/issues/2739

  • Bugfix #3087: The --use-fs-snapshot option now works on windows/386

    Restic failed to create VSS snapshots on windows/386 with the following error:

    GetSnapshotProperties() failed: E_INVALIDARG (0x80070057)

    This is now fixed.

    https://github.com/restic/restic/issues/3087 https://github.com/restic/restic/pull/3090

  • Bugfix #3100: Do not require gs bucket permissions when running init

    Restic used to require bucket level permissions for the gs backend in order to initialize a restic repository.

    It now allows a gs service account to initialize a repository if the bucket does exist and the service account has permissions to write/read to that bucket.

    https://github.com/restic/restic/issues/3100

  • Bugfix #3111: Correctly detect output redirection for backup command on Windows

    On Windows, since restic 0.10.0 the backup command did not properly detect when the output was redirected to a file. This caused restic to output terminal control characters. This has been fixed by correcting the terminal detection.

    https://github.com/restic/restic/issues/3111 https://github.com/restic/restic/pull/3150

  • Bugfix #3151: Don't create invalid snapshots when backup is interrupted

    When canceling a backup run at a certain moment it was possible that restic created a snapshot with an invalid "null" tree. This caused check and other operations to fail. The backup command now properly handles interruptions and never saves a snapshot when interrupted.

    https://github.com/restic/restic/issues/3151 https://github.com/restic/restic/pull/3164

  • Bugfix #3166: Improve error handling in the restore command

    The restore command used to not print errors while downloading file contents from the repository. It also incorrectly exited with a zero error code even when there were errors during the restore process. This has all been fixed and restore now returns with a non-zero exit code when there's an error.

    https://github.com/restic/restic/issues/3166 https://github.com/restic/restic/pull/3207

  • Bugfix #3232: Correct statistics for overlapping targets

    A user reported that restic's statistics and progress information during backup was not correctly calculated when the backup targets (files/dirs to save) overlap. For example, consider a directory foo which contains (among others) a file foo/bar. When restic backup foo foo/bar was run, restic counted the size of the file foo/bar twice, so the completeness percentage as well as the number of files was wrong. This is now corrected.

    https://github.com/restic/restic/issues/3232 https://github.com/restic/restic/pull/3243

  • Bugfix #3014: Fix sporadic stream reset between rclone and restic

    Sometimes when using restic with the rclone backend, an error message similar to the following would be printed:

    Didn't finish writing GET request (wrote 0/xxx): http2: stream closed

    It was found that this was caused by restic closing the connection to rclone to soon when downloading data. A workaround has been added which waits for the end of the download before closing the connection.

    https://github.com/rclone/rclone/issues/2598 https://github.com/restic/restic/pull/3014

  • Bugfix #3152: Do not hang until foregrounded when completed in background

    On Linux, when running in the background restic failed to stop the terminal output of the backup command after it had completed. This caused restic to hang until moved to the foreground. This has now been fixed.

    https://github.com/restic/restic/pull/3152 https://forum.restic.net/t/restic-alpine-container-cron-hangs-epoll-pwait/3334

  • Bugfix #3249: Improve error handling in gs backend

    The gs backend did not notice when the last step of completing a file upload failed. Under rare circumstances, this could cause missing files in the backup repository. This has now been fixed.

    https://github.com/restic/restic/pull/3249

  • Change #3095: Deleting files on Google Drive now moves them to the trash

    When deleting files on Google Drive via the rclone backend, restic used to bypass the trash folder required that one used the -o rclone.args option to enable usage of the trash folder. This ensured that deleted files in Google Drive were not kept indefinitely in the trash folder. However, since Google Drive's trash retention policy changed to deleting trashed files after 30 days, this is no longer needed.

    Restic now leaves it up to rclone and its configuration to use or not use the trash folder when deleting files. The default is to use the trash folder, as of rclone 1.53.2. To re-enable the restic 0.11 behavior, set the RCLONE_DRIVE_USE_TRASH environment variable or change the rclone configuration. See the rclone documentation for more details.

    https://github.com/restic/restic/issues/3095 https://github.com/restic/restic/pull/3102

  • Enhancement #2186: Allow specifying percentage in check --read-data-subset

    We've enhanced the check command's --read-data-subset option to also accept a percentage (e.g. 2.5% or 10%). This will check the given percentage of pack files (which are randomly selected on each run).

    https://github.com/restic/restic/issues/2186 https://github.com/restic/restic/pull/3038

  • Enhancement #2453: Report permanent/fatal backend errors earlier

    When encountering errors in reading from or writing to storage backends, restic retries the failing operation up to nine times (for a total of ten attempts). It used to retry all backend operations, but now detects some permanent error conditions so that it can report fatal errors earlier.

    Permanent failures include local disks being full, SSH connections dropping and permission errors.

    https://github.com/restic/restic/issues/2453 https://github.com/restic/restic/issues/3180 https://github.com/restic/restic/pull/3170 https://github.com/restic/restic/pull/3181

  • Enhancement #2528: Add Alibaba/Aliyun OSS support in the s3 backend

    A new extended option s3.bucket-lookup has been added to support Alibaba/Aliyun OSS in the s3 backend. The option can be set to one of the following values:

    • auto - Existing behaviour - dns - Use DNS style bucket access - path - Use path style bucket access

    To make the s3 backend work with Alibaba/Aliyun OSS you must set s3.bucket-lookup to dns and set the s3.region parameter. For example:

    Restic -o s3.bucket-lookup=dns -o s3.region=oss-eu-west-1 -r s3:https://oss-eu-west-1.aliyuncs.com/bucketname init

    Note that s3.region must be set, otherwise the MinIO SDK tries to look it up and it seems that Alibaba doesn't support that properly.

    https://github.com/restic/restic/issues/2528 https://github.com/restic/restic/pull/2535

  • Enhancement #2706: Configurable progress reports for non-interactive terminals

    The backup, check and prune commands never printed any progress reports on non-interactive terminals. This behavior is now configurable using the RESTIC_PROGRESS_FPS environment variable. Use for example a value of 1 for an update every second, or 0.01666 for an update every minute.

    The backup command now also prints the current progress when restic receives a SIGUSR1 signal.

    Setting the RESTIC_PROGRESS_FPS environment variable or sending a SIGUSR1 signal prints a status report even when --quiet was specified.

    https://github.com/restic/restic/issues/2706 https://github.com/restic/restic/issues/3194 https://github.com/restic/restic/pull/3199

  • Enhancement #2944: Add backup options --files-from-{verbatim,raw}

    The new backup options --files-from-verbatim and --files-from-raw read a list of files to back up from a file. Unlike the existing --files-from option, these options do not interpret the listed filenames as glob patterns; instead, whitespace in filenames is preserved as-is and no pattern expansion is done. Please see the documentation for specifics.

    These new options are highly recommended over --files-from, when using a script to generate the list of files to back up.

    https://github.com/restic/restic/issues/2944 https://github.com/restic/restic/issues/3013

  • Enhancement #3083: Allow usage of deprecated S3 ListObjects API

    Some S3 API implementations, e.g. Ceph before version 14.2.5, have a broken ListObjectsV2 implementation which causes problems for restic when using their API endpoints. When a broken server implementation is used, restic prints errors similar to the following:

    List() returned error: Truncated response should have continuation token set

    As a temporary workaround, restic now allows using the older ListObjects endpoint by setting the s3.list-objects-v1 extended option, for instance:

    Restic -o s3.list-objects-v1=true snapshots

    Please note that this option may be removed in future versions of restic.

    https://github.com/restic/restic/issues/3083 https://github.com/restic/restic/pull/3085

  • Enhancement #3147: Support additional environment variables for Swift authentication

    The swift backend now supports the following additional environment variables for passing authentication details to restic: OS_USER_ID, OS_USER_DOMAIN_ID, OS_PROJECT_DOMAIN_ID and OS_TRUST_ID

    Depending on the openrc configuration file these might be required when the user and project domains differ from one another.

    https://github.com/restic/restic/issues/3147 https://github.com/restic/restic/pull/3158

  • Enhancement #3191: Add release binaries for MIPS architectures

    We've added a few new architectures for Linux to the release binaries: mips, mipsle, mips64, and mip64le. MIPS is mostly used for low-end embedded systems.

    https://github.com/restic/restic/issues/3191 https://github.com/restic/restic/pull/3208

  • Enhancement #909: Back up mountpoints as empty directories

    When the --one-file-system option is specified to restic backup, it ignores all file systems mounted below one of the target directories. This means that when a snapshot is restored, users needed to manually recreate the mountpoint directories.

    Restic now backs up mountpoints as empty directories and therefore implements the same approach as tar.

    https://github.com/restic/restic/issues/909 https://github.com/restic/restic/pull/3119

  • Enhancement #3250: Add several more error checks

    We've added a lot more error checks in places where errors were previously ignored (as hinted by the static analysis program errcheck via golangci-lint).

    https://github.com/restic/restic/pull/3250

  • Enhancement #2718: Improve prune performance and make it more customizable

    The prune command is now much faster. This is especially the case for remote repositories or repositories with not much data to remove. Also the memory usage of the prune command is now reduced.

    Restic used to rebuild the index from scratch after pruning. This could lead to missing packs in the index in some cases for eventually consistent backends such as e.g. Amazon S3. This behavior is now changed and the index rebuilding uses the information already known by prune.

    By default, the prune command no longer removes all unused data. This behavior can be fine-tuned by new options, like the acceptable amount of unused space or the maximum size of data to reorganize. For more details, please see https://restic.readthedocs.io/en/stable/060_forget.html .

    Moreover, prune now accepts the --dry-run option and also running forget --dry-run --prune will show what prune would do.

    This enhancement also fixes several open issues, e.g.: - https://github.com/restic/restic/issues/1140 - https://github.com/restic/restic/issues/1599 - https://github.com/restic/restic/issues/1985 - https://github.com/restic/restic/issues/2112 - https://github.com/restic/restic/issues/2227 - https://github.com/restic/restic/issues/2305

    https://github.com/restic/restic/pull/2718 https://github.com/restic/restic/pull/2842

  • Enhancement #2495: Add option to let backup trust mtime without checking ctime

    The backup command used to require that both ctime and mtime of a file matched with a previously backed up version to determine that the file was unchanged. In other words, if either ctime or mtime of the file had changed, it would be considered changed and restic would read the file's content again to back up the relevant (changed) parts of it.

    The new option --ignore-ctime makes restic look at mtime only, such that ctime changes for a file does not cause restic to read the file's contents again.

    The check for both ctime and mtime was introduced in restic 0.9.6 to make backups more reliable in the face of programs that reset mtime (some Unix archivers do that), but it turned out to often be expensive because it made restic read file contents even if only the metadata (owner, permissions) of a file had changed. The new --ignore-ctime option lets the user restore the 0.9.5 behavior when needed. The existing --ignore-inode option already turned off this behavior, but also removed a different check.

    Please note that changes in files' metadata are still recorded, regardless of the command line options provided to the backup command.

    https://github.com/restic/restic/issues/2495 https://github.com/restic/restic/issues/2558 https://github.com/restic/restic/issues/2819 https://github.com/restic/restic/pull/2823

  • Enhancement #2941: Speed up the repacking step of the prune command

    The repack step of the prune command, which moves still used file parts into new pack files such that the old ones can be garbage collected later on, now processes multiple pack files in parallel. This is especially beneficial for high latency backends or when using a fast network connection.

    https://github.com/restic/restic/pull/2941

  • Enhancement #3006: Speed up the rebuild-index command

    We've optimized the rebuild-index command. Now, existing index entries are used to minimize the number of pack files that must be read. This speeds up the index rebuild a lot.

    Additionally, the option --read-all-packs has been added, implementing the previous behavior.

    https://github.com/restic/restic/pull/3006 https://github.com/restic/restic/issue/2547

  • Enhancement #3048: Add more checks for index and pack files in the check command

    The check command run with the --read-data or --read-data-subset options used to only verify only the pack file content - it did not check if the blobs within the pack are correctly contained in the index.

    A check for the latter is now in place, which can print the following error:

    Blob ID is not contained in index or position is incorrect

    Another test is also added, which compares pack file sizes computed from the index and the pack header with the actual file size. This test is able to detect truncated pack files.

    If the index is not correct, it can be rebuilt by using the rebuild-index command.

    Having added these tests, restic check is now able to detect non-existing blobs which are wrongly referenced in the index. This situation could have lead to missing data.

    https://github.com/restic/restic/pull/3048 https://github.com/restic/restic/pull/3082

  • Enhancement #2433: Make the dump command support zip format

    Previously, restic could dump the contents of a whole folder structure only in the tar format. The dump command now has a new flag to change output format to zip. Just pass --archive zip as an option to restic dump.

    https://github.com/restic/restic/pull/2433 https://github.com/restic/restic/pull/3081

  • Enhancement #3099: Reduce memory usage of check command

    The check command now requires less memory if it is run without the --check-unused option.

    https://github.com/restic/restic/pull/3099

  • Enhancement #3106: Parallelize scan of snapshot content in copy and prune

    The copy and prune commands used to traverse the directories of snapshots one by one to find used data. This snapshot traversal is now parallized which can speed up this step several times.

    In addition the check command now reports how many snapshots have already been processed.

    https://github.com/restic/restic/pull/3106

  • Enhancement #3130: Parallelize reading of locks and snapshots

    Restic used to read snapshots sequentially. For repositories containing many snapshots this slowed down commands which have to read all snapshots.

    Now the reading of snapshots is parallelized. This speeds up for example prune, backup and other commands that search for snapshots with certain properties or which have to find the latest snapshot.

    The speed up also applies to locks stored in the backup repository.

    https://github.com/restic/restic/pull/3130 https://github.com/restic/restic/pull/3174

  • Enhancement #3254: Enable HTTP/2 for backend connections

    Go's HTTP library usually automatically chooses between HTTP/1.x and HTTP/2 depending on what the server supports. But for compatibility this mechanism is disabled if DialContext is used (which is the case for restic). This change allows restic's HTTP client to negotiate HTTP/2 if supported by the server.

    https://github.com/restic/restic/pull/3254

Changelog for restic 0.11.0 (2020-11-05)

The following sections list the changes in restic 0.11.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1212: Restore timestamps and permissions on intermediate directories
  • Fix #1756: Mark repository files as read-only when using the local backend
  • Fix #2241: Hide password in REST backend repository URLs
  • Fix #2319: Correctly dump directories into tar files
  • Fix #2491: Don't require self-update --output placeholder file
  • Fix #2834: Fix rare cases of backup command hanging forever
  • Fix #2938: Fix manpage formatting
  • Fix #2942: Make --exclude-larger-than handle disappearing files
  • Fix #2951: Restic generate, help and self-update no longer check passwords
  • Fix #2979: Make snapshots --json output [] instead of null when no snapshots
  • Enh #2969: Optimize check for unchanged files during backup
  • Enh #340: Add support for Volume Shadow Copy Service (VSS) on Windows
  • Enh #2849: Authenticate to Google Cloud Storage with access token
  • Enh #1458: New option --repository-file
  • Enh #2978: Warn if parent snapshot cannot be loaded during backup

Details

Changelog for restic 0.10.0 (2020-09-19)

The following sections list the changes in restic 0.10.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1863: Report correct number of directories processed by backup
  • Fix #2254: Fix tar issues when dumping /
  • Fix #2281: Handle format verbs like '%' properly in find output
  • Fix #2298: Do not hang when run as a background job
  • Fix #2389: Fix mangled json output of backup command
  • Fix #2390: Refresh lock timestamp
  • Fix #2429: Backup --json reports total_bytes_processed as 0
  • Fix #2469: Fix incorrect bytes stats in diff command
  • Fix #2518: Do not crash with Synology NAS sftp server
  • Fix #2531: Fix incorrect size calculation in stats --mode restore-size
  • Fix #2537: Fix incorrect file counts in stats --mode restore-size
  • Fix #2592: SFTP backend supports IPv6 addresses
  • Fix #2607: Honor RESTIC_CACHE_DIR environment variable on Mac and Windows
  • Fix #2668: Don't abort the stats command when data blobs are missing
  • Fix #2674: Add stricter prune error checks
  • Fix #2899: Fix possible crash in the progress bar of check --read-data
  • Chg #2482: Remove vendored dependencies
  • Chg #2546: Return exit code 3 when failing to backup all source data
  • Chg #2600: Update dependencies, require Go >= 1.13
  • Chg #1597: Honor the --no-lock flag in the mount command
  • Enh #1570: Support specifying multiple host flags for various commands
  • Enh #1680: Optimize restic mount
  • Enh #2072: Display snapshot date when using restic find
  • Enh #2175: Allow specifying user and host when creating keys
  • Enh #2277: Add support for ppc64le
  • Enh #2395: Ignore sync errors when operation not supported by local filesystem
  • Enh #2427: Add flag --iexclude-file to backup command
  • Enh #2569: Support excluding files by their size
  • Enh #2571: Self-heal missing file parts during backup of unchanged files
  • Enh #2858: Support filtering snapshots by tag and path in the stats command
  • Enh #323: Add command for copying snapshots between repositories
  • Enh #551: Use optimized library for hash calculation of file chunks
  • Enh #2195: Simplify and improve restore performance
  • Enh #2328: Improve speed of check command
  • Enh #2423: Support user@domain parsing as user
  • Enh #2576: Improve the chunking algorithm
  • Enh #2598: Improve speed of diff command
  • Enh #2599: Slightly reduce memory usage of prune and stats commands
  • Enh #2733: S3 backend: Add support for WebIdentityTokenFile
  • Enh #2773: Optimize handling of new index entries
  • Enh #2781: Reduce memory consumption of in-memory index
  • Enh #2786: Optimize list blobs command
  • Enh #2790: Optimized file access in restic mount
  • Enh #2840: Speed-up file deletion in forget, prune and rebuild-index

Details

Changelog for restic 0.9.6 (2019-11-22)

The following sections list the changes in restic 0.9.6 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #2063: Allow absolute path for filename when backing up from stdin
  • Fix #2174: Save files with invalid timestamps
  • Fix #2249: Read fresh metadata for unmodified files
  • Fix #2301: Add upper bound for t in --read-data-subset=n/t
  • Fix #2321: Check errors when loading index files
  • Enh #2179: Use ctime when checking for file changes
  • Enh #2306: Allow multiple retries for interactive password input
  • Enh #2330: Make --group-by accept both singular and plural
  • Enh #2350: Add option to configure S3 region

Details

  • Bugfix #2063: Allow absolute path for filename when backing up from stdin

    When backing up from stdin, handle directory path for --stdin-filename. This can be used to specify the full path for the backed-up file.

    https://github.com/restic/restic/issues/2063

  • Bugfix #2174: Save files with invalid timestamps

    When restic reads invalid timestamps (year is before 0000 or after 9999) it refused to read and archive the file. We've changed the behavior and will now save modified timestamps with the year set to either 0000 or 9999, the rest of the timestamp stays the same, so the file will be saved (albeit with a bogus timestamp).

    https://github.com/restic/restic/issues/2174 https://github.com/restic/restic/issues/1173

  • Bugfix #2249: Read fresh metadata for unmodified files

    Restic took all metadata for files which were detected as unmodified, not taking into account changed metadata (ownership, mode). This is now corrected.

    https://github.com/restic/restic/issues/2249 https://github.com/restic/restic/pull/2252

  • Bugfix #2301: Add upper bound for t in --read-data-subset=n/t

    256 is the effective maximum for t, but restic would allow larger values, leading to strange behavior.

    https://github.com/restic/restic/issues/2301 https://github.com/restic/restic/pull/2304

  • Bugfix #2321: Check errors when loading index files

    Restic now checks and handles errors which occur when loading index files, the missing check leads to odd errors (and a stack trace printed to users) later. This was reported in the forum.

    https://github.com/restic/restic/pull/2321 https://forum.restic.net/t/check-rebuild-index-prune/1848/13

  • Enhancement #2179: Use ctime when checking for file changes

    Previously, restic only checked a file's mtime (along with other non-timestamp metadata) to decide if a file has changed. This could cause restic to not notice that a file has changed (and therefore continue to store the old version, as opposed to the modified version) if something edits the file and then resets the timestamp. Restic now also checks the ctime of files, so any modifications to a file should be noticed, and the modified file will be backed up. The ctime check will be disabled if the --ignore-inode flag was given.

    If this change causes problems for you, please open an issue, and we can look in to adding a seperate flag to disable just the ctime check.

    https://github.com/restic/restic/issues/2179 https://github.com/restic/restic/pull/2212

  • Enhancement #2306: Allow multiple retries for interactive password input

    Restic used to quit if the repository password was typed incorrectly once. Restic will now ask the user again for the repository password if typed incorrectly. The user will now get three tries to input the correct password before restic quits.

    https://github.com/restic/restic/issues/2306

  • Enhancement #2330: Make --group-by accept both singular and plural

    One can now use the values host/hosts, path/paths and tag / tags interchangeably in the --group-by argument.

    https://github.com/restic/restic/issues/2330

  • Enhancement #2350: Add option to configure S3 region

    We've added a new option for setting the region when accessing an S3-compatible service. For some providers, it is required to set this to a valid value. You can do that either by setting the environment variable AWS_DEFAULT_REGION or using the option s3.region, e.g. like this: -o s3.region="us-east-1".

    https://github.com/restic/restic/pull/2350

Changelog for restic 0.9.5 (2019-04-23)

The following sections list the changes in restic 0.9.5 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #2135: Return error when no bytes could be read from stdin
  • Fix #2181: Don't cancel timeout after 30 seconds for self-update
  • Fix #2203: Fix reading passwords from stdin
  • Fix #2224: Don't abort the find command when a tree can't be loaded
  • Enh #1895: Add case insensitive include & exclude options
  • Enh #1937: Support streaming JSON output for backup
  • Enh #2155: Add Openstack application credential auth for Swift
  • Enh #2184: Add --json support to forget command
  • Enh #2037: Add group-by option to snapshots command
  • Enh #2124: Ability to dump folders to tar via stdout
  • Enh #2139: Return error if no bytes could be read for backup --stdin
  • Enh #2205: Add --ignore-inode option to backup cmd
  • Enh #2220: Add config option to set S3 storage class

Details

  • Bugfix #2135: Return error when no bytes could be read from stdin

    We assume that users reading backup data from stdin want to know when no data could be read, so now restic returns an error when backup --stdin is called but no bytes could be read. Usually, this means that an earlier command in a pipe has failed. The documentation was amended and now recommends setting the pipefail option (set -o pipefail).

    https://github.com/restic/restic/pull/2135 https://github.com/restic/restic/pull/2139

  • Bugfix #2181: Don't cancel timeout after 30 seconds for self-update

    https://github.com/restic/restic/issues/2181

  • Bugfix #2203: Fix reading passwords from stdin

    Passwords for the init, key add, and key passwd commands can now be read from non-terminal stdin.

    https://github.com/restic/restic/issues/2203

  • Bugfix #2224: Don't abort the find command when a tree can't be loaded

    Change the find command so that missing trees don't result in a crash. Instead, the error is logged to the debug log, and the tree ID is displayed along with the snapshot it belongs to. This makes it possible to recover repositories that are missing trees by forgetting the snapshots they are used in.

    https://github.com/restic/restic/issues/2224

  • Enhancement #1895: Add case insensitive include & exclude options

    The backup and restore commands now have --iexclude and --iinclude flags as case insensitive variants of --exclude and --include.

    https://github.com/restic/restic/issues/1895 https://github.com/restic/restic/pull/2032

  • Enhancement #1937: Support streaming JSON output for backup

    We've added support for getting machine-readable status output during backup, just pass the flag --json for restic backup and restic will output a stream of JSON objects which contain the current progress.

    https://github.com/restic/restic/issues/1937 https://github.com/restic/restic/pull/1944

  • Enhancement #2155: Add Openstack application credential auth for Swift

    Since Openstack Queens Identity (auth V3) service supports an application credential auth method. It allows to create a technical account with the limited roles. This commit adds an application credential authentication method for the Swift backend.

    https://github.com/restic/restic/issues/2155

  • Enhancement #2184: Add --json support to forget command

    The forget command now supports the --json argument, outputting the information about what is (or would-be) kept and removed from the repository.

    https://github.com/restic/restic/issues/2184 https://github.com/restic/restic/pull/2185

  • Enhancement #2037: Add group-by option to snapshots command

    We have added an option to group the output of the snapshots command, similar to the output of the forget command. The option has been called "--group-by" and accepts any combination of the values "host", "paths" and "tags", separated by commas. Default behavior (not specifying --group-by) has not been changed. We have added support of the grouping to the JSON output.

    https://github.com/restic/restic/issues/2037 https://github.com/restic/restic/pull/2087

  • Enhancement #2124: Ability to dump folders to tar via stdout

    We've added the ability to dump whole folders to stdout via the dump command. Restic now requires at least Go 1.10 due to a limitation of the standard library for Go <= 1.9.

    https://github.com/restic/restic/issues/2123 https://github.com/restic/restic/pull/2124

  • Enhancement #2139: Return error if no bytes could be read for backup --stdin

    When restic is used to backup the output of a program, like mysqldump | restic backup --stdin, it now returns an error if no bytes could be read at all. This catches the failure case when mysqldump failed for some reason and did not output any data to stdout.

    https://github.com/restic/restic/pull/2139

  • Enhancement #2205: Add --ignore-inode option to backup cmd

    This option handles backup of virtual filesystems that do not keep fixed inodes for files, like Fuse-based, pCloud, etc. Ignoring inode changes allows to consider the file as unchanged if last modification date and size are unchanged.

    https://github.com/restic/restic/issues/1631 https://github.com/restic/restic/pull/2205 https://github.com/restic/restic/pull/2047

  • Enhancement #2220: Add config option to set S3 storage class

    The s3.storage-class option can be passed to restic (using -o) to specify the storage class to be used for S3 objects created by restic.

    The storage class is passed as-is to S3, so it needs to be understood by the API. On AWS, it can be one of STANDARD, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING and REDUCED_REDUNDANCY. If unspecified, the default storage class is used (STANDARD on AWS).

    You can mix storage classes in the same bucket, and the setting isn't stored in the restic repository, so be sure to specify it with each command that writes to S3.

    https://github.com/restic/restic/issues/706 https://github.com/restic/restic/pull/2220

Changelog for restic 0.9.4 (2019-01-06)

The following sections list the changes in restic 0.9.4 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1989: Google Cloud Storage: Respect bandwidth limit
  • Fix #2040: Add host name filter shorthand flag for stats command
  • Fix #2068: Correctly return error loading data
  • Fix #2095: Consistently use local time for snapshots times
  • Enh #1605: Concurrent restore
  • Enh #2089: Increase granularity of the "keep within" retention policy
  • Enh #2097: Add key hinting
  • Enh #2017: Mount: Enforce FUSE Unix permissions with allow-other
  • Enh #2070: Make all commands display timestamps in local time
  • Enh #2085: Allow --files-from to be specified multiple times
  • Enh #2094: Run command to get password

Details

  • Bugfix #1989: Google Cloud Storage: Respect bandwidth limit

    The GCS backend did not respect the bandwidth limit configured, a previous commit accidentally removed support for it.

    https://github.com/restic/restic/issues/1989 https://github.com/restic/restic/pull/2100

  • Bugfix #2040: Add host name filter shorthand flag for stats command

    The default value for --host flag was set to 'H' (the shorthand version of the flag), this caused the lookup for the latest snapshot to fail.

    Add shorthand flag -H for --host (with empty default so if these flags are not specified the latest snapshot will not filter by host name).

    Also add shorthand -H for backup command.

    https://github.com/restic/restic/issues/2040

  • Bugfix #2068: Correctly return error loading data

    In one case during prune and check, an error loading data from the backend is not returned properly. This is now corrected.

    https://github.com/restic/restic/issues/1999#issuecomment-433737921 https://github.com/restic/restic/pull/2068

  • Bugfix #2095: Consistently use local time for snapshots times

    By default snapshots created with restic backup were set to local time, but when the --time flag was used the provided timestamp was parsed as UTC. With this change all snapshots times are set to local time.

    https://github.com/restic/restic/pull/2095

  • Enhancement #1605: Concurrent restore

    This change significantly improves restore performance, especially when using high-latency remote repositories like B2.

    The implementation now uses several concurrent threads to download and process multiple remote files concurrently. To further reduce restore time, each remote file is downloaded using a single repository request.

    https://github.com/restic/restic/issues/1605 https://github.com/restic/restic/pull/1719

  • Enhancement #2089: Increase granularity of the "keep within" retention policy

    The keep-within option of the forget command now accepts time ranges with an hourly granularity. For example, running restic forget --keep-within 3d12h will keep all the snapshots made within three days and twelve hours from the time of the latest snapshot.

    https://github.com/restic/restic/issues/2089 https://github.com/restic/restic/pull/2090

  • Enhancement #2097: Add key hinting

    Added a new option --key-hint and corresponding environment variable RESTIC_KEY_HINT. The key hint is a key ID to try decrypting first, before other keys in the repository.

    This change will benefit repositories with many keys; if the correct key hint is supplied then restic only needs to check one key. If the key hint is incorrect (the key does not exist, or the password is incorrect) then restic will check all keys, as usual.

    https://github.com/restic/restic/issues/2097

  • Enhancement #2017: Mount: Enforce FUSE Unix permissions with allow-other

    The fuse mount (restic mount) now lets the kernel check the permissions of the files within snapshots (this is done through the DefaultPermissions FUSE option) when the option --allow-other is specified.

    To restore the old behavior, we've added the --no-default-permissions option. This allows all users that have access to the mount point to access all files within the snapshots.

    https://github.com/restic/restic/pull/2017

  • Enhancement #2070: Make all commands display timestamps in local time

    Restic used to drop the timezone information from displayed timestamps, it now converts timestamps to local time before printing them so the times can be easily compared to.

    https://github.com/restic/restic/pull/2070

  • Enhancement #2085: Allow --files-from to be specified multiple times

    Before, restic took only the last file specified with --files-from into account, this is now corrected.

    https://github.com/restic/restic/issues/2085 https://github.com/restic/restic/pull/2086

  • Enhancement #2094: Run command to get password

    We've added the --password-command option which allows specifying a command that restic runs every time the password for the repository is needed, so it can be integrated with a password manager or keyring. The option can also be set via the environment variable $RESTIC_PASSWORD_COMMAND.

    https://github.com/restic/restic/pull/2094

Changelog for restic 0.9.3 (2018-10-13)

The following sections list the changes in restic 0.9.3 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1935: Remove truncated files from cache
  • Fix #1978: Do not return an error when the scanner is slower than backup
  • Enh #1766: Restore: suppress lchown errors when not running as root
  • Enh #1909: Reject files/dirs by name first
  • Enh #1940: Add directory filter to ls command
  • Enh #1967: Use --host everywhere
  • Enh #2028: Display size of cache directories
  • Enh #1777: Improve the find command
  • Enh #1876: Display reason why forget keeps snapshots
  • Enh #1891: Accept glob in paths loaded via --files-from
  • Enh #1920: Vendor dependencies with Go 1.11 Modules
  • Enh #1949: Add new command self-update
  • Enh #1953: Ls: Add JSON output support for restic ls cmd
  • Enh #1962: Stream JSON output for ls command

Details

  • Bugfix #1935: Remove truncated files from cache

    When a file in the local cache is truncated, and restic tries to access data beyond the end of the (cached) file, it used to return an error "EOF". This is now fixed, such truncated files are removed and the data is fetched directly from the backend.

    https://github.com/restic/restic/issues/1935

  • Bugfix #1978: Do not return an error when the scanner is slower than backup

    When restic makes a backup, there's a background task called "scanner" which collects information on how many files and directories are to be saved, in order to display progress information to the user. When the backup finishes faster than the scanner, it is aborted because the result is not needed any more. This logic contained a bug, where quitting the scanner process was treated as an error, and caused restic to print an unhelpful error message ("context canceled").

    https://github.com/restic/restic/issues/1978 https://github.com/restic/restic/pull/1991

  • Enhancement #1766: Restore: suppress lchown errors when not running as root

    Like "cp" and "rsync" do, restic now only reports errors for changing the ownership of files during restore if it is run as root, on non-Windows operating systems. On Windows, the error is reported as usual.

    https://github.com/restic/restic/issues/1766

  • Enhancement #1909: Reject files/dirs by name first

    The current scanner/archiver code had an architectural limitation: it always ran the lstat() system call on all files and directories before a decision to include/exclude the file/dir was made. This lead to a lot of unnecessary system calls for items that could have been rejected by their name or path only.

    We've changed the archiver/scanner implementation so that it now first rejects by name/path, and only runs the system call on the remaining items. This reduces the number of lstat() system calls a lot (depending on the exclude settings).

    https://github.com/restic/restic/issues/1909 https://github.com/restic/restic/pull/1912

  • Enhancement #1940: Add directory filter to ls command

    The ls command can now be filtered by directories, so that only files in the given directories will be shown. If the --recursive flag is specified, then ls will traverse subfolders and list their files as well.

    It used to be possible to specify multiple snapshots, but that has been replaced by only one snapshot and the possibility of specifying multiple directories.

    Specifying directories constrains the walk, which can significantly speed up the listing.

    https://github.com/restic/restic/issues/1940 https://github.com/restic/restic/pull/1941

  • Enhancement #1967: Use --host everywhere

    We now use the flag --host for all commands which need a host name, using --hostname (e.g. for restic backup) still works, but will print a deprecation warning. Also, add the short option -H where possible.

    https://github.com/restic/restic/issues/1967

  • Enhancement #2028: Display size of cache directories

    The cache command now by default shows the size of the individual cache directories. It can be disabled with --no-size.

    https://github.com/restic/restic/issues/2028 https://github.com/restic/restic/pull/2033

  • Enhancement #1777: Improve the find command

    We've updated the find command to support multiple patterns.

    restic find is now able to list the snapshots containing a specific tree or blob, or even the snapshots that contain blobs belonging to a given pack. A list of IDs can be given, as long as they all have the same type.

    The command find can also display the pack IDs the blobs belong to, if the --show-pack-id flag is provided.

    https://github.com/restic/restic/issues/1777 https://github.com/restic/restic/pull/1780

  • Enhancement #1876: Display reason why forget keeps snapshots

    We've added a column to the list of snapshots forget keeps which details the reasons to keep a particuliar snapshot. This makes debugging policies for forget much easier. Please remember to always try things out with --dry-run!

    https://github.com/restic/restic/pull/1876

  • Enhancement #1891: Accept glob in paths loaded via --files-from

    Before that, behaviour was different if paths were appended to command line or from a file, because wild card characters were expanded by shell if appended to command line, but not expanded if loaded from file.

    https://github.com/restic/restic/issues/1891

  • Enhancement #1920: Vendor dependencies with Go 1.11 Modules

    Until now, we've used dep for managing dependencies, we've now switch to using Go modules. For users this does not change much, only if you want to compile restic without downloading anything with Go 1.11, then you need to run: go build -mod=vendor build.go

    https://github.com/restic/restic/pull/1920

  • Enhancement #1949: Add new command self-update

    We have added a new command called self-update which downloads the latest released version of restic from GitHub and replaces the current binary with it. It does not rely on any external program (so it'll work everywhere), but still verifies the GPG signature using the embedded GPG public key.

    By default, the self-update command is hidden behind the selfupdate built tag, which is only set when restic is built using build.go (including official releases). The reason for this is that downstream distributions will then not include the command by default, so users are encouraged to use the platform-specific distribution mechanism.

    https://github.com/restic/restic/pull/1949

  • Enhancement #1953: Ls: Add JSON output support for restic ls cmd

    We've implemented listing files in the repository with JSON as output, just pass --json as an option to restic ls. This makes the output of the command machine readable.

    https://github.com/restic/restic/pull/1953

  • Enhancement #1962: Stream JSON output for ls command

    The ls command now supports JSON output with the global --json flag, and this change streams out JSON messages one object at a time rather than en entire array buffered in memory before encoding. The advantage is it allows large listings to be handled efficiently.

    Two message types are printed: snapshots and nodes. A snapshot object will precede node objects which belong to that snapshot. The struct_type field can be used to determine which kind of message an object is.

    https://github.com/restic/restic/pull/1962

Changelog for restic 0.9.2 (2018-08-06)

The following sections list the changes in restic 0.9.2 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1854: Allow saving files/dirs on different fs with --one-file-system
  • Fix #1870: Fix restore with --include
  • Fix #1880: Use --cache-dir argument for check command
  • Fix #1893: Return error when exclude file cannot be read
  • Fix #1861: Fix case-insensitive search with restic find
  • Enh #1906: Add support for B2 application keys
  • Enh #874: Add stats command to get information about a repository
  • Enh #1772: Add restore --verify to verify restored file content
  • Enh #1853: Add JSON output support to restic key list
  • Enh #1477: S3 backend: accept AWS_SESSION_TOKEN
  • Enh #1901: Update the Backblaze B2 library

Details

  • Bugfix #1854: Allow saving files/dirs on different fs with --one-file-system

    Restic now allows saving files/dirs on a different file system in a subdir correctly even when --one-file-system is specified.

    The first thing the restic archiver code does is to build a tree of the target files/directories. If it detects that a parent directory is already included (e.g. restic backup /foo /foo/bar/baz), it'll ignore the latter argument.

    Without --one-file-system, that's perfectly valid: If /foo is to be archived, it will include /foo/bar/baz. But with --one-file-system, /foo/bar/baz may reside on a different file system, so it won't be included with /foo.

    https://github.com/restic/restic/issues/1854 https://github.com/restic/restic/pull/1855

  • Bugfix #1870: Fix restore with --include

    We fixed a bug which prevented restic to restore files with an include filter.

    https://github.com/restic/restic/issues/1870 https://github.com/restic/restic/pull/1900

  • Bugfix #1880: Use --cache-dir argument for check command

    check command now uses a temporary sub-directory of the specified directory if set using the --cache-dir argument. If not set, the cache directory is created in the default temporary directory as before. In either case a temporary cache is used to ensure the actual repository is checked (rather than a local copy).

    The --cache-dir argument was not used by the check command, instead a cache directory was created in the temporary directory.

    https://github.com/restic/restic/issues/1880

  • Bugfix #1893: Return error when exclude file cannot be read

    A bug was found: when multiple exclude files were passed to restic and one of them could not be read, an error was printed and restic continued, ignoring even the existing exclude files. Now, an error message is printed and restic aborts when an exclude file cannot be read.

    https://github.com/restic/restic/issues/1893

  • Bugfix #1861: Fix case-insensitive search with restic find

    We've fixed the behavior for restic find -i PATTERN, which was broken in v0.9.1.

    https://github.com/restic/restic/pull/1861

  • Enhancement #1906: Add support for B2 application keys

    Restic can now use so-called "application keys" which can be created in the B2 dashboard and were only introduced recently. In contrast to the "master key", such keys can be restricted to a specific bucket and/or path.

    https://github.com/restic/restic/issues/1906 https://github.com/restic/restic/pull/1914

  • Enhancement #874: Add stats command to get information about a repository

    https://github.com/restic/restic/issues/874 https://github.com/restic/restic/pull/1729

  • Enhancement #1772: Add restore --verify to verify restored file content

    Restore will print error message if restored file content does not match expected SHA256 checksum

    https://github.com/restic/restic/pull/1772

  • Enhancement #1853: Add JSON output support to restic key list

    This PR enables users to get the output of restic key list in JSON in addition to the existing table format.

    https://github.com/restic/restic/pull/1853

  • Enhancement #1477: S3 backend: accept AWS_SESSION_TOKEN

    Before, it was not possible to use s3 backend with AWS temporary security credentials(with AWS_SESSION_TOKEN). This change gives higher priority to credentials.EnvAWS credentials provider.

    https://github.com/restic/restic/issues/1477 https://github.com/restic/restic/pull/1479 https://github.com/restic/restic/pull/1647

  • Enhancement #1901: Update the Backblaze B2 library

    We've updated the library we're using for accessing the Backblaze B2 service to 0.5.0 to include support for upcoming so-called "application keys". With this feature, you can create access credentials for B2 which are restricted to e.g. a single bucket or even a sub-directory of a bucket.

    https://github.com/restic/restic/pull/1901 https://github.com/kurin/blazer

Changelog for restic 0.9.1 (2018-06-10)

The following sections list the changes in restic 0.9.1 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1801: Add limiting bandwidth to the rclone backend
  • Fix #1822: Allow uploading large files to MS Azure
  • Fix #1825: Correct find to not skip snapshots
  • Fix #1833: Fix caching files on error
  • Fix #1834: Resolve deadlock

Details

  • Bugfix #1801: Add limiting bandwidth to the rclone backend

    The rclone backend did not respect --limit-upload or --limit-download. Oftentimes it's not necessary to use this, as the limiting in rclone itself should be used because it gives much better results, but in case a remote instance of rclone is used (e.g. called via ssh), it is still relevant to limit the bandwidth from restic to rclone.

    https://github.com/restic/restic/issues/1801

  • Bugfix #1822: Allow uploading large files to MS Azure

    Sometimes, restic creates files to be uploaded to the repository which are quite large, e.g. when saving directories with many entries or very large files. The MS Azure API does not allow uploading files larger that 256MiB directly, rather restic needs to upload them in blocks of 100MiB. This is now implemented.

    https://github.com/restic/restic/issues/1822

  • Bugfix #1825: Correct find to not skip snapshots

    Under certain circumstances, the find command was found to skip snapshots containing directories with files to look for when the directories haven't been modified at all, and were already printed as part of a different snapshot. This is now corrected.

    In addition, we've switched to our own matching/pattern implementation, so now things like restic find "/home/user/foo/**/main.go" are possible.

    https://github.com/restic/restic/issues/1825 https://github.com/restic/restic/issues/1823

  • Bugfix #1833: Fix caching files on error

    During check it may happen that different threads access the same file in the backend, which is then downloaded into the cache only once. When that fails, only the thread which is responsible for downloading the file signals the correct error. The other threads just assume that the file has been downloaded successfully and then get an error when they try to access the cached file.

    https://github.com/restic/restic/issues/1833

  • Bugfix #1834: Resolve deadlock

    When the "scanning" process restic runs to find out how much data there is does not finish before the backup itself is done, restic stops doing anything. This is resolved now.

    https://github.com/restic/restic/issues/1834 https://github.com/restic/restic/pull/1835

Changelog for restic 0.9.0 (2018-05-21)

The following sections list the changes in restic 0.9.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1608: Respect time stamp for new backup when reading from stdin
  • Fix #1652: Ignore/remove invalid lock files
  • Fix #1730: Ignore sockets for restore
  • Fix #1684: Fix backend tests for rest-server
  • Fix #1745: Correctly parse the argument to --tls-client-cert
  • Enh #1433: Support UTF-16 encoding and process Byte Order Mark
  • Enh #1561: Allow using rclone to access other services
  • Enh #1665: Improve cache handling for restic check
  • Enh #1721: Add cache command to list cache dirs
  • Enh #1758: Allow saving OneDrive folders in Windows
  • Enh #549: Rework archiver code
  • Enh #1552: Use Google Application Default credentials
  • Enh #1477: Accept AWS_SESSION_TOKEN for the s3 backend
  • Enh #1648: Ignore AWS permission denied error when creating a repository
  • Enh #1649: Add illumos/Solaris support
  • Enh #1709: Improve messages restic check prints
  • Enh #827: Add --new-password-file flag for non-interactive password changes
  • Enh #1735: Allow keeping a time range of snaphots
  • Enh #1782: Use default AWS credentials chain for S3 backend

Details

Changelog for restic 0.8.3 (2018-02-26)

The following sections list the changes in restic 0.8.3 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1633: Fixed unexpected 'pack file cannot be listed' error
  • Fix #1641: Ignore files with invalid names in the repo
  • Fix #1638: Handle errors listing files in the backend
  • Enh #1497: Add --read-data-subset flag to check command
  • Enh #1560: Retry all repository file download errors
  • Enh #1623: Don't check for presence of files in the backend before writing
  • Enh #1634: Upgrade B2 client library, reduce HTTP requests

Details

  • Bugfix #1633: Fixed unexpected 'pack file cannot be listed' error

    Due to a regression introduced in 0.8.2, the rebuild-index and prune commands failed to read pack files with size of 587, 588, 589 or 590 bytes.

    https://github.com/restic/restic/issues/1633 https://github.com/restic/restic/pull/1635

  • Bugfix #1641: Ignore files with invalid names in the repo

    The release 0.8.2 introduced a bug: when restic encounters files in the repo which do not have a valid name, it tries to load a file with a name of lots of zeroes instead of ignoring it. This is now resolved, invalid file names are just ignored.

    https://github.com/restic/restic/issues/1641 https://github.com/restic/restic/pull/1643 https://forum.restic.net/t/help-fixing-repo-no-such-file/485/3

  • Bugfix #1638: Handle errors listing files in the backend

    A user reported in the forum that restic completes a backup although a concurrent prune operation was running. A few error messages were printed, but the backup was attempted and completed successfully. No error code was returned.

    This should not happen: The repository is exclusively locked during prune, so when restic backup is run in parallel, it should abort and return an error code instead.

    It was found that the bug was in the code introduced only recently, which retries a List() operation on the backend should that fail. It is now corrected.

    https://github.com/restic/restic/pull/1638 https://forum.restic.net/t/restic-backup-returns-0-exit-code-when-already-locked/484

  • Enhancement #1497: Add --read-data-subset flag to check command

    This change introduces ability to check integrity of a subset of repository data packs. This can be used to spread integrity check of larger repositories over a period of time.

    https://github.com/restic/restic/issues/1497 https://github.com/restic/restic/pull/1556

  • Enhancement #1560: Retry all repository file download errors

    Restic will now retry failed downloads, similar to other operations.

    https://github.com/restic/restic/pull/1560

  • Enhancement #1623: Don't check for presence of files in the backend before writing

    Before, all backend implementations were required to return an error if the file that is to be written already exists in the backend. For most backends, that means making a request (e.g. via HTTP) and returning an error when the file already exists.

    This is not accurate, the file could have been created between the HTTP request testing for it, and when writing starts, so we've relaxed this requeriment, which saves one additional HTTP request per newly added file.

    https://github.com/restic/restic/pull/1623

  • Enhancement #1634: Upgrade B2 client library, reduce HTTP requests

    We've upgraded the B2 client library restic uses to access BackBlaze B2. This reduces the number of HTTP requests needed to upload a new file from two to one, which should improve throughput to B2.

    https://github.com/restic/restic/pull/1634

Changelog for restic 0.8.2 (2018-02-17)

The following sections list the changes in restic 0.8.2 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1506: Limit bandwith at the http.RoundTripper for HTTP based backends
  • Fix #1512: Restore directory permissions as the last step
  • Fix #1528: Correctly create missing subdirs in data/
  • Fix #1590: Strip spaces for lines read via --files-from
  • Fix #1589: Complete intermediate index upload
  • Fix #1594: Google Cloud Storage: Use generic HTTP transport
  • Fix #1595: Backup: Remove bandwidth display
  • Enh #1522: Add support for TLS client certificate authentication
  • Enh #1541: Reduce number of remote requests during repository check
  • Enh #1567: Reduce number of backend requests for rebuild-index and prune
  • Enh #1507: Only reload snapshots once per minute for fuse mount
  • Enh #1538: Reduce memory allocations for querying the index
  • Enh #1549: Speed up querying across indices and scanning existing files
  • Enh #1554: Fuse/mount: Correctly handle EOF, add template option
  • Enh #1564: Don't terminate ssh on SIGINT
  • Enh #1579: Retry Backend.List() in case of errors
  • Enh #1584: Limit index file size

Details

Changelog for restic 0.8.1 (2017-12-27)

The following sections list the changes in restic 0.8.1 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1457: Improve s3 backend with DigitalOcean Spaces
  • Fix #1454: Correct cache dir location for Windows and Darwin
  • Fix #1459: Disable handling SIGPIPE
  • Chg #1452: Do not save atime by default
  • Enh #1436: Add code to detect old cache directories
  • Enh #1439: Improve cancellation logic
  • Enh #11: Add the diff command

Details

Changelog for restic 0.8.0 (2017-11-26)

The following sections list the changes in restic 0.8.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Sec #1445: Prevent writing outside the target directory during restore
  • Fix #1256: Re-enable workaround for S3 backend
  • Fix #1291: Reuse backend TCP connections to BackBlaze B2
  • Fix #1317: Run prune when forget --prune is called with just snapshot IDs
  • Fix #1437: Remove implicit path /restic for the s3 backend
  • Enh #1102: Add subdirectory ids to fuse mount
  • Enh #1114: Add --cacert to specify TLS certificates to check against
  • Enh #1216: Add upload/download limiting
  • Enh #1271: Cache results for excludes for backup
  • Enh #1274: Add generate command, replaces manpage and autocomplete
  • Enh #1367: Allow comments in files read from via --file-from
  • Enh #448: Sftp backend prompts for password
  • Enh #510: Add dump command
  • Enh #1040: Add local metadata cache
  • Enh #1249: Add latest symlink in fuse mount
  • Enh #1269: Add --compact to forget command
  • Enh #1281: Google Cloud Storage backend needs less permissions
  • Enh #1319: Make check print no errors found explicitly
  • Enh #1353: Retry failed backend requests

Details

Changelog for restic 0.7.3 (2017-09-20)

The following sections list the changes in restic 0.7.3 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1246: List all files stored in Google Cloud Storage

Details

Changelog for restic 0.7.2 (2017-09-13)

The following sections list the changes in restic 0.7.2 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1167: Do not create a local repo unless init is used
  • Fix #1164: Make the key remove command behave as documented
  • Fix #1191: Make sure to write profiling files on interrupt
  • Enh #1132: Make key command always prompt for a password
  • Enh #1179: Resolve name conflicts, append a counter
  • Enh #1218: Add --compact to snapshots command
  • Enh #317: Add --exclude-caches and --exclude-if-present
  • Enh #697: Automatically generate man pages for all restic commands
  • Enh #1044: Improve restore, do not traverse/load excluded directories
  • Enh #1061: Add Dockerfile and official Docker image
  • Enh #1126: Use the standard Go git repository layout, use dep for vendoring
  • Enh #1134: Add support for storing backups on Google Cloud Storage
  • Enh #1144: Properly report errors when reading files with exclude patterns
  • Enh #1149: Add support for storing backups on Microsoft Azure Blob Storage
  • Enh #1196: Add --group-by to forget command for flexible grouping
  • Enh #1203: Print stats on all BSD systems when SIGINFO (ctrl+t) is received
  • Enh #1205: Allow specifying time/date for a backup with --time

Details

Changelog for restic 0.7.1 (2017-07-22)

The following sections list the changes in restic 0.7.1 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1115: Fix prune, only include existing files in indexes
  • Enh #1055: Create subdirs below data/ for local/sftp backends
  • Enh #1067: Allow loading credentials for s3 from IAM
  • Enh #1073: Add migrate cmd to migrate from s3legacy to default layout
  • Enh #1081: Clarify semantic for --tasg for the forget command
  • Enh #1080: Ignore chmod() errors on filesystems which do not support it
  • Enh #1082: Print stats on SIGINFO on Darwin and FreeBSD (ctrl+t)

Details

Changelog for restic 0.7.0 (2017-07-01)

The following sections list the changes in restic 0.7.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Fix #1013: Switch back to using the high-level minio-go API for s3
  • Fix #965: Switch to default repo layout for the s3 backend
  • Enh #1021: Detect invalid backend name and print error
  • Enh #1029: Remove invalid pack files when prune is run
  • Enh #512: Add Backblaze B2 backend
  • Enh #636: Add dirs tags and hosts to fuse mount
  • Enh #989: Improve performance of the find command
  • Enh #975: Add new backend for OpenStack Swift
  • Enh #998: Improve performance of the fuse mount

Details

Changelog for restic 0.6.1 (2017-06-01)

The following sections list the changes in restic 0.6.1 relevant to restic users. The changes are ordered by importance.

Summary

  • Enh #985: Allow multiple parallel idle HTTP connections
  • Enh #981: Remove temporary path from binary in build.go
  • Enh #974: Remove regular status reports

Details

  • Enhancement #985: Allow multiple parallel idle HTTP connections

    Backends based on HTTP now allow several idle connections in parallel. This is especially important for the REST backend, which (when used with a local server) may create a lot connections and exhaust available ports quickly.

    https://github.com/restic/restic/issues/985 https://github.com/restic/restic/pull/986

  • Enhancement #981: Remove temporary path from binary in build.go

    The build.go now strips the temporary directory used for compilation from the binary. This is the first step in enabling reproducible builds.

    https://github.com/restic/restic/pull/981

  • Enhancement #974: Remove regular status reports

    Regular status report: We've removed the status report that was printed every 10 seconds when restic is run non-interactively. You can still force reporting the current status by sending a USR1 signal to the process.

    https://github.com/restic/restic/pull/974

Changelog for restic 0.6.0 (2017-05-29)

The following sections list the changes in restic 0.6.0 relevant to restic users. The changes are ordered by importance.

Summary

  • Enh #957: Make forget consistent
  • Enh #966: Unify repository layout for all backends
  • Enh #962: Improve memory and runtime for the s3 backend

Details