@irtaza9 Why iDRAC and XCP-ng Backups Are Slow (I hope this is helpful, assuming I understand your topology and configuration correctly): • iDRAC Virtual Media / HTML5 Limits: iDRAC virtual media or browser-based streaming sessions are heavily throttled by encryption overhead and are not designed for bulk high-speed data exports. Furthermore, if the iDRAC dedicated network port is negotiated at 100 Mbps instead of 1 Gbps (check for an orange link light), transfer speeds will crawl. • Xen Orchestra (XOA) / XAPI Bottlenecks: XCP-ng exports VM data through the XAPI stack by generating compressed .xva streams or full backups, which can heavily tax CPU cores on the XOA/dom0 appliance and cap throughput around 50–80 MiB/s even on fast networks. So, check with top or xentop what your dom0 load is when you have an active backup to see if the CPU and/ or memory are overburdened. • CPU Starvation on XOA: Backup worker processes (backupWorker.mjs) can saturate available vCPUs on the Xen Orchestra appliance if it is only allocated 2 vCPUs. Again, check with top or xentop whetgher your vCPUS are saturated.

@zorro I would advise not backing up the same vms with both XO and veeam. One or the other. No did not see the update yet. I will look and check. Edit - thanks or pointing out the new version. I was still on 13.1.0.411. Downloading update now.

For some reason, we have the same issue (missing disks / snapshot-of) on our environment. (XO from source commit a5077) This is a major issue for us. We use Terraform to manage our VMs, and the missing VDIs are causing Terraform to fail. As a result, we are currently unable to manage our VMs using Terraform. ➜ dacsvm-db02 git:(main) tofu plan -var-file="dacsvm-db02.tfvars" module.vm.xenorchestra_vm.vm: Refreshing state... [id=e36fcd8a-b88c-42f7-6d61-2aa639f63b4a] Planning failed. OpenTofu encountered an error while generating this plan. ╷ │ Error: Could not find client.VDI with query: {VDIId:cad7d739-35c2-4585-9991-4c2f3fc6531c SrId: NameLabel: NameDescription: Size:0 VBDs:[] Parent: PoolId: Tags:[]} │ │ with module.vm.xenorchestra_vm.vm, │ on ../modules/vm/main.tf line 16, in resource "xenorchestra_vm" "vm": │ 16: resource "xenorchestra_vm" "vm" { │ ╵

@Velocity1192 If you can wait a little, we are atively working on the new XO6 backup job uI, that will come with some changes : one schedule per job, but with conditionnal actions You will run an incremental job, and will be able to define that the schedule of sunday is a full,and even run a healthcheck on it The ETA is on 6.11 ( next month release )