@Pilow @acebmxer Thanx for your replies. And sorry, i havent seen your first reply between my last posts with the link to your existing Thread. So, i think this is some kind of a bigger thing. Will handle with care, but i have to leave for today. Maybe i have time to test the snapshot and revert workarounds on the weekend. But these are all production VMs. Have to coordinate. I have 2 NFS-SRs in the Pool. Will try to migrate VMs from one to the other and see if this helps. Kind Regards and thx again Alex

@poddingue there is a notion of appliance too (group of VMs) https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands where you can start/stop a group of VMs, never tried it, doesn't seem to have a boot order in the vAPP neither

@poddingue Thanks for your input. Yes I'm aware that basically everything on the VM is incorporated into the snapshot. Including settings and metadata. This is acctually why I was surprised that the creation date wasn't preserved as part of that metadata. And as you say, if one uses that metric to track VM history. Then it can, and will, throw you off. I'll gladly submit this as a feature request. But my gut feeling is that it is more akin to a bug than missing feature per se. Thanks!

@pkgw I tested it with a cluster size of 2 megabytes. I got similar results to those with the default size.