سجل إصدارات ⁨Duplicati⁩

إصدارات 20262026

1. 2.4.1.0

   الأحدث إصدار تصحيحي عبر GitHub Releases صدر في 29 أكتوبر 2026

   سجل التغييرات

   # About this release This release builds on version 2.4.0.1 with a large number of bug fixes, and adds three new features: incremental (delta) backups of Microsoft 365 and Google Workspace, and restore tests that can run after backups and be switched on remotely from the console. The local database format is updated by this release. See "Downgrading" below before going back to an earlier version. ## Delta walk for Microsoft 365 and Google Workspace Microsoft 365 and Google Workspace backups no longer need to list every item on every run. The providers now store a delta token with each backup and use the Microsoft Graph and Google change APIs, so later backups list only what was created, changed, moved or removed since the previous backup and carry the rest forward from it. For Microsoft 365 this covers mail folders, SharePoint and group document libraries. For Google Workspace it covers Gmail, Drive, Calendar and Contacts. Delta tracking is enabled by default. The first backup, the first backup after the local database is recreated, and the backup after one that was stopped still list everything in full. Delta tracking can be turned off per service with `--office365-disable-mail-delta`, `--office365-disable-drive-delta`, `--google-disable-gmail-delta`, `--google-disable-drive-delta`, `--google-disable-calendar-delta` and `--google-disable-contacts-delta`. If a document library reports more changes than `--office365-drive-delta-max-items` or `--google-drive-delta-max-items`, the library is listed in full instead. A backup that combines a Microsoft 365 or Google Workspace source with the USN change journal or `--changed-files` is now refused with an error, as the two mechanisms cannot be combined. ## Restore tests A new restore test operation restores a sample of a backup from the remote destination into a temporary folder and verifies it, so the backup is regularly proven to be restorable. It is available as the `restore-test` command in the command line and in ServerUtil, and through the server API. The sample is chosen with `--restore-test-mode`: a number of random files, a percentage of the backup size, every file, or a rolling mode that prefers files that have not been verified recently. The test can be limited with `--restore-test-max-download-size` and `--restore-test-max-runtime`, can rebuild a temporary database from the destination with `--restore-test-recreate-database`, and can compare the restored files with the source files with `--restore-test-compare-source`. Set `--perform-restore-test-after` to run a restore test as the last step of a backup whenever the previous test is older than the given interval. When the machine is connected to the Duplicati console, the console can set this interval for its backups, so restore tests can be switched on remotely. A restore test after a backup does not change the result of the backup, but a failed test is reported with its own notification. ## Improved support for Sync jobs With this version, Sync jobs now store their logs so the logs can be viewed after the job has completed. Several places where the Sync job was showing options that were only relevant to restores are now updated. ## Other new features - Backup versions can be given a label with the `set-version-label` command. The labels are also stored on the destination, so a database recreate keeps them. - Point-in-time access to a destination: with `--remote-point-in-time`, the S3 and Duplicati Storage destinations read the destination as it was at the given time, using bucket versioning. The destination is read-only in this mode. - Report modules can send reports for other operations than backups, chosen with `--send-http-operations`, `--send-mail-operations`, `--send-xmpp-operations` and `--send-telegram-operations`. Backup reports remain the default. - A restore on an existing backup can now carry additional advanced options. - The new `--disable-secret-provider` option disables the default secret provider, the configured secret provider, or both. `--disable-default-secret-provider` still works but is deprecated. The server now also reports which secret provider is active. - Duplicati Storage can be used as a secondary target, and supports object locking. - Uploads to Google Cloud Storage now carry a CRC32 checksum. - SMB servers that require SMB 3.1.1 can be used with `--enable-smb311`. - Neon Object Storage has been added to the list of S3 providers. ## Changed behavior - A backup that asks for object locks on a bucket or container that does not have locking enabled now completes with a warning that no locks were applied, instead of failing. This applies to S3, B2, Azure, Google Cloud Storage and Duplicati Storage. - Options in source and destination urls are now validated, so an option that no module supports is reported with a warning. - The Microsoft 365 site classifications "Classic" and "Communication" have been removed, as they never matched any site. - When a restore does not specify overwrite, restore permissions or skip metadata, the settings of the backup and the server defaults now apply instead of turning them off. ## Downgrading This release updates the local database from version 19 to version 22 and the sync database to version 1. Version 2.4.0.1 cannot open the newer databases. To go back to 2.4.0.1, downgrade the databases with the DatabaseTool `downgrade` command first. Its default target versions now match 2.4.0.1, so no version options are needed. ## Fixes Aborting a backup no longer waits for a stuck source listing, file open, size or metadata read, and a stop or abort that arrives before the operation is ready is kept. Restores keep an appended file when restoring without `--overwrite`, do not read through a link when restoring a symbolic link to a file, keep the drive letter folder when restoring Windows paths in place, and stop when `--restore-path` has no value. A partial restore no longer warns about the folders it has to crea …

   linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · arm64 · appimage SHA-256 linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · x64 · deb SHA-256 linux · x64 · deb SHA-256 linux · x64 · appimage SHA-256 linux · x64 · deb SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 linux · x64 · appimage SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 macos · arm64 · pkg SHA-256 macos · arm64 · pkg SHA-256 macos · arm64 · dmg SHA-256 macos · arm64 · pkg SHA-256 macos · x64 · pkg SHA-256 macos · x64 · pkg SHA-256 macos · x64 · dmg SHA-256 macos · x64 · pkg SHA-256 windows · arm64 · msi SHA-256 windows · arm64 · portable SHA-256 windows · arm64 · msi SHA-256 windows · arm64 · portable SHA-256 windows · x64 · msi SHA-256 windows · x64 · portable SHA-256 windows · x64 · msi SHA-256 windows · x64 · portable SHA-256 windows · x86 · msi SHA-256 windows · x86 · portable SHA-256

2. 2.4.0.1

   عبر GitHub Releases صدر في 7 أكتوبر 2026

   سجل التغييرات

   # About this release This release patches version 2.4.0.0 with fixes for a number of issues that were discovered after the release. The main focus of this release is stability, with many fixes to restore, abort handling and the new sync mode, along with security hardening of the server and remote control. ## Usability fixes The search feature would allow you to select files, but would send incorrect paths to the restore flow. On Windows, this would result in no files selected in the search view being restored. ## Security and Privacy The login setup has been hardened against weak passwords, the remote control requests have been locked down and require per-message keys. The remote control connection now works on NAS devices that use integrated authentication (Synology DSM). Path redaction in logs and reports has been improved, and secrets in lists now have an additional layer of protection. A new reduced reporting mode (`--reduced-reporting`) limits reports leaving the machine to log message ids, counters and dates, without message text, error messages or file names. The HTTP status report has a matching `--http-report-status-reduced-reporting` option. The setting can also be enforced from the console for users requiring it. ## Restore and Abort Fixes A restore now carries on with the next file when a single file fails, instead of stopping the whole restore. Several issues that could cause a restore to hang have been fixed, including releasing blocks for skipped files, releasing all restore processes when a volume cannot be produced, and releasing the restore stages on every exit path. A missing destination folder is now reported before the restore starts. Aborting a backup or other operation no longer waits for a stuck source file read, a stuck backend call, or a block processor that has stopped. Aborting a repair while it reads the local database no longer discards the database. ## Sync Mode Fixes The sync mode introduced in 2.4.0.0 has received a number of fixes: folder sync on some destinations, zero-byte uploads to Google Drive and Google Cloud, case-insensitive remotes, duplicate remote listings, sync metadata and last-run handling, and lower memory use by not storing remote operations in memory. The synchronization tool now passes the correct arguments to its backends, ignores folder entries in listings, renames through the backend, and counts failed deletes and renames in its return code. ## Stability and Performance The wasted space calculation used for compacting has been improved, deleting filesets uses less memory, and SQLite memory usage has been further reduced. Database connections are now closed when opening or setting up a local database fails, and the server now takes the database lock in a few paths that previously skipped it. Resuming after sleep no longer waits for the suspend handling to finish, and Windows is allowed to sleep again when an operation ends. Tasks and HTTP status reports now report errors from operations that finished without throwing. ## Backend and Provider Fixes - Google Drive: keep every copy of a duplicated name, and report no quota for shared drives instead of the user's own quota. - Google Workspace: handle inactive accounts, emit a root folder, and fix the restore scope. - MS365: fix restore of large emails. - Drime: fix incomplete listings beyond the pagination limit. - S3: add RelAix to the list of providers. - SMB: improved error detection. - Duplicati backend: show error messages from the console. - An unknown destination quota is no longer treated as a full destination, and the manual quota is kept when the backend quota is disabled. ## Windows Installer and Shell Integration The MSI now remembers the install location on upgrade, and the path browse button has been fixed. The Windows shell overlay has been fixed. It requires the folder status service, which is disabled by default and can only be enabled from the commandline with `--webservice-enable-folder-status-service=true`. ## Other Changes The command line tools have a number of fixes to listing and searching, such as listing the latest version when none is given, searching sub-folders, looking up file versions by full path, and handling folders given without a trailing separator. Purge and set-locks now stop when the given version or time matches no fileset, and a queued command keeps the versions it named when it was sent. The old UI has fixes for editing local folder and S3 destinations, restore version grouping and selecting a restore root. This release also adds an option to prevent the server from creating a new database (`--webservice-dont-autocreate-database`), support for runner identity and license usage collection, and fixes for packaging `libc_wrapper.so` and for running when the account has no home folder. ## Detailed list of changes: - Don't warn on report module errors - Fix remote access on NAS - Remember install location for MSI - Stop waiting for a stuck source file read when the backup is aborted - Answer a block's sender when the block processor stops - List the roots of a multi-drive backup without waiting - Let the queue runner be disposed before it is terminated - Release the blocks of a file the restore skips - Report a missing destination folder before a restore starts - Say which file is missing when the Windows modules cannot load - Close the connection when the setup of a backup or delete database fails - Try the next port when the system refuses the one the server binds - Resume after a sleep even if the suspend is still being handled - Fixed the path browse button in the MSI - Keep the local database when a repair is aborted while reading it - Report the errors of an operation that finished without throwing in the HTTP status report - Let Windows sleep again when an operation ends - Say that search looks at every version when none is given - Return the oldest live log entries after the one a client has seen - Group restore versions by …

   linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · arm64 · appimage SHA-256 linux · arm64 · deb SHA-256 linux · arm64 · rpm SHA-256 linux · x64 · deb SHA-256 linux · x64 · deb SHA-256 linux · x64 · appimage SHA-256 linux · x64 · deb SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 linux · x64 · appimage SHA-256 linux · x64 · deb SHA-256 linux · x64 · rpm SHA-256 macos · arm64 · pkg SHA-256 macos · arm64 · pkg SHA-256 macos · arm64 · dmg SHA-256 macos · arm64 · pkg SHA-256 macos · x64 · pkg SHA-256 macos · x64 · pkg SHA-256 macos · x64 · dmg SHA-256 macos · x64 · pkg SHA-256 windows · arm64 · msi SHA-256 windows · arm64 · portable SHA-256 windows · arm64 · msi SHA-256 windows · arm64 · portable SHA-256 windows · x64 · msi SHA-256 windows · x64 · portable SHA-256 windows · x64 · msi SHA-256 windows · x64 · portable SHA-256 windows · x86 · portable SHA-256 windows · x86 · msi SHA-256

   إصدار قديم — ثبّت أحدث إصدار ما لم تحتج هذا الإصدار للتوافق.