Feature request - Schedule synthetic full apart from backup

[anton]

Hi Veeam,

It would be great if we can schedule the synthetic full apart from the normal backups; or at least give or backup priority over synthetic full.
We currently have 15 jobs (Incremental) and every saturday we create a synthetic full (using ReFS fast clone, per vm backup chain)

The synthetic full starts at the end of the backup job, but can block other jobs from making the backup (since the repository concurrency is reached).

To have maximum control it would be great if we can schedule the synthetic full apart from the backup job. So we run the backup jobs (incremental) and we schedule an synthetic full later.
An alternative would be to give the synthetic full operation a lower priority; so that backups will always be finished first and synthetic fulls will be made afterwards.

[Shestakov]

Hi Anton and welcome to the community!
Synthetic transformation takes place at the end of the job run so the job is not finished until the synthetic operations are done. How much time does synthetic transformation take in your case?
Backup jobs can work fine in parallel. Do you use job chaining?
Thanks!

[anton]

Hi Shestakov,

Thanks for your reply!
The issue is that synthetic full is taking hours.
Since we limited the amount of jobs on the repository; other backup jobs will be waiting for resources until the synthetic full is done.
We are not use job chaining (except a few tape jobs)

[Shestakov]

My recommendation is to schedule jobs and synthetic transformation so they don`t overlap. You may also size repositories accordingly. I doubt that synthetic transformation apart from the job is a good idea as it may cause bugs and incomprehension.
Thanks for the request!

[mkretzer]

@shestakov: Sorry but if we uses REFS fast clone he can have all the drives in the world and still would have issues that synthetics and other backups do not mix well because of the performance issues you get after 4-5 weeks with REFS.

We have 96 drives doing nearly nothing while fast clone was running and many incr backups just writing with a few MB/s.

Until this is solved by MS a seperate merge would really be useful!

[Shestakov]

Got it. We will take your feedback into consideration.
Thanks!