@rzr
Seems to be OK
ran a few backups and installed a new VM
XO-lite was already on 0.21.0 (13f98) after the update 2 weeks ago.. Don't know if it's the same.

Ran the 2 updates released today and...
Back to only showing one VM in Backup/Restore as it did a month or 2 ago.
Ran the replication job and all VMs showed up in Backup/Restore again. (XO5)

[17:00 30] xoa@xoa:~$ sudo journalctl -u xo-server -f
Apr 30 16:23:13 xoa xo-server[569]: 2026-04-30T14:23:13.264Z xo:main INFO Setting up / → /usr/local/lib/node_modules/@xen-orchestra/web/dist
Apr 30 16:26:27 xoa xo-server[569]: 2026-04-30T14:26:27.942Z xo:rest-api:error-handler INFO [GET] /users/370331c9-fe77-49db-b2a0-e38f776607bd (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.549Z xo:rest-api:error-handler INFO [GET] /pools (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.555Z xo:rest-api:error-handler INFO [GET] /hosts (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.563Z xo:rest-api:error-handler INFO [GET] /vms (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.627Z xo:rest-api:error-handler INFO [GET] /tasks (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /alarms (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /vdis (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /srs (403)

My is XOA

@Baronvaile
Started my 6.4.0 test VM and got the same

@Baronvaile
Have You tested wit CTRL-F5 to update Your browser

just found out that it's the same on XO5

I removed 1 host from the pool and the local storage from that host didn't get purged

Tested but not much
Seems fine so far

@florent
I get the same result as @pilow
I'm not logged in if that has anything to do with it

@Bastien-Nollet
I'm running c1e5f btw

It's been working for 5 days, but today I saw only 1 backup/restore again.
Then a CR-job ran and I can see all of the backup/restore again

After the work You put in fixing
https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm/18

It seems like VDI-size in VMs VDIS is back to showing size of snapshot instead of size of VM.

Still working fine
But after this work You put in it seems like VDI-size in VMs VDIS is back to showing size of snapshot instead of size of VM.
I'l update the XO6 thread
https://xcp-ng.org/forum/topic/11604/xo-6-dedicated-thread-for-all-your-feedback/169

On 28c5e
I today had it switched from all to none 2 times.
Then it stayed at showing none
The remote seemed to be OK
I updated to 372a2 and at the moment it's showing all
Time will tell

@MathieuRA said:

Hi, regarding your backups which do not appear on the XO5 restore page, I suggest you to open a new topic

Forgot to include the link to the new topic
https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm

Thank's for Your input but I get a feeling You're using AI, right?
Unfortunately I didn't say in the beginning of this thread that it has it's origin in
https://xcp-ng.org/forum/topic/12031/backup-info-under-vm-tab-in-v6-never-loads...
@acebmxer and I have experienced this behavior in several test and master branches

@RianKellyIT said:

re-enabling the disabled manual job made all VMs appear.

Yes, for a couple of minutes, then they disappeared again and come back randomly.
there is no consistency in the appear / disappear. Sometimes You se all, sometimes 1 and sometimes none.
There where no VMs in that manual job, it was disabled because not in use.

All jobs are enabled in backup overview or sequences as stated above

@Pilow said:

@ph7 try to put RETENTION to 1 in the schedule, as you are using LTR parameters

I was running the shedule with 20 mins backup retention and it is running fine together with the LTR
And here is the manual I ran at 14:56 removed

@Bastien-Nollet said:

It may just me a network issue.

You may have a point there
My backup server is not at the same place as the host
and there may have been some other "heavy" traffic on anoter VLAN in that trunk between the switches.
@acebmxer How is it at Your place

And I was able to restore from 15:05 backup
edit: bad spelling