Request new feature to create synthetic or full backup

[matfra]

First: sorry for my English

I’ve 10 forward incremental backup, one for every virtual machine.
I scheduled for every day of the week the start of backup of “VM1” at 10:30 pm.
For backup of “VM2” the start is “ After the job: VM1”
For backup of “VM3” the start is “ After the job: VM2”
etc until “VM10"
On every forward backup, there are 14 restore points. Every Saturday I set the creation of synthetic full backup.
The problem is that, for some backup, it's not created the synthetic backup.
This is my situation:

Backup | Day Start | Hour Start | Day End | Hour End | File |
VM1 | Friday 22/09 | 10:30 pm | Friday 22/09 | 10:37 pm | VIB |
VM2 | Friday 22/09 | 10:37 pm | Friday 22/09 | 10:49 pm | VIB |
VM3 | Friday 22/09 | 10:49 pm | Friday 22/09 | 10:10 pm | VIB |
VM4 | Friday 22/09 | 11:10 pm | Friday 22/09 | 11:24 pm | VIB |
VM5 | Friday 22/09 | 11:24 pm | Friday 22/09 | 11:29 pm | VIB |
VM6 | Friday 22/09 | 11:29 pm | Friday 22/09 | 11:37 pm | VIB |
VM7 | Friday 22/09 | 11:37 pm | Friday 22/09 | 11:45 pm | VIB |
VM8 | Friday 22/09 | 11:45 pm | Saturday 23/09 | 01:19 am | VIB |
VM9 | Saturday 23/09 | 01:19 am | Saturday 23/09 | 01:26 am | VBK |
VM10 | Saturday 23/09 | 01:26 am | Saturday 23/09 | 01:36 am | VBK |

VM1 | Saturday 23/09 | 10:30 pm | Saturday 23/09 | 10:50 pm | VBK |
VM2 | Saturday 23/09 | 10:51 pm | Saturday 23/09 | 11:18 pm | VBK |
VM3 | Saturday 23/09 | 10:19 pm | Sunday 24/09 | 00:40 am| VBK |
VM4 | Sunday 24/09 | 00:40 am | Sunday 24/09 | 01:03 am | VIB |
VM5 | Sunday 24/09 | 01:03 am | Sunday 24/09 | 01:14 am | VIB |
VM6 | Sunday 24/09 | 01:15 am | Sunday 24/09 | 01:29 am | VIB |
VM7 | Sunday 24/09 | 01:30 am | Sunday 24/09 | 01:45 am | VIB |
VM8 | Sunday 24/09 | 01:45 am | Sunday 24/09 | 03:35 am | VIB |
VM9 | Sunday 24/09 | 03:35 am | Sunday 24/09 | 03:41 am | VIB |
VM10 | Sunday 24/09 | 03:41 am | Sunday 24/09 | 03:49 am | VIB |

How you can see, for the backup of VM4, VM5, VM6, VM7, VM8 it’s NEVER created the VBK. In this situation the restore points increase infinitely.
Could you introduce a new feature to create synthetic (or full) backup after “n” incremental?

[PTide]

Hi,

If the backup jobs generate incremental backups on Saturday despite of synthetic full option being checked then I'd suggest you to contact our support team directly as this is unexpected behaviour. Once you do please post your case ID.

Thank you

[matfra]

I've already contacted the support. Case # 02322954
A technician telephoned me. He said that there is currently no function and he suggested me to open post in this forum.

[PTide]

It seems that because of "After this job" scheduling all the jobs (VM4, VM5, VM6, VM7, VM8) have been shifted towards so that when they start its already Sunday thus synthetic full is not triggered.

Thanks

[foggy]

This is one of the reasons why job chaining is against the best practices. You'd better start all the jobs ~at the same time with short intervals and let automatic resource scheduling do its job.

[matfra]

It seems that because of "After this job" scheduling all the jobs (VM4, VM5, VM6, VM7, VM8) have been shifted towards so that when they start its already Sunday thus synthetic full is not triggered.

Yes, the problem is this. That's why I asked the feature

This is one of the reasons why job chaining is against the best practices

I didn't know. For me is a good solution. I have resources to start one job at a time. This solution guarantees me to do all the work with maximum time optimization.
I think if the software allows this kind of scheduling, should handle the situation I described

You'd better start all the jobs at the same time with short intervals and let automatic resource scheduling do its job.

How can I do? As I wrote above, I have no resources to run more than one job at a time

Apologize yet, but it is not easy for me to express certain concepts in English

[PTide]

You feature request has been noted. Meanwhile you can use proxy and repository concurrent tasks settings to limit the number of virtual disks being processed concurrently. That will cause jobs to queue up and wait for resources get available. Although that's a workaround it should work fine.

Thanks

[matfra]

Ok, thank you