@edsilber Yeah I'm not really sure, I also assumed that cron (and XO would use the cron pattern for months). Clearly it doesn't.
Using AT on the CLI of your host/pool should work (I imagine). But yeah having a "Run Now" function in XO would be killer.
I've been have a re-occurring issue where my backups get stuck when attempting the transfer part of the health check. I'm using XO from sources. Currently on commit 54459, but this issue has persisted over multiple updates. It's not always the same VM(s) each time. The remote target is a TrueNAS box sharing via Samba. The health checks are set to transfer to a HDD directly on the host. I do have the time out option configured for 3 hours, but that seems to be being ignored at this point. I usually just restart the xo-server service and then retry the failed ones, but at this point I seem to have to do that after every backup.
Example:
[image: 1761779483775-c21d124c-3903-48a9-9e0e-8cfc5a3e36a0-image.png]
Hi!
The new standard way to import is here: https://xen-orchestra.com/#!/xoa
Let me know if you have any issue. It's still in beta yet, and we got one small issue to fix (it won't fetch the XO username/password, so it's still admin@admin.net / admin)
That's normal. If you boot the replicated VMs, then blocks will be changed. It mean no further delta replication will work on this VM. Force boot it if you lost the original VM and you don't care about delta toward the copy anymore. If you just want to test the VM without doing a new full (breaking the delta chain), boot with a copy. I think I explained that in this video: https://www.youtube.com/watch?v=FfUqIwT8KzI
That's a display glitch.
In case someone ran into the same problem here is how I solved it.
I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle.
I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now.
Thanks you everyone for your help.
Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected
