perhaps "in the context of a proceeding RPU, do not start halted VMs" ? or "boot only halted VMs that have HA enabled" ? but I can imagine corner cases where this is not wanted. some chicken & egg problem.

Hi @olivierlambert and @pilow Thank you for your answers, it helps a lot, Regards, Olivier

@Aleksander There are plenty of examples on this forum. We have used Nvidia T4, it works very well.

@florent We have allways been a veeam customer since vwmare. I have moved over to the beta version of veeam for our windows servers. XOA is only backing up our linux servers. So half the workload was removed from backups.

@flakpyro that's a good news ( but at least another user saw this) we are currently testing the branch ensuring that at least the fix don't create other issues

Hi, thanks for the heads-up, we will see about doing some comparison with the backups refactoring on our dev environment to check if we lost some speed and try to fix it if so. Very happy to hear that the issue is mostly resolved. We will patch this ASAP.

@anthoinebThe problem still persists; when can we expect it to be resolved?

@Mark-C this is not forgotten, but file level restore has been under priorised, so it didn't get much work it is now quite high on our backlog , so expect good news in the next months

@tsukraw No worries! Just glad that we can all help each other out!

@pilow @majorp93 Hi, we've detected a memory leak at the REST API level. We pushed a fix on the branch: mra-fix-rest-memory-leak Can you test the branch?

@TechGrips Sorry, there is no quick test to be sure the VM is not corrupted. The usual way would be to make a healthcheck. We cannot be sure everything is ok as it concerns multiple tar linked to each other. If it keeps warning you on the same backups, it may be due to a faulty parent. You would need for this to create a new chain of snapshot

@McHenry 19 VMs is 19 Chains of 16 VDIs at each hourly run, a new snapshot is created (some minutes) and the oldest one is merged/garbage collected in the first snap (time undetermined) I guess 19 merge + chain garbage collected seems to not be able to be done in the one hour timeframe before next CR is done you possibly have a chain growing can you check in DASHBOARD/HEALTH the unhealthy VDI section at 11 am ?