Want to compare insecure_nbd but doesn't seem to work (secure does)

olivierlambert

It's only relevant to compare secure vs secure or insecure vs insecure. @florent will guide you when he's around

sluflyer06

florent

hi,

in theory, the insecure nbd should work when adding the insecure_nbd flag to the purpose of the network . Have you got any error message in the xo logs ?

you can add in the xapiOptions part

preferNbd = true
nbdOptions.readAhead = 20 # default 10

also do you remote store disks as multiple blocks ?

regards

sluflyer06

@florent Yes to multiple blocks. I did see this in host>networks page.

I do (and did) have the preferNbd set.

florent

@sluflyer06 we did a rework on NBD, to be able to use it everywhere, paving the way for some nice features like retry on network error

but it may have an impact on block based backup. I will make a branch which should alleviate this today

florent

@sluflyer06 can you test the speed with this branch based on master https://github.com/vatesfr/xen-orchestra/pull/6840

The backup job must have only one remote , which must be block based, and without a continuous replication

Warning : this is not production ready, this branch is only to find where the potential gains are.

fbeauchamp opened this pull request in vatesfr/xen-orchestra

draft feat(@xen-orchestra/backups): use parallel reading whith NBD + blocks to only one remote #6840

sluflyer06

@florent How would I verify for testing if its insecure NBD or not? I switched to your branch and rebuilt, I see the same message about not allowed but dunno if that matters.

florent

@sluflyer06 For now , I get back to the first problem : NBD should be faster than xapi export ( or at least as fast)

now I 'm working on enabling insecure

edit : the not allowed is only to inform the user that it can't be set through XO, but it should be used for backup if present

sluflyer06

@florent like Oliver was telling me, to compare secure to secure, it is faster than https,.still curious if anyway to try insecure.

Also. Is there a way to update XO (from sources) without losing the config.yaml or just a minor inconvenience until NBD is fully rolled into XO? (I assume we'll get told when we don't have to run custom config for NBD whenever it's ready?)

florent

@sluflyer06 the warning on XO is to discourage the mass. But you can really try

you can make a config.toml file in ~/.config/xo-server/config.*.toml , it should be loaded , and won't be changed by an XO update . https://github.com/JsCommunity/app-conf