Planned active full backup didnt work

[Globatech]

Hi there,
we are under Veaam B&R version 9.5.0.823 but this issue was there before. For some task the active full backup didnt start. For exemple a task with 30 incrementals and a active planned the 3rd saturday of each month the active full never start so we have to start it manually. This cause that the "cleaning job" never happen to so we have like 250 files (days) in our storage for this task.
Does anyone have a idea how to make it work?... Is there a way to recreate the job and relink the all the active storage files?

TY

[veremin]

Aren't you using chain type of schedule, where one job starts after the other one? Thanks.

[Globatech]

Yes they are chained and that approach make sens because only the first one was able to succeed is full job scheduled. Should we disabled that chain? TY

[foggy]

The chained jobs start on the next day, not on the day full backup is scheduled at. That's why it is never performed. Job chaining is not considered as best practice.

[Globatech]

Do you think that if i disable the chained job the next full backup will be able to clean all the files that are older than the retention date? If not how can i do that? TY

[veremin]

The obsolete restore points will be cleaned, once certain number of incremental passes are performed after new full backup (e.g. 7 days retention period = 6 incremental passes after new active full backup). Thanks.

[Globatech]

Thanks i will give it a try next weekend and give you my feedback next week.

[veremin]

These visuals will probably explain retention concept for forward incremental mode better. Thanks.

[Globatech]

Ive make somes change on the scheluded task and ive disabled the chain, so the full backup have succeed but that didnt clear all the other older restore point. Anything should i do here?
TY

[foggy]

No, old backups will be cleaned up automatically when the number of restore points in the new chain will reach the specified retention.

[onc]

Hi,

i have 2 backup jobs:

Backup Job1: Host with some exclusions
Backup Job2: Exclusions from Job1

Both with following same settings (compared side by side):
Retention policy -> Restore points to keep on disk: 15
Incremental -> Create synthetic full backup periodically: Saturday
Active Full backup -> Create active full backup periodically: Monthly First Saturday (every month)


When i select restore following restore points are offered:

for Job1: 16 restore points are offered, every saturday is a full backup, with increment backups between (as i expected with this settings)
for Job2: 107 restore points are offered, the oldest restore point is a full backup (106 days ago), everything else is an increment backup

Anyone can give me a hint why Job2 behaves not like Job1?

Thanks in advance,
Carsten

[veremin]

Are those jobs chained by any chance? Thanks.

[onc]

Thank you for the reference to chaining and problems related to chaining jobs.

Job1 is planned for 10pm. I checked the mails that are send after finishing the job, and i have seen an incremental backup takes only ~1 hour. So Job2 (incremental) will always start at the same day.
But a full backup usually takes more then 2 hours. So i think the problem was the "trigger" for Job2 "full backup at saturday" is never met. I will change this setting.

[veremin]

Hmm, if both jobs are scheduled for the same day (Saturday), and both of them got executed on it, then, there should not have been any problems with active full backup.

If that's the case, kindly, reach our support team and let them confirm your backup job settings.

Thanks.