2012 LinuxQuestions.org Members Choice AwardsThis forum is for the 2012 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite products of 2012. This is your chance to be heard! Voting ends on February 4th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
because I like fast backups that maintain history of the file system. These tools also store the backups in a normal file system so you don't need to use special tools to restore data.
Although it only piggy-backs on rsync I had to give some love to fs-archiver. Great little tool. Even plays nice with Windows boot partitions. Version 0.7 will be something special when it is released!!
If the backup is on the same physical site as the data, and some disaster blows the whole house away, it doesn't matter how clever and diligent your backup practices are.
Note that rsync (as cp) has a -a --archive option that does most of the work for backups (of course someone would come up with it, given its obvious usefullness). In particular, in rsync, -a equals -rtpoglD, which differs from yours in the only fact that it also preservers device nodes and special files in the process. So, you might get
which is easier to remember (putting "-av" is almost an immediate reflex when I write "rsync"). The --delete has its pros and cons, the -c (for checksumming) is nice, but I think that for cron jobs --progress is somewhat strange ;-) (though interesting in a one-shot)
I like almost everything the -a option does (including its fewer keystrokes), but I wonder what the benefit of copying directories without recursing (-d) is? Maybe I'm missing something.
I use this command to clone one drive of personal data to another, including removing junk files and such. For an incremental/archive backup, --delete is probably inappropriate. For my purposes, though, it keeps everything able to fit on one hard drive! :-)
I agree with you on the -c (MD5sum check) option, since it's quite slow and CPU-intensive. I only use it in a "one-shot" context. For a cron job, I'd almost certainly leave it out. It's good for "making extra sure," but not so much for anything else.
Agreed. I have no shortage of disk, so I prefer simply imaging most machines. It is the fastest full backup,
and restore for any major catastrophe (ie: dead drive ) by far.
But since you don't consider it as a candidate, I use rsync quite alot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.