Difference between revisions of "Synchronization and backup programs"

From ArchWiki
Jump to navigation Jump to search
(Removed Backup-Manager, as upstream is dead)
(→‎See also: fixed broken link)
 
(508 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
[[Category:Data compression and archiving]]
+
[[Category:Synchronization]]
[[Category:System recovery]]
+
[[Category:Backup]]
[[ru:Backup Programs]]
+
[[Category:Software comparisons]]
This wiki page contains information about various backup programs. It's a good idea to ''have'' regular backups of important data, most notably configuration files ({{Ic|/etc/*}}) and the local pacman database (usually {{Ic|/var/lib/pacman/local/*}}).
+
[[de:Backups]]
 +
[[ja:バックアッププログラム]]
 +
[[ru:Synchronization and backup programs]]
 +
[[zh-hans:Synchronization and backup programs]]
 +
{{Related articles start}}
 +
{{Related|System backup}}
 +
{{Related|Disk cloning}}
 +
{{Related|List of applications#File sharing}}
 +
{{Related|System maintenance#Backup}}
 +
{{Related|Dotfiles}}
 +
{{Related|File recovery}}
 +
{{Related articles end}}
  
== Introduction ==
+
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.
Before you start trying various programs out, try to think about your needs, e.g. consider the following questions:
 
* What backup medium do I have available? (CD, DVD, remote server, external hard drive, etc.)
 
* How often do I plan to backup? (daily, weekly, monthly, etc.)
 
* What features do I expect from the backup solution? (compression, encryption, handles renames, etc.)
 
* How do I plan to restore backups if needed?
 
  
== Incremental backups ==
+
== Backup overview ==
Applications that can do incremental backups remember and take into account what data has been backed up during the last run 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.
 
  
=== Rsync-type backups ===
+
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 main characteristic of this type of backups is that they maintain a copy of the directory you want to keep a backup of, in a traditional "mirror" fashion.
 
  
Certain rsync-type packages also do snapshot backups by storing files which describe how the contents of files and folders changed from the last backup (so-called 'diffs'). Hence, they are inherently incremental, but usually they do not have compression or encryption. On the other hand, a working copy of everything is immediately available, no decompression/decryption needed. A downside to rsync-type programs is that they cannot be easily burned and restored from a CD or DVD.
+
* 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.
  
==== Console ====
+
== Data synchronization ==
* {{App|[[rsync]]|A file transfer program to keep remote files in sync.
 
** rsync almost always makes a mirror of the source.
 
** Impossible to restore a full backup before the most recent backup (but you can use --backup to keep old versions of the files).
 
** Standard install on all distros.
 
** Can run over SSH (port 22) or native rsync protocol (port 873).
 
** Win32 version available.
 
|http://rsync.samba.org/|{{Pkg|rsync}}}}
 
  
* {{App|[[Wikipedia:Rsync#Variations|rdiff-backup]]|A utility for local/remote mirroring and incremental backups.
+
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.
** Stores the most recent backup as regular files.
 
** To revert to older versions, you apply the diff files to recreate the older versions.
 
** It is granularly incremental (delta backup), it only stores changes to a file; will not create a new copy of a file upon change.
 
** Win32 version available.
 
|http://www.nongnu.org/rdiff-backup/|{{Pkg|rdiff-backup}}}}
 
  
* {{App|rsnapshot|A remote filesystem snapshot utility.
+
See also:
** Does not store diffs, instead it copies entire files if they have changed.
+
* [[List of applications/Utilities#File synchronization]]
** Creates hard links between a series of backed-up trees (snapshots).
+
* [[List of applications/Internet#Cloud synchronization clients]]
** It is differential in that the size of the backup is only the original backup size plus the size of all files that have changed since the last backup.
+
* [[Wikipedia:Comparison of file synchronization software]]
** Destination filesystem must support hard links.
 
** Win32 version available.
 
|http://www.rsnapshot.org/|{{Pkg|rsnapshot}}}}
 
  
* {{App|SafeKeep|A client/server backup system which uses rdiff-backup.
+
=== Legend ===
** Integrates with Linux LVM and databases to create consistent backups.
 
** Bandwidth throttling.
 
|http://safekeep.sourceforge.net/|{{AUR|safekeep}}}}
 
  
* {{App|Link-Backup|A tool similar to rsync based scripts, but which does not use rsync.
+
;Name: The application name, linking to the ArchWiki article or the official website.
** Creates hard links between a series of backed-up trees (snapshots).
+
;Package: A link to the package.
** Intelligently handles renames, moves, and duplicate files without additional storage or transfer.
+
;Implementation: The programming language, library, or utility that the application is based on.
** The backup directory contains {{ic|.catalog}}, a catalog of all unique file instances; backup trees hard-link to this catalog.
+
;Delta transfer: Only the modified ''parts'' of files are transferred.
** Transfer occurs over standard I/O locally or remotely between a client and server instance of this script.
+
;Encrypted transfer: Data is encrypted by default when transferred over the network.
** It copies itself to the server; it does not need to be installed on the server.
+
;FS metadata: File system permissions and attributes are synchronized.
** Requires SSH for remote backups.
+
;Resumable: The synchronization can be resumed if interrupted.
** It resumes stopped backups; it can even be told to run for an arbitrary number of minutes.
+
;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|hsync}}, which ''only'' synchronizes renames.
|http://www.scottlu.com/Content/Link-Backup.html|{{AUR|link-backup}}}}
+
;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.
 +
;CLI: The application provides a command-line interface.
 +
;Other interfaces: The application has the specified user interfaces, e.g. GUI, TUI, or web-based.
 +
;License: The license of the server and client applications.
 +
;Other platforms: Supported operating systems other than Linux.
 +
;Maintained: The project is maintained.
 +
;Specificity: Brief notes about special features that notably set the application apart from the others.
  
* {{App|[[Wikipedia:Unison (file synchronizer)|Unison]]|A program that synchronizes files between two machines over network (LAN or Inet) using a smart diff method + rsync. Allows the user to interactively choose which changes to push, pull, or merge.|http://www.cis.upenn.edu/~bcpierce/unison/|{{Pkg|unison}}}}
+
=== Table ===
  
* {{App|oldtime|A highly customizable and configurable backup & restore system.|https://github.com/GutenYe/oldtime|{{AUR?|oldtime}}}}
+
{{Style|Explicitly list supported protocols / tools. Drop ''Encrypted transfer'' column because it depends on the protocol / tool. Simplify and color ''Change propagation'' column and move it leftwards. Split unmaintained into subsection? See also [[User:Larivact/drafts/Synchronization and backup programs#Synchronization]].}}
 +
{{Expansion|Fill in the blanks.}}
  
==== Graphical ====
+
{| class="wikitable sortable" style="text-align: center"
* {{App|Back In Time|A simple backup tool for Linux inspired by the [[Wikipedia:FlyBack|FlyBack]] and [https://wiki.ubuntu.com/TimeVault/ TimeVault] projects.
+
! Name
** Creates hard links between a series of backed-up trees (snapshots).
+
! Package
** Really is just a front-end to {{ic|rsync}}, {{ic|diff}}, {{ic|cp}}.
+
! Implementation
** A new snapshot is created only if something changed since the last snapshot.
+
! Delta transfer
|http://backintime.le-web.org/|{{AUR|backintime}}}}
+
! Encrypted transfer
 +
! FS metadata
 +
! Resumable
 +
! Handles renames
 +
! Version control
 +
! Change propagation
 +
! Conflict resolution
 +
! FS monitoring
 +
! CLI
 +
! Other interfaces
 +
! License
 +
! Other platforms
 +
! Maintained
 +
! Specificity
 +
|-
 +
! [https://www.freefilesync.org/ FreeFileSync]
 +
| {{AUR|freefilesync}}
 +
| C++
 +
| ?
 +
| {{G|SFTP [http://www.freefilesync.org/faq.php#features]}}
 +
| ?
 +
| ?
 +
| {{G|Yes [http://www.freefilesync.org/faq.php#features]}}
 +
| {{G|1=Yes [http://www.freefilesync.org/manual.php?topic=versioning]}}
 +
|'''uni'''directional / '''multi'''directional
 +
| {{Yes}}
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
| {{B|GPL}}
 +
| Windows, macOS
 +
| {{Yes}}
 +
|
 +
|-
 +
! [https://git-annex.branchable.com/ git-annex]
 +
| {{Pkg|git-annex}}
 +
| Haskell, git
 +
| {{G|rsync [http://git-annex.branchable.com/transferring_data/]}}
 +
| {{G|rsync, others [http://git-annex.branchable.com/transferring_data/]}}
 +
| {{R|No, but has custom non-FS metadata [https://git-annex.branchable.com/metadata/]}}
 +
| {{G|Yes [https://git-annex.branchable.com/transferring_data/]}}
 +
| {{G|Yes, content-addressable storage}}
 +
| {{Yes}}
 +
| '''multi'''directional; with git remotes [http://git-annex.branchable.com/sync/]
 +
| {{G|renames conflicting files [http://git-annex.branchable.com/automatic_conflict_resolution/]}}
 +
| {{G|optional, git-annex assistant}}
 +
| {{Yes}}
 +
| {{G|[http://git-annex.branchable.com/assistant/ git-annex assistant]}}
 +
| {{B|GPLv3}}
 +
| macOS, Android (beta), Windows (beta)
 +
| {{Yes}}
 +
| {{L|Manage files with git}}
 +
|-
 +
! [http://www.netpower.fr/osync osync.sh]
 +
| {{AUR|osync}}
 +
| Bash, based on rsync
 +
| {{G|rsync}}
 +
| {{G|rsync}}
 +
| ?
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| '''bi'''directional
 +
| {{G|keeps multiple versions of a file [http://www.netpower.fr/sites/default/files/soft/html-doc/osync_v1.2.html#toc-Subsubsection-1.3.1]}}
 +
| {{G|optional [https://github.com/deajan/osync#daemon-mode]}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{B|BSD}}
 +
|
 +
| {{Yes}}
 +
|
 +
|-
 +
! [https://rclone.org/ rclone]
 +
| {{Pkg|rclone}}
 +
| Go
 +
| {{No}} [https://rclone.org/faq/#why-doesn-t-rclone-support-partial-transfers-binary-diffs-like-rsync]
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| '''uni'''directional [https://rclone.org/faq/#can-rclone-do-bi-directional-sync]
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{G|[https://github.com/mmozeiko/RcloneBrowser RcloneBrowser]}}
 +
| {{B|MIT}}
 +
| *BSD, Plan9, Solaris, Windows, macOS
 +
| {{Yes}}
 +
| {{L|Optimized for synchronization with cloud storage, behavior varies with the features supported by the remote location.}}
 +
|-
 +
! [http://www.nongnu.org/rdiff-backup/ rdiff-backup]
 +
| {{Pkg|rdiff-backup}}
 +
| Python 2, librsync
 +
| {{G|rsync}}
 +
| {{G|rsync}}
 +
| {{Yes}}
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
|colspan="2"| '''uni'''directional
 +
| {{No}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{B|GPL}}
 +
| Win32
 +
| ?
 +
|
 +
|-
 +
! [[Resilio Sync]]
 +
| {{aur|rslsync}}
 +
| C++
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| '''multi'''directional
 +
| ?
 +
| ?
 +
| {{No}}
 +
| {{G|Web}}
 +
| {{V|Proprietary freemium}}
 +
| FreeBSD, Windows, macOS, Android, iOS, Windows Phone, Amazon Kindle Fire
 +
| {{Yes}}
 +
| {{L|P2P sync}}
 +
|-
 +
! [[rsync]]
 +
| {{pkg|rsync}}
 +
| C
 +
| {{Yes}}
 +
| {{G|SSH or native protocol}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{G|
 +
* {{ic|--link-dest}} with hard links [http://www.ibm.com/developerworks/aix/library/au-spunix_rsync/index.html#backup]
 +
* {{ic|--backup}}
 +
}}
 +
|colspan="2"| '''uni'''directional
 +
| {{No}}
 +
| {{Yes}}
 +
| {{G|[[Rsync#Front-ends]]}}
 +
| {{B|GPLv3}}
 +
| Win32
 +
| {{Yes}}
 +
| {{L|Standard tool present on all Linux distributions.}}
 +
|-
 +
! [https://sparkleshare.org/ SparkleShare]
 +
| {{Pkg|sparkleshare}}
 +
| C#, git
 +
| {{Yes}}
 +
| {{G|AES-256}} [https://github.com/hbons/SparkleShare/wiki/Client-Side-Encryption]
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
| {{B|GPLv3}}
 +
| Windows, macOS
 +
| {{Yes}}
 +
| It can sync with any Git server over SSH.
 +
|-
 +
! [https://www.syncany.org/ Syncany]
 +
| {{AUR|syncany}}
 +
| Java
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{B|GPLv3}}
 +
|
 +
| {{No}} [https://github.com/syncany/syncany/graphs/contributors]
 +
|
 +
|-
 +
! [[Syncthing]]
 +
| {{pkg|syncthing}}
 +
| Go
 +
| {{G|Yes [http://docs.syncthing.net/users/faq.html#is-synchronization-fast]}}
 +
| {{G|Yes [http://docs.syncthing.net/users/security.html]}}
 +
| {{Y|partial [http://docs.syncthing.net/users/faq.html#what-things-are-synced]}}
 +
| {{G|Yes }}
 +
| ?
 +
| {{G|Yes [http://docs.syncthing.net/users/versioning.html]}}, previous versions moved to archive folder
 +
| '''multi'''directional
 +
| {{G|renames one file [https://docs.syncthing.net/users/faq.html#what-if-there-is-a-conflict]}}
 +
| {{G|Yes}}
 +
| {{Yes}}
 +
| {{G|Web, GTK}}
 +
| {{B|MPL v2}}
 +
| BSD, Windows, macOS, Android, Kindle Paperwhite
 +
| {{Yes}}
 +
| {{L|P2P sync}}
 +
|-
 +
! [http://synkron.sourceforge.net/ Synkron]
 +
| {{AUR|synkron}}
 +
| C++
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| '''multi'''directional
 +
| ?
 +
| ?
 +
| {{No}}
 +
| {{G|Qt}}
 +
| {{B|GPLv2}}
 +
| Windows, macOS
 +
| {{R|[https://sourceforge.net/projects/synkron/ No]}}
 +
|
 +
|-
 +
! [[taskd]]
 +
| {{Pkg|taskd}}
 +
| C++, Python
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| '''multi'''directional
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{B|MIT}}
 +
| Android
 +
| {{Yes}}
 +
|
 +
|-
 +
! [[Unison]]
 +
| {{pkg|unison}}
 +
| OCaml
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Y|partial [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html#perms]}}
 +
| {{G|optional [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html#speeding]}}
 +
| {{No}}
 +
| {{G|Yes [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html#backups]}}
 +
| '''bi'''directional
 +
| {{G|interactive}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{G|GTK2}}
 +
| {{B|GPL}}
 +
| FreeBSD, Windows, macOS, Android
 +
| {{G|Yes [http://www.cis.upenn.edu/~bcpierce/unison/status.html]}}
 +
|
 +
|}
  
* {{App|[[Wikipedia:FlyBack|FlyBack]]|A clone of Apple's [[Wikipedia:Time Machine (Mac OS)|Time Machine]], a backup utility for Mac OS X.|http://www.flyback-project.org/|{{AUR|flyback}}}}
+
== Incremental backups ==
 
 
* {{App|[[Wikipedia:Areca Backup|Areca Backup]]|An easy to use and reliable backup solution for Linux and Windows.
 
** Written in Java.
 
** Primarily archive-based (zip), but will do file-based backup as well.
 
** Delta backup supported (stores only changes).
 
|http://areca.sourceforge.net/|{{AUR|areca}}}}
 
 
 
* {{App|[[Wikipedia:LuckyBackup|luckyBackup]]|An easy program to backup and sync your files.
 
** It is written in Qt and C++.
 
** It has sync, backup (with include and exclude options) and restore capabilities.
 
** It can do remote connection backups, scheduled backups.
 
** A command line mode.
 
|http://luckybackup.sourceforge.net/index.html|{{AUR|luckybackup}}}}
 
 
 
* {{App|syncBackup|A front-end for rsync that provides a fast and extraordinary copying tool. It offers the most common options that control its behavior and permit very flexible specification of the set of files to be copied.
 
|http://www.darhon.com/syncbackup|{{AUR|syncbackup}}}}
 
 
 
* {{App|[[BackupPC]]|A high-performance, enterprise-grade system for backing up Unix, Linux, Windows, and Mac OS X desktops and laptops to a remote server.
 
** Deduplication: Identical files across multiple backups of the same or different PCs are stored only once resulting in substantial savings in disk storage and disk I/O.
 
** Optional compression support further reducing disk storage.
 
** No client-side software is needed.
 
** Simple but powerful web-based UI.
 
|http://backuppc.sourceforge.net/index.html|{{Pkg|backuppc}}}}
 
 
 
=== Other backups ===
 
Most other backup applications tend to create (big) archive files and (of course) keep track of what's been archived. Creating {{ic|.tar.bz2}} or {{ic|.tar.gz}} archives has the advantage that you can extract the backups with just tar/bzip2/gzip, so you do not need to have the backup program around.
 
 
 
==== Console ====
 
* {{App|Arch Backup|A trivial backup script with simple configuration.
 
** Configurable compression method.
 
** Multiple backup targets.
 
|http://code.google.com/p/archlinux-stuff/|{{Pkg|arch-backup}}}}
 
 
 
* {{App|[[Backup with hdup|hdup]]|A very simple command line backup tool.
 
** Creates tar.gz or tar.bz2 archives.
 
** Supports gpg encryption.
 
** Supports pushing over SSH.
 
** Multiple backup targets.
 
|http://miek.nl/projects/hdup2/|{{AUR|hdup}}}}
 
 
 
* {{App|rdup|A platform for backups that provides scripts to facilitate backups and delegates the encryption, compression, transfer and packaging to other utilities in a true Unix-way.
 
** Creates tar.gz archives or rsync-type copy.
 
** Encryption (gpg, blowfish and others); also applies for rsync-type copy.
 
** Compression (also for rsync-type copy).
 
|http://miek.nl/projects/rdup|{{AUR|rdup}}}}
 
 
 
* {{App|[[Duplicity]]|A simple command-line utility which allows encrypted compressed incremental backup to nearly any storage.
 
** Supports gpg encryption and signing.
 
** Supports gzip compression.
 
** Supports full or incremental backups, incremental backup stores only difference between new and old file.
 
** Supports pushing over FTP, SSH, rsync, WebDAV, WebDAVs, HSi and Amazon S3 or local filesystem.
 
|http://www.nongnu.org/duplicity/|{{Pkg|duplicity}}}}
 
 
 
* {{App|[[Wikipedia:DAR (Disk Archiver)|DAR]]|A full-featured command-line backup tool, short for Disk ARchive.
 
** It uses its own format for archives (so you need to have it around when you want to restore).
 
** Supports splitting backups into more files by size.
 
** Makefile-type config files, some custom scripts are available along with it.
 
** Supports basic encryption.
 
** Automatic backup using [[cron]] is possible with {{AUR|sarab}}.
 
|http://dar.linux.free.fr/|{{AUR|dar}} {{AUR|kdar}} (fontend)}}
 
 
 
* {{App|Manent|An algorithmically strong backup and archival program. NOTE: no upstream activity since 2009.
 
** Efficient backup to anything that looks like a storage.
 
** Works well over a slow and unreliable network.
 
** Offers online access to the contents of the backup.
 
** Backed up storage is completely encrypted.
 
** Several computers can use the same storage for backup, automatically sharing data.
 
** Not reliant on timestamps of the remote system to detect changes.
 
** Cross-platform support for Unicode file names.
 
|http://code.google.com/p/manent/|{{AUR|manent}}}}
 
 
 
* {{App|btar|tar-compatible archiver
 
** Fast archive creation (multicore compression or ciphering)
 
** Arbitrary chain of compression/ciphers (calls any compression/ciphering programs)
 
** Indexed archive retrieval or listing
 
** Redundancy
 
** Serialization through pipes (and only one file per backup)
 
** Can be extracted or checked with gnutar
 
** Differential backups of multiple levels
 
** Optional encoding of big files with rsync-differences
 
|http://viric.name/cgi-bin/btar|{{AUR|btar}}}}
 
 
 
==== Graphical ====
 
* {{App|Backerupper|A simple program for backing up selected directories over a local network. Its main intended purpose is backing up a user's personal data.
 
** Creates {{ic|.tar.gz}} archives.
 
** Configurable backup frequency, backup time and max copies.
 
|http://sourceforge.net/projects/backerupper/|{{AUR|backerupper}}}}
 
 
 
* {{App|[[Duplicity|Déjà Dup]]|A simple GTK+ backup program. It hides the complexity of doing backups the 'right way' (encrypted, off-site, and regular) and uses duplicity as the backend.
 
** Automatic, timed backup configurable in GUI.
 
** Restore wizard.
 
** Integrated into the Nautilus file manager.
 
** Inherits several features of duplicity.
 
|https://launchpad.net/deja-dup|{{Pkg|deja-dup|}}}}
 
  
* {{App|Synkron|A folder synchronization tool.
+
Applications that can do [[Wikipedia:Incremental backup|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.
** Syncs multiple folders.
 
** Can exclude files from sync based on wildcards.
 
** Restores files.
 
** Cross-platform support.
 
|http://synkron.sourceforge.net/|{{AUR|synkron}}}}
 
  
== Cloud backups ==
+
See also:
* {{App|[[Wikipedia:CrashPlan|CrashPlan]]|An online/offsite backup solution.
+
* [[List of applications/Security#Backup programs]]
** Unlimited online space for very reasonable pricing.
+
* [[Wikipedia:List of backup software]]
** Automatic and incremental backups to multiple destinations.
+
* [[Wikipedia:Comparison of backup software]]
** Intuitive GUI.
+
* [[Wikipedia:Comparison of online backup services]]
** Offers encryption and de-duplication.
 
** Software is generally free.
 
|http://www.crashplan.com/|{{AUR|crashplan}}}}
 
  
* {{App|[[Dropbox]]|A popular file-sharing service.
+
'''Legend:'''
** A daemon monitors a specified directory, and uploads incremental changes to dropbox.com. 
 
** Changes automatically show up on your other computers. 
 
** Includes file sharing and a public directory. 
 
** You can recover deleted files. 
 
** Community written add-ons. 
 
** Free accounts have 2GB storage.
 
|http://www.getdropbox.com|{{AUR|dropbox}} {{AUR|nautilus-dropbox}}}}
 
  
* {{App|[[Wikipedia:Jungle Disk|Jungle Disk]]|An online backup tool that stores its data in Amazon S3 or Rackspace Cloud Files.
+
* '''Name''': the application name, linking to the ArchWiki article or the official website.
** A Nautilus extension.
+
* '''Package''': a link to the package.
** Only paid plans available.
+
* '''Implementation''': the programming language, library, or utility that the application is based on.
|http://www.jungledisk.com/|{{AUR|nautilus-jungledisk}}}}
+
* '''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.
  
* {{App|Tarsnap|A secure online backup service for BSD, Linux, OS X, Solaris and Windows (through Cygwin).
+
=== Single machine ===
** Compressed encrypted backups to Amazon S3 Servers.
 
** Automate via [[cron]].
 
** Incremental backups.
 
** Backup any files or directories.
 
** Command line only client.
 
** Pay only for usage (bandwidth and storage).
 
|http://www.tarsnap.com|{{Pkg|tarsnap}}}}
 
  
* {{App|[[Wikipedia:Wuala|Wuala]]|A secure online storage, file synchronization, versioning and backup service.
+
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.
** Closed source, free and paid version available.
 
** Free account holds 5GB.
 
** Includes file sharing and a public directory.
 
** Incremental backup and sync are both supported.
 
** Social networking features.
 
** All files in the cloud are first encrypted locally.
 
|http://www.wuala.com/|{{AUR|wuala}}, {{AUR|wuala-daemon}} – to run as daemon}}
 
  
* {{App|[[Wikipedia:SpiderOak|SpiderOak]]|An online backup tool for Windows, Mac and Linux users to back up, share, sync, access and store[1] their data.
+
==== Chunk-based increments ====
** Free and paid version available.
 
** Free account holds 2GB.
 
** Includes file sharing and a public directory.
 
** Incremental backup and sync are both supported.
 
|https://spideroak.com/|{{AUR|spideroak}}}}
 
  
* {{App|[[Ubuntu One]]|An online storage service with sync and sharing across platforms.
+
{{Expansion|Fill in the blanks. ''FS metadata'' column: What does ''Immature'' mean? ''Resumable'' column: What does ''Pausing only'' / ''Kinda through tar'' mean?}}
** Free and payed versions available.
 
** Free account with 5GB.
 
** Mobile access.
 
** Music streaming.
 
|https://one.ubuntu.com/services/|{{Pkg|ubuntuone-client}}}}
 
  
* {{App|Packrat|A simple, modular backup system that uses [[Wikipedia:DAR (Disk Archiver)|DAR]] to take full or incremental backups of files and can store them locally, on a remote system via SSH, or on Amazon S3.|http://www.zeroflux.org/projects|{{AUR|packrat}}}}
+
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.
  
== Non-incremental backups ==
+
{| class="wikitable sortable" style="text-align:center"
Another type of backups are those used in case of a disaster. These include application that allow easy backup of entire filesystems and recovery in case of failure, usually in the form of a Live CD or USB drive. The contains complete system images from one or more specific points in time and are frequently used by to record known good configurations.
+
! 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
 +
|-
 +
! [http://areca.sourceforge.net/ Areca Backup]
 +
| {{AUR|areca}}
 +
| Java
 +
| {{G|Zip, Zip64}}
 +
| {{G|AES128, AES256}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Y|Pausing only}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| GPLv2
 +
| Windows
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://borgbackup.readthedocs.org/en/stable/ BorgBackup]
 +
| {{Pkg|borg}} {{AUR|borg-bin}}
 +
| Python, C (Cython)
 +
| {{G|lz4, zlib, lzma, zstd}}
 +
| {{G|AES256}}
 +
| {{Yes}}
 +
| {{G|SSH}}
 +
| {{Yes}} [http://borgbackup.readthedocs.org/en/stable/faq.html#which-file-types-attributes-etc-are-preserved]
 +
| {{Yes}} [http://borgbackup.readthedocs.org/en/stable/usage.html#borg-mount]
 +
| {{Yes}} [http://borgbackup.readthedocs.org/en/stable/faq.html#if-a-backup-stops-mid-way-does-the-already-backed-up-data-stay-there]
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{G|third party}}
 +
| BSD
 +
| *BSD, macOS, Windows (Cygwin / WSL)[https://borgbackup.readthedocs.io/en/stable/#main-features]
 +
| {{Yes}}
 +
| {{L|Deduplication based on variable length chunks; support both local and SSH-based remote backup destination.}}
 +
|-
 +
! [http://viric.name/cgi-bin/btar btar]
 +
| {{AUR|btar}}{{Broken package link|{{aur-mirror|btar}}}}
 +
| C
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{No}}
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv3
 +
|
 +
| {{Yes}}
 +
| {{L|Redundancy, indexed extraction, multicore compression, input and output serialisation, tolerance to partial archive errors.}}
 +
|-
 +
! [https://bup.github.io/ bup]
 +
| {{Pkg|bup}} {{AUR|bup-git}}
 +
| C, Python, git
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{G|Immature}}
 +
| {{Yes}} [https://bup.github.io/man/bup-fuse.html]
 +
| {{G|pick up where you left off [https://github.com/bup/bup/blob/master/README.md#reasons-bup-is-awesome]}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{G|{{AUR|bups}}}}
 +
| GPLv2
 +
| NetBSD, Windows, macOS
 +
| {{Yes}}
 +
| {{L|Same storage format as git.}}
 +
|-
 +
! [http://www.duplicati.com/ Duplicati]
 +
| {{AUR|duplicati-latest}}
 +
| C#
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Y|Pausing only}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| LGPL
 +
| Windows, macOS
 +
| {{Yes}}
 +
|
 +
|-
 +
! [[Duplicity]]
 +
| {{Pkg|duplicity}}
 +
| librsync
 +
| {{G|gzip}}
 +
| {{G|gpg}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{G|[[Duplicity#Front-ends|Yes]]}}
 +
| GPL
 +
|
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://kde-apps.org/content/show.php/Kup+Backup+System?content=147465 Kup Backup System]
 +
| {{Pkg|kup}}
 +
| rsync, bup front-end
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{G|Immature}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Y|bup}}
 +
| {{G|Qt}}
 +
| GPLv2
 +
|
 +
| {{Yes}}
 +
|
 +
|-
 +
! [https://obnam.org/ obnam]
 +
| {{AUR|obnam}}
 +
| Python
 +
| {{Yes}}
 +
| {{G|GnuPG}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| {{G|checkpoints every 100MB}}
 +
| ?
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv3
 +
|
 +
| {{R|[https://blog.liw.fi/posts/2017/08/13/retiring_obnam/ No]}}
 +
|
 +
|-
 +
! [https://restic.net/ restic]
 +
| {{Pkg|restic}} {{AUR|restic-git}}
 +
| Go
 +
| {{No}} [https://github.com/restic/restic/issues/21]
 +
| {{G|AES-256}} [https://github.com/restic/restic/blob/master/doc/Design.md]
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}} [https://restic.readthedocs.io/en/latest/manual_rest.html#metadata-handling]
 +
| {{Yes}} [https://restic.readthedocs.io/en/stable/050_restore.html#restore-using-mount]
 +
| {{Yes}} [https://github.com/restic/restic/pull/310]
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}} [https://github.com/restic/restic/issues/60]
 +
| BSD
 +
| OpenBSD, Windows, macOS
 +
| {{Yes}}
 +
| {{L|Supports storage on various cloud services natively and through {{Pkg|rclone}}.}}
 +
|-
 +
! [http://zbackup.org/ ZBackup]
 +
| {{AUR|zbackup}}
 +
| C++
 +
| {{G|LZMA, LZO}}
 +
| {{G|AES}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{R|planned [https://github.com/zbackup/zbackup#improvements]}}
 +
| {{No}}
 +
| {{Y|Kinda through tar}}
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv2
 +
|
 +
| {{Yes}}
 +
| {{L|Repository consists of immutable files.}}
 +
|}
  
* {{App|Q7Z|P7Zip GUI for Linux, which attempts to simplify data compression and backup.  It can create the following archive types: 7z, BZip2, Zip, GZip, Tar.
+
==== File-based increments ====
** Updates existing archives quickly.
 
** Backup multiple folders to a storage location.
 
** Create or extract protected archives.
 
** Lessen effort by using archiving profiles and lists.
 
|http://k7z.sourceforge.net/|{{AUR|q7z}}}}
 
  
* {{App|[[Partclone]]|A tool that can be used to back up and restore a partition while considering only used blocks.
+
{{Expansion|Fill in the blanks.}}
** Supports ext2, ext3, hfs+, reiser3.5, reiser3.6, reiser4, ext4 and btrfs.
 
** Supports compression.
 
|http://partclone.nchc.org.tw/trac/|{{AUR|partclone}}}}
 
  
* {{App|[[Wikipedia:Redo Backup and Recovery|Redo Backup and Recovery]]|A backup and disaster recovery application that runs from a bootable Linux CD image.
+
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.
** Is capable of bare-metal backup and recovery of disk partitions.
 
** Uses [http://www.xpud.org/ xPUD] and [[Partclone]] for the backend.
 
|http://www.redobackup.org/|{{AUR?|redobackup}}}}
 
  
* {{App|[[Wikipedia:Clonezilla|Clonezilla]]|A disaster recovery, disk cloning, disk imaging and deployment solution.
+
'''Specific legend:'''
** Boots from live CD, USB flash drive, or PXE server.
 
** Supports ext2, ext3, ext4, reiserfs, reiser4, xfs, jfs, btrfs FAT32, NTFS, HFS+ and others.
 
** Uses Partclone (default), Partimage (optional), ntfsclone (optional), or dd to image or clone a partition.
 
** Multicasting server to restore to many machines at once.
 
|http://clonezilla.org/|{{AUR|clonezilla}}}}
 
  
* {{App|[[Wikipedia:Partimage|Partimage]]|A disk cloning utility for Linux/UNIX environments.
+
* '''Hard links''': whether unmodified files are stored as hard links to previous versions.
** Has a Live CD.
 
** Supports the most popular filesystems on Linux, Windows and Mac OS.
 
** Compression.
 
** Saving to multiple CDs or DVDs or across a network using Samba/NFS.
 
|http://www.partimage.org/Main_Page|{{Pkg|partimage}}}}
 
  
* {{App|FSArchiver|A safe and flexible file-system backup and deployment tool
+
{| class="wikitable sortable" style="text-align:center"
** Support for basic file attributes (permissions, owner, ...).
+
! Name
** Support for multiple file-systems per archive.
+
! Package
** Support for extended attributes (they are used by SELinux).
+
! Implementation
** Support the basic file-system attributes (label, uuid, block-size) for all linux file-systems.
+
! Compressed storage
** Support for [http://www.fsarchiver.org/Cloning-ntfs ntfs filesystems] (ability to create flexible clones of a Windows partitions).
+
! Encrypted storage
** Checksumming of everything which is written in the archive (headers, data blocks, whole files).
+
! Delta transfer
** Ability to restore an archive which is corrupt (it will just skip the current file).
+
! Encrypted transfer
** Multi-threaded lzo, gzip, bzip2, lzma compression.
+
! FS metadata
** Support for splitting large archives into several files with a fixed maximum size.
+
! Easy access
** Encryption of the archive using a password. Based on blowfish from libcrypto from [[OpenSSL]].
+
! Resumable
** Support backup of a mounted root filesystem (-A option).
+
! Handles renames
|http://www.fsarchiver.org/Main_Page|{{Pkg|fsarchiver}}}}
+
! Hard links
 +
! CLI
 +
! Other interfaces
 +
! Licence
 +
! Other platforms
 +
! Maintained
 +
! Specificity
 +
|-
 +
! [[Back In Time]]
 +
| {{AUR|backintime}}
 +
| Python, rsync, diff
 +
| {{No}}
 +
| {{No}}
 +
| {{G|rsync}}
 +
| {{G|rsync}}
 +
| {{G|rsync}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{No}}
 +
| {{G|Yes [http://backintime.le-web.org/documentation/]}}
 +
| {{Yes}}
 +
| {{G|Qt}}
 +
| GPLv2
 +
|
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://dar.linux.free.fr/ DAR] (Disk ARchive)
 +
| {{AUR|dar}}
 +
| C++
 +
| {{G|special archive format}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| {{R|No [http://dar.linux.free.fr/doc/Features.html]}}
 +
| {{Yes}}
 +
| {{G|{{AUR|dargui}}}}
 +
| GPL
 +
| FreeBSD, NetBSD, Windows, macOS
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://www.scottlu.com/Content/Link-Backup.html Link-Backup]
 +
| {{AUR|link-backup}}
 +
| Python 2
 +
| {{No}}
 +
| {{No}}
 +
| ?
 +
| {{G|SSH}}
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{R|No [http://www.scottlu.com/Content/Link-Backup.html]}}
 +
| {{Yes}}
 +
| {{No}}
 +
| MIT
 +
|
 +
| {{No}}
 +
| {{L|It copies itself to the server.}}
 +
|-
 +
! [https://github.com/miekg/rdup rdup]
 +
| {{AUR|rdup}}
 +
| C
 +
| {{G|tar.gz}}
 +
| {{G|gpg, blowfish and others}}
 +
| ?
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv3
 +
|
 +
| {{No}}
 +
| {{L|Set of command-line tools.}}
 +
|-
 +
! [[rsnapshot]]
 +
| {{Pkg|rsnapshot}}
 +
| rsync
 +
| {{No}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| {{G|Yes [http://rsnapshot.org/rsnapshot/docs/docbook/rest.html]}}
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv2
 +
| Win32
 +
| {{R| No [https://github.com/rsnapshot/rsnapshot/issues/191]}}
 +
|
 +
|-
 +
! [https://launchpad.net/sbackup sbackup]
 +
| {{AUR|sbackup}}
 +
| Python
 +
| {{G|gzip, bzip2}}
 +
| {{No}}
 +
| ?
 +
| {{G|SSH}}
 +
| ?
 +
| {{No}}
 +
| {{No}}
 +
| {{No}}
 +
| {{No}}
 +
| {{No}}
 +
| {{G|GTK}}
 +
| GPLv3
 +
|
 +
| {{No}}
 +
|
 +
|-
 +
! [https://github.com/teejee2008/timeshift TimeShift]
 +
| {{AUR|timeshift}}
 +
| rsync
 +
| {{No}}
 +
| {{No}}
 +
| {{G|rsync}}
 +
| {{G|rsync}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| {{No}}
 +
| {{G|GTK}}
 +
| GPLv3
 +
| Designed for full-system backups to dedicated devices.
 +
| {{Yes}}
 +
|
 +
|}
  
* {{App|[[Wikipedia:Mondo Rescue|Mondo Rescue]]|A disaster recovery solution to create backup media that can be used to redeploy the damaged system.
+
=== Network oriented ===
** Image-based backups, supporting Linux/Windows.
 
** Compression rate is adjustable.
 
** Can backup live systems (without having to halt it).
 
** Can split image over many files.
 
** Supports booting to a Live CD to perform a full restore.
 
** Can backup/restore over NFS, from CDs, tape drives and and other media.
 
** Can verify backups.
 
|http://www.mondorescue.org/|{{AUR|mondo}}}}
 
  
== Versioning systems ==
+
{{Expansion|Fill in the blanks. ''Encrypted transfer'' column: What does ''Internet transfers only'' mean?}}
These are traditionally used for keeping track of software development; but if you want to have a simple way to manage your config files in one directory, it might be a good solution.
 
  
=== Version control systems ===
+
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.
{{Wikipedia|Comparison of revision control software}}.
 
  
* {{App|[[Git]]|A distributed revision control and source code management system with an emphasis on speed.
+
'''Specific legend:'''
** Very easy creation, merging, and deletion of branches.
 
** Nearly all operations are performed locally, giving it a huge speed advantage on centralized systems.
 
** Has a "staging area" or "index", this is an intermediate area where commits can be formatted and reviewed before completing the commit.
 
** Does not handle binary files very well.
 
|http://git-scm.com/|{{Pkg|git}}}}
 
  
* {{App|[[Subversion]]|A full-featured centralized version control system originally designed to be a better CVS.
+
* '''Control direction''': Pull: server logs into client. Push: client initiates backup session.
** Renamed/copied/moved/removed files retain full revision history.
+
* '''Increment type''': the strategy used to reduce used space by deduplicating data (i.e., besides compression).
** Native support for binary files, with space-efficient binary-diff storage.
+
** '''file-based''': if a file is modified, the entire new version is stored at each snapshot.
** Costs proportional to change size, not to data size.
+
*** '''hard-links''': whether unmodified files are stored as hard links to previous versions.
** Allows arbitrary metadata ("properties") to be attached to any file or directory.
+
** '''chunk-based''': only the modified ''parts'' of files are stored at each snapshot.
|http://subversion.apache.org/|{{Pkg|subversion}}}}
 
  
* {{App|[[Mercurial]]|A distributed version control system written in Python and similar in many ways to Git.
+
{| class="wikitable sortable" style="text-align:center"
** Platform independent.
+
! Name
** Support for [http://mercurial.selenic.com/wiki/UsingExtensions extensions].
+
! Package
** A set of commands consistent with Subversion.
+
! Implementation
** Supports tags.
+
! Control direction
|http://mercurial.selenic.com/|{{Pkg|mercurial}}}}
+
! 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]]
 +
| {{Pkg|backuppc}}
 +
| Perl
 +
| Pull
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| ?
 +
| file-based, hard links [http://backuppc.sourceforge.net/faq/BackupPC.html#Backup-basics]
 +
| {{No}}
 +
| {{G|Web}}
 +
| GPLv2
 +
| Any (no client needed)
 +
| {{Yes}}
 +
| {{L|Identical files across backups of the same or different clients are stored only once.}}
 +
|-
 +
! [http://www.bacula.org Bacula]
 +
| [https://aur.archlinux.org/packages/?K=bacula bacula*] in [[AUR]]
 +
| C++
 +
| Pull
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| file-based [http://burp.grke.org/why.html]
 +
| {{Yes}}
 +
| {{G|GUI, Web}}
 +
| AGPLv3
 +
| Windows, macOS
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://burp.grke.org burp]
 +
| {{AUR|burp-backup}}
 +
| librsync
 +
| Push
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| chunk-based [http://burp.grke.org/why.html]
 +
| {{Yes}}
 +
| {{G|[https://git.ziirish.me/ziirish/burp-ui burp-ui]}}
 +
| AGPLv3
 +
| Windows, macOS
 +
| {{Yes}}
 +
|
 +
|-
 +
! [http://safekeep.sourceforge.net/ SafeKeep]
 +
| {{AUR|safekeep}}
 +
| rdiff-backup
 +
| Pull
 +
| {{No}}
 +
| {{No}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| chunk-based [http://safekeep.sourceforge.net/safekeep.html]
 +
| {{Yes}}
 +
| {{Yes}}
 +
| GPL
 +
|
 +
| {{No}}
 +
| {{L|Integrates with [[LVM]] and databases to create consistent backups. Bandwidth throttling.}}
 +
|-
 +
! [http://www.snebu.com Snebu]
 +
| {{AUR|snebu}}{{Broken package link|{{aur-mirror|snebu}}}}
 +
| C
 +
| Push or Pull
 +
| {{Yes}}
 +
| {{No}}
 +
| ?
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| file-based [http://www.snebu.com/#_concepts]
 +
| {{Yes}}
 +
| {{No}}
 +
| GPLv3
 +
|
 +
| ?
 +
| {{L|Supports arbitrary retention schedules.}}
 +
|-
 +
! [http://www.initzero.it/portal/soluzioni/software-open-source/synbak-universal-backup-system_2623.html Synbak]
 +
| {{Pkg|synbak}}
 +
| Multitool wrapper
 +
| ?
 +
| {{Yes}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| ?
 +
| ?
 +
| ?
 +
| ?
 +
| {{No}}
 +
| {{G|Web}}
 +
| GPLv3
 +
|
 +
| {{Yes}}
 +
| {{L|Unifies several backup methods.}}
 +
|-
 +
! [https://www.urbackup.org UrBackup]
 +
| [https://aur.archlinux.org/packages/?K=urbackup urbackup*] in [[AUR]]
 +
| C++
 +
| Pull
 +
| {{No}}
 +
| {{No}}
 +
| {{Yes}}
 +
| {{Y|Internet transfers only}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}}
 +
| file-based,hard-links and symlinks[http://blog.urbackup.org/156/symbolically-linking-directories-during-incremental-file-backups]/chunk-based CoW-Snapshots[http://blog.urbackup.org/83/file-backup-storage-with-btrfs-snapshots]
 +
| {{Yes}} (client)
 +
| {{G|GUI, Web}}
 +
| AGPLv3+
 +
| Windows, macOS
 +
| {{Yes}}
 +
| {{L|Identical files across backups of the same or different clients are stored only once. Integrates with LVM, dattobd and btrfs for file system snapshots.}}
 +
|}
  
* {{App|[[Wikipedia:Bazaar (software)|Bazaar]]|A distributed version control system that helps you track project history over time and to collaborate easily with others.
+
== Version control systems ==
** Similar commands to Subversion.
 
** Supports working with or without a central server.
 
** Support for working with some other revision control systems
 
** Complete Unicode support.
 
|http://bazaar.canonical.com/en/|{{Pkg|bzr}}}}
 
  
* {{App|[[Wikipedia:Darcs|Darcs]]|A distributed revision control system that was designed to replace traditional, centralized source control systems such as CVS and Subversion.
+
While [[Wikipedia:version control system|version control systems]] are mostly used for source code, they can track any files in a directory.
** Offline mode.
 
** Easy branching and merging.
 
** Written in Haskell.
 
** Not very fast.
 
|http://darcs.net/|{{AUR|darcs}}}}
 
  
=== VCS-based backups ===
+
See [[List of applications/Utilities#Version control systems]] and [[dotfiles]].
  
* {{App|Gibak|A backup system based on [[Git]].
+
== See also ==
** Supports binary diffs.
 
** Uses all of Git's features (such as {{ic|.gitignore}} for filtering files).
 
** Uses Git's hook system to save information that Git does not (permissions, mtime, empty directories, etc).
 
|https://github.com/pangloss/gibak|{{AUR|gibak}}}}
 
* {{App|bup|A fledgling Git-based backup solution written in Python and C.
 
** Uses a rolling checksum algorithm (similar to rsync) to split large files into chunks.
 
** Can back up directly to a remote bup server.
 
** Has an improved index format to allow you to track many files.
 
|https://github.com/apenwarr/bup|{{AUR|bup}}}}
 
* {{App|ColdStorage|Another backup tool using Git at its core, written in [[Qt]].|http://gitorious.org/coldstorage|{{AUR|coldstorage-git}}}}
 
  
== External Resources ==
 
 
* [http://www.halfgaar.net/backing-up-unix Backing up Linux and other Unix(-like) systems]
 
* [http://www.halfgaar.net/backing-up-unix Backing up Linux and other Unix(-like) systems]
* [http://www.askapache.com/security/mirror-using-rsync-ssh.html Mirroring an Entire Site using Rsync over SSH]
+
* [https://github.com/restic/others Exhaustive list of backup solutions for Linux]
 +
* [http://www.si-journal.org/index.php/JSI/article/view/205 Performance comparison of five remote incremental backup tools: Rsync, Rdiff-backup, Duplicity, Areca and Link-Backup]
 +
* [http://www.askapache.com/security/mirror-using-rsync-ssh.html Mirroring an Entire Site using Rsync over SSH]{{Dead link|2018|09|14}}
 +
* [https://github.com/artur-shaik/rsync-snapshots rsync-snapshots.sh] — Local and remote snapshot backup using rsync with hard links

Latest revision as of 06:38, 12 September 2019

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.

Backup overview

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.

Data synchronization

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.

See also:

Legend

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.
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.
Resumable
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 hsyncAUR, 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.
CLI
The application provides a command-line interface.
Other interfaces
The application has the specified user interfaces, e.g. GUI, TUI, or web-based.
License
The license of the server and client applications.
Other platforms
Supported operating systems other than Linux.
Maintained
The project is maintained.
Specificity
Brief notes about special features that notably set the application apart from the others.

Table

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: Explicitly list supported protocols / tools. Drop Encrypted transfer column because it depends on the protocol / tool. Simplify and color Change propagation column and move it leftwards. Split unmaintained into subsection? See also User:Larivact/drafts/Synchronization and backup programs#Synchronization. (Discuss in Talk:Synchronization and backup programs#)

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the blanks. (Discuss in Talk:Synchronization and backup programs#)
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 freefilesyncAUR C++ ? SFTP [1] ? ? Yes [2] Yes [3] unidirectional / multidirectional Yes ? No Yes GPL Windows, macOS Yes
git-annex git-annex Haskell, git rsync [4] rsync, others [5] No, but has custom non-FS metadata [6] Yes [7] Yes, content-addressable storage Yes multidirectional; with git remotes [8] renames conflicting files [9] optional, git-annex assistant Yes git-annex assistant GPLv3 macOS, Android (beta), Windows (beta) Yes Manage files with git
osync.sh osyncAUR Bash, based on rsync rsync rsync ? Yes No Yes bidirectional keeps multiple versions of a file [10] optional [11] Yes No BSD Yes
rclone rclone Go No [12] ? ? ? ? ? unidirectional [13] ? ? 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 rdiff-backup Python 2, librsync rsync rsync Yes ? No Yes unidirectional No Yes No GPL Win32 ?
Resilio Sync rslsyncAUR C++ Yes Yes ? Yes ? Yes multidirectional ? ? No Web Proprietary freemium FreeBSD, Windows, macOS, Android, iOS, Windows Phone, Amazon Kindle Fire Yes P2P sync
rsync rsync C Yes SSH or native protocol Yes Yes No
  • --link-dest with hard links [14]
  • --backup
unidirectional No Yes Rsync#Front-ends GPLv3 Win32 Yes Standard tool present on all Linux distributions.
SparkleShare sparkleshare C#, git Yes AES-256 [15] ? ? Yes Yes ? ? ? No Yes GPLv3 Windows, macOS Yes It can sync with any Git server over SSH.
Syncany syncanyAUR Java ? ? ? ? ? ? ? ? ? Yes Yes GPLv3 No [16]
Syncthing syncthing Go Yes [17] Yes [18] partial [19] Yes ? Yes [20], previous versions moved to archive folder multidirectional renames one file [21] Yes Yes Web, GTK MPL v2 BSD, Windows, macOS, Android, Kindle Paperwhite Yes P2P sync
Synkron synkronAUR C++ ? ? ? ? ? ? multidirectional ? ? No Qt GPLv2 Windows, macOS No
taskd taskd C++, Python Yes Yes ? Yes ? ? multidirectional ? No Yes No MIT Android Yes
Unison unison OCaml Yes Yes partial [22] optional [23] No Yes [24] bidirectional interactive No Yes GTK2 GPL FreeBSD, Windows, macOS, Android Yes [25]

Incremental backups

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.

See also:

Legend:

  • 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.

Single machine

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.

Chunk-based increments

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the blanks. FS metadata column: What does Immature mean? Resumable column: What does Pausing only / Kinda through tar mean? (Discuss in Talk:Synchronization and backup programs#)

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 arecaAUR Java Zip, Zip64 AES128, AES256 Yes Yes Yes No Pausing only No Yes Yes GPLv2 Windows Yes
BorgBackup borg borg-binAUR Python, C (Cython) lz4, zlib, lzma, zstd AES256 Yes SSH Yes [26] Yes [27] Yes [28] Yes Yes third party BSD *BSD, macOS, Windows (Cygwin / WSL)[29] Yes Deduplication based on variable length chunks; support both local and SSH-based remote backup destination.
btar btarAUR[broken link: archived in aur-mirror] 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 bup bup-gitAUR C, Python, git Yes No Yes Yes Immature Yes [30] pick up where you left off [31] Yes Yes bupsAUR GPLv2 NetBSD, Windows, macOS Yes Same storage format as git.
Duplicati duplicati-latestAUR C# Yes Yes Yes Yes Yes No Pausing only No Yes Yes LGPL Windows, macOS Yes
Duplicity duplicity librsync gzip gpg Yes Yes ? No Yes No Yes Yes GPL Yes
Kup Backup System kup rsync, bup front-end Yes Yes Yes Yes Immature Yes No Yes bup Qt GPLv2 Yes
obnam obnamAUR Python Yes GnuPG Yes Yes ? Yes checkpoints every 100MB ? Yes No GPLv3 No
restic restic restic-gitAUR Go No [32] AES-256 [33] Yes Yes Yes [34] Yes [35] Yes [36] Yes Yes No [37] BSD OpenBSD, Windows, macOS Yes Supports storage on various cloud services natively and through rclone.
ZBackup zbackupAUR C++ LZMA, LZO AES Yes Yes ? planned [38] No Kinda through tar Yes No GPLv2 Yes Repository consists of immutable files.

File-based increments

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the blanks. (Discuss in Talk:Synchronization and backup programs#)

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.

Specific legend:

  • 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 backintimeAUR Python, rsync, diff No No rsync rsync rsync Yes No No Yes [39] Yes Qt GPLv2 Yes
DAR (Disk ARchive) darAUR C++ special archive format Yes Yes Yes ? ? ? ? No [40] Yes darguiAUR GPL FreeBSD, NetBSD, Windows, macOS Yes
Link-Backup link-backupAUR Python 2 No No ? SSH ? ? Yes Yes No [41] Yes No MIT No It copies itself to the server.
rdup rdupAUR C tar.gz gpg, blowfish and others ? ? ? Yes ? No Yes Yes No GPLv3 No Set of command-line tools.
rsnapshot rsnapshot rsync No No Yes Yes ? ? ? ? Yes [42] Yes No GPLv2 Win32 No [43]
sbackup sbackupAUR Python gzip, bzip2 No ? SSH ? No No No No No GTK GPLv3 No
TimeShift timeshiftAUR rsync No No rsync rsync ? ? ? ? Yes No GTK GPLv3 Designed for full-system backups to dedicated devices. Yes

Network oriented

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the blanks. Encrypted transfer column: What does Internet transfers only mean? (Discuss in Talk:Synchronization and backup programs#)

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.

Specific legend:

  • 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.
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 backuppc Perl Pull Yes No Yes Yes Yes No Yes ? file-based, hard links [44] 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 [45] Yes GUI, Web AGPLv3 Windows, macOS Yes
burp burp-backupAUR librsync Push Yes Yes Yes Yes Yes ? Yes ? chunk-based [46] Yes burp-ui AGPLv3 Windows, macOS Yes
SafeKeep safekeepAUR rdiff-backup Pull No No ? Yes ? ? ? ? chunk-based [47] Yes Yes GPL No Integrates with LVM and databases to create consistent backups. Bandwidth throttling.
Snebu snebuAUR[broken link: archived in aur-mirror] C Push or Pull Yes No ? Yes ? ? ? ? file-based [48] Yes No GPLv3 ? Supports arbitrary retention schedules.
Synbak 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[49]/chunk-based CoW-Snapshots[50] 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.

See List of applications/Utilities#Version control systems and dotfiles.

See also