@olivierlambert thank you for your reply!
We have updated to the most recent commit (af87d) and we will monitor our backup schedules over the next week. I will post more logs if the issue presents itself again.
To add more information, we were on commit 4d3dc when the issue presented itself and before updating yesterday to 20a89.
Hi @olivierlambert we have just come across the same issue again today after the latest update.
Please see below the log file for the delta backup schedule that performed full backups instead. I can't seem to find anything in the logs to help.
@olivierlambert thank you for your reply!
We have updated to the most recent commit (af87d) and we will monitor our backup schedules over the next week. I will post more logs if the issue presents itself again.
To add more information, we were on commit 4d3dc when the issue presented itself and before updating yesterday to 20a89.
Hi team,
Thank you for creating and maintaining this product, and making it available to all.
We have come across a situation where it seems that some of our 'Delta' backup schedules are randomly performing 'Full' backups of each machine instead of the incremental, smaller sized backups.
It seems to occur randomly but as you can see in the image for this particular schedule, the transfer size hovers around 15-25 GiB (which are all delta backups) before performing a full backup causing the transfer size to increase to 460 GiB.
We are aware of the 'full backup interval' feature however we don't have this set to anything. Is there a hidden default value for this? Or is there something else that we are missing?
Our current version we are running can be seen in the final image.
Any help is greatly appreciated! Thank you 
