Indeed, you are right and it's about to be fixed very soon. Thanks!

@rtjdamen I was in the same situation I made a new schedule, BCK-Man with a tag BCK-Man. When I needed a manual backup, I added the tag to that VM

@Danp how can u resolve from this?

Hi, Can you describe the target/objective you want to achieve/expect?

@DustinB thanks all, the agent based backups seem to work the way we need, we removed the older alike backup appliances so fully on xoa backup now. I saw alike is going opensource but almost no activity on the github account, i expect that the product will discontinue as it is allready pretty outdated, nice chance for XOA to fill the gap.

I would like to ask a followup question to confirm. so IF using sequences, we should disable the backup tasks on the overview tab?

@olivierlambert nope not at all. i have a feeling that it's not the disks but more like the overhead on cpu of that boxes. V3 is more lightweight.

So far this seems to work well. we will test this and inform if there is any issue with it. On behalf of my customer i would like to thank you for the quick response!

@ph7 thanks guys!

@rtjdamen NBD scales relatively well, yes.

@julien-f maybe there can we some recoverypoint endpoint? or remotes?

In the end it turned out the license was bound to the network card, we needed to recreate it with the original mac and the license server started again! Case closed!

Documented at https://xen-orchestra.com/docs/xoa.html#other-interfaces

A good specification is always better to do things correctly (and to estimate the work needed)

@olivierlambert We observed that a VM with higher memory usage on XenServer reacts more slowly compared to VMware. This might be related to the different functioning of XenServer tools. We resized the VMs where customers had complained, and this led to significant improvements. Additionally, we adjusted the VGA switch. While it's unclear if this had a major impact, after increasing the memory and setting the switch, we received positive feedback from the previously dissatisfied customers.

Okay then try CPU cap at 400