Best posts made by Danp

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

@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.

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

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

@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.

This sounds like the same issue discussed here. If you are using XOA (the prebuilt appliance), then you should either contact support for the fix or wait until the next release (tomorrow?) and then retest using the latest release channel.

@DCT said in Cannot Delete a VM Template through CLI or XE:

xe template-param-clear uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30 param-name=is-a-template

Try this instead --

xe template-param-set is-a-template=false uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30

Then try to access the VM in XO and disable the Protect from accidental deletion option. Hopefully you will be able to delete it once that's done.

@julien-f Technically, it is possible with post processing as I mentioned above. Here's an example using jq and awk --

 xo-cli --list-objects type=VM-snapshot | jq '.[]."$snapshot_of"' | sort | uniq -c | awk -F " " '{print "{\"uuid\":" $2 ",\"count\":" $1"}"}'| jq ' select( .count > 1)'

Output looks like this --

{
  "uuid": "07604606-e937-5147-2dac-c1b4280df234",
  "count": 2
}
{
  "uuid": "0f11c701-c5e5-b09b-4c5f-00cf38153783",
  "count": 2
}
{
  "uuid": "83139da5-48d5-33f6-79f9-79ea91a7163c",
  "count": 2
}
{
  "uuid": "fb4703e4-bfd6-47b8-3fd1-f1f52f9ed234",
  "count": 2
}
{
  "uuid": "ff8b29e3-4445-5b22-e475-450270f2a7f3",
  "count": 2
}

Note: I am not proficient with these linux utilities so there may be better ways to accomplish this.

There was a recent change that resulted in the launched module being renamed. You need to redo your service so that it loads ./dist/cli.mjs instead of ./bin/xo-server

You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.

You need a space between the URL and the user name.