Hopefully I find some time on the weekend to do some tests with --run-script-before-required.
(Linux newbie: have to learn about scripts, checking week days, times, …)
Even your thread "missing files" error after switching to custom retention policy confirm my thoughts about having multiple jobs (one everyday) for the same data.
=> I’m sure that we need something like I described in the first post.
Another example:
On job on Monday and Tuesday running multiple times a day saving to Cloud1.
On job on Wednesday and Thursday running multiple times a day saving to Cloud2.
On job on Friday and weekend running multiple times a day saving to Cloud3.
PLUS a good retention sheme like just keeping the last backup of the day (done the week after backup)
->
- multiple backup versions from Monday and Tuesday in the current week
- reduced one week later to the latest versions of Monday and Tuesday
- later on reduced to the latest version of Tuesday
- …
The cause of trouble with the backend will not always be duplicati itself.
Many might be out of our control.