Retry of incremental backup changes to active full

[dyna]

I have an incremental backup starting 22:00 and with active fulls on friday.
If in the thursday night backup VMs will fail in the first try, it will be retried but after midnight making it officially friday and the backup of those VMs will change to active full. It's not even trying to hide it, the job log entry will simply change from "Backupname (Incremental)" to "Backupname (Active full) (Retry 1)".
The problem is that if it happens changes are it's on big VMs like fileservers and causing extra delays for possible backup copy jobs, in our case turning a backup+copy from a 7 hour run into an 18 hour run.

I could change the schedule of course but i'm guessing this is not intended behavior but correct me if i'm wrong.

[foggy]

I'd say the behavior is expected from the product perspective, since you have active full scheduled for Friday and the first job run on this day should be full. Though this might not be fully expected from the user's perspective, so I will discuss this internally.

Anyway, full backup shouldn't affect backup copy job, since it copies only changes regardless of whether the latest restore point is full or incremental.

[uk1984]

I have a recent case where I am having exactly the same issue as described here.
Support has suggested that I contact R&D via this topic since support sees not responsibility
because it is broken aehm "works as designed" and also wants no interaction with RD and
prefers the customer doing the work.

So here I am again the middleman between support and R&D just wanting something "fixed",
let's see if Veeam wants it, too...

This is my case:
Case #07918409 — History showing incremental instead of "(Full)" Backups

Best Regards