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.

Hi,

XOSTOR on XCP-ng 8.2.1 has been supported since it was released approx 9 months ago. XOSTOR on XCP-ng 8.3 is still in the beta phase, so not officially supported.

Regards, Dan

@irtaza9 Can you elaborate on how you are making this API call? FWIW, vm.create is from the older JSON-RPC API, not the REST API.

Some of your numbers are confusing to me. For instance --

2x4GB mirrored HDD (hardware raid

I should have plenty of space, as my boot drive is 500MB and my overall default storage repository is 4GB.

The minimum disk size for installing XCP-ng is 46GB as shown here.

Can you show us the output of lsblk and df -h on your host?

Hi @PGibson,

Are you storing ISOs in a local directory on the XCP-ng host? This is one of the major causes for the host having storage issues, where the root partition becomes full due to these ISOs.

If that isn't the problem, the I suggest reviewing the logs to try to identify the cause -- https://docs.xcp-ng.org/troubleshooting/log-files/

Regards, Dan

@irtaza9 Not AFAIK.

VM creation is almost instantaneous for me, and I'm running on older hardware (E5-2680). How long does it typically take for VM creation on your end?

@al-indigo The fix is included in XOA 5.103.0, which was released last week.

https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.md

[Backup/LTR] Fix computation for the last week of the year (PR #8269)

@kagbasi-ngc Take a look at this KB article. Also see this prior thread -- https://xcp-ng.org/forum/topic/5902/permissions-for-users-to-be-able-to-snapshot

@Nevering Can't say that I've seen this behavior previously. Have you installed the available patches on this host and then rebooted it?

@rtjdamen The VDI has already been left in a paused state by tapdisk, which leads to the MAP_DUPLICATE_KEY when it tries to pause the disk the next time.