reversed incremental and active full backups

[serverbu]

Hello,

a question regarding the active full backup option in conjunction with reversed incremental backups.
On a normal (incremental backup) job with 14 restore points (one every day) and active full backups every weekend, we get a backup chain consisting of 14 files, 12 vib and 2 vbk, this is as expected.
A reversed incremental job with 14 restore points and active full backup every weekend, we expected a chain of 12 vrb and 2 vbk.
But in reality we get 14 files, 13 vrb and only 1 vbk (of the present day).

We wanted to keep a reverse chain of 14 days with a ful backup every weekend so that a restore of the oldest days only has to apply half as much increments, is there a way to implent the job that way?

[veremin]

First of all, with reversed incremental mode, there is no need to run active full backup that frequently, normally users run active full backup once every 1 to 3 months. Additionally, regardless of backup mode active full backup creates additional .vbk file. In other words, once it's finished, there should be a new .vbk file in target repository. Are you positive that full backup did take place?

We wanted to keep a reverse chain of 14 days with a ful backup every weekend so that a restore of the oldest days only has to apply half as much increments, is there a way to implent the job that way?

Could you elaborate on the last portion, as I'm not sure whether I totally follow your train of thought?

Thanks.

[foggy]

We wanted to keep a reverse chain of 14 days with a ful backup every weekend so that a restore of the oldest days only has to apply half as much increments, is there a way to implent the job that way?

With weekly active full, it should be just like you want it to be - maximum 6 increments depending on each full backup. So, as Vladimir has already assumed, most likely some of the recent fulls was not performed. Though, I would also concur with Vladimir regarding excessiveness of a weekly active fulls for reversed incremental mode.