Enable NBD Backups for a network
lawrencesystems Ambassador 📣
I am running xo-server 5.109.0 & xo-web 5.111.0 and I have enabled NBD from the UI and verified that the parameter is showing on that network. This is the network on which XO is talking to XCP-NG .
xe network-param-list uuid=12eaf1ae-9596-723e-a534-4d5a101ec4b4
uuid ( RO) : 12eaf1ae-9596-723e-a534-4d5a101ec4b4 name-label ( RW): Dot3 name-description ( RW): VIF-uuids (SRO): 66e895eb-b52a-a370-37a4-4bd74f299be0; 345ff1c0-0ea2-44dd-6308-07eabd75f770; 36072018-1e8b-03ea-a675-94c7b540e0e2 PIF-uuids (SRO): cc5f027f-cdf4-1e17-f393-51bf450c6855 MTU ( RW): 1500 bridge ( RO): xenbr3 managed ( RO): true other-config (MRW): blobs ( RO): tags (SRW): default-locking-mode ( RW): unlocked purpose (SRW): nbd
I know I also have to be using the multiple data blocks on for the backup repository but I do have a few other questions:
- Because the NBD option is now in the XO UI do I still need to edit the XO config.toml file & restart XO to enable or is that automatic?
- Are there any firewall changes on the XCP-NG host or does this work over 443?
- Does it matter if XO is running in another pool?
- In the Xen Orchestra 5.76 Blog Post it was mentioned the "Lock" in the new "NBD" row which I see but is there some change I need to make?
olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑💼
Adding @florent in the loop (I'm at FOSDEM right now, so not really available)
You still need to enable it in config fr now. I hope we 'll be able to improve the ui to enable it on a per backup setting later
The nbd protocol use the 10809 port in TCP by default. XO only read from this port f the host.
The Nbd setting is used for the whole xo, regardeless of the pool
The lock have been replaced by a select, which is more self explanatory . I think the main control pint is to check if there is multiple NBD network for a VM, XO use the first one returned by the Xapi, and it may be , for example, a managemet network as opposed to a backup / high speed one