diff options
author | Lars Wirzenius <liw@liw.fi> | 2021-02-05 10:43:05 +0200 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2021-02-05 10:46:03 +0200 |
commit | cf48cc44697907ba6a2c1bd096be2027a5eb8bef (patch) | |
tree | d38abf594679ee0dc78a159d0bbd525614ffa403 /obnam.md | |
parent | 3eaa4c7dc1e3b7b6126f1e9ac818f01f400fee14 (diff) | |
download | obnam2-cf48cc44697907ba6a2c1bd096be2027a5eb8bef.tar.gz |
doc: Obnam only does push backups
Diffstat (limited to 'obnam.md')
-rw-r--r-- | obnam.md | 19 |
1 files changed, 19 insertions, 0 deletions
@@ -419,6 +419,25 @@ can be replaced with stronger ones. This will allow Obnam to migrate to a stronger algorithm when attacks against the current one become too scary. +## On pull versus push backups + +Obnam only does push backups. This means the client runs on the host +where the live data is, and sends it to the server. + +Backups could also be pulled, in that the server reaches out tot he +host where the live data is, retrieves the data, and stores it on the +server. Obnam does not do this, due to the hard requirement that live +data never leaves its host in cleartext. + +The reason pull backups are of interest in many use cases is because +they allow central administration of backups, which can simplify +things a lot in a large organization. Central backup administration +can be achieved with Obnam in a more complicated way: the installation +and configuration of live data hosts is done in a central fashion +using configuration management, and if necessary, backups can be +triggered on each host by having the server reach out and run the +Obnam client. + # File metadata Files in a file system contain data and have metadata: data about the |