2 times the charm I have no idea why it failed initially, but at least you tested the magic rollback As you can see, it's really a GREAT feature

@michmoor0725 said in Only one back up wont restore: @manilx Thank you for the link. The fix in that thread worked. tldr. Problem with the ronivay self compiled code. Reverting to old commits fixed issue. Will be watching for a fix. This is a known issue that is in-progress, the issue isn't with the installation script you chose, but with XO Source specifically. Error: self-signed certificate This is something like the 15 topic here on the forums.

@flakpyro said in File restore error on LVMs: @john-c Do you know what would cause them to change? I am testing a restore from last nights backup so i assume the UUIDs have not changed. I could do a full restore from last nights backup however and compare to be sure. Do the restore then compare to check, to see whether they have changed. If you have done any of the following or if XOA has done any of the following when performing the requested functions, it would cause the UUID for LVMs to change:- Create a new LVM Edit Metadata Directly Delete and recreate Change Filesystem UUID Change the member disk's location address - virtual bus connecting virtual disk Also if the actions in XOA or XCP-ng affect the member disk's address visible inside of the VM then this would affect the metadata. @florent Your employer did that new Debian 12 based XOA since 2021 are the packages for lvm2 and any relevant NodeJS NPM ones included in the appliance?

@Hannes_5253 No, my mistake.... I think it was this post. (off buy a digit... 8117 vs 8177)

No problem! Did you manage to do what you need?