On May 30th, 2019 a small update was released by Veeam for the product Veeam Availability for Nutanix AHV 1.0. this update contains some bug fixes that will improve performance but also could improve your day to day management of the proxy appliance and your Nutanix AHV backups.
The release notes can be found at the bottom of this post.
You can see from the release notes linked below the detailed improvements that have been made but a summarised list of those are as follows:
Update 2 includes:
- Improved backup performance and optimal operation
- In some cases, the proxy appliance would schedule too many parallel tasks causing resource and performance issues. The bug has been fixed to offer optimal operation
- Resolved issue with configuration backups being larger than required due to ignoring of configuration backup settings
- Fixed bugs in with deleted VM retention not properly cleaning backups of deleted VMs
- Fixed bug with Veeam Availability for Nutanix AHV service crashes in rare circumstances
- Fixed bug with backup failures on highly loaded proxy appliances
In order for this update to take place you are required to take a configuration backup and redeploy the Veeam Nutanix Proxy Appliance, this appliance is a small virtual machine disk that can be obtained from the link below.
To firstly take that Configuration backup you should follow this instruction.
The configuration backup contains everything you have configured from your job settings and schedules as well as your connection to your AHV cluster and Veeam Backup & Replication server.
If you choose not to backup the configuration and complete the following steps, you will have the required update 2 deployed but no access to the configuration will be available.
Once you have the configuration backup then you can proceed with the deployment steps also outlined here in a previous post.
- Turn off the VM where the proxy appliance is installed.
- Download the latest version of Veeam Availability for Nutanix AHV from: www.veeam.com/availability-nutanix-ahv-download.html.
- In the Nutanix AHV cluster, create a VM that meets System Requirements.
- In the VM settings add a new disk and specify the Veeam Availability for Nutanix AHV VMDK as a boot disk.
- Power on the VM.
- Copy the web console URL address specified in the VM console, and open the URL using a web-browser.
- In the opened welcome screen, enter the default credentials (login: admin, password: admin) and click the arrow button.
- In the Install-Restore wizard, click Restore and follow the steps of the Restore wizard to restore your configuration settings from the backup file.
- After the deploy process, you can remove the VM used for the previous version of Veeam Availability for Nutanix AHV.
This list of steps can also be found here.
The final step is to update the license on the Veeam Proxy Appliance. This can be done by following these steps.
Release Notes – https://www.veeam.com/veeam_nutanix_ahv_1_0_release_notes_rn.pdf
Update 2 – https://my.veeam.com/#/kb2956
Automate the update
The above steps could also be better automated by using a terraform script I created recently for the deployment steps of the Veeam proxy appliance. For this to work follow this walk through and download the update 2 vmdk to your web server to make this happen.
Before you modify or make changes to your terraform scripts you should ensure that you have your configuration backup. You can then perform a terraform destroy, you will see within AHV that your proxy appliance is then deleted. Next we need to modify your terraform scripts to see the new vmdk for update 2. Upload the file to your web server and find this line of command.
My advice would be to keep the old code running and start a new deployment. This way you can always failback.
And replace with the newly uploaded vmdk.
Once the update and upload are complete, you should then run terraform apply and confirm by adding yes to the value.
Firstly, login to the console.
Then select “Restore” to upload your configuration backup
Depending on your network configuration your newly deployed proxy appliance may be on a different IP to your previous one of the steps you will reach through the restore wizard is the network configuration.
Pretty straight forward, remember the proxy appliance does not contain any of your backup data it is just the data mover and job scheduler so it is possible for a new one to deployed with the configuration backup added each time.