This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
osbackup:concepts:01_roles [2017/06/20 20:35] Thomas Aeby [The backup repository] |
osbackup:concepts:01_roles [2017/06/20 20:49] Thomas Aeby |
||
---|---|---|---|
Line 12: | Line 12: | ||
===== The backup repository ===== | ===== The backup repository ===== | ||
- | The actual backups are stored file-by-file in the same structure as on the backup client. The backup repository needs to have access to a sufficiently large storage volume (rule of thumb: at least twice the size of the data to be backed up) with a decent file system. Ext3/ext4, xfs, btrfs, zfs will do, file systems with limitted capabilities like NTFS, FAT, exFAT won't. | + | The actual backups are stored file-by-file in the same structure as on the backup client. The backup repository needs to have access to a sufficiently large storage volume (rule of thumb: at least twice the size of the data to be backed up, but of course your retention policy will have a big influence) with a decent file system. Ext3/ext4, xfs, btrfs, zfs will do, file systems with limitted capabilities like NTFS, FAT, exFAT won't. Pluggable disks (USB, RDX, hotplug SATA, etc.) are completely ok. |
+ | Multiple backup repositories and synchronisation between them is possible, e.g. for running backups on a local storage during the night and slowly synchronizing them to a remote backup repository during the day. | ||
+ | |||
+ | ===== The backup client ===== | ||
+ | |||
+ | The system to be backed up. Currently, Windows and Unixoid systems are supported. Besides file-by-file backups some limitted imaging capabilities via external tools (ODIN, NTFSClone) are available, too. | ||
+ | |||
+ | ===== The backup controller ===== | ||
+ | |||
+ | The backup controller starts and monitors backups, (optionally) holds a backup inventory and sends notifications and reports via mail. Usually, tasks are run via cron. | ||
+ | |||
+ | |||
+ | ===== Communication between the components ===== | ||
+ | |||
+ | Most of the communication is done through SSH and rsync. A few of the features make use of SMB file sharing. | ||