Live Sync with lsyncd

Productivity Sauce
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. If this is what you want, then you need the lsyncd tool, a command-line utility which uses rsync to synchronize (or rather mirror) local directories with a remote machine in real time. To install lsyncd on your machine, download the latest .tar.gz archive from the project's Web site, unpack it, and use the terminal to switch to the resulted directory. Run then the ./configure command followed by make, and make install (the latter command requires root privileges). lsyncd is rather straightforward in use, as it features just one command and a handful of options. The lsyncd command requires only two parameters: the source and the target directory, for example:
lsyncd /path/to/source /path/to/target
This command syncs two local directories, but lsyncd can also mirror a local directory to a folder on a remote machine. For example, the following command syncs the source directory on the local machine with the target directory on a remote machine which has the 192.168.1.7 IP address, connecting to the remote server as the user "monkey":
lsyncd /path/to/source monkey@192.168.1.7:/path/to/target/
In most cases, you have to provide a password to successfully connect to a remote server, so to make the command above work, you have to use the --no-daemon option which prevents the process from running as a daemon:
lsyncd --no-daemon /path/to/source monkey@192.168.1.7:/path/to/target/
Another useful option is --exclude. As the name suggests, it allows you to specify files or directories that you don't want to sync.
Comments
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
openSUSE Joins End of 10
openSUSE has decided to not only join the End of 10 movement but it also will no longer support the Deepin Desktop Environment.
-
New Version of Flatpak Released
Flatpak 1.16.1 is now available as the latest, stable version with various improvements.
-
IBM Announces Powerhouse Linux Server
IBM has unleashed a seriously powerful Linux server with the LinuxONE Emperor 5.
-
Plasma Ends LTS Releases
The KDE Plasma development team is doing away with the LTS releases for a good reason.
-
Arch Linux Available for Windows Subsystem for Linux
If you've ever wanted to use a rolling release distribution with WSL, now's your chance.
-
System76 Releases COSMIC Alpha 7
With scores of bug fixes and a really cool workspaces feature, COSMIC is looking to soon migrate from alpha to beta.
-
OpenMandriva Lx 6.0 Available for Installation
The latest release of OpenMandriva has arrived with a new kernel, an updated Plasma desktop, and a server edition.
-
TrueNAS 25.04 Arrives with Thousands of Changes
One of the most popular Linux-based NAS solutions has rolled out the latest edition, based on Ubuntu 25.04.
-
Fedora 42 Available with Two New Spins
The latest release from the Fedora Project includes the usual updates, a new kernel, an official KDE Plasma spin, and a new System76 spin.
-
So Long, ArcoLinux
The ArcoLinux distribution is the latest Linux distribution to shut down.
Live Sync with lsyncd
be it sysadmins or home users. We use tar as a basis for our own backup script,
but I recognize the power of rsync as a basis.
Also, there's so many tools to choose from, and I guess rsync tools can mix,
e.g. you can have lsyncd running, while also having a tool like rsyncBackup or
Rdiff-backup ?
Don't forget to make backups for databases (MySQL for example) with their tools, though,
to keep databases consistent!
Anyway, I like tools based on proven and mature simple Un*x tools like tar and rsync,
cause you'll also have all other Un*x tools to mix with them, e.g. being able to keep a cron
job separate from your backup program itself keeps things manageable.
Mike