@CJ Currently I do not see any bottleneck with disk and network IOPS as far as XOA and the remote destination are concerned. I'll look into a network share for the VMs if I notice that is becoming a bottleneck.

@CJ That's exactly what I'm doing now. Backup takes 8 hours with no concurrency, 4 hours with concurrency set to 4 and 3 hours with concurrency set to 6. The backups are full in order to align with some SLAs. I'll share more updates as my tests progress.

@CJ Thanks for your response, I'm not backing up with memory and I do not have any bottleneck with XO even when concurrency is set to 6. I thought there is a setting I'm not aware of that could make backup run more efficiently by focusing on VMs from different pools.

Hi everyone, I have XOA connected to 6 pools with a total of 24 VMs. I set backup concurrency to 4 and thought it would pick VMs from different pools but it doesn't seem to be so.

In order to maximize resources, is there a way to prevent backing up 4 concurrent VMs from the same pool?