Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
After installing Veeam Backup & Replication 11a (11.0.1.1261), one or more of the following may occur:
After updating Veeam Backup & Replication to 11a, the AHV Backup Proxy is updated to Veeam Backup for Nutanix AHV v3. The AHV Backup Proxy update process updates the proxy components and the appliance's operating system from Ubuntu 16.04 LTS to 18.04 LTS. If the appliance operating system or one of the proxy components fails to update during this upgrade, it can leave the proxy in a malfunctioning state.
The following have been identified by Veeam Support to cause the described symptoms :
Find the scenario and solution described below that best fits your situation.
I. AHV Backup Proxy Web Console and Veeam Backup & Replication list each other as Unavailable
The AHV Backup Proxy cannot resolve the hostname of the Veeam Backup & Replication server to the correct IP address. If custom entries were added to the /etc/hosts file before the upgrade, they might need to be added again, as the Ubuntu OS update may have removed them.
Check whether DNS servers are shown in the network configuration and if they are not - add them back. If they are not there, and the checkbox for automatic obtaining is ticked and greyed out - it helps to check-uncheck the same checkbox for IP-address parameters 1-3 times.
For more information, review Configuring Network Settings and Configuring Hostname Resolution in the Veeam Backup for Nutanix AHV 3.0 user guide.
sudo bash dns_fix.sh
sudo service systemd-resolved restart
cat /etc/resolv.conf
bf0da8311168a880077279aa1d5cca2c
92d8f6ddb9a3650e9c1e623e67a07cd1aaf298b8
II. The AHV Backup Proxy update displays an error message about being unable to download updates.
Ensure that the repositories listed in Used Ports can be reached by the AHV Backup Proxy, then rerun the update.
III. AHV Backup Proxy Web Console displays a 502 Gateway Timeout error
This typically means the update process failed. Reboot the proxy by going into Prism and choosing "Guest Reboot". If the 502 Gateway Timeout errors persist, you must deploy a new AHV Backup Proxy. Expand the section below, and follow the steps.
These steps should only be used when the AHV Backup Proxy fails to update or updates into a malfunctioning state.
The process below will guide you through reverting the AHV Backup Proxy, removing it, and finally creating a new AHV Backup Proxy. This process will utilize the snapshots of the AHV Backup Proxy that occur because, by default, Veeam creates a Protection Domain named VeeamBackupProtection and places the proxy into it. A snapshot job for this Protection Domain is run daily from the proxy.
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.