This incident has now been resolved, any affected backup sets will run as expected on their next scheduled backup run.
Posted 3 months ago. Jun 04, 2019 - 08:49 BST
We are continuing to work on a fix for this issue.
Posted 3 months ago. Jun 04, 2019 - 08:48 BST
The issue was tracked down to a connectivity issue on cluster 001 between the production and replication systems causing several backup sets to be held in a 'locked' state. This was reported by clients as a connectivity issue.