Danp

Danp

Restart the toolstack on each server.

Danp

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

Danp

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

Danp

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.

Danp

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

Danp

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.

Danp

@JoyceBabu They are now available at https://www.xenserver.com/downloads

Danp

IIUC, the Smart Reboot option found on the host's Advanced tab does what you are asking.

Danp

@jr-m4 Yes, it seems that all dropdown lists are broken by a recent dependency update. XO team has been notified.

Danp

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

Danp

It's possible that the issue lies within VMware Workstation.

Danp

Have you attempted to analyze the exported file using qemu-img?
For example:

qemu-img info file.vmdk
qemu-img check file.vmdk

Danp

Ah... ok. I think I originally checked the VM export.

This could be a bug. Does it occur with all VDIs? What happens if you try to import the file back into XO?

Danp

@abudef What steps are you performing to export the VDI as a VMDK?

Danp

@jcdick1 Ideally you should open a ticket via the Support Portal and provide the tunnel ID there along with a link to this discussion.

Danp

@jcdick1 We can take a look using the support tunnel of your XOA instance.

Danp

Have you check the status of the nodes and for faulty resources?

linstor n l
linstor r l --faulty

Danp

Please switch back to the Stable release channel and then let us know if the issue goes away.

Details for switching release channels can be found here -- https://help.vates.tech/help/en-us/30-versions-and-updates/21-xoa-versions

Danp

If you are running XOA, not XO from sources, then we could take a look remotely using the support tunnel.

Otherwise, make sure that you have patched and rebooted each pool member.

Danp

Check the output of dmesg -T|grep -Eiv 'guest|capacity|promiscuous' on the host. It's likely that there was a network disconnect at some point and you have a stuck mount. You could also check to see if df -h hangs when you execute it on the host.

Danp

@Danp