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.

The XOSTOR SR will continue to operate even if the XOA is down, removed, etc.

@carloum70 You're welcome! It's always best to test using the latest source to avoid reporting an issue that has already been fixed.

@carloum70 What is your current commit? Can you show us the complete error log (check under Settings > Logs)?

The bash prompt may be displaying the incorrect time due to these lines in /etc/bash.bashrc --

# Default user timezone is EST
if [ -z "$TZ" ]
then
  export TZ=EST
fi

Are you getting the expected result if you comment out this section of code and then reboot?

@DustinB Could be. Adding more RAM to dom0 can be done if needed.

@DustinB said in Alarms in XO:

The issue is host hst150 in pool HST150 is using more than 95% of the available memory

Isn't this related to the dom0 memory, not the host's total memory?

@bikemuch As mentioned previously, you don't need a CentOS 10 template in order to deploy a VM with this newer version of CentOS. It will work just fine using a template from an earlier version of CentOS.

There is actually a good bit more available in the hub as seen in the screenshot below. You may need to register the appliance in order to access this feature.

@bikemuch Those base templates don't yet exist. You will be fine using the closest available template (ie: Centos 9 / Debian 12).

FYI, there is a cloud-init enabled Debian 13 template available in XOA's Hub.

Have you checked under Settings > Logs to see if there is any relevant information there? You could also check the XO logs by issuing journalctl -u xo-server -f -n 50 from the CLI.

There is some information available in the docs -- https://docs.xen-orchestra.com/backups#restore-a-backup

A new VM is created when you restore a VM from backup. The log entry should have a link that you can click to go directly to the new VM unless you have already deleted it, which is when the "VM not found!" message will appear.