Restore only showing 1 VM

[MathieuRA]

@Team-XO-Backend Someone can take a look at it? I won't be to much available this week

[acebmxer]

I posted in the original thread that this issue only exists in this test branch. When i switched back to master branch all restore points were visable.

Edit - Just updated to 875ce and now back to single vm listed for restore... Commit bfb0a05 did not have issue.

Edit 2 - Updated to a6c50 and restore points are back again.

[Bastien Nollet]

@MathieuRA

I'll have a look

[ph7]

@Bastien-Nollet
I don't know, played around with it a little bit, all seemed to work, so I updated to master a6c50 as @acebmxer did and it still seems OK, so maybe we can put this on hold for now and put the energy on something else

[Bastien Nollet]

@ph7 Ok, let's do this.

If it happens again, can you check that XO can still access your remote on which missing VM backups are stored? (by using button "test your remote" on page settings > remote)

It may just me a network issue.

[ph7]

@Bastien-Nollet
It's a 1Gbit 4xHDD NFS where usually I get ~ 600 Mbit

Just a test to see how it looks when it's OK

[Bastien Nollet]

@ph7 Ok, thanks.

But the most important will be to do this test while some VMs are missing from the backup restore page (if it happens again)

[ph7]

@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

[acebmxer]

@ph7

Well prior to installing the latest commit from today will was back working. Just updated to 28c5e and now back to 1 vm restore point again.

Not sure why these multiple issues keep popping up and going away just to pop back up again between releases.

I still have two open support tickets open waiting for responses for work. One about the recent 8.3 updates other about mirror backup broken.

[RianKellyIT]

The clue is in your own observation: re-enabling the disabled manual job made all VMs appear. The Backup Restore (V5) view likely filters its restore list based on which backup jobs are currently enabled, if a job is disabled, its associated VMs may not be indexed into the restore view even if backups from that job exist on the remote.

This is different from how the older restore view worked, where it would scan the remote and show everything regardless of job state. The V5 restore view appears to be building its list from job metadata rather than from a direct remote scan.

A few things worth verifying:

Check whether the one VM that does appear is covered by a currently-enabled job, and the others are only covered by disabled jobs. If that pattern holds consistently, that's the root cause and it's a V5 behavior change worth reporting to the XO team. In the XO UI, go to Backup → Jobs and check which jobs are enabled. If you temporarily enable all jobs, does the restore list show all VMs? And when you disable some again, does it immediately drop those VMs from the list?

If the behavior is confirmed, filing it against the backup v5 restore view filter logic would be useful, the restore UI should show all VMs that have restorable backups on the remote, regardless of whether the originating job is currently active or not.

Given you're on a test branch focused on reactivity fixes, this could also be a rendering/state issue where the component isn't re-fetching when job state changes, the list gets built once and doesn't update until you navigate away and back.