Clear cache via WEB_GUI and remove old Revision

Hello,
I would like to delete old revisions, but I can only find tutorials for the cli.
how can I delete old revisions via WEB-GUI?

Another question is how can I clear the cache?

thank you for your help.

For the web edition, under the Schedule section/panel, in addition to a backup job there’s an option to add a pruning job. After scheduling pruning, the Options column can be used to manage the retention policy (e.g., enter “-keep 7:30” to keep all backups made during the past 30 days and only 1 per week thereafter; “-keep 0:365” keeps only backups made during the past 365 days). The following help pages might be of interest:

The CLI tutorials also apply to the web edition because it’s the same CLI program that’s being launched by the web microservice. The pathnames are a little different, but the usage is the same if you want to delete specific revisions without the web GUI.

I’m not aware of a specific button in the web GUI for clearing the local cache. Chunks in the cache are removed as part of the pruning process but if there’s a disk space issue it can be manually cleared. Search for a directory named “.duplicacy-web” and under there are subdirectories named “cache”. Note that part of the function of the cache is to reduce the amount of downloads required, so depending on your storage medium/provider it might impact your monthly fees.

Thanks for your answer.
I’ve already done a prune several times, but the check still gives errors.
I hope that someone can help me with the problem.

Here is the complete log.log.txt (17.0 KB)

Looking over your log file, the check errors are referring to missing chunks on your Unraid NAS so clearing your local cache folder won’t fix the errors, but as a last resort, chunks in your local cache could be used to repair the remote backups so it’s worth holding onto them at least for the time being.

Parsing and filtering the log output reduced the results to 7 missing chunks (several of the chunks are shared by 14 revisions):

102d3dc6982fc142cf4c92eb5fbcdf818b631899aaf0591a927b11adfe8d1f84
1c98caf6ba5356943cc2d97950781b57b1b3e632bda7e078c94ef990808f17e3
377c91860bb5cd1d63a530763ba184431435342fb1e6cc5a699d58a87176d558
524c7c60357ab8591a8b6f68b5a3579bf63f88dc49b7784bb11532113e25cb62
5fed83b3a7059fe45b488f8e8cffd6d204ab665d524e9757c6dc2f0a84c842c8
71c790bca7d1d08da60ff8406717fef6011e050ac5bdac3b217e2221e34d5ca6
b1728ab730f3a7a6f09827784f637bd8b3734a4ae926451181d3052aa1e2ce22

There are several reasons why chunks could be missing or misplaced so the first step is to log onto the Unraid NAS and manually check for the existence of the 7 missing chunks. It’ll help rule out storage media issues. The Duplicacy wiki has a tutorial on resolving missing chunks that goes into more details: Missing Chunks