Behavior of Periodic Active Full with Reversed Incrementals

[eiskra]

I'd like to clarify the behavior in the following circumstance:

If the job is set to run as Reversed Incremental with an Active Full the last Saturday of every month, with a retention of 20 restore points, then:
On the day after the last Saturday of the month, will there be ONE full .vbk file on the repository's drive, or will there be two full .vbk files?

If the job is set to run as Reversed Incremental with an Active Full the last Saturday of every month, with a retention of 70 restore points, then:
On the day after the last Saturday of the month, will there be ONE full .vbk file on the repository's drive, or FOUR?

[foggy]

If the job is set to run as Reversed Incremental with an Active Full the last Saturday of every month, with a retention of 20 restore points, then:
On the day after the last Saturday of the month, will there be ONE full .vbk file on the repository's drive, or will there be two full .vbk files?

Since active full starts a backup chain anew, there will be two VBK files on disk after performing an active full, until the new chain accumulates the required number of restore points (20 in this case) and previous full will be deleted according to retention.

If the job is set to run as Reversed Incremental with an Active Full the last Saturday of every month, with a retention of 70 restore points, then:
On the day after the last Saturday of the month, will there be ONE full .vbk file on the repository's drive, or FOUR?

There will be four VBK files (the oldest one will be deleted according to retention after ~10 days, depending on the particular month and the number of days in it).

[eiskra]

Thanks for the clarification.