BigSister

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Components and Roles ======

In order to run backups, the following components act in concert:
  * the backup controller starting backups, keeping inventory records, sending out notifications
  * the backup client: the system being backed up
  * the backup repository: the storage holding the actual backups

In the most simple use case those roles are all implemented on the same machine. Also, a central controller is supported but not required - it is up to you if you prefer to run a controller on each client or one single central one.

You will need to install the backup software at least on the backup controller and the backup repository. The backup client can be backed up without installing the backup software (but requires SSH and rsync).

===== 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. Pluggable disks (USB, RDX, hotplug SATA, etc.) are completely ok.

BigSister

User Tools

Site Tools

Page Tools