mirror of
https://github.com/zrepl/zrepl.git
synced 2024-12-23 07:28:57 +01:00
docs: prune: fix typo
This commit is contained in:
parent
501645f918
commit
93ccdb8024
@ -4,7 +4,7 @@ Pruning Policies
|
|||||||
================
|
================
|
||||||
|
|
||||||
In zrepl, *pruning* means *destroying snapshots*.
|
In zrepl, *pruning* means *destroying snapshots*.
|
||||||
Pruning must happen on both sides of a replication or the systems would inevitable run out of disk space at some point.
|
Pruning must happen on both sides of a replication or the systems would inevitably run out of disk space at some point.
|
||||||
|
|
||||||
Typically, the requirements to temporal resolution and maximum retention time differ per side.
|
Typically, the requirements to temporal resolution and maximum retention time differ per side.
|
||||||
For example, when using zrepl to back up a busy database server, you will want high temporal resolution (snapshots every 10 min) for the last 24h in case of administrative disasters, but cannot afford to store them for much longer because you might have high turnover volume in the database.
|
For example, when using zrepl to back up a busy database server, you will want high temporal resolution (snapshots every 10 min) for the last 24h in case of administrative disasters, but cannot afford to store them for much longer because you might have high turnover volume in the database.
|
||||||
|
Loading…
Reference in New Issue
Block a user