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.

@anik I believe that you have some of the names backwards.

• XO Lite is available by default on XCP-ng 8.3. See the documentation for how to access it on XCP-ng 8.2.1.

• The newer XO 6 interface is accessible from XOA by using /v6. It may need to be explicitly enabled to use it on XO from sources.

@coolsport00 Export the VM as an OVA file, then import this on the XCP-ng side.

@webminster The XOA dev team will need to verify that everything still works correctly before Netbox 4.3 will be officially supported. As explained in the documentation, you can force it to attempt to work with newer versions by editing your xo-server configuration like so:

[netbox]
checkNetboxVersion = false

Note the warning from the documentation --

Please be aware that by doing this, a Netbox update might make XO delete some of your data in Netbox.

@ferrao Prior to the latest release, the trial worked without actually activating the license on the XOA > Licenses tab. Double check that the license is activated (should look like this) --

This is what it will look like if the license hasn't been activated --

@ferrao Make sure that you've activated the trial license under the XOA > Licenses tab.

Hi @ferrao,

This is with XOA Free, correct? Have you tried switching to the Stable release channel?

Dan

Hi,

I'm pretty sure this is planned to be addressed in XO6.

Dan

@ph7 @Lhoust

Thinking about this further, it may be that way for you because you are using XOA Free, which I think they reverted to v5.105.0 because of the upgrade issue.

With a trial license in place, I get 5.105 with the Stable channel and 5.106 with the Latest channel.

@Lhoust said in XOA fails after update to 5.106.0:

For me Today, 5.105 is still what is available on the latest channel...

Are you sure? Please try pressing Ctrl+F5 to force reload the page.

@Lhoust Thanks for the feedback. The developers will fix the issue with XOA Free ASAP.

Although switching the channel from latest to stable dropped XOA Free down to 5.105, XOA Free remained Expired License LOCKED. Yesterday Quick Deploy was Blocked, therefore I used the Source Code Version to restore my XOA Free 5.105 Backup, which worked normally.

What do you mean by blocked? Was the site down?

Today my Restored XOA Free 5.105 shows 5.105 is the "Current" Version, XOA 5.106.1 is NO longer available as an upgrade.

This is accurate if you are on the Stable release channel. v5.106.1 is still available on the Latest release channel.