Thanks for the report - I've done some investigation and identified an issue where a backups can report as failed internally as Site Manager doesn't receive a process completion message correctly due to a bug in the Agent service. This does not affect the backup process or the integrity of backed up data, but does cause the Site Manager server to requeue the backup - the intended sequence of events is:
-> Site Manager launches a "launch backup" message to start the backup
<- Agent starts the backup process and sends a backup start message
<- Agent sends a backup complete message
< Agent sends a "launch backup" complete message
-> Site Manager removes the task from the internal scheduler and moves on
The bug causes the last Agent message to not send. In this case, Site Manager knows the backup was successful, but continues to wait for the backup process to complete (this is the Cleanup on Agent state). After a timeout waiting for the completion message, Site Manager moves on, but this triggers to 'retry on failure' logic of the queue.
We'll be deploying a new version to fix this today or shortly after, in the mean time, please temporarily turn off the retry on failure logic of the schedule.
See our reviews on