• http://fr.wikipedia.org/wiki/Time_Machine_%28logiciel%29
  • * Par défaut, Time Machine ne permet la sauvegarde que vers un disque local, un disque externe (USB ou Firewire) ou une Time Capsule. Cependant il est possible de sauvegarder vers un disque réseau (de type NAS par exemple) ou tout autre type de disque en suivant cette procédure : http://www.engadget.com/2007/11/10/how-to-enable-time-machine-on-unsupported-volumes/
• http://www.engadget.com/2007/11/10/how-to-enable-time-machine-on-unsupported-volumes/

Solutions unidirectionnelles pour Linux

svn

Rsync

• sauvegarde un répertoire ou synchronyse deux répertoires mais ne sauvegarde pas les modifications entre deux sessions
• PRO : famous for its delta-transfer algorithm, which reduces the amount of data sent over the network by sending only the differences between the source files and the existing files in the destination
• PRO : --partial permet de reprendre un transfert interrompu
• PRO : -P allows rsync to continue interrupted transfers and show a progress status for each file
• --link-dest this is a neat way to make full backups of your computers without losing much space. rsync links unchanged files to the previous backup (using hard-links, see below if you don't know hard-links) and only claims space for changed files. This only works if you have a backup at hand, otherwise you have to make at least one backup beforehand.
• CON : rsync really can't handle file renames properly - at all
• site officiel : http://rsync.samba.org/
• essayer : rsync -aP /home/charles/0/0En-cours charles@rn7.net:/home/charles/sync
  • a : rlptgoD (no -H,-A,-X) = recursive, symlinks as symlinks, preserve permissions, preserve modification times, preserve group, preserve owner (super-user only), same as --devices --specials (preserve device files (super-user only), preserve special files)
  • P : same as --partial --progress (keep partially transferred files, show progress during transfer)

#!/bin/sh

date=`date "+%Y-%m-%dT%H_%M_%S"`
HOME=/home/user/

rsync -azP \
  --delete \
  --delete-excluded \
  --exclude-from=$HOME/.rsync/exclude \
  --link-dest=../current \
  $HOME user@backupserver:Backups/incomplete_back-$date \
  && ssh user@backupserver \
  "mv Backups/incomplete_back-$date Backups/back-$date \
  && rm -f Backups/current \
  && ln -s back-$date Backups/current"

Grsync : interface pour rsync

• http://en.wikipedia.org/wiki/Grsync

rdiff-backup

• Using rdiff, a utility called rdiff-backup has been created, capable of maintaining a backup mirror of a file or directory either locally or remotely over the network, on another server. rdiff-backup stores incremental rdiff deltas with the backup, with which it is possible to recreate any backup point. See: http://en.wikipedia.org/wiki/Rsync
• PRO : the best features of a mirror and an incremental backup
• PRO : In most cases, the command rdiff-backup dir1 dir2 will work out-of-the-box to backup dir1 to dir2.
• rdiff-backup dir1 user@system::/dir2 will backup dir1 to dir2 on a different system (provided rdiff-backup is installed on both systems).
• PRO : rdiff-backup makes the backup directory into an almost exact copy of the source directory (the only difference is one extra subdirectory on the backup side)
• rdiff-backup saves those changes in the form of reverse diffs, so you can recover the older form of the file.
• rdiff-backup uses librsync, which implements the same efficient diffing algorithm that rsync uses. It works on binary files as well as text, so only a fraction of the data in your database would be saved in each incremental backup
• CON : rdiff-backup doit être installé sur le client et sur le serveur (dans le cas contraire voir duplicity)
• CON : rdiff-backup recommence à chaque backup interrompu :(
• Frontend pour rdiff-backup :
  • [standard dans Ubuntu] Keep : http://jr.falleri.free.fr/keep/wiki/Home
  • [standard dans Ubuntu] pyBackPack : http://andrewprice.me.uk/projects/pybackpack/
• Infrastructure de sauvegarde comprenant les bases Mysql, etc. : https://labs.riseup.net/code/projects/show/backupninja
• Pour sauvegarder plusieurs machines accessibles sur le réseau : http://www.delodder.be/blog/howto/slbackup-a-great-wrapper-for-rdiff-backup/

• rdiff-backup --check-destination-dir --include-special-files -v5 /home/charles/0/0En-cours charles@rn7.net::/home/charles/sync
  • récupération : rdiff-backup -r now charles@rn7.net::/home/charles/sync /home/charles/0/0En-cours
  • sshfs charles@rn7.net:/home/charles /home/charles/tmp

• rdiff-backup -v5 --exclude /home/charles/0 --exclude /home/charles/.gvfs /home/charles/ /media/Sauvegarde2/zz-backup
• rdiff-backup -v5 --exclude /home/charles/0 /home/charles chn@ns39106.ovh.net::./backup
• rdiff-backup -v5 --exclude /home/charles/0 /home/charles root@ns39106.ovh.net::/home/chn/backup

• récupérer : http://rdiff-backup.nongnu.org/examples.html

duplicity

• PRO : Encrypted bandwidth-efficient backup using the rsync algorithm
• CON : les contenus sont encryptés
• duplicity is a variation on rdiff-backup that allows for backups without cooperation from the storage server, as with simple storage services like Amazon S3. It works by generating the hashes for each block in advance, encrypting them, and storing them on the server, then retrieving them when doing an incremental backup. The rest of the data is also stored encrypted for security purposes. http://en.wikipedia.org/wiki/Rdiff-backup#Variations
• duplicity --ssh-askpass -v5 /home/charles/0/0En-cours ssh://charles@rn7.net//home/charles/duplicity

Déjà Dup

• "uses duplicity as the backend"

link-backup

• Link-Backup is a backup utility that creates hard links between a series of backed-up trees, ...
• ... and intelligently handles renames, moves, and duplicate files without additional storage or transfer. ...
• ... Transfer occurs over standard i/o locally or remotely between a client and server instance of this script. Remote backups rely on the secure remote shell program ssh. Link-Backup comes with a web based viewer of the backups it makes.
• python lb.py /home/charles/0/0En-cours charles@rn7.net:/home/charles/lb

Bup

• bluffant mais encore trop neuf
• uses the packfile format from git
• Data is "automagically" shared between incremental backups without having to know which backup is based on which other one - even if the backups are made from two different computers that don't even know about each other.
• bup compare des bouts de fichiers sans se préoccuper du nom des fichiers, il gère donc très bien :
  • le renommage de fichiers
  • les fichiers en double
  • les fichiers identiques répartis sur plusieurs machines
• You can back up directly to a remote bup server, without needing tons of temporary disk space on the computer being backed up. And if your backup is interrupted halfway through, the next run will pick up where you left off.
• Even when a backup is incremental, you don't have to worry about restoring the full backup, then each of the incrementals in turn; an incremental backup acts as if it's a full backup, it just takes less disk space.
• You can mount your bup repository as a FUSE filesystem and access the content that way, and even export it over Samba.
• you don't have to specify that this backup is incremental, it just saves space automatically

Flyback

• Flyback 0.5 basé sur rsync : http://www.ubuntu-unleashed.com/2008/05/introducing-flyback-apples-time-machine.html

• Flyback 0.6 basé sur GIT : http://code.google.com/p/flyback/
  • with Places/Bookmarks column and snapshots only when something changed
  • Git cannot archive files that can't fit into main memory. So most large files are excluded from backups by default (in the preferences). Hopefully they will fix this bug soon.

Backintime

• Backintime basé sur rsync : http://backintime.le-web.org/screenshots/
  • snapshots only when something changed
  • très user-friendly mais ne fonctionne qu'avec des répertoires montés localement

Timevault

• Restore functionality is integrated into Nautilus - previous versions of a file or directory that has a snapshot can be accessed by examining the properties and selecting the 'Previous Versions' tab.
• Snapshots don't use space for the files that haven't changed but instead simply add a link to the same data on disk.
• Timevault semble ne pas fonctionner sur Lucid, ce dernier étant fourni avec python2.6 et Timevault nécessitant python2.5. Voir ce rapport de bug sur Launchpad : https://bugs.launchpad.net/timevault/+bug/540283

Solutions bidirectionnelles

Subversion

Unison

• unison /home/charles/0/0En-cours ssh://charles@rn7.net//home/charles/unison

Meld

• QtdSync? basé sur rsync : http://qtdtools.doering-thomas.de/page.php?seite=0&sub=0&lang=en
• Unison basé sur rsync : http://www.cis.upenn.edu/~bcpierce/unison/
• Grsync : http://www.opbyte.it/grsync/
• http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp
• http://winscp.net/eng/docs/lang:fr
• http://www.rsync.net/resources/howto/windows_backup_agent.html ?

• Unison basé sur rsync : http://www.cis.upenn.edu/~bcpierce/unison/
• Grsync : http://www.opbyte.it/grsync/

• très très peu cher !!!!! : 3$/100Go/mois : http://www.datastorageunit.com/
• http://en.wikipedia.org/wiki/Amazon_S3
• http://en.wikipedia.org/wiki/Comparison_of_online_backup_services

• http://clonezilla.org/

• pyBackPack : interface graphique au logiciel de sauvegarde + miroir incrémental rdiff-backup
  • http://projects.sucs.org/projects/pybackpack/
  • http://www.nongnu.org/rdiff-backup/
  • http://code.google.com/p/flyback/
  • https://launchpad.net/timevault
  • http://maketecheasier.com/time-machine-for-ubuntu-try-timevault-and-flyback/2008/03/07
  • http://www.howtoforge.com/creating-snapshot-backups-with-flyback-ubuntu-7.10
  • http://www.korben.info/timevault-la-machine-a-voyager-dans-le-temps-pour-ne-plus-jamais-perdre-ses-fichiers.html
  • http://www.howtoforge.com/snapshot-backups-with-timevault-ubuntu-7.10-p3