Managing SSH chroots to backup a lot of machines

Go to file

Jérémy Lecour bc72111e13 redirects stderr to stdout for traceroute OpenBSD outputs a line to stderr when starting a traceroute. It makes cron to send an email.		2016-10-04 11:33:03 +02:00
etc	Now in Git!	2010-09-09 01:07:03 +02:00
PLAN-SAUVEGARDES.template	Now in Git!	2010-09-09 01:07:03 +02:00
README_EN.md	Updated French README.	2015-08-28 19:01:06 +02:00
README_FR.md	typo	2015-11-24 19:50:51 +01:00
chroot-ssh.sh	Fix #1533 : revert chroot-dir -> chroot-name change	2015-08-14 18:44:55 +02:00
evobackup	Errors with new init script	2014-06-19 04:55:27 +02:00
evobackup-inc.sh	chmod +x for executables.	2015-07-02 15:21:29 +02:00
evobackup-rm.sh	chmod +x for executables.	2015-07-02 15:21:29 +02:00
jail_init.sh	Added jail_init.sh.	2016-06-03 14:31:09 +02:00
zzz_evobackup	redirects stderr to stdout for traceroute	2016-10-04 11:33:03 +02: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.