Live data from Hacker News

Time-Machine-style backup with rsync

github.com

1–10 of 52 posts

Re: Time-Machine-style backup with rsync

#4
post #2

This looks great, doesn't seem to need anything other than rsync installed. You should also check out rsnapshot: http://www.rsnapshot.org/ , it does a great job and has many of the features that this script does.

Agreed. I've used rsnapshot for years and am not sure how this script really differs (better or worse). I can say that rsnapshot is a real workhorse that gives me a lot of peace of mind.

Re: Time-Machine-style backup with rsync

#6
When will this trend of "like time machine" backup software going to stop ?

Time Machine, as can be seen here http://www.apple.com/support/timemachine/ time machine is tightly integrated in the os and provides a self-defining interface and user experience.

This github page is for a wrapper shell script around rsync, which is not like time machine.

This has been going on for a while now, see Timevault (https://wiki.ubuntu.com/TimeVault ), back in time (http://backintime.le-web.org/ ) or flyback (http://www.flyback-project.org/ ).

Please telling us your backup solution is like time machine when it lacks the kind of UX time machine offers, thanks !

Re: Time-Machine-style backup with rsync

#9
Missing some options for extended attributes (SELinux, ACLs) and (on OSX) resource forks.

Also, if you're doing multiple backups of the same data to a filesystem over time, it's worth doing 'cp -al' from the previous backup to the current backup destination, then rsync over the top of that - that way multiple copies of files which haven't changed don't take up any extra space.

Re: Time-Machine-style backup with rsync

#10
I have written a similar script that I use for many years now. These sort of backups are very convenient.

I started too with hard links but nowadays I prefer to format my backup disk with BTRFS and use btrfs snapshots instead, though I still support hard links.

I prefer btrfs snapshots due to their support for COW, so if I decide to play with a backup I won't mess all the other versions of this backup. With hard links you should never write to your existing backups.

Lately I added a helper script to mount remote filesystems and lock mysql databases but it could be easier to use.

Most of my code is checks to make sure I won't write somewhere I shouldn't to.

https://github.com/andmarios/mrbStudio

Post reply on HN