fix(adminmanual): Document data retention and possible issues #11626
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/backport to stable28 |
|
/backport to stable27 |
|
/backport to stable26 |
tcitworld
approved these changes
Mar 8, 2024
admin_manual/groupware/contacts.rst
Outdated
|
|
||
| php occ config:app:set totalNumberOfSyncTokensToKeep --value=30000 | ||
|
|
||
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active contacts users the system would only keep an average of 10 changes per user. This will lead to premature data deletion and synchronization problems. |
There was a problem hiding this comment.
Suggested change
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active contacts users the system would only keep an average of 10 changes per user. This will lead to premature data deletion and synchronization problems. | |
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active synced addressbooks the system would only keep an average of 10 changes per sync. This will lead to premature data deletion and synchronization problems. |
For clarity
admin_manual/groupware/calendar.rst
Outdated
|
|
||
| php occ config:app:set totalNumberOfSyncTokensToKeep --value=30000 | ||
|
|
||
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active calendar users the system would only keep an average of 10 changes per user. This will lead to premature data deletion and synchronization problems. |
There was a problem hiding this comment.
Suggested change
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active calendar users the system would only keep an average of 10 changes per user. This will lead to premature data deletion and synchronization problems. | |
| The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active synced calendars the system would only keep an average of 10 changes per calendar. This will lead to premature data deletion and synchronization problems. |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
ChristophWurst
force-pushed
the
feat/adminmanual/dav-data-retention
branch
from
fe59317
to
bb03c7f
Compare
tcitworld
requested changes
Mar 8, 2024
|
|
||
| .. versionadded:: 26.0.0 | ||
|
|
||
| You can configure how long Nextcloud keeps some of the calendar data. |
There was a problem hiding this comment.
Suggested change
| You can configure how long Nextcloud keeps some of the calendar data. | |
| You can configure how long Nextcloud keeps some of the calendar sync tokens. |
|
|
||
| .. versionadded:: 26.0.0 | ||
|
|
||
| You can configure how long Nextcloud keeps some of the contacts data. |
There was a problem hiding this comment.
Suggested change
| You can configure how long Nextcloud keeps some of the contacts data. | |
| You can configure how long Nextcloud keeps some of the contacts sync tokens. |
| @@ -21,6 +21,10 @@ A brief overview of changes: | |||
|
|
|||
| See for more information: :ref:`email-smtp-config`. | |||
|
|
|||
| DAV data retention | |||
There was a problem hiding this comment.
Suggested change
| DAV data retention | |
| DAV sync tokens retention |
| DAV data retention | ||
| ------------------ | ||
|
|
||
| A mechanism to clean up old CalDAV and CardDAV data has been added. See :ref:`CalDAV retention <caldav-data-retention>` and :ref:`CardDAV retention <carddav-data-retention>` and make sure it fits your installation size. |
There was a problem hiding this comment.
Suggested change
| A mechanism to clean up old CalDAV and CardDAV data has been added. See :ref:`CalDAV retention <caldav-data-retention>` and :ref:`CardDAV retention <carddav-data-retention>` and make sure it fits your installation size. | |
| A mechanism to clean up old CalDAV and CardDAV sync tokens has been added. See :ref:`CalDAV retention <caldav-data-retention>` and :ref:`CardDAV retention <carddav-data-retention>` and make sure it fits your installation size. |
|
/backport to stable29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Backstory: found an instance where entries were deleted from calendarchanges before connected clients had a chance to read the latest changes.
🖼️ Screenshots