https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNzQyIiwiaGFzaCI6ImRjZDI0YTQ2LTM5NWItNDk3NS05ZDg3LTQ0ODAyY2VkODFmNyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Availability for Nutanix backup fails after upgrade to AOS 5.8.0.1 or later

Challenge

Veeam Availability for Nutanix backup job fails with:

Backup VM [ID: 4a89ffc5-68b3-4be0-b117-0591dcec184e' Name: 'MYVM’] failed. Error: Backup was unsuccessful. Preparing VM for backup failed, 1."

Prism Element dashboard shows the following failed tasks:
User-added image

The following conditions are met:

  1. Nutanix AOS is upgraded up to 5.8.0.1 within STS (Short Term Support) release branch;
  2. Affinity rules are configured for the affected machines:
​​ User-added image

Cause

This is a known Nutanix issue and is tracked by Nutanix as an internal bug ENG-163615 which was discovered after the release of Nutanix AOS 5.6.1.
 

Solution

Upgrade to AOS 5.9.1 where ENG-163615 was resolved.  If an upgrade is not an option, you may disable the host affinity rules for the affected VMs as a workaround.
 
LTS (Long Term Support) release branch is not affected by this issue at the moment.
 
KB ID:
2742
Product:
Veeam Backup for Nutanix AHV
Version:
1.0.342
Published:
2018-08-31
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later