The deep dive is not supposed to be needed in 2.0.4.5 beta. That was the workaround for a bug now fixed.
For 2.0.4.5 users, Backup failing due to unexpected difference in fileset retracts that workaround. Now you can (I think) take the error message’s information without the workaround, and run The DELETE command.
Unexpected difference in fileset version 0: 12/5/2018 6:39:53 PM (database id: 3), found 2 entries, but expected 3
is the backup error I got from an FTP failure I forced to test “Unexpected difference in fileset” errors [2.0.3.9], and doing a delete of that version took care of it. I haven’t seen other versions, but maybe it’s always on 0…
Did you save your old database before deleting it? If so, it’s possible we can still try the above idea on fixing, otherwise I’m not immediately sure what to say about your new error. Perhaps someone else will comment…