You cannot delete a backup if it has failed and it remains in the locked state. Automatically detecting this and unlocking the task would be helpful (though may causing locking semantic problems).
Alternatively an option in the UI to manually unlock a failed backup much like you can with virtual servers would be a good start.
It usually unlocks after failure, but in about 50% of 17 cases with us where backups failed due to a backup server failure they were stuck in the locked state.
If this issue occurs with an AutoBackup backup, the schedule stops running completely and does not recover (see https://onapp.zendesk.com/entries/26333506-Backups-should-be-reliable-Failed-backups-should-not-prevent-it-from-running-in-the-next-period-)
Please sign in to leave a comment.