Veeam 8 Update 2 + Virtual Labs = No DNS?

[lightsout]

All,

I'm not sure when this started, but the behaviour I'm seeing is quite consistent. Our Sure Backups boot up fine, and ping, etc but nothing that is dependent on a domain controller (which has is also running in the virtual lab) works. Even trying to login using a domain account tells you there is no domain available, despite the domain controller being up and accepting logins via the console.

By logging in as local admin, I can see it has an IP from the virtual appliance. Howeverthe DNS servers which I have configured in the virtual lab, is missing, and I've got 3 IPv6 addresses instead. Using nslookup shows no DNS is working, and hence why I have all the problems.

Has anyone else seen this issue? It seems to be recent, so I am wondering if it started after I applied Update 2, or if some Microsoft patch has changed something!

Thanks!

[nefes]

Have you already opened support case?
Could you please clarify this quote:

Howeverthe DNS servers which I have configured in the virtual lab, is missing, and I've got 3 IPv6 addresses instead.

Do you have separate VM or VMs, which should serve as DNS server, or it is your DC? Am I correct that VM is correctly powered on in virtual lab, but haven't got IPv4 dhcp address?

[lightsout]

No case yet, but I wanted to be sure first.

1. Yes, the DNS should be set to a VM (domain controller) which is also running.
2. All of the servers are getting their IPs via DHCP from the virtual appliance.
3. But they're not getting DNS servers from DHCP, despite it being configured, from the virtual appliance. If I set it by hand, then everything works fine.

[marc.rousseau]

I'm able to reproduce your problem.
There's a typo in startup script "/etc/init.d/network/dhcp-daemons.sh" of veeam proxy appliance.

This script generate a config file for dhcp interface. For example : /etc/dhcpd.eth1

Code: Select all

start 10.32.6.1
end 10.32.6.254
interface eth1
pidfile /var/run/udhcpd.eth1.pid
lease_file /var/lib/misc/udhcpd.eth1.leases
option subnet 255.255.255.0
option router 10.32.6.254
option lease 1200
option dns /settings/dhcp_daemons/dhcpd[1]/nameservers/nameserver[1]
option dns /settings/dhcp_daemons/dhcpd[1]/nameservers/nameserver[2]

As you can see "option dns" lines are not properly formatted

To resolve that you can edit "/etc/init.d/network/dhcp-daemons.sh" script and replace line 59

Code: Select all

DNS=`xmlstarlet sel -t -v \"/settings/dhcp_daemons/dhcpd[$i]/nameservers/nameserver[$j]\" $CONFIG_FILE`

by

Code: Select all

DNS=`xmlstarlet sel -t -v "/settings/dhcp_daemons/dhcpd[$i]/nameservers/nameserver[$j]" $CONFIG_FILE`

Rebuild veeam proxy appliance ISO using procedure in this post : http://forums.veeam.com/veeam-backup-re ... 28064.html

... or wait for a fix

[foggy]

Thanks, Marc. This will be addressed in the next update.

[lightsout]

Great, I was going to put a ticket in, but I guess no need now.

Do we have any sort of ETA on the update? Gostev mentioned a Update 2a as a possibility?

[foggy]

Chances are this will be included in Update 2a.

[Tim783]

Hi, I am going to be upgrading to update 2 within the next few days, but need to make use of the virtual lab feature.

Can I just make a copy of the current iso's
Upgrade
rename the new iso's and replace with the old

Do you think this will work?

Thanks

[Gostev]

No, this will not work. The reason for this bug is that the appliance have had a major remake in U2 to support new functionality, so the updated product code is simply not compatible with the old appliance any longer. Thanks!

[Tim783]

ok thanks Gostev, just thought I would check.

Could you give me an idea as to when update 2a might be released?

Cheers

[Gostev]

When it's ready™
But Soon™

[lightsout]

Our initial tests of Update 2a still show the problem. Can you confirm if it was in the update or not?

[foggy]

The fix for the issue discussed above was included in the Update2a, so please open a case if you still experience it.

[lightsout]

Ok, it has been fixed. We applied the patch but didn't update the VL image, once this was done, it worked.