its still there ie the host is still atached to that vdi im thinking this is the issue why my backups wont run anymore if not i will do it on the xen server cli, but it would be nice to know why this isnt working

Indeed, also we reported the problem to Citrix, they might provide a fix one way or another.

server has 10G DAC to dedicated 10G SW, Disk its writing to is a NAS iSCSI Target with a single 10GBe NIC. Network Traffic is low under 30Mb/s  png) first peek is memory read.

This may be related to https://github.com/xcp-ng/xcp/issues/282 My guess is that the tools ISO was mounted into the XO VM, then updates were applied to the host that contained an update of the tools ISO, which led to the XO VM having an non-existing tools ISO still mounted. I have made a change in 8.1 to avoid that (eject all tools ISOs after updating the ISO, not just from shutdown VMs), and testing will tell us whether that's a good solution. To solve the situation, you usually just need to eject the ISO with xe vm-cd-eject, not xe vm-cd-remove, as @tuxen said. If you had a snapshot of the VM before removing the CD drive, I think restoring it should bring the CD drive back and then you can eject the CD with xe vm-cd-eject... Unless restoring the snapshot also fails. Else as tuxen said you need to recreate a CD/DVD device and attach it to the VM. iw0der created this issue in xcp-ng/xcp open This operation cannot be performed because the specified virtual disk could not be found #282

OK, seems I wasn't trying hard enough. I was trying to mount the tools under the iso list, but when I look further down the list to xc-ng Tools it turns out I can mount the tools from there as long as I do it manually (mount /dev/sr0 /media/blahblah). Installed now, all good.

@gskger said in XCP-ng Center: Future: @borzel: I second that! From time to time, I try to move over to XOA, but I always keep coming back to XCP-ng Center. XCP-ng Center supports my administrative tasks in a straight forward way (at least apart from backups ) and gives me all the information I need. Thank's for doing a great job! Same here. XO is good but doesn't give you the same sort of overview that you get from xcp-ng center. Everything is somewhat hidden away under its on set of sub menus.

Because there's a ton of dependencies, and we try to decouple things, this work takes time. We should be able to run on a more recent version of Node soon, and when it will be the case, our doc will be updated accordingly. That's exactly why we can't support 3rd party installers. Our doc might change and during the interval, if the 3rd party installer isn't following, then it will break.

It's just a missing info in a config file of the appliance. Not a big deal, just surprising to see that now, despite the fact it was there before.

If you create two separated jobs. One for the CR and one for the Rolling snapshot they will not interfere.

I deployed using bash -c "$(curl -s http://xoa.io/deploy)" Only today - worked fine.

Looks very good to me, thanks!

We're seeing the same kind of development on two servers. Nothing interesting in dmesg or so. Will have to resize for now I guess.

HA-Lizards a little rough around the edges, but it gets the job done at the end of the day. But it will be nice to have those features just built in.

It's pretty simple: just replace "xva" in the image by VHD and that's it. Otherwise it's explained https://xen-orchestra.com/docs/delta_backups.html If you still have questions, let me know

For the moment I've had to create several backup jobs instead of one big backup it's e.g. servers01-06, 07-12, 13-18. Which isn't ideal as it's harder to manage, but is what it is!

@akurzawa xo-server is not explicitly multi-processed, but it uses async IO calls in Node which should lead to multi-threaded operations. Anyway, we are currently working on reimplementing backups for the proxy and it will eventually lead to using multiple processes. These changes will at the end be merged back to xo-server as well.

Yes, I would try that

So please open a support ticket, that would be easier to assist

@olivierlambert Thanks again for the reply. I’m looking into it more. I think I need to add the storage directly to the VM running XO. I was trying to use a drive connected to a drive on my local network. Though it says it can talk to the drive, it does not reach it. I’m trying now to add an NFS to the XO server.

I've been spending some time on it for the last few nights, and my skills are improving little by little. I think Ubuntu desktop was the closest I got to functional, there is a custom image for the Rpi3b+ that I found and it was one of the attempts that got to trying to start the XO-server service and failed. I was never able to get the xo-server to start manually either and the log files didn't give me anything I understood. One of the versions that worked the least was CentOS 7 for RPi, node.js is not available for it in the normal repos. I have more experience with CentOS from a few years ago and more comfortable with it, may have to look into compiling all the dependencies from source to see if I can make it work. I think an RPi 4b with 2gb or 4gb of RAM might be a better choice, but I have the 3b+.