restore metadata for pool -> incompatible version
-
@payback007 Have you tried restoring the metadata prior to installing patches on the host?
-
@danp Restoring with installation from latest .iso the error was different. Don't remember the exact failures, but there was a statement about "missing columns". Searching the forum brought me to your post in 06/2024 to apply all the available patches. Patched then with "yum" and 155 packages were updated. Then the new failure with "restore incompatible version" came up. Due to missing XO capability that moment, I did the update using command line, maybe that's the failure?
-
My understanding is that you can only restore metadata to the exact same version of xapi. Does your old pool still exist?
-
No the old pool is fully gone. There was a risk for compromised network incl. hypervisor password. So the pool is destroyed. VMs are still available or available by backup. Need to access some of them without network to backup so data and to re-install win11-VMs without new activation. For the win11-VMs I need all the settings/data not only the VHD disk file.
And possibility to upgrade to different xcp-ng-versions for restore? At the moment the hypervisor is at latest 8.3 .iso -> so at least I think I Need to update to the latest version before 09/12/2025.
-
@Danp said in restore metadata for pool -> incompatible version:
My understanding is that you can only restore metadata to the exact same version of xapi. Does your old pool still exist?
This is quite the limitation. Is it documented?
-
Let me ping @team-xapi-network
-
So just for my understanding. For restoring a metadata backup or maybe also other backups I need the correct XAPI version, but a XCP-ng user is not able to select/control the needed version? Sounds lika a chicken-egg-problem…
Is it not possible to have a new .iso-Image, whenever such updates are provided? It would be an easy way on case of new Installation.
-
If you look at the metadata files on the backup remote, you should see two files: data and metadata.json.
Search either of these for the term "xapi_build", and that should let you know the version of xapi that was active when the backup was made. With this additional information, it should be possible to calculate which updates to apply to your host.
-
Ok, found the value, „xapi_build: 25.27.0“
How can I upgrade to this special version?
-
*** Warning ***This process and the attached file is only appropriate for restoring towards XAPI 25.27.0. Use this procedure at your own risk.
We recently put together a solution for a customer that had this exact issue. Below are the basic instructions to update freshly installed 8.3 hosts to the set of updates that were available on October 24th, including XAPI 25.27.0 --
- Install XCP-ng 8.3.0 LTS
- scp the attached
package_list_for_update.txtto the hosts /root. This file contains package versions from our update repository on October 24th. - then, on the hosts, from /root:
cat package_list_for_update.txt | xargs yum update-to -y- This will output a lot of messages saying that this or that package is not found. That's expected. Then it will proceed to install the updates. In my tests, 73 of them.
- Once the update completes, reboot the host.
- Restore the XAPI metadata
- Restart XAPI
- Verify that XAPI is running.
- Install the remaining updates with
yum update -y. - Reboot
