- Veeam Support Knowledge Base
- Veeam Backup for Nutanix AHV Proxy Appliance failure to update to v3
Veeam Backup for Nutanix AHV Proxy Appliance failure to update to v3
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
After installing Veeam Backup & Replication 11a (11.0.1.1261), one or more of the following may occur:
- An AHV Backup Proxy is listed as Unavailable in the Veeam Backup & Replication console.
- The AHV Backup Proxy's Web Console dashboard lists the backup server as unavailable.
- Accessing the AHV Backup Proxy's Web Console results in a page that displays a 502 Gateway Timeout.
- The update wizard or the Veeam Updater displays an error stating, "Failed to update Ubuntu to version 18.04.6 LTS."
- AHV Backup jobs fail to run.
- Restoring to an AHV cluster is not possible.
Cause
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 :
- The software update removed some custom entries in the /etc/hosts file on the proxy.
- Ubuntu failed to update to 18.04 LTS.
- The Nginx component failed to update.
Solution
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.
If the above steps do not resolve the DNS list in the /etc/hosts file, expand and follow these additional steps.
- Download the DNS Fix Script (see below).
- Uncompress the script and upload it to the /home/<user> directory on the AHV proxy using your preferred SFTP client.
Note: You may need to enable SSH on the AHV Proxy.
- SSH to the AHV Proxy and execute the script:
sudo bash dns_fix.sh- Restart the Proxy service:
Alternatively, you may reboot the AHV Proxy.
sudo service systemd-resolved restart- Check whether the nameservers are now properly listed in the /etc/resolv.conf:
cat /etc/resolv.confbf0da8311168a880077279aa1d5cca2cSHA-1:
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.
Steps to redeploy AHV Backup Proxy after failed update
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.
- Turn off incorrectly upgraded Proxy VM.
- Restore the proxy to a working condition:
- Log into Prism Element.
- Open Data Protection and click on VeeamBackupProtection.
- Click on Local Snapshots.
- Restore the most recent snapshot.
- Power on the restored proxy VM.
- This should revert to a functional pre-update proxy.
- With the proxy functional, save the configuration backup using the web console:
Click the gear icon >> Appliance Settings >> Config Backup button
- Power off the AHV Backup Proxy via Prism
- Remove the AHV Backup Proxy from Veeam Backup & Replication.
- Deploy a new AHV Backup Proxy.
- Restore the configuration saved in step 2.
- Edit the AHV Backup Proxy from within Veeam Backup & Replication, and proceed through each page, finally clicking finish to re-sync the proxy to the backup server.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.