Vitality, I have contacted support for the hotfix and even linked to this thread but got this reply:
Unfortunately, there is no hotfix for that OIB issue, but the current workaround is:
You can workaround this issue for now by expanding the backup set, right-clicking on the problematic vm(s) and deleting from disk (This is also why removal from dynamic org folder did the trick). The next job run will run a full for that particular guest. To avoid this on non SQL/Exchange servers, just disable log truncation as it is not necessary. For SQL/Exchange, we'll need to ensure VSS is functioning properly for log truncation, if that is how you are leverage Veeam VSS in your restoration planning/process.
As someone else says this could be very misguiding to some, suggesting to delete from disk but not mentioning that this will remove previous backups. I am having this problem with an Exchange server and after forcing a full backup I still recieve this error message so I will try to truncate logs at the start of the job but I do not want to disable it entirely. Could this be at all related to the fact that that Exchange backup can take anything up to 20 Hours for us?