khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-02 17:59:36 +07:00
Code Issues Packages Projects Releases Wiki Activity

fix: added the paragraph above note

Browse Source
This commit is contained in:
yemkareems
2025-10-23 14:18:47 +05:30
parent 02dfcf09be
commit 4917b8bbd0
1 changed files with 19 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
admin_manual/configuration_files/file_versioning.rst
View File

@@ -21,6 +21,20 @@ The Versions app never uses more than 50% of the user's currently available
free space. If the stored versions exceed this limit, Nextcloud deletes the
oldest file versions until it meets the disk space limit again.
The ``versions_retention_obligation`` setting behaves slightly differently
depending on whether version expiration is triggered by an *explicit job run*
(for example, via ``occ versions:expire`` or a scheduled background job) or by
*automatic expiry*.
Explicit job-based expiration is *strict* and adheres closely to the configured
``versions_retention_obligation``.
Auto-expiry follows the same retention principles but may apply them more flexibly, allowing minor deviations when
necessary to maintain adequate free storage space.
This distinction can lead to different results depending on whether cleanup is
performed automatically or manually.
.. note:: Versions named by a user will never be deleted.
You may alter the default pattern in ``config.php``. The default setting is
@@ -30,12 +44,12 @@ You may alter the default pattern in ``config.php``. The default setting is
Additional options are:
* ``D, auto``
Keep versions at least for D days, apply expiration rules to all versions
* ``D, auto``
Keep versions at least for D days, apply expiration rules to all versions
that are older than D days
* ``auto, D``
Delete all versions that are older than D days automatically, delete other
* ``auto, D``
Delete all versions that are older than D days automatically, delete other
versions according to expiration rules
* ``D1, D2``
@@ -54,22 +68,4 @@ Deactivate background job: ``occ config:app:set --value=no files_versions backgr
Activate background job: ``occ config:app:delete files_versions background_job_expire_versions``
Expire versions: ``occ versions:expire`` or ``occ versions:expire --quiet`` (without the progress bar)
.. note::
*Deviations in behavior: “job run” vs “auto-expiry”*
The ``versions_retention_obligation`` setting behaves slightly differently
depending on whether version expiration is triggered by an *explicit job run*
(for example, via ``occ versions:expire`` or a scheduled background job) or by
*automatic expiry*.
Explicit job-based expiration is *strict* and adheres closely to the configured
``versions_retention_obligation``.
Auto-expiry follows the same retention principles but may apply them more flexibly, allowing minor deviations when
necessary to maintain adequate free storage space.
This distinction can lead to different results depending on whether cleanup is
performed automatically or manually.
Expire versions: ``occ versions:expire`` or ``occ versions:expire --quiet`` (without the progress bar)