srch

If the hostname is changed for a machine with Veeam Backup & Replication installed the console may fail to open with an error, ...

19.07.2011 · VIX Error: Failed to resolve host Code: 30006

08.10.2021 · Select the VM and click Console. Open the console.vv file and log in to the VM console using credentials that you specified for Veeam Backup for RHV in Install Veeam Backup for Red Hat Virtualization. At the end of the text, add the IP address, FQDN and the hostname for the Veeam Backup & Replication server and the RHV host.

When trying to add the server on Veeam Backup, it lists all the hyper-v hosts, however it fails with the error "Failed to resolve host name ...

May 15, 2015 · Make sure that you can open the mentioned file share via regular windows explorer (for both host name and ip address set in the path). Additionally, please make sure that you've set the correct credentials in case anonymous access to this shared folder is disabled. Cheers!

For instructions on how to configure resolution of hostnames, see the following guides: Configuring AHV Backup Proxy server to resolve hostname ...

Oct 07, 2021 · Configuring AHV Backup Proxy server to resolve hostname of Veeam Backup & Replication server. To make the AHV Backup Proxy server correctly resolve the hostname of the Veeam Backup & Replication server, the DNS zone where the AHV Backup Proxy server is located must contain a DNS resource record for the Veeam Backup & Replication server.

07.10.2021 · Configuring AHV Backup Proxy server to resolve hostname of Veeam Backup & Replication server. To make the AHV Backup Proxy server correctly resolve the hostname of the Veeam Backup & Replication server, the DNS zone where the AHV Backup Proxy server is located must contain a DNS resource record for the Veeam Backup & Replication server. To add a new …

14.05.2015 · Make sure that you can open the mentioned file share via regular windows explorer (for both host name and ip address set in the path). Additionally, please make sure that you've set the correct credentials in case anonymous access to this shared folder is disabled. Cheers!

Jul 19, 2011 · VIX Error: Failed to resolve host Code: 30006

Are you seeing this error on a standalone agent or in the Veeam B&R console? Did you use a DNS name for the backup target or an IP address?

Oct 08, 2021 · Configuring Veeam Backup for RHV Server to Resolve Hostname of Veeam Backup & Replication Server. To make the Veeam Backup for RHV server correctly resolve the hostname of the Veeam Backup & Replication server, the DNS zone where the Veeam Backup for RHV server is located must contain a DNS resource record for the Veeam Backup & Replication server.

05.10.2017 · To fix this issue, update the product configuration with the current hostname by following these steps: Open the Configuration Database Connection Settings program, which should appear in the all programs menu of the Veeam Backup & Replication server. Within this program, select Veeam Backup and Replication then click next. Look for Server name.

Domain Name System (DNS) resolution is critical for Veeam Backup ... Protection (VADP) so the backup proxy server must be able to resolve the FQDN via DNS.

VIX Error: Failed to resolve host Code: 30006. KB ID: 1057. Product: Veeam Backup & Replication.

Veeam Community discussions and solutions for: error: unable to obtain IP ... becasuse the both server ping all IPs and name resolve is ok.

Seems it wont accept my credentials, but they are correct. Server is not a domain member. I have tried with servername\Administrator and ...

USA-Veeam Server is set up as proxy on UK-Veeam Server ... [11.01.2019 12:55:05] <01> Error Failed to resolve DNS name. Host name: ...

Oct 05, 2017 · To fix this issue, update the product configuration with the current hostname by following these steps: Open the Configuration Database Connection Settings program, which should appear in the all programs menu of the Veeam Backup & Replication server. Within this program, select Veeam Backup and Replication then click next. Look for Server name.

11.05.2021 · We have a SOBR configured with EC2 as the primary and S3 as the capacity tier. Veeam can backup to both backup repositories (independently) successfully, however when attempting an offload job from EC2 to S3 we are encountering the following error: resolve: Host not found (authoritative) In the task logs, this is shown as: