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.

Click the person icon below the Sign Out option to access the settings for the currently logged in user.

You have to remove some entries from the pool parameters. The first step is to pull the pool's other_config parameter --

[17:31 xcp-slnqfzrh ~]# xe pool-param-get uuid=63b7154a-1a6c-8642-525e-c6abb0acxxx  param-name=other-config
xo:clientInfo:579c9820-a9fc-5ff0-0065-6eca7813677f: {"lastConnected":1770075085319,"networkInterfaces":{"enX0":[{"address":"192.168.1.123","netmask":"255.255.255.0","family":"IPv4","mac":"66:04:08:97:5e:e8","internal":false,"cidr":"192.168.1.123/24"},{"address":"fe80::6404:8ff:fe97:5ee8","netmask":"ffff:ffff:ffff:ffff::","family":"IPv6","mac":"66:04:08:97:5e:e8","internal":false,"cidr":"fe80::6404:8ff:fe97:5ee8/64","scopeid":2}]}}; auto_poweron: true; memory-ratio-hvm: 0.25; memory-ratio-pv: 0.25

Then you need to remove this entry using this syntax --

xe pool-param-remove uuid=<pool_uuid> param-name=other-config param-key=xo:clientInfo:<vm_uuid>

Having good backups of your VMs would be a smart choice before proceeding.

Installed yesterday on my R620; no issues experienced thus far.

@robertblissitt You can check /var/log/yum.log on the XCP-ng hosts to see when the updates were actually applied, but there isn't anything in a standard installation of XO / XCP-ng that would trigger an "automated" update of missing patches.

Yes, it should work correctly if you use fields. Also, I think uuid need to be lower case.

The details are here -- https://xcp-ng.org/forum/post/70075

Hi,

This is explained in this KB article -- https://help.vates.tech/kb/en-us/30/21

Regards,

Dan

@swaio Yes, I'm aware of the issue with that script ATM. I haven't decided on the best way to fix it. Perhaps display a warning instead of aborting the script.

Here are some steps that should allow you to successfully update using the existing script --

sudo n lts
curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | sudo bash 
sudo n 18
sudo systemctl restart xo-server.service 

HTH, Dan

Look under the configuration for the backup-reports plugin, which can be found under Settings > Plugins.