Synchronization and backup programs
This page lists and compares applications that synchronize data between two or more locations, and those that build on top of such functionality to make incremental copies of important data for backup purposes. Because of their relationship, the two groups share several traits that justify describing them in the same article.
Having backups of important data is a necessary measure to take, since human and machine processing errors are very likely to generate corruption as time passes, and also the physical media where the data is stored is inevitably destined to fail. In order to choose the best program for one's own needs, the following aspects should be considered:
- The type of backup medium that is going to store the data, e.g. CD, DVD, remote server, external hard drive, etc.
- The planned frequency of backups, e.g. daily, weekly, monthly, etc.
- The features expected from the backup solution, e.g. compression, encryption, handles renames, etc.
- The planned method to restore backups if needed.
These applications simply keep directories synchronized between multiple locations/machines, in a "mirror" fashion. Nonetheless, most of them still allow storing and reverting to old revisions of modified or deleted files.
- List of applications/Utilities#File synchronization
- List of applications/Internet#Cloud synchronization clients
- Wikipedia:Comparison of file synchronization software
- The application name, linking to the ArchWiki article or the official website.
- A link to the package.
- The programming language, library, or utility that the application is based on.
- Delta transfer
- Only the modified parts of files are transferred.
- Encrypted transfer
- Data is encrypted by default when transferred over the network.
- FS metadata
- File system permissions and attributes are synchronized.
- The synchronization can be resumed if interrupted.
- Handles renames
- Moved/renamed files are detected and not stored or transferred twice. It typically means that a checksum of files or its chunks is computed. Applications missing this functionality can be supplemented by combining with AUR, which only synchronizes renames.
- Version control
- The old version of files are backed up (reverse incremental backup).
- Change propagation
- Specifies in how many directions changes can be propagated.
- unidirectional means one-way synchronization of two locations,
- bidirectional means two-way synchronization of two locations and
- multidirectional means full synchronization of more than two locations.
- Conflict resolution
- The application handles file conflicts, either automatically or interactively, i.e. it does not silently discard conflicting files. This attribute does not apply to applications that only propagate changes in one direction.
- FS monitoring
- The application listens to file system events to trigger the synchronization.
- The application provides a command-line interface.
- Other interfaces
- The application has the specified user interfaces, e.g. GUI, TUI, or web-based.
- The license of the server and client applications.
- Other platforms
- Supported operating systems other than Linux.
- The project is maintained.
- Brief notes about special features that notably set the application apart from the others.
|Name||Package||Implementation||Delta transfer||Encrypted transfer||FS metadata||Resumable||Handles renames||Version control||Change propagation||Conflict resolution||FS monitoring||CLI||Other interfaces||License||Other platforms||Maintained||Specificity|
|FreeFileSync||AUR||C++||?||SFTP ||?||?||Yes ||Yes ||unidirectional / multidirectional||Yes||?||No||Yes||GPL||Windows, macOS||Yes|
|git-annex||Haskell, git||rsync ||rsync ||?||?||?||Yes||multidirectional; with git remotes ||renames conflicting files ||?||Yes||git-annex assistant||GPLv3||macOS, Android (beta), Windows (beta)||Yes||Manage files with git|
|osync.sh||AUR||Bash, based on rsync||rsync||rsync||?||Yes||No||Yes||bidirectional||keeps multiple versions of a file ||optional ||Yes||No||BSD||Yes|
|rclone||Go||No ||?||?||?||?||?||unidirectional ||?||?||Yes||RcloneBrowser||MIT||*BSD, Plan9, Solaris, Windows, macOS||Yes||Optimized for synchronization with cloud storage, behavior varies with the features supported by the remote location.|
|rdiff-backup||Python 2, librsync||rsync||rsync||Yes||?||No||Yes||unidirectional||No||Yes||No||GPL||Win32||?|
|Resilio Sync||AUR||C++||Yes||Yes||?||Yes||?||Yes||multidirectional||?||?||No||Web||Proprietary freemium||FreeBSD, Windows, macOS, Android, iOS, Windows Phone, Amazon Kindle Fire||Yes||P2P sync|
|rsync||C||Yes||SSH or native protocol||Yes||Yes||No||
||unidirectional||No||Yes||Rsync#Front-ends||GPLv3||Win32||Yes||Standard tool present on all Linux distributions.|
|SparkleShare||C#, git||Yes||AES-256 ||?||?||Yes||Yes||?||?||?||No||Yes||GPLv3||Windows, macOS||Yes||It can sync with any Git server over SSH.|
|Syncthing||Go||Yes ||Yes ||partial ||Yes||?||Yes , previous versions moved to archive folder||multidirectional||renames one file ||Yes||Yes||Web, GTK||MPL v2||BSD, Windows, macOS, Android, Kindle Paperwhite||Yes||P2P sync|
|Unison||OCaml||Yes||Yes||partial ||optional ||No||Yes ||bidirectional||interactive||No||Yes||GTK2||GPL||FreeBSD, Windows, macOS, Android||Yes |
Applications that can do incremental backups remember and take into account what data has been backed up during the last run (so-called "diffs") and eliminate the need to have duplicates of unchanged data. Restoring the data to a certain point in time would require locating the last full backup and all the incremental backups from then to the moment when it is supposed to be restored. This sort of backup is useful for those who do it very often.
- List of applications/Security#Backup programs
- Wikipedia:List of backup software
- Wikipedia:Comparison of backup software
- Wikipedia:Comparison of online backup services
- Name: the application name, linking to the ArchWiki article or the official website.
- Package: a link to the package.
- Implementation: the programming language, library, or utility that the application is based on.
- Compressed storage: compression is used for storage.
- Encrypted storage: encryption is used for storage.
- Delta transfer: only the modified parts of files are transferred.
- Encrypted transfer: data is encrypted by default when transferred over a network.
- FS metadata: file system permissions and attributes are backed up.
- Easy access: the backup is stored plainly in the file system, or is mountable as such.
- Resumable: the backup can be resumed without restarting it if interrupted.
- Handles renames: moved/renamed files are detected and not stored or transferred twice; it typically means that a checksum is computed for files or chunks thereof.
- CLI: the application is command-line driven, i.e. it is scriptable.
- Other interfaces: the application has the specified user interfaces, e.g. GUI, TUI, or web-based.
- Licence: the licence of the server and client applications.
- Other platforms: supported operating systems other than Linux.
- Maintained: whether the project is maintained.
- Specificity: brief notes about special features that notably set the application apart from the others.
These applications are aimed at backing up data from the machine they are installed on, although the backup destination can be located on an external machine or storage media.
If a file is modified, these applications store only its changed parts at the next snapshot. Compared to #File-based increments applications, these are more space-efficient, especially when large files receive small modifications; on the other hand, the archived snapshots have to be opened with the backup application that created them, since the files have to be reconstructed from the stored binary diffs.
|Name||Package||Implementation||Compressed storage||Encrypted storage||Delta transfer||Encrypted transfer||FS metadata||Easy access||Resumable||Handles renames||CLI||Other interfaces||Licence||Other platforms||Maintained||Specificity|
|Areca Backup||AUR||Java||Zip, Zip64||AES128, AES256||Yes||Yes||Yes||No||Pausing only||No||Yes||Yes||GPLv2||Windows||Yes|
|BorgBackup||Python, C (Cython)||lz4, zlib, lzma, zstd||AES256||Yes||SSH||Yes ||Yes ||Yes ||Yes||Yes||third party||BSD||*BSD, macOS, Windows (Cygwin / WSL)||Yes||Deduplication based on variable length chunks; support both local and SSH-based remote backup destination.|
|btar||broken link: archived in aur-mirror]AUR[||C||Yes||Yes||Yes||Yes||?||No||?||?||Yes||No||GPLv3||Yes||Redundancy, indexed extraction, multicore compression, input and output serialisation, tolerance to partial archive errors.|
|bup||AUR||C, Python, git||Yes||No||Yes||Yes||Immature||Yes ||pick up where you left off ||Yes||Yes||AUR||GPLv2||NetBSD, Windows, macOS||Yes||Same storage format as git.|
|Kup Backup System||rsync, bup front-end||Yes||Yes||Yes||Yes||Immature||Yes||No||Yes||bup||Qt||GPLv2||Yes|
|obnam||AUR||Python||Yes||GnuPG||Yes||Yes||?||Yes||checkpoints every 100MB||?||Yes||No||GPLv3||No|
|restic||AUR||Go||No ||AES-256 ||Yes||Yes||Yes ||Yes ||Yes ||Yes||Yes||No ||BSD||OpenBSD, Windows, macOS||Yes||Supports storage on various cloud services natively and through.|
|ZBackup||AUR||C++||LZMA, LZO||AES||Yes||Yes||?||planned ||No||Kinda through tar||Yes||No||GPLv2||Yes||Repository consists of immutable files.|
If a file is modified, these applications store its new version entirely at the next snapshot. Compared to #Chunk-based increments applications, these are less space-efficient, especially when large files receive small modifications; on the other hand, often the archived snapshots can be opened without the need to have the backup application installed.
- Hard links: whether unmodified files are stored as hard links to previous versions.
|Name||Package||Implementation||Compressed storage||Encrypted storage||Delta transfer||Encrypted transfer||FS metadata||Easy access||Resumable||Handles renames||Hard links||CLI||Other interfaces||Licence||Other platforms||Maintained||Specificity|
|Back In Time||AUR||Python, rsync, diff||No||No||rsync||rsync||rsync||Yes||No||No||Yes ||Yes||Qt||GPLv2||Yes|
|DAR (Disk ARchive)||AUR||C++||special archive format||Yes||Yes||Yes||?||?||?||?||No ||Yes||AUR||GPL||FreeBSD, NetBSD, Windows, macOS||Yes|
|Link-Backup||AUR||Python 2||No||No||?||SSH||?||?||Yes||Yes||No ||Yes||No||MIT||No||It copies itself to the server.|
|rdup||AUR||C||tar.gz||gpg, blowfish and others||?||?||?||Yes||?||No||Yes||Yes||No||GPLv3||No||Set of command-line tools.|
|rsnapshot||rsync||No||No||Yes||Yes||?||?||?||?||Yes ||Yes||No||GPLv2||Win32||No |
|TimeShift||AUR||rsync||No||No||rsync||rsync||?||?||?||?||Yes||No||GTK||GPLv3||Designed for full-system backups to dedicated devices.||Yes|
These applications have been designed to centralize the backup of several machines connected to a network, through a server-client model. In general they are more complicated to deploy, compared to #Single machine solutions.
- Control direction: Pull: server logs into client. Push: client initiates backup session.
- Increment type: the strategy used to reduce used space by deduplicating data (i.e., besides compression).
- file-based: if a file is modified, the entire new version is stored at each snapshot.
- hard-links: whether unmodified files are stored as hard links to previous versions.
- chunk-based: only the modified parts of files are stored at each snapshot.
- file-based: if a file is modified, the entire new version is stored at each snapshot.
|Name||Package||Implementation||Control direction||Compressed storage||Encrypted storage||Delta transfer||Encrypted transfer||FS metadata||Easy access||Resumable||Handles renames||Increment type||CLI||Other interfaces||Licence||Other platforms||Maintained||Specificity|
|BackupPC||Perl||Pull||Yes||No||Yes||Yes||Yes||No||Yes||?||file-based, hard links ||No||Web||GPLv2||Any (no client needed)||Yes||Identical files across backups of the same or different clients are stored only once.|
|Bacula||bacula* in AUR||C++||Pull||Yes||Yes||?||Yes||?||?||Yes||?||file-based ||Yes||GUI, Web||AGPLv3||Windows, macOS||Yes|
|burp||AUR||librsync||Push||Yes||Yes||Yes||Yes||Yes||?||Yes||?||chunk-based ||Yes||burp-ui||AGPLv3||Windows, macOS||Yes|
|SafeKeep||AUR||rdiff-backup||Pull||No||No||?||Yes||?||?||?||?||chunk-based ||Yes||Yes||GPL||No||Integrates with LVM and databases to create consistent backups. Bandwidth throttling.|
|Snebu||broken link: archived in aur-mirror]AUR[||C||Push or Pull||Yes||No||?||Yes||?||?||?||?||file-based ||Yes||No||GPLv3||?||Supports arbitrary retention schedules.|
|Synbak||Multitool wrapper||?||Yes||No||Yes||Yes||Yes||?||?||?||?||No||Web||GPLv3||Yes||Unifies several backup methods.|
|UrBackup||urbackup* in AUR||C++||Pull||No||No||Yes||Internet transfers only||Yes||Yes||Yes||Yes||file-based,hard-links and symlinks/chunk-based CoW-Snapshots||Yes (client)||GUI, Web||AGPLv3+||Windows, macOS||Yes||Identical files across backups of the same or different clients are stored only once. Integrates with LVM, dattobd and btrfs for file system snapshots.|
Version control systems
While version control systems are mostly used for source code, they can track any files in a directory.
- Backing up Linux and other Unix(-like) systems
- Exhaustive list of backup solutions for Linux
- Performance comparison of five remote incremental backup tools: Rsync, Rdiff-backup, Duplicity, Areca and Link-Backup
- Mirroring an Entire Site using Rsync over SSH[dead link 2018-09-14]
- rsync-snapshot.sh[dead link 2018-09-14] — Local and remote snapshot backup using rsync with hard links