[Feature Request] Processing VMs in Job in descending size order

[Refruit]

Hello,

we are using a dedicated backup job for a specific customer, who deploys VMs on it's own inside our VMware Infrastructure. To make sure everything is backuped, the Job is configured to backup everything inside the customers resource pool.
So splitting the VMs into multiple Jobs to optimize parallelism seems not possible in this scenario.
It would be great if we had an option to process the VMs inside the Job in descending size order so that big VMs are processed first. I think the advantage would be that the whole Backup Job isn't waiting forever to complete by processing big VMs at the end.

Best regards

[PetrM]

Hello,

Maybe I misunderstood the question but you can define VM processing order in this step of job configuration wizard. Isn't it what you're seeking for?

Thanks!

[Refruit]

Hello,

we are not adding every VM sone by one as we do not know when the customers deploys new VMs. We are adding the root Resource Pool / Folder in its entirety.
So in the processing order we only have 1 object (the Folder) and no vms themselfes.

[PetrM]

Ok, the request is noted but I cannot give any ETA as it depends on many different factors like for example the number of similar requests, priorities of other requests etc.

Thanks!

[Refruit]

Thank you very much!

[EWMarco]

I'd like to vehemently +1 this request.

I cannot tell you how much we're sweating when we have to retry a VM that is several TB in size and very active during production hours.