ABR 11 Custom Backup Archive Cleanup Issue

Retention policy won't delete the only existing backup (backup chain, as deleting the full deletes depending incrementals). IIRC it's possible with 'when there is insufficient space' rule or using 'simplified archive names' mode (if your location allows).

Before creating a new full backup, the software will delete the entire archive and start a new one.

So if you schedule two backup plans with simplified naming - one with fulls and one with incrementals - 'full' plan will delete the whole chain before creating new full backup.

Is there an possibility to create a full backup only after the incremental backup fails due to lack of free space?

Example:
full back size 200 GB compressed
daily incremental 30 GB
backup target; a set of 500 GB USB drives.

The goal is to create one single job and get maximum of backup instances, means perform incremental backups as long as free space is available
but after incremental fails after space exhausted it should just create a full backup.

UG:(4.2.5.4) > If there is only one full backup left, and an incremental or differential backup is in progress, an error occurs saying there is a lack of available space

It won't automaitcally start full ackup instead of incremental, but you may try to use 'Time since last backup' scheduling for 'full' backup, if it takes into account the last backup of another type (i.e. incremental), or somehow detect failure of incremental backup and use scheduling by 'windows event log event' to trigger full backup.

Thanks, just turned on windows event logging

I would prefer to keep the full backup on each single disk, but could not found a job definition so far.

Is there any rule of thumb how many free space is required to delete a single incremental backup depending from the size.
I made some test and saw that it fails even if 200 of 500 GB were available.
Also the fact, that it seems to be a very long process to remove a single incremental backup, let me think about to delete either all
incremental or overwrite the full backup.

We managing the backup history with rotating disks.
What I'm looking for is just to have at least a full backup each morning without any intervention
and the possibility to use the remaining disk space for incremental backups.

At this time I have an incremetal backup job only.
On a empty disk a full backup will created, then incrementals, but it fails if there is not enough space for the incremental.

///ARMIN and egge99,

try this link, it looks similar to your scenarios.