NBD setup - No such item
-
@Tristis-Oris it hae to let the encrypted traffic flow through the 10809 port. XO will connect directly to the hosts through NBD, not only to the master
-
@florent sounds pretty simple. Nothing at my network should block that traffic.
Anyway, if i got rejected packets at iptables - backup task try to connect NBD server. Then it can't do something, so i should get an error at XO, but it not happens.
-
No such item
task happens when host interface at statusnone
without IP. -
@olivierlambert i hope your vacation WAS good, be we are stuck a bit here
-
-
bump
-
-
once again i configured it on fresh, test cluster, and it working.
so it some problem with iptables on production. But it default, same 8.2.1 clean installation.
Both this hosts have only 1 connected link, so it both backup and management.
On prod i try empty default backup network, or NBD link network - no effect. So maybe it still going through managemnt link without NBD?aaaaand enabled NBD on Mng link - now it working. SO yes, it ignore specified backup link.
Or this option didn't work, because NBD now enabled only on Mng link, so it can't go through backup link. -
next weird thing.
i enabled NBD on all manage interfaces at all pools.
it working with CR backup, but shouldn't, at least because it no option to enable NBD.
it working with half of other delta backup tasks, but not for all. Main backup is still without nbd.
only idea, it probably because of 1 small pool with few vm, where i forget to enable NBD. so 1 VM without nbd, force it to work in usual mode?
-
@Tristis-Oris said in NBD setup - No such item:
next weird thing.
i enabled NBD on all manage interfaces at all pools.
it working with CR backup, but shouldn't, at least because it no option to enable NBD.
it working with half of other delta backup tasks, but not for all. Main backup is still without nbd.
only idea, it probably because of 1 small pool with few vm, where i forget to enable NBD. so 1 VM without nbd, force it to work in usual mode?
that is really puzzling. I don't forget this issue, but I don't have much idea of how to fix this
Did you add the preferNbd flag to the config files ?
-
@florent lets a brief summary.
nbd work only via management interface. If nbd enabled on any another interface and specified as pool backup interface, it don't work (the issue with blocked packets at iptables). That was a main reason of my problem.
For now i made it work at all my pools. Max single thread speed increased 80-90 > 140-150. At usual backup task (when daily delta very small) it show same 10-40Mb, because it done too fast. Average task time decreased fo about twice.
-
@Tristis-Oris said in NBD setup - No such item:
@florent lets a brief summary.
nbd work only via management interface. If nbd enabled on any another interface and specified as pool backup interface, it don't work (the issue with blocked packets at iptables). That was a main reason of my problem.
For now i made it work at all my pools. Max single thread speed increased 80-90 > 140-150. At usual backup task (when daily delta very small) it show same 10-40Mb, because it done too fast. Average task time decreased fo about twice.
That is really strange, but it is also useful. We'll try to see why , and update the doc accordingly
-
@florent also it works too good.
i don' used advanced mode for CR backup, so NBD is disabled for job.
but task is working with nbd)
-
that log appear again, without any actions from my side.