[feature request] - parallel processing and VM order

[nicolas.dassy]

Good afternoon all,

Like you know, many of us are using "parallel processing" feature to improve performance and reduce the backup time window.
Unfortunately, this feature is "global" and cannot be disabled on specific job.

In our case, for some jobs, we have to be sure to process VM in a specific order (egg. "cluster/DAG" applications which must be put in maintenance mode, script to execute before to backup the other VMs...).
If we are not able to grant the processing order, the production should be impacted (network flapping, database down or placed in protection mode...). Create multiple jobs (one VM per job) to ensure that the order
is granted is not a solution.

Is it possible to add this feature in the next release?

option 1: simply the possibility to disable the parallel processing feature at the job level
option 2: add the possibility to disable the parallel processing for VMs (still at the job level) added in job asa "VM object" (and thus not like a container where VM order cannot be specified).

Thanks for your feedback or comments about this new feature.

Regards,

Nicolas

[PTide]

Hi,

As a possible workaround I can suggest you to assign a separate proxy for the job and limit the amount of concurrent tasks in its settings. That should work fine if VMs contain the same or nearly the same amount of disks. Anyway the request has been noted.

P.S. BTW, are there any other reasons except an increased management complexity to avoid creating separate jobs for each VM?

Thank you for the feedback!

[nicolas.dassy]

Hi PTide,

This environment backups a cloud platform with several hundreds of VMs and dozens of jobs.
We have to follow standards to avoid to have too much "exception" in the job configuration and management.
That's why we cannot create these separate jobs. Of course, we have some "exception" but we cannot imagine
to create some jobs with just one VM in it to grant the processing order.