On Fri, Feb 02, 2018 at 05:32:36PM -1000, Joel Roth wrote: > Dear list, > > For years I'd used a couple of rsync scripts for backup, > usually just full snapshots. > > I knew there is an option using hardlinks that behaves like > the Mac Time Machine app, giving cheap incremental backups. > > https://blog.interlinked.org/tutorials/rsync_time_machine.html > > And now I fool around with it myself. > > Since I have map UUIDs to mount points in /etc/fstab, > I can put the full paths in the backup script > and simply run it without parameters to get a > date-and-time-stamped directory containing a full backup. > > Probably you all have something much better, but for the > sake of discussion, and will post my humble offering. > > The clever part of the code is using a symlink > .../backups/current/ to provide rsync with the --link-dest > argument, the tree of files available for hardlinking during > next backup pass. > > Also, the one-file-system argument to rsync lets me backup > the root directory without pulling in other mounts. > > The current script doesn't support copying over a network, > but can be easily achieved by consulting online resources > (left as an exercise to the reader.) > > Obviously, you will need to configure it. Note that the directories > excluded from backup are created in the last step. > > probably someone has done it better... >
There's rdiff-backup, which uses an efficient algorithm to identify what has changed and transmit the diffs over the network. It also keeps a history of old backups on the backup drive, so you can restore as of a previous date. And the files themselves are readable on the backup drive, as ng as you don't have them compressed or encrypted. -- hendrik _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
