11–20 of 52 posts
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.
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.u…
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.u…
Please elaborate on what you are missing from the wanna-bes
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.u…
Please elaborate on what you are missing from the wanna-bes
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.
Isn't that already taken care of by its use of rsync's --link-dst option?
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.
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.
I've used dirvish for several years (nearly a decade), both locally and remotely without issue. No configuration is necessary on the client, only on the backup server (alternatively you can flip it and put all of your configuration on the client). Uses rsync, hard links, and can keep snapshots at various intervals.
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.
> 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 Isn't that already taken care of by its use of rsync's --link-dst option?
Earlier quoted context omitted.
> 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 Isn't that already taken care of by its use of rsync's --link-dst option?
Depends if the backup's on the same filesystem as the source.
Doesn't vim intentionally do this if it edits files that are hard linked? emacs breaks the hard link. I'm not saying either behavior is best, but in this case one might be surprising!