@Bastien-Nollet
I have tested it since the 05c6f release and it seems to work fine

@Bastien-Nollet
I have tested it since the 05c6f release and it seems to work fine

@Chico008
Use a file manager outside of XO, it will keep the name of the iso
@sir_alex_leo
I don't know but are they of the same type ??
Total Width: 128 bits Data Width: 64 bits
Total Width: 64 bits Data Width: 64 bits
@Forza
I started experimenting with this function in dec -24 and have run it in "production" in my homelab since jan -25
I suggest You keep the Backup retension (52) to 1.
this is my setup

Sequence

Schedules

And this is the result from one of my VMs


As You can see all the backups from jan - apr and most of may are removed
I am waiting to see what will happen when we go into 2026, If I remember correctly,there was some bug at 2024 -> 2025 but hopefully I get my first yearly backup
@lsouai-vates
No worries, I just wanted to report, I'm not using it, just testing 
Xen Orchestra, commit 2dd45 from docs
This is similar to the problem from this thread
https://xcp-ng.org/forum/topic/11227/boot-new-vm-to-iso-in-xo-lite?_=1762071345524
When creating a new VM from v6 with Debian Trixie 13 template.
I can't find any where to disable secure boot and the VM won't start
And I also get this:
The topology is "greyed out"

and no default network

In XO-Lite all is fine. Aren't they using the same code?
@McHenry
Use the builtin function, just press Rolling pool update when there is updates available.
Home/Pools/"Ryssen#

The rest is automatic or should I say, magic 
The new template for debian 13 is working in XO-Lite 
@mx234
I'm running netbird with an exit node and I get access to my LAN.
Everything works great
@rk9268vc
I got no info for You, but is the host updated?

I also take this opportunity to call for more feedback on the previous batch of updates,
Well I updated a few days ago, tough I dont run much of the updated functions on my simple home lab, it all seems to work fine.
i7 gen 4 and NFS
Now testing the new updates......
@McHenry
Check Your performance plugin settings
I don't remember if 0,95 triggerlevel is 95% or 0,95%
@McHenry
You can try to schedule a rolling pool update.
Since I'm not used to using git, I was running a few tests on my "test" host.
I had made a change in my "one line commando"
My memory is not in best shape so I forgot the change and ran it in my update.
Now It's sorted out and ran a new update and voila
@olivierlambert
As usual, I'm an Idiot
No need to involve @lsouai-vates
I am checking what went wrong and report back
@olivierlambert
I'l report tomorrow after next backup tonight
I now see that I also got a errormessage around the time I updated:
Unable to get the true granularity: 60
vm.stats
{
"id": "46bfadff-6002-299e-506a-abbf9a9aa8a8"
}
{
"message": "Unable to get the true granularity: 60",
"name": "FaultyGranularity",
"stack": "FaultyGranularity: Unable to get the true granularity: 60
at XapiStats._getAndUpdateStats (file:///root/xen-orchestra/packages/xo-server/src/xapi-stats.mjs:396:13)
at runNextTicks (node:internal/process/task_queues:65:5)
at processImmediate (node:internal/timers:453:9)
at process.callbackTrampoline (node:internal/async_hooks:130:17)
at Task.runInside (/root/xen-orchestra/@vates/task/index.js:175:22)
at Task.run (/root/xen-orchestra/@vates/task/index.js:159:20)
at Api.#callApiMethod (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}