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.

According to the documentation, you only need xfsprogs.

Not for me. Maybe a peering issue with your ISP. Have you tried running a tracert?

@Prilly It is possible that this change came from the XS side. The following if from their Known Issues for CH 8.2 --

The backup and restore capability in xsconsole is temporarily not available. We are actively investigating a replacement solution. (CP-48776)

I don't view this as being sneaky or malicious on the part of Vates. Hopefully @stormi can shed some light on the subject.

@steff22 Yes, you can use the code button in the toolbar or you can manually enter the backtick characters.

@steff22 Please use the proper markdown codes when pasting big blocks of text, ie --

```
paste your text here
```

Hi,

This error is telling you that you don't have enough free space on the SR where the VDI currently reside.

Regards,
Dan

Check out the pending updates that were released earlier today.

@AlexQuorum You may want to try the command again, this time adding --force to it.

@AlexQuorum This can happen if xo-web hasn't had a commit since the last time you ran the build process. I believe that this has been discussed previously on the forum, so you may want to search for the prior discussions.

You can also try running the command yarn run turbo run build --filter xo-web to forcibly rebuild that particular module.

The documentation is outdated as they've switched to using chrony for the NTP client. If you have support, then I recommend opening a ticket so that we can investigate why your system times are off.