meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:backup:overview [2016/05/18 09:47] – [Performance] niziaklinux:backup:overview [2025/12/09 09:00] (current) – niziak
Line 1: Line 1:
-====== Headline ======+====== Backup SW ====== 
 + 
 +===== borg ===== 
 +  * (+) deduplication using rolling hashe (buzhash) - only chunks are stored on remote (hashes are calculated before chunk compression, so change compression settings 
 +will only be applied to new chunks) 
 +  * (-) a bit more complex CLI than duplicity 
 +  * (+) subsequent backups are light - no full/increment backups concept. 
 +  * (+) raw/block devices support
  
 ===== rsync ===== ===== rsync =====
Line 5: Line 12:
   * no build-in incremental snapshots support    * no build-in incremental snapshots support 
   * incremental backups of modified files possible (using --backup and --backup-dir params)   * incremental backups of modified files possible (using --backup and --backup-dir params)
 +
 +==== delete files ====
 +<code bash>
 +rsync --delete-missing-args --backup --files-from list_file_to_delete.txt src/ 192.168.1.1::root/
 +</code>
 +
  
 ===== rsnapshot ===== ===== rsnapshot =====
Line 16: Line 29:
   * special directory ''rdiff-backup-data'' are also created at dest where old versions are kept   * special directory ''rdiff-backup-data'' are also created at dest where old versions are kept
   * [[http://www.nongnu.org/rdiff-backup/]]   * [[http://www.nongnu.org/rdiff-backup/]]
 +  * <code>sudo apt-get install python-pylibacl python-xattr</code>
  
 ===== duplicity ===== ===== duplicity =====
   * No direct access to backups. Backups are stored in PGP encrypted/compressed tar volumes.   * No direct access to backups. Backups are stored in PGP encrypted/compressed tar volumes.
   * Restarting of broken backup needs only to re-download first volume from destination   * Restarting of broken backup needs only to re-download first volume from destination
 +  * Full backups are overhead
  
 ===== duply ===== ===== duply =====
   * front end to duplicity   * front end to duplicity
  
 +<code bash>
 +duply my-backup backup
 +duply my-backup cleanup --extra-clean --force
 +</code>
  
 ====== Performance ====== ====== Performance ======