Please, dear Veeam developers, finally get the Windows Agent Client and B&R CE to *resolve DNS* properly!!!
I've been using Veeam since version 2 and regularly struggle with one-third of new installations, running a Windows PC on a hard drive or as a VM with B&R when I specify a NAS or backup server as the storage destination.
I've been managing small networks for 30 years and know how to configure perfectly functioning DNS, including DHCP, with IPv4 and IPv6 (currently Windows Server 2019 Std). Ping, nslookup, dig, etc., work on the client and the B&R host system. Only this Veeam fails to find the host after a few seconds of trying (with and without FQDN) and annoys me with an error message that could easily have come from Microsoft ("missing workgroup"... in a domain, crazy!).
Sometimes entering the IP address of the storage host works, sometimes it works, but not for long.
I know hundreds of threads on the same topic, but NOW there's a working solution, because the DNS is OK.
Veeam is cool, but this is a huge disappointment!
PS:
- I'm also terrified of upgrading Veeam B&R 11 -> v12. I've had too many bad experiences!
- And the uninstallation is as messy as it gets. So many leftovers and dysfunctions!
- The client refuses to configure because it's supposedly managed by B&R. But it isn't!
... :-/
Too many featuritis?
Actually Using Veeam Agent for Win, latest download and Veeam B&R v11 with 5 (sic!) Clients.
Greetings - Axel from GER
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Jan 19, 2022 6:40 pm
- Full Name: Axel Frankenberg
- Contact:
-
- Product Manager
- Posts: 10797
- Liked: 2940 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam B&R + Windows Agent - Please implement functional DNS
Hi Axel,
If you are experiencing a technical issue, please provide a case number so we can discuss it with the QA/R&D teams to determine if any changes are needed.
Additionally, please note that using the Community Edition to provide services to customers is against our End User License Agreement (EULA – Chapter 2. Prohibited Use). Running more than one Community Edition deployment in your own datacenter is also not permitted.
Your statements suggest that you may be using the Community Edition to provide implementation services to customers:
Fabian
If you are experiencing a technical issue, please provide a case number so we can discuss it with the QA/R&D teams to determine if any changes are needed.
Additionally, please note that using the Community Edition to provide services to customers is against our End User License Agreement (EULA – Chapter 2. Prohibited Use). Running more than one Community Edition deployment in your own datacenter is also not permitted.
Your statements suggest that you may be using the Community Edition to provide implementation services to customers:
Please, dear Veeam developers, finally get the Windows Agent Client and B&R CE to *resolve DNS* properly!!!
Best regards,and regularly struggle with one-third of new installations
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 6 guests