|Number of watchers on Github||1156|
|Number of open issues||61|
|Average time to close an issue||about 1 month|
|Average time to merge a PR||2 months|
|Open pull requests||24+|
|Closed pull requests||23+|
|Last commit||almost 3 years ago|
|Repo Created||about 8 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||rsnapshot|
|Do you use rsnapshot? Leave a review!|
|View open issues (61)|
|View rsnapshot activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
rsnapshot comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details.
rsnapshot is a filesystem snapshot utility based on rsync. rsnapshot makes it easy to make periodic snapshots of local machines, and remote machines over ssh. The code makes extensive use of hard links whenever possible, to greatly reduce the disk space required.
It is written entirely in perl with no module dependencies, and has been tested with versions 5.004 through 5.16.3. It should work on any reasonably modern UNIX compatible OS. It has been tested successfully on the following operating systems:
If this is your first experience with rsnapshot, you may want to read the rsnapshot HOWTO at http://www.rsnapshot.org/. The HOWTO will give you a detailed walk-through on how to get rsnapshot up and running in explicit detail.
For a reference of all available commands, see the rsnapshot man page.
If you are upgrading from version 1.1.6 or earlier, make sure you read the file Upgrading from 1.1.
For installation or upgrade instructions please read the INSTALL doc.
If you want to work on improving rsnapshot please read the CONTRIBUTING doc.
If you want to ask a question or have a general discussion use the Mailing List.
Note that systems which use GNU cp version 5.9 or later will have problems
with rsnapshot versions up to and including 1.2.3, if
cmd_cp is enabled
(and points at the later gnu cp). This is no longer a problem since
rsnapshot 1.2.9, as it strips off trailing slashes when running cp.
If you have rsync version 2.5.7 or later, you may want to enable the link_dest parameter in the rsnapshot.conf file.
If you are running Linux but do not have the problem above, you should
cmd_cp parameter in rsnapshot.conf (especially if you do not
have link_dest enabled).
Be advised that currently
link_dest doesn't do well with unavailable hosts.
Specifically, if a remote host is unavailable using
link_dest, there will
be no latest backup of that machine, and a full re-sync will be required
when it becomes available. Using the other methods, the last good snapshot
will be preserved, preventing the need for a re-sync. We hope to streamline
this in the future.
Once you have installed rsnapshot, you will need to configure it.
The default configuration file is /etc/rsnapshot.conf, although the exact path
may be different depending on how the program was installed. If this
file does not exist, copy
/etc/rsnapshot.conf.default over to
/etc/rsnapshot.conf and edit it to suit your tastes. See the man page for
the full list of configuration options.
/etc/rsnapshot.conf contains your chosen settings, do a quick sanity
check to make sure everything is ready to go:
$ rsnapshot configtest
If this works, you can see essentially what will happen when you run it for
real by executing the following command (where interval is
$ rsnapshot -t [interval]
Once you are happy with everything, the final step is to setup a cron job to automate your backups. Here is a quick example which makes backups every four hours, and beta backups for a week:
0 */4 * * * /usr/local/bin/rsnapshot alpha 50 23 * * * /usr/local/bin/rsnapshot beta
In the previous example, there will be six
taken each day (at 0,4,8,12,16, and 20 hours). There will also
be beta snapshots taken every night at 11:50PM. The number of
snapshots that are saved depends on the
interval settings in
interval alpha 6
This means that every time
rsnapshot alpha is run, it will make a
new snapshot, rotate the old ones, and retain the most recent six
If you prefer instead to have three levels of backups (which we'll
delta), you might set up cron like this:
00 00 * * * /usr/local/bin/rsnapshot beta 00 23 * * 6 /usr/local/bin/rsnapshot gamma 00 22 1 * * /usr/local/bin/rsnapshot delta
This specifies a
beta rsnapshot at midnight, a
on Saturdays at 11:00pm and a
delta rsnapshot at 10pm on the
first day of each month.
Note that the backups are done from the highest interval first
(in this case
delta) and go down to the lowest interval. If
you are not having cron invoke the
alpha snapshot interval,
then you must also ensure that
alpha is not listed as one of
your intervals in rsnapshot.conf (for example, comment out alpha,
beta becomes the lowest interval).
Remember that it is only the lowest interval which actually does
the rsync to back up the relevant source directories, the higher
intervals just rotate snapshots around. Unless you have enabled
sync_first in your configuration-file, in which case only the
pseudo-interval does the actual rsync, and all real intervals
just rotate snapshots.
For the full documentation, type
man rsnapshot once it is installed,
or visit http://www.rsnapshot.org/. The HowTo on the web site has a
detailed overview of how to install and configure rsnapshot, and things
like how to set it up so users can restore their own files.
If you plan on using the
backup_script parameter in your backup scheme,
take a look at the
utils/-directory in the source distribution for several
example scripts. The
utils/rsnapreport.pl script is well worth a look.
Please see the AUTHORS file for the complete list of contributors.