From 9c37bebcecc3d811bc61cc2d6da7729d1cb848b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Schie=C3=9Fle?= Date: Mon, 15 Apr 2013 12:16:18 +0300 Subject: [PATCH] Explain the expire operation of versions --- user_manual/files/versioncontrol.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/user_manual/files/versioncontrol.rst b/user_manual/files/versioncontrol.rst index 779c689b9..18d348689 100644 --- a/user_manual/files/versioncontrol.rst +++ b/user_manual/files/versioncontrol.rst @@ -7,3 +7,21 @@ via the history tab. This tab also links to the history page, where you can roll back a file to any previous version. Changes made at intervals greater than two minutes are saved in data/[user]/versions, and made accessible using the above pages. + + +The versioning app expires old versions automatically to make sure that +the user doesn't run out of space. Following pattern is used to delete +old versions: + +* For the first 10 seconds ownCloud keeps one version every 2 seconds +* For the first hour ownCloud keeps one version every minute +* For the first 24 hours ownCloud keeps one version every hour +* For the first 30 days ownCloud keeps one version every day +* After the first 30 days ownCloud keeps one version every week + +The versions are adjusted along this pattern every time a new version gets +created. + +Beside that the version app takes care to never use more that 50% of your +currently available free space. If your versions exceed this limit ownCloud +delete the oldest versions until it meets the memory usage limit again.