Full Backup Date Shift

[macbergil]

Hi,
sometimes we noticed a one day shift during the execution of full backup (ie: configuration settings for full backup is "7D", but backup is executed after 8D).

The event is triggered because the time of the last full backup is before current start time.

Example log:
`Data dell'ultimo backup completo: Sat Mar 16 19:21:18 2019
NOTICE 1
. Data dell'ultimo backup completo: Sat Mar 16 19:21:18 2019

--------------[ Statistiche del backup ]--------------
StartTime 1552846872.62 (Sun Mar 17 19:21:12 2019)
EndTime 1552847954.54 (Sun Mar 17 19:39:14 2019)
ElapsedTime 1081.92 (18 minutes 1.92 seconds)
SourceFiles 1755775
SourceFileSize 1137161314644 (1.03 TB)
NewFiles 0
NewFileSize 0 (0 bytes)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 0
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 20 (20 bytes)
Errors 0
------------------------------------------------------`

As you can see the Last full backup date is Sat Mar 16 19:21:18 2019, but the start time of the current backup is Sun Mar 17 19:21:12 2019. For only 6 seconds scripts not trigger full backup, but instead incremental backup.

This is a common behavior in production environment and sometimes is a problem because full backup is very large and it should be scheduled the same day of week (ie: for bandwith problem).

Do you have any solutions?
Thanks in advance

Domenico

[douglascrp]

Hello.

Unfortunately, it seems there is nothing we can do about it, as this is managed by duplicity.
I also have some environments where the backup process can take 24 hours, even more, to complete.

If you find something about the topic, please, share it with us.