I am using DLO and I have it set for scheduled backups and the completion backup is always messy it gives me in a day that it is 90% and the next day it becomes 32% or so for no reason can someone explain how the process of calculating the backup completion is done through out the scheduled backup and after the scheduled backup.
I understand your confusion and this is something seen more when Scheduled Backups are configured. I will try to explain why below;
DLO is primarily designed to be run with Continuous Backups, so that files are backed up as soon as changes are detected; that is the default setting. That means that the user data is protected sooner and that the load on the network is spread out across the working day, instead of all user data being queued to be backed up at a scheduled time and the processing\network load that will cause.
The Backup completion % shown in the DLO Admin Console is being reported from the user machine about the percentage of the total files that are currently protected and with Continuous backups would normally be a true reflection of the status, as the files are being backed up almost as soon as they change.
In a Scheduled backup scenario, the Backup completion percentage will fluctuate during the day, as files are being changed and queued to be backed up, as backups are only being taken at scheduled times (daily?). If the user machine is connected and can reach the DLO server, the DLO Agent is designed to send an update of it's status every 15min; that will have an impact on the Backup completion percentage during the day. For example:
This means that, when using Scheduled backups, the Backup completion % (percentage of files that are fully protected) will reduce between backup times. That is to be expected if the DLO Agent is online, to update it's status and file changes are being queued for the next backup.
I hope this explains what you are seeing and why.