restic 0.16.2 → 0.18.1
9 releases · 3 breaking changes · 6 security fixes · 0 advisories fixed
6security3breaking4deprecated66feature74fix
Breaking changes
- breaking Bugfix #5421: Fix rare crash if directory is removed during backup In restic 0.18.0, the backup command could crash if a directory was removed between reading its metadata and listing its directory content. This has now been fixed. in 0.18.1
- breaking Bugfix #2165: Ignore disappeared backup source files The backup command now quietly skips files that are removed between directory listing and backup, instead of printing errors like: error: lstat /some/file/name: no such file or directory in 0.18.0
- breaking Bugfix #5063: Correctly backup extended metadata when using VSS on Windows On Windows, when creating a backup with the --use-fs-snapshot option, restic read extended metadata from the original filesystem path instead of from the snapshot. This could result in errors if files were removed during… in 0.17.2
Security changes
- security Security #5291: Mitigate attack on content-defined chunking algorithm Restic uses Rabin Fingerprints for its content-defined chunker. The algorithm relies on a secret polynomial to split files into chunks. As shown in the paper "Chunking Attacks on File Backup Services using Content-Defined… in 0.18.0
- security Bugfix #5169: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot When running backup with the --use-fs-snapshot option in Windows with admin rights, event logs like Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr =… in 0.18.0
- security Bugfix #5003: Fix metadata errors during backup of removable disks on Windows Since restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below. error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.… in 0.17.3
- security Bugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error On Windows, creating a backup could sometimes trigger the following error: error: nodeFromFileInfo [...]: get named security info failed with: a required privilege is not held by the client. This has now been fixed. in 0.17.1
- security Enhancement #1786: Support repositories with empty password Restic previously required a password to create or operate on repositories. Using the new option --insecure-no-password it is now possible to disable this requirement. Restic will not prompt for a password when using this option. For… in 0.17.0
- security Enhancement #4873: Update dependencies A few potentially vulnerable dependencies were updated. in 0.16.5
Deprecations
- deprecated Change #5162: Promote feature flags The deprecate-legacy-index, deprecate-s3-legacy-layout, explicit-s3-anonymous-auth and safe-forget-keep-tags features are now stable and can no longer be disabled. The corresponding feature flags will be removed in restic 0.19.0. in 0.18.0
- deprecated Chg: Deprecate legacy index format and s3legacy repository layout in 0.17.0
- deprecated Change #4602: Deprecate legacy index format and s3legacy repository layout Support for the legacy index format used by restic before version 0.2.0 has been deprecated and will be removed in the next minor restic version. You can use restic repair index to update the index to the current format. It… in 0.17.0
- deprecated Enhancement #4664: Make ls use message_type field in JSON output The ls command was the only restic command that used the struct_type field in its JSON output format to specify the message type. The JSON output of the ls command now also includes the message_type field, which is consistent with… in 0.17.0
Every release in between
fixFix: Correctly handle backup --stdin-filename with directory paths
fixFix: Accept RESTIC_HOST environment variable in forget command
fixFix: Ignore "chmod not supported" errors when writing files
fixFix: Ignore EOPNOTSUPP errors for extended attributes
fixFix: Fix rare crash if directory is removed during backup
fixFix: Stop retrying uploads when rest-server runs out of space
fixFix: Improve handling of download retries in check command
fixBugfix #5324: Correctly handle backup --stdin-filename with directory paths In restic 0.18.0, the backup command failed if a filename that includes at least a directory was passed to --stdin-filename. For example, --stdin-filename /foo/bar resulted in the following error: Fatal: unable to save…
fixBugfix #5325: Accept RESTIC_HOST environment variable in forget command The forget command did not use the host name from the RESTIC_HOST environment variable when filtering snapshots. This has now been fixed.
fixBugfix #5342: Ignore "chmod not supported" errors when writing files Restic 0.18.0 introduced a bug that caused chmod xxx: operation not supported errors to appear when writing to a local file repository that did not support chmod (like CIFS or WebDAV mounted via FUSE). Restic now ignores those…
fixBugfix #5344: Ignore EOPNOTSUPP errors for extended attributes Restic 0.18.0 added extended attribute support for NetBSD 10+, but not all NetBSD filesystems support extended attributes. Other BSD systems can likewise return EOPNOTSUPP, so restic now ignores these errors.
breakingBugfix #5421: Fix rare crash if directory is removed during backup In restic 0.18.0, the backup command could crash if a directory was removed between reading its metadata and listing its directory content. This has now been fixed.
fixBugfix #5429: Stop retrying uploads when rest-server runs out of space When rest-server returns a 507 Insufficient Storage error, it indicates that no more storage capacity is available. Restic now correctly stops retrying uploads in this case.
fixBugfix #5467: Improve handling of download retries in check command In very rare cases, the check command could unnecessarily report repository damage if the backend returned incomplete, corrupted data on the first download try which is afterwards resolved by a download retry. This could result in…
fixFix: Correctly restore long filepaths' timestamp on old Windows
fixFix: Ignore disappeared backup source files
fixFix: Include root tree when searching using find --tree
fixFix: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot
fixFix: Fix duplicate data handling in prune --max-unused
fixFix: Fix creation of oversized index by repair index --read-all-packs
fixFix: Fix rare crash in command output
featureEnh: Add JSON support to check command
featureEnh: Allow excluding online-only cloud files (e.g. OneDrive)
featureEnh: Add sort option to ls command
featureEnh: Add support for Microsoft Blob Storage access tiers
featureEnh: Add snapshot summary statistics to rewritten snapshots
featureEnh: Add SLSA provenance to GHCR container images
featureEnh: Add retry mechanism for loading repository config
featureEnh: Allow including/excluding extended file attributes during restore
featureEnh: Add start and end timestamps to backup JSON output
featureEnh: Add DragonFlyBSD support
featureEnh: Add experimental S3 cold storage support
featureEnh: Add xattr support for NetBSD 10+
securitySecurity #5291: Mitigate attack on content-defined chunking algorithm Restic uses Rabin Fingerprints for its content-defined chunker. The algorithm relies on a secret polynomial to split files into chunks. As shown in the paper "Chunking Attacks on File Backup Services using Content-Defined…
fixBugfix #1843: Correctly restore long filepaths' timestamp on old Windows The restore command now correctly restores timestamps for files with paths longer than 256 characters on Windows versions prior to Windows 10 1607.
breakingBugfix #2165: Ignore disappeared backup source files The backup command now quietly skips files that are removed between directory listing and backup, instead of printing errors like: error: lstat /some/file/name: no such file or directory
securityBugfix #5169: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot When running backup with the --use-fs-snapshot option in Windows with admin rights, event logs like Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr =…
featureChange #4938: Update dependencies and require Go 1.23 or newer We have updated all dependencies. Restic now requires Go 1.23 or newer to build. This also disables support for TLS versions older than TLS 1.2. On Windows, restic now requires at least Windows 10 or Windows Server 2016. On macOS,…
deprecatedChange #5162: Promote feature flags The deprecate-legacy-index, deprecate-s3-legacy-layout, explicit-s3-anonymous-auth and safe-forget-keep-tags features are now stable and can no longer be disabled. The corresponding feature flags will be removed in restic 0.19.0.
featureEnhancement #1378: Add JSON support to check command The check command now supports the --json option to output all statistics in JSON format.
featureEnhancement #3697: Allow excluding online-only cloud files (e.g. OneDrive) Restic treated files synced using OneDrive Files On-Demand as though they were regular files. This caused issues with VSS and could cause OneDrive to download all files. Restic now allows the user to exclude these files…
featureEnhancement #4179: Add sort option to ls command The ls -l command output can now be sorted using the new --sort option for the fields name, size, time (same as mtime), mtime, atime, ctime and extension. A --reverse option is also available.
featureEnhancement #4433: Change default sort order for find output The find command now sorts snapshots from newest to oldest by default. The previous oldest-to-newest order can be restored using the new --reverse option.
featureEnhancement #4521: Add support for Microsoft Blob Storage access tiers The new -o azure.access-tier= option allows specifying the access tier (Hot, Cool or Cold) for objects created in Microsoft Blob Storage. If unspecified, the storage account's default tier is used. There is no official Archive…
featureEnhancement #4942: Add snapshot summary statistics to rewritten snapshots The rewrite command now supports a --snapshot-summary option to add statistics data to snapshots. Only two fields in the summary will be non-zero: TotalFilesProcessed and TotalBytesProcessed. For snapshots rewritten using…
featureEnhancement #4983: Add SLSA provenance to GHCR container images Restic's GitHub Container Registry (GHCR) image build workflow now includes SLSA (Supply-chain Levels for Software Artifacts) provenance generation. Please see the restic documentation for more information about verifying SLSA…
featureEnhancement #5081: Add retry mechanism for loading repository config Restic now retries loading the repository config file when opening a repository. The init command now also retries backend operations.
featureEnhancement #5089: Allow including/excluding extended file attributes during restore The restore command now supports the --exclude-xattr and --include-xattr options to control which extended file attributes will be restored. By default, all attributes are restored.
featureEnhancement #5109: Make small pack size configurable for prune The prune command now supports the --repack-smaller-than option that allows repacking pack files smaller than a specified size.
featureEnhancement #5119: Add start and end timestamps to backup JSON output The JSON output of the backup command now includes backup_start and backup_end timestamps, containing the start and end time of the backup.
featureEnhancement #5131: Add DragonFlyBSD support Restic can now be compiled on DragonflyBSD.
featureEnhancement #5137: Make tag command print which snapshots were modified The tag command now outputs which snapshots were modified along with their new snapshot ID. The command supports the --json option for machine-readable output.
featureEnhancement #5173: Add experimental S3 cold storage support Introduce S3 backend options for transitioning pack files from cold to hot storage on S3 and S3-compatible providers. Note: this only works for the prune, copy and restore commands for now. This experimental feature is gated behind the…
featureEnhancement #5174: Add xattr support for NetBSD 10+ Extended attribute support for backup and restore operations is now available on NetBSD version 10 and later.
+24 more items in the release notesfixFix: Fix unusable mount on macOS Sonoma
fixFix: Fix metadata errors during backup of removable disks on Windows
fixFix: Do not retry load/list operation if SFTP connection is broken
fixFix: Fix metadata error on Windows for backups using VSS
featureEnh: Allow prune --dry-run without lock
fixBugfix #4971: Fix unusable mount on macOS Sonoma On macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved.
securityBugfix #5003: Fix metadata errors during backup of removable disks on Windows Since restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below. error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.…
fixBugfix #5101: Do not retry load/list operation if SFTP connection is broken When using restic with the SFTP backend, backend operations that load a file or list files were retried even if the SFTP connection was broken. This has now been fixed.…
fixBugfix #5107: Fix metadata error on Windows for backups using VSS Since restic 0.17.2, when creating a backup on Windows using --use-fs-snapshot, restic would report an error like the following: error: incomplete metadata for C:\: get EA failed while opening file handle for path…
featureEnhancement #5096: Allow prune --dry-run without lock The prune --dry-run --no-lock now allows performing a dry-run without locking the repository. Note that if the repository is modified concurrently, prune may return inaccurate statistics or errors.
fixFix: Support container-level SAS/SAT tokens for Azure backend
fixFix: Resolve potential error during concurrent cache cleanup
fixFix: Return error if tag fails to lock repository
fixFix: Exclude irregular files from backups
fixFix: Correctly backup extended metadata when using VSS on Windows
fixBugfix #4004: Support container-level SAS/SAT tokens for Azure backend Restic previously expected SAS/SAT tokens to be generated at the account level, which prevented tokens created at the container level from being used to initialize a repository. This caused an error when attempting to…
fixBugfix #5047: Resolve potential error during concurrent cache cleanup When multiple restic processes ran concurrently, they could compete to remove obsolete snapshots from the local backend cache, sometimes leading to a "no such file or directory" error. Restic now suppresses this error to prevent…
fixBugfix #5050: Return error if tag fails to lock repository Since restic 0.17.0, the tag command did not return an error when it failed to open or lock the repository. This issue has now been fixed.
fixBugfix #5057: Exclude irregular files from backups Since restic 0.17.1, files with the type irregular could mistakenly be included in snapshots, especially when backing up special file types on Windows that restic cannot process. This issue has now been fixed. Previously, this bug caused the check…
breakingBugfix #5063: Correctly backup extended metadata when using VSS on Windows On Windows, when creating a backup with the --use-fs-snapshot option, restic read extended metadata from the original filesystem path instead of from the snapshot. This could result in errors if files were removed during…
fixFix: Correctly handle volume names in backup command on Windows
fixFix: Include missing backup error text with --json
fixFix: Correctly handle long paths on older Windows versions
fixFix: Fix delayed cancellation of certain commands
fixFix: Don't ignore metadata-setting errors during restore
fixFix: Correctly restore timestamp for files with resource forks on macOS
fixFix: Prevent backup --stdin-from-command from panicking
fixFix: Skip extended attribute processing on unsupported Windows volumes
fixFix: Fix spurious "A Required Privilege Is Not Held by the Client" error
fixFix: Fix rare failures to retry locking a repository
fixFix: Improve HTTP/2 support for REST backend
otherChg: Also back up files with incomplete metadata
otherEnh: Display progress bar for restore --verify
otherEnh: Automatically clear removed snapshots from cache
otherEnh: Print JSON-formatted errors during restore --json
otherEnh: Return exit code 12 for "bad password" errors
otherEnh: Make timeout for stuck requests customizable
fixBugfix #2004: Correctly handle volume names in backup command on Windows On Windows, when the specified backup target only included the volume name without a trailing slash, for example, C:, then restoring the resulting snapshot would result in an error. Note that using C:\ as backup target worked…
fixBugfix #4945: Include missing backup error text with --json Previously, when running a backup with the --json option, restic failed to include the actual error message in the output, resulting in "error": {} being displayed. This has now been fixed, and restic now includes the error text in JSON…
fixBugfix #4953: Correctly handle long paths on older Windows versions On older Windows versions, like Windows Server 2012, restic 0.17.0 failed to back up files with long paths. This problem has now been resolved.
fixBugfix #4957: Fix delayed cancellation of certain commands Since restic 0.17.0, some commands did not immediately respond to cancellation via Ctrl-C (SIGINT) and continued running for a short period. The most affected commands were diff,find, ls, stats and rewrite. This is now resolved.
fixBugfix #4958: Don't ignore metadata-setting errors during restore Previously, restic used to ignore errors when setting timestamps, attributes, or file modes during a restore. It now reports those errors, except for permission related errors when running without root privileges.
fixBugfix #4969: Correctly restore timestamp for files with resource forks on macOS On macOS, timestamps were not restored for files with resource forks. This has now been fixed.
fixBugfix #4975: Prevent backup --stdin-from-command from panicking Restic would previously crash if --stdin-from-command was specified without providing a command. This issue has now been fixed.
fixBugfix #4980: Skip extended attribute processing on unsupported Windows volumes With restic 0.17.0, backups of certain Windows paths, such as network drives, failed due to errors while fetching extended attributes. Restic now skips extended attribute processing for volumes where they are not…
securityBugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error On Windows, creating a backup could sometimes trigger the following error: error: nodeFromFileInfo [...]: get named security info failed with: a required privilege is not held by the client. This has now been fixed.
fixBugfix #5005: Fix rare failures to retry locking a repository Restic 0.17.0 could in rare cases fail to retry locking a repository if one of the lock files failed to load, resulting in the error: unable to create lock in backend: circuit breaker open for file This issue has now been addressed. The…
fixBugfix #5018: Improve HTTP/2 support for REST backend If rest-server tried to gracefully shut down an HTTP/2 connection still in use by the client, it could result in the following error: http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after…
otherChange #4953: Also back up files with incomplete metadata If restic failed to read extended metadata for a file or folder during a backup, then the file or folder was not included in the resulting snapshot. Instead, a warning message was printed along with returning exit code 3 once the backup was…
otherEnhancement #4795: Display progress bar for restore --verify When the restore command is run with --verify, it now displays a progress bar while the verification step is running. The progress bar is not shown when the --json flag is specified.
otherEnhancement #4934: Automatically clear removed snapshots from cache Previously, restic only removed snapshots from the cache on the host where the forget command was executed. On other hosts that use the same repository, the old snapshots remained in the cache. Restic now automatically clears old…
otherEnhancement #4944: Print JSON-formatted errors during restore --json Restic used to print any restore errors directly to the console as freeform text messages, even when using the --json option. Now, when --json is specified, restic prints them as JSON formatted messages.
otherEnhancement #4959: Return exit code 12 for "bad password" errors Restic now returns exit code 12 when it cannot open the repository due to an incorrect password.
otherEnhancement #4970: Make timeout for stuck requests customizable Restic monitors connections to the backend to detect stuck requests. If a request does not return any data within five minutes, restic assumes the request is stuck and retries it. However, for large repositories this timeout might be…
fixFix: Handle unreadable xattrs in folders above backup source
fixFix: Fix slow SFTP upload performance
fixFix: Correct hardlink handling in stats command
deprecatedChg: Deprecate legacy index format and s3legacy repository layout
featureEnh: Add bitrot detection to diff command
featureEnh: Add --delete option to restore command
featureEnh: Add extended options to configure Windows Shadow Copy Service
featureEnh: Add support for FUSE-T with mount on macOS
featureEnh: Add --json option to version command
featureEnh: Add --ncdu option to ls command
featureEnh: Add support for feature flags
featureEnh: Add --target option to the dump command
featureEnh: Allow specifying --host via environment variable
featureEnh: Allow specifying custom User-Agent for outgoing requests
featureEnh: Add restore options to read include/exclude patterns from files
featureEnh: Add dry-run support to restore command
featureChange #4540: Require at least ARMv6 for ARM binaries The official release binaries of restic now require at least ARMv6 support for ARM platforms.
deprecatedChange #4602: Deprecate legacy index format and s3legacy repository layout Support for the legacy index format used by restic before version 0.2.0 has been deprecated and will be removed in the next minor restic version. You can use restic repair index to update the index to the current format. It…
featureChange #4627: Redesign backend error handling to improve reliability Restic now downloads pack files in large chunks instead of using a streaming download. This prevents failures due to interrupted streams. The restore command now also retries downloading individual blobs that could not be…
featureChange #4707: Disable S3 anonymous authentication by default When using the S3 backend with anonymous authentication, it continuously tried to retrieve new authentication credentials, causing bad performance. Now, to use anonymous authentication, it is necessary to pass the extended option -o…
featureEnhancement #662: Optionally skip snapshot creation if nothing changed The backup command always created a snapshot even if nothing in the backup set changed compared to the parent snapshot. Restic now supports the --skip-if-unchanged option for the backup command, which omits creating a snapshot…
featureEnhancement #805: Add bitrot detection to diff command The output of the diff command now includes the modifier ? for files to indicate bitrot in backed up files. The ? will appear whenever there is a difference in content while the metadata is exactly the same. Since files with unchanged metadata…
securityEnhancement #1786: Support repositories with empty password Restic previously required a password to create or operate on repositories. Using the new option --insecure-no-password it is now possible to disable this requirement. Restic will not prompt for a password when using this option. For…
featureEnhancement #2348: Add --delete option to restore command The restore command now supports a --delete option that allows removing files and directories from the target directory that do not exist in the snapshot. This option also allows files in the snapshot to replace non-empty directories having…
featureEnhancement #3067: Add extended options to configure Windows Shadow Copy Service Previous, restic always used a 120 seconds timeout and unconditionally created VSS snapshots for all volume mount points on disk. This behavior can now be fine-tuned by the following new extended options (available…
featureEnhancement #4048: Add support for FUSE-T with mount on macOS The restic mount command now supports creating FUSE mounts using FUSE-T on macOS.
featureEnhancement #4287: Support connection to rest-server using unix socket Restic now supports using a unix socket to connect to a rest-server version 0.13.0 or later. This allows running restic as follows: rest-server --listen unix:/tmp/rest.socket --data /path/to/data & restic -r…
featureEnhancement #4472: Support AWS Assume Role for S3 backend Previously only credentials discovered via the Minio discovery methods were used to authenticate. However, there are many circumstances where the discovered credentials have lower permissions and need to assume a specific role. This is now…
featureEnhancement #4547: Add --json option to version command Restic now supports outputting restic version along with the Go version, OS and architecture used to build restic in JSON format using version --json.
featureEnhancement #4549: Add --ncdu option to ls command NCDU (NCurses Disk Usage) is a tool to analyse disk usage of directories. It has an option to save a directory tree and analyse it later. The ls command now supports outputting snapshot information in the NCDU format using the --ncdu option.…
featureEnhancement #4573: Support rewriting host and time metadata in snapshots The rewrite command now supports rewriting the host and/or time metadata of a snapshot using the new --new-host and --new-time options.
featureEnhancement #4601: Add support for feature flags Restic now supports feature flags that can be used to enable and disable experimental features. The flags can be set using the environment variable RESTIC_FEATURES. To get a list of currently supported feature flags, use the features command.
deprecatedEnhancement #4664: Make ls use message_type field in JSON output The ls command was the only restic command that used the struct_type field in its JSON output format to specify the message type. The JSON output of the ls command now also includes the message_type field, which is consistent with…
featureEnhancement #4676: Make key command's actions separate sub-commands Each of the add, list, remove and passwd actions provided by the key command is now a separate sub-command and have its own documentation which can be invoked using restic key --help.
featureEnhancement #4678: Add --target option to the dump command Restic dump always printed to the standard output. It now supports specifying a --target file to write its output to.
featureEnhancement #4733: Allow specifying --host via environment variable Restic commands that operate on snapshots, such as restic backup and restic snapshots, support the --host option to specify the hostname for grouping snapshots. Such commands now also support specifying the hostname via the…
featureEnhancement #4764: Support forgetting all snapshots The forget command now supports the --unsafe-allow-remove-all option, which removes all snapshots in the repository. This option must always be combined with a snapshot filter (by host, path or tag). For example, the command forget --tag example…
featureEnhancement #4768: Allow specifying custom User-Agent for outgoing requests Restic now supports setting a custom User-Agent for outgoing HTTP requests using the global option --http-user-agent or the RESTIC_HTTP_USER_AGENT environment variable.
featureEnhancement #4781: Add restore options to read include/exclude patterns from files Restic now supports reading include and exclude patterns from files using the --include-file, --exclude-file, --iinclude-file and --iexclude-file options of the restore command.
featureEnhancement #4839: Add dry-run support to restore command The restore command now supports the --dry-run option to perform a dry run. Pass the --verbose=2 option to see which files would remain unchanged, and which would be updated or freshly restored.
+78 more items in the release notesfeatureEnh: Add option to force use of Azure CLI credential
otherEnh: Update dependencies
featureEnhancement #4799: Add option to force use of Azure CLI credential A new environment variable AZURE_FORCE_CLI_CREDENTIAL=true allows forcing the use of Azure CLI credential, ignoring other credentials like managed identity.
securityEnhancement #4873: Update dependencies A few potentially vulnerable dependencies were updated.
fixFix: Downgrade zstd library to fix rare data corruption at max. compression
featureEnh: Add extra verification of data integrity before upload
fixBugfix #4677: Downgrade zstd library to fix rare data corruption at max. compression In restic 0.16.3, backups where the compression level was set to max (using --compression max) could in rare and very specific circumstances result in data corruption due to a bug in the library used for…
fixEnhancement #4529: Add extra verification of data integrity before upload Hardware issues, or a bug in restic or its dependencies, could previously cause corruption in the files restic created and stored in the repository. Detecting such corruption previously required explicitly running the check…
fixFix: Improve errors for irregular files on Windows
fixFix: Support backup of deduplicated files on Windows again
fixFix: Improve error handling for rclone backend
fixFix: Correct restore progress information if an error occurs
fixFix: Improve reliability of restoring large files
fixBugfix #4560: Improve errors for irregular files on Windows Since Go 1.21, most filesystem reparse points on Windows are considered to be irregular files. This caused restic to show an error: invalid node type "" error message for those files. This error message has now been improved and includes…
fixBugfix #4574: Support backup of deduplicated files on Windows again With the official release builds of restic 0.16.1 and 0.16.2, it was not possible to back up files that were deduplicated by the corresponding Windows Server feature. This also applied to restic versions built using Go…
fixBugfix #4612: Improve error handling for rclone backend Since restic 0.16.0, if rclone encountered an error while listing files, this could in rare circumstances cause restic to assume that there are no files. Although unlikely, this situation could result in data loss if it were to happen right…
fixBugfix #4624: Correct restore progress information if an error occurs If an error occurred while restoring a snapshot, this could cause the restore progress bar to show incorrect information. In addition, if a data file could not be loaded completely, then errors would also be reported for some…
fixBugfix #4626: Improve reliability of restoring large files In some cases restic failed to restore large files that frequently contain the same file chunk. In combination with certain backends, this could result in network connection timeouts that caused incomplete restores. Restic now includes…