@olivierlambert Haha, it's so obvious! Didn't even think to select both at the same time. Genious, thanks.

Thanks for the response I got it working
John

@thorcraftit seems like perhaps a permissions error, what does your share properties on truenas look like for this host? Is the allowed IP or denied IP boxes populated at all? Attach a screenshot if you can. Here's what mine looks like:

f76ebeef-c5cf-452e-8a43-28144d9a8c94-image.png

Note that the mapall user and group must have permissions on the shared folder, I typically create a user on the freenas system just for xen shares, and give it ownership of the folder/dataset that's being shared. this ensures you don't have any weird permissions issues. I think in your case the key boxes to examine are the authorized networks however.

What does your Services > NFS > Settings look like? here's mine:

3ccf191c-575c-4094-b91f-b4e12e6a4091-image.png

Lastly and perhaps most importantly, can you run "yum install nmap" and then "nmap 172.16.60.200" on both a working host, and then this non-working host? Paste the results of both here - if they differ, for instance if the non-working server doesn't see any RPC services running like I suspect, that will heavily point towards a firewall/network/ACL issue

@cfm56 The error was probably due to https://github.com/vatesfr/xen-orchestra/issues/5836

This did not impact the import of the config though, anyway it should be fixed now 🙂

trader418 created this issue in vatesfr/xen-orchestra closed Config restore error #5836

But what about merging delta backup? This require write access.

Except if we completely "move" the merge logic in the storage itself (which will be possible in few months)

That's because of XCP-ng/XenServer design. The host isn't pushing data, it's only exposing an HTTP handler to pull from it.

You can use XO Proxies if you prefer: https://xen-orchestra.com/docs/proxy.html

@darkbeldin Thank you. That was just off the bottom of the screen and I did scroll past it a few times, but being a little lonely icon, when all the other items have text, it didn't even register as a thing!

@pdonias @olivierlambert hey thanks for adding this in latest release!!

45658591-208e-46f6-b3af-74144019b94e-CleanShot 2021-07-02 at 19.36.01@2x.png

@danp tnx

Questions for @julien-f I suppose 🙂

Hi!

That's is possible, you just need to shutdown all VMs using disks in there.

Then, 4 steps:
0. Find the PBD currently connected to this SR via xe pbd-list

Save the PBD information somewhere (xe pbd-param-list uuid=<PBD UUID> Unplug and remove the PBD (xe pbd-unplug and xe pbd-destroy Recreate the PBD by just changing the information using xe pbd-create

In short, the PBD is like the "cable" between your host and your SR. Removing it won't remove any actual data, just the link between them. If you recreate it, and replug it, you'll find everything back 🙂

It doesn't work like Citrix patches. Xen Orchestra will send a XAPI command to the host, that will in fact do a yum update command. The result is returned to XO and it will display available updates.

We got a system using the best mirror for you: https://xcp-ng.org/docs/mirrors.html#original-mirror

@olivierlambert cool, thanks

Hi,

Please open a support ticket, that would be easier to assist 🙂 (you can also open a support tunnel so we can remotely access your XOA to investigate faster, see https://help.vates.fr/kb/en-us/9-xen-orchestra-appliance-xoa/16-create-a-support-tunnel )

edit: don't forget to go in XOA/Support then doing an XOA check, see https://help.vates.fr/kb/en-us/9-xen-orchestra-appliance-xoa/17-xoa-check

@black_sam Thanks for your feedback 🙂

@station-already hehe glad you got it figured out 🙂 Indeed, management interface changes are pretty "violent" in terms of how much they change and interrupt, so a reboot helps quite often - same for changing the virtual adapter/PIF assigned to a VM - alway a good idea to reboot the VM

@julien-f said in Backup failed with message "HTTP request has been canceled":

node -p 'require.resolve("xen-api")'

Hi all,

I think the problem is fixed now. thanks for your help

@danp after update, backup works fine, thanks

This means your NFS server doesn't support NFSv3.