One of the handiest tools you'll ever have on Linux (and other *nix systems) is rsync. As the name implies, rsync is used to sync files on remote and local machines. You can use rsync to copy files to remote systems and back again, or to make backups to locally mounted hard drives.

The beauty of rsync is that its syntax and command line options are exactly the same for local and remote directories synchronizations,

rsync is a very useful and powerful program for doing incremental transfers of files, whether that is locally or remotely. It can, however, take a little while to familiarise yourself with how rsync works before you can get started with it however.

Backup like a PRO using one most popular linux backup tool alternatives called rsync. RSync backups data and does it very clean and well. Rsync only transfers those data that have been modified and changed so that the destination host has an exact replica from the source host.

rsync is an open source utility that provides fast incremental file transfer. rsync uses the "rsync algorithm" which provides a very fast method synchronization of two server
.

Synchronizing two machines (such as a laptop and a desktop computer) is easier and faster when you use rsync, which boasts an efficient algorithm and options for just about everything you might need. And if a command-line operation isn't your thing, several graphic tools make using rsync easier still.

Krsync is a simple GUI frontend for the famous rsync to synchronize files and directories between systems or even two different directories on the same server. Krsync is a Kommander based GUI for rsync.

rsync is an excellent and versatile backup tool, but it does have one drawback: you have to run it manually when you want to back up your data. Sure, you can use cron to create scheduled backups, but even this solution cannot provide seamless live synchronization.

We've all seen countless articles, blog and forum posts explaining how to back up a server with rsync and other tools. While I've cringed when people talked about using non-scalable methods, there actually is a place for quick and dirty backup mechanisms.