VBR 13.1 virtual lab observations (managed linux servers without internet connectivity vs timeouts)

[BostjanUNIJA]

Hi. I Would just like to add my observations on my home lab preparation of testing all the new roles (probably this behavior is similiar in previous versions), but for test purpose (i am trying to test different scenarios of replicas with virtual appliance by adding two dedicated proxy; one on source and one on the destination, just to compare nbd and hot add). For proxy server role I have created a dedicated ubuntu 24.04 server. This server does not have connection to the internet, and when I am adding this linux server as a managed server on vbr 13.1 windows console takes 'ages' to add this server. With the help of a friend (aka AI) I have figured it out it's related to timeouts because the linux server doesn't have access to the internet and it's probably triggering apt get update commands until it timeouts. So it took about 6 minutes for adding each component (Veeam Data Mover Service 8 minuts, HpeStoreOnce 6 minutes...). At the end it lasted about 30minutes to add a simple linux ubuntu as a managed server with no internet connectivity.
I have repeated the scenario by installing additional linux ubuntu (this time by adding a 2nd nic, so I allowed access to the internet). This time adding server as managed server was finished in rought 1-2 minutes (luckily i have a good lab environment, nvme ssd, 128gb ram, a good cpu etc).

For future realeases excluding this timeout while adding dedicated managed servers (which will serve as proxy) would be grateful especially for those environments that have strict isolated networks. Luckily this is currently just a home lab, but in production environment I would be unhappy why it takes so long. You guys can probably replicate/test the exact same scenario that I did, and will probably get the same results. Keep up the good work guys! Intention is not to criticise but to share my observations...
#sharingiscarring

[Mildur]

Hi Bostjan,

Thanks for sharing. I'm aware that some of our timeouts could be reduced. I also reported some of them already during the first days of v13.0.

While it is true that we can test the same scenario, it would be really helpful for our R&D team to have a copy of your logs when you encounter any strange behavior during your testing.
Would you be able to submit a support case with your findings? Technical and performance issues should be investigated by our Customer Support team first, and they can then forward the case to R&D if required.

Thank you,
Fabian