Restart the toolstack on each server.

You should be able to delete the snapshots without causing any harm. A couple of things to keep in mind --

• If the snapshot is associated with an existing backup job, then the next run of that job will result in a full backup instead of a delta

• It may take some time for the snapshots to coalesce following deletion, so this could still affect your backups until they are completely removed

• If you want to delete the backups associated with the old job, then you can from the Backup > Health tab in XO

It is also possible to perform this activity from within XO as described here. There are some prerequisites for performing this action that you should review -- https://docs.xcp-ng.org/installation/requirements/#-pool-requirements

I would setup a Continuous Replication backup job to create a duplicate VM on the new storage repository. When you are ready to perform the cutover, shutdown the original VM, perform one final run of the CR job, and then start the new VM on the new pool.

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.

The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.

@JoyceBabu They are now available at https://www.xenserver.com/downloads

@jr-m4 Yes, it seems that all dropdown lists are broken by a recent dependency update. XO team has been notified.

@BrianDLC The error ""EACCES: permission denied" should have pointed you to a permissions error to begin with.

Since we have no knowledge of how that script operates, it often makes more sense to refer you to their repo for help rather than us guessing at the reason for the issue.

@Ascar I suspect that Olivier means to register with the XO instance using this syntax --

xo-cli register [--allowUnauthorized] [--expiresIn <duration>] [--otp <otp>] <XO-Server URL> <username> [<password>]

You can run xo-cli without any parameters to get the full usage text.

@MarcVdS The new ISO is already available. See this post for more details.

@DaleDibbadel said in Lost VMs disk after using new SR:

Brought in trunas, set a SR device: /dev/sda, rebooted Dell, now VMs wont start.

Please elaborate on the exact commands that you ran here. Also, you may want to provide the output from lsblk to provide some additional context.

Do you have a backup of your pool metadata?

*** 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.txt to 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

package_list_for_update.txt

Hi,

Can you show us the output from the following command?

xe vdi-param-list uuid=<uuid_of_target_vdi>

Dan

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.

My understanding is that you can only restore metadata to the exact same version of xapi. Does your old pool still exist?

@payback007 Have you tried restoring the metadata prior to installing patches on the host?

@john.c said in "NOT_SUPPORTED_DURING_UPGRADE()" error after yesterday's update:

Please be careful of tenses (past tense etc),

Yeah... I was trying to be helpful, but I was clearly in too much of a hurry.

Mea culpa

s/rebooting/rebooted

Apologies for the miswording on my end.

@archw I'm confused by your recent responses. I asked --

Were the hosts rebooting after the patches were applied?

to which you replied --

Nope!

but then you stated

I always reboot at the conclusion of the update and did as well this time.

Which is correct?