mirror of
https://github.com/nextcloud/documentation.git
synced 2025-10-26 11:18:02 +00:00
Explain the expire operation of versions
This commit is contained in:
parent
7ca74c43e0
commit
9c37bebcec
@ -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.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user