Topics created by Zevgeny

@olivierlambert The update has fixed it, thanks!

@Zevgeny

For a few snapshots it's fine - the issue comes when you have large numbers. Most of my first-hand experience with this specific issue comes from Hyper-V but the logic applies here.

This is from VMware but the concept is the same and has some good reading on snapshots in general.

Running a virtual machine on a snapshot for extended periods of time can cause instability and data loss.
https://kb.vmware.com/s/article/1015180

The underlying issue stems from the nature of snapshots. With none you have a single VHD containing all of the data for the VM, once you take a snapshot a new delta VHD is created with all new data written going forward from the time of the snapshot. So, in order to have a complete VM you have the original VHD + the delta VHD.

This is fine in smaller numbers, but once you start having 10, 15, 20+ snapshots, every one of those represents an additional VHD in the chain. This results in performance degradation because you're reading from multiple potential files as only new data is written to the deltas.

This is actually from XO's blog: https://xen-orchestra.com/blog/xenserver-coalesce-detection-in-xen-orchestra/

@fohdeesha Great, thank you!

@zevgeny Hi, yes this can be easily done by just creating a new network as you described. VMs will be able to access anything in that network/subnet without extra configuration. If they ever need to talk to things outside of that network/subnet (like the internet), they would need a router to route the traffic between subnets

It's not that complicated: it's in a folder with the UUID of the backup job, then the VM is within it's UUID folder. That's it.

@zevgeny Hi,

You can export the config for your XOA in Settings > Config > Export and import it on your new XOA

This need to be groomed first. But we are pretty tight this month. Ping @marcungeschikts

Hello @Zevgeny .
Finally, we won't be able to display if the vm has changed since the snapshot.

@jaayb Amazing, TYSM!

@olivierlambert Ok, thanks. I will create another topic for the display issue.

@olivierlambert having exactly the same issue as wcom939 reported.
What did you mean by "Can you try with xe command to see if you have the same error?" ? 🙂 Migrate using CLI? there are too many options:)

Hard to tell. If it happens again, try immediately to compare XO behavior with other clients to see if we can tell where is the problem 🙂