I might have figured out why @JonMikelV and @mr-flibble had trouble getting the fileset number from their error message to match anything in the regular UI. See Backup failing due to unexpected difference in fileset.
By any chance do either of you have your broken database around? It might be useful to experiment with, but we’d probably want to keep testing from harming anything (including destination data) that’s now running well.