Fix schema on README
This commit is contained in:
parent
7493327b1b
commit
207386de28
|
@ -11,12 +11,14 @@ Incrementals are stored outside of the chroot using hard links or btrfs snapshot
|
||||||
(So incrementals are not available for clients). Using this method we can keep tens
|
(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.
|
of backup of each client securely and not using too much space.
|
||||||
|
|
||||||
|
~~~
|
||||||
Backup server
|
Backup server
|
||||||
************
|
************
|
||||||
Server 1 ------ SSH/rsync -------> * tcp/2222 *
|
Server 1 ------ SSH/rsync -------> * tcp/2222 *
|
||||||
* *
|
* *
|
||||||
Server 2 ------ SSH/rsync -------> * tcp/2223 *
|
Server 2 ------ SSH/rsync -------> * tcp/2223 *
|
||||||
************
|
************
|
||||||
|
~~~
|
||||||
|
|
||||||
This method uses standard tools (ssh, rsync, cp -al, btrfs subvolume). EvoBackup
|
This method uses standard tools (ssh, rsync, cp -al, btrfs subvolume). EvoBackup
|
||||||
is used for many years by Evolix for back up each day hundreds of servers which
|
is used for many years by Evolix for back up each day hundreds of servers which
|
||||||
|
|
Loading…
Reference in a new issue