Hi,
My question is rather simple: is there a way to configure a minimum delay between 2 consecutive automatic backups (let’s say 1 day) ? For instance, when a backup is delayed because the computer to backup is off, I observe a first backup because of the missing previous planned backup, then a second one a few dozens of minutes later when it is time to a new planned backup to occur. The second one is useless to me.
Thank you for your answers
Welcome to the forum @Emmanuel1
One question is what part of it causes hurt, however here are some ideas to deal with it.
There’s no option for a minimum delay. When Duplicati is up, backups run per schedule.
There are two things you can do to avoid backups that are too close together. The easier method is a retention policy where you can define a minimum time between two backups, however that only reduces backups after discovery. In your scenario, you could make the second backup delete when backup after it sees it’s too close to missed one that ran late.
Retention policy describes that method.
Scripts allow skipping a backup based on an exit code, e.g. if backup is near one before it, which would save a bit of storage. Duplicati deduplicates data, so its savings would be low because probably little would have changed in a few dozens of minutes. You would save a dlist file which says what’s in the backup, but its size will vary depending on the backup.
REM The following exit codes are supported:
REM
REM - 0: OK, run operation
REM - 1: OK, don't run operation
REM - 2: Warning, run operation
REM - 3: Warning, don't run operation
REM - 4: Error, run operation
REM - 5: Error don't run operation
REM - other: Error don't run operation
Scripts are OS-dependent. If you’re interested in this, please say what OS you are using.
Thank you for the answer.
I didn’t know about the complete syntax for retention policy. Useful to spare storage.
For the script, sure there is a possibility. The OS is mostly Windows.