Managing SSH chroots to backup a lot of machines

Go to file

Victor LABORIE ebedc7b06c Better file hierarchy		2017-01-12 10:25:41 +01:00
debian	Better file hierarchy	2017-01-12 10:25:41 +01:00
docs	Better file hierarchy	2017-01-12 10:25:41 +01:00
tpl	Better file hierarchy	2017-01-12 10:25:41 +01:00
.gitignore	Initial version of Debian package	2017-01-11 18:47:10 +01:00
bkctld	Initial version of Debian package	2017-01-11 18:47:10 +01:00
bkctld.conf	Better file hierarchy	2017-01-12 10:25:41 +01:00
bkctld.sysvinit	Better file hierarchy	2017-01-12 10:25:41 +01:00
README_EN.md	Updated French README.	2015-08-28 19:01:06 +02:00
README_FR.md	Rename bkctl to bkctld	2017-01-09 14:16:03 +01:00

README_EN.md

EvoBackup

EvoBackup is a bunch of shell scripts to create a backup server which will handle the backup of many servers (clients). Licence is GPLv2.

The main principle uses SSH chroot (called "jails" in the FreeBSD world) for each client to backup. Each client will upload his data every day using rsync in his chroot (using root account). Incrementals are stored outside of the chroot using hard links. (So incrementals are not available for clients). Using this method we can keep tens of backup of each client securely and not using too much space.

                                Backup server
                                ************

Server 1 ------ SSH/rsync -------> * tcp/2222 * * * Server 2 ------ SSH/rsync -------> * tcp/2223 * ************

This method uses standard tools (ssh, rsync, cp -al). EvoBackup is used for many years by Evolix for back up each day hundreds of servers which uses many terabytes of data.