What I do is to wrap rdiff-backup in a bash script. An older version of what I have in service can be found here: https://github.com/meganerd/bash_scripts/blob/master/backup/BackupWrapper.sh
I am not sure how rdiff-backup stores time internally, but it does track changes over time. You can for example get a version from a particular day, assuming that you have not purged backups of that age (by default it should keep growing until you tell it to delete data older than X, where X can be just about any amount and unit of time). Increasingly I am moving my large data (primarily VM and disk images) around with btrfs, since I can can create instant copy on write snapshots, and very efficiently transfer all of that over a network. See the following ARS article for a pretty good explanation: http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/ On Fri, Apr 25, 2014 at 2:21 PM, Joe S <joes...@shaw.ca> wrote: > I'm using this on a home computer. I have used rsync in the > past. I was looking into what else was out there or if there was > something better. I've heard of snap-shots, but don't really > know what that is about or if that is a good idea. I want to > backup my /home and config files in / that I would need if I had > to reinstall. Do these programs keep track of all the meta data > like ctimes etc? > > Thanks > > On Thu, 24 Apr 2014 12:38:32 -0600 > caziz <ca...@cuug.ab.ca> wrote: > > > For my needs, rsync commands in a script is fine. > > > > For both backup and limited archive. rsnapshot too old > > school? (Please God let that file I just found out I > > accidentally munched last month be copied somewhere) > > > > > > > > On 14-04-24 12:02 PM, Gustin Johnson wrote: > > > I have used rdiff-backup in a cronjob for years. It keeps > > > date based archives and is space efficient (uses the rsync > > > algorithm). > > > > > > For Windows machines I usually use the built in backup > > > utility on recent versions to save to a samba share on a > > > Linux box that I then archive again via rdiff-backup. > > > > > > What the data size is, what the OS is, and the budget, would > > > help us to give more specific answers. > > > > > > > > > On Thu, Apr 24, 2014 at 8:04 AM, Richard Carter > > > <carter.r....@gmail.com <mailto:carter.r....@gmail.com>> > > > wrote: > > > > > > I've had good success with Back In Time. > > > > > > Robin > > > > > > > > > On Wed, Apr 23, 2014 at 6:37 PM, Mel Walters > > > <melwalt...@telus.net <mailto:melwalt...@telus.net>> wrote: > > > > > > On Sun, 2014-04-20 at 19:35 -0600, Joe S wrote: > > > > I am looking for advice on what is a good > > > > method/program to backup. I am using this for a > > > > home computer. Will backup to a separate hard > > > > drive and some info on a DVD. I have used rsync, > > > > but am wondering if there are other methods that > > > > would do this as well or better. > > > > > > > > Thanks > > > > > > > I can give a somewhat general answer for an average > > > user. > > > > > > I have been looking at the GUI lucky-backup that > > > uses rsync. > > > > > > Seems to work well as a simple solution if you are > > > backing up some sub directories off of your /home/yourname > > > directory. Pay attention to the "Type" category. You might > > > want to try a test directory to see what happens. > > > > > > If you do your home directory you could potentially > > > end up with too much dot file and dot directories data that > > > could add up big time on a modern Linux workstation > > > depending on what is installed. But there is a way to select > > > exclusions with the advanced mode. Do you like that solution? > > > > > > People usually also want 1/ email address 2/ book > > > backup and browser > > > > > > Mel > > > > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines > > > (http://clug.ca/ml_guidelines.php) **Please remove these > > > lines when replying > > > > > > > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines > > > (http://clug.ca/ml_guidelines.php) **Please remove these > > > lines when replying > > > > > > > > > > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > **Please remove these lines when replying > > > > > _______________________________________________ > clug-talk mailing list > clug-talk@clug.ca > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying >
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying