From 93ccdb802438c8e178791f70bd6081156c6e4fe8 Mon Sep 17 00:00:00 2001 From: Christian Schwarz Date: Tue, 17 Sep 2019 23:54:11 +0200 Subject: [PATCH] docs: prune: fix typo --- docs/configuration/prune.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/prune.rst b/docs/configuration/prune.rst index d6ab343..76edd48 100644 --- a/docs/configuration/prune.rst +++ b/docs/configuration/prune.rst @@ -4,7 +4,7 @@ Pruning Policies ================ 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. 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.