Well, because we can't control any client anytime! it's just impossible in our case, and denied access of backup section to our client it's just an bad policy.... We NEED an real solution, not an patch of disable stuck client backupWhy not? As far as I know this bug occurs when a subscription backup has been setup with remote storage and the connection fails to the remote storage. So why can't you temporary disable/remove backups for these clients/subscriptions? Their backups aren't working anyway? Leaving the 'bad' backups enabled impacts your own backups and presumably those of you other clients.
Or am I missing something?
An "bad" backup simply SHOULDNT impact anythings... as it was the case before this MU