Hi Paulo,
I highly recommend you open a case with
Veeam support if you have yet to do so. While I offer some insights on the job retry behavior below, Veeam support can help you review logs and resolve the underlying issue on why full backups are not succeeding on some VM(s) in your environment.
Short answer: There is not a method to force an incremental backup, unless you're using
Veeam Agent for Windows. Only an Active Full backup can be created ad-hoc.
Long answer: Depending on your backup job configuration and if
all or some of the VMs in the Active Full backup job failed, this behavior varies.
All of VMs fail
By design, Active Full backups only occur on the day(s) configured in the backup job. If all VMs in the backup job fail (including retries for that day) and the next backup cycle doesn't fall on an Active Full day, then the next backup will be an incremental. This also means, that incrementals after the last successful Full backup will
not be deleted to preserve the existing backup chain. No override is necessary.
Some of the VMs fail
In this case, some of the VMs in the backup job completed their Active Full backup while others failed. In this state, during the next backup cycle, incrementals will be created for the VMs that succeeded in the previous full backup while full backups will be created for the VMs that failed during the previous backup cycle.
Given the limited information I have on your configuration, I believe this is what you're experiencing.
More information on the logic of this process can be found in
Veeam documentation.
