VAW 2.0 to VBR - Multiple Machines Same Name

[gatorheelz]

We have a couple of segregated environments (think prod/dev/test) in AWS that we'd like to use VAW2 to backup to our VBR. Each of the AWS environments has a set of servers that have common Windows computer/NETBIOS names. Unfortunately we do not have an option to rename the machines easily.

We have found that after installing VAW2, the second machine with the same name is not able verify the license after entering the server address and credentials. It eventually times out after a few minutes.

Are there any known workarounds for this issue?

[gatorheelz]

Just to add, we have attempted using a different agent account on the VBR as well as a different destination repository without success.

[Mike Resseler]

Hmmm,

I doubt this is going to be possible as we use the computer name in combination with something hardware based (can't remember anymore what it is) to identify.
Since you can't easily rename the machines, would it be an option to have 3 VBR instances? (They can be virtual, doesn't have to be all physical boxes). With Enterprise Manager you can manage those 3

[gatorheelz]

Issue might be unrelated to the computer name as when I installed VBR in a local instance and attempted to configure the VAW2 instances to connect to it, we still had an issue connecting.

Will contact support.

[Mike Resseler]

OK. You did gave the right people access to the repository? https://helpcenter.veeam.com/docs/agent ... tml?ver=20

[gatorheelz]

Yes, and we've tried a couple of combinations:
VAW2 Free to VBR, VAW2 Server to VBR, VAW1.5 to VBR, VAW2 to VCC.

None of these work. The VBR and VCC are in a different environment than primary, so the root issue is not the computer name as I initially suspected.

[gatorheelz]

We have 6 other VAW2 Server machines in the same environment (AWS) that do not have this license/connectivity issue.

[Mike Resseler]

Ok. (Well not OK but...) Do you already have a support number/ case?