<pre><code> sbackup rsync bacula amanda clonezilla </code></pre> <p>..all of these and a few others are all good. It's just a matter of which tool you use. While the tool is important, no one here has mentioned methodology, which I'll recommend here.</p> <p>Do a fully weekly backup and then daily incremental backups. So if you do a full backup on Friday and your system borks on Monday, you need only install the full Friday backup followed by the incremental backups of Saturday and Sunday to get back to where you were before the crash.</p> <p>Have redundant redundancy that is redundant. In other words, have a RAID 1 setup, do your backups as noted above, and also have those same backups backed up not only locally, but off-site as well such as via an online storage facility.</p> <p>Lastly...... the most overlooked and rarely ever done step of testing your backups!! Backups that are never tested are worthless. All too often times what happens is that a system crashes and it's only then that the person finds out that their backup schema has failed them because they never tested the backups before the system crashed.</p> <p>All the geeky tools, scripts, etc are absolutely worthless unless the backups can be used to restore the system. There's many ways to bake the cake, but if the cake isn't edible, what good is it, ya know what I mean?</p>