#1 Global Leader in Data Protection & Ransomware Recovery

Backups Fail After Upgrade to AOS 5.8.0.1 or Later

KB ID: 2742
Product: Veeam Backup for Nutanix AHV | 2.0 | 2.1 | 3.0 | 4.0
Published: 2018-08-31
Last Modified: 2024-03-05
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please try again later.

Article Applicability

This article documents a bug (ENG-163615) Nutanix discovered in AOS 5.6.1 and resolved in AOS 5.9.1.

These AOS versions were supported by all versions of Veeam Backup for Nutanix AHV up to version 5. Starting with Veeam Backup for Nutanix AHV 5, the minimum required AOS version was 6.5. As such, this article is only relevant to:

  • Environments running AOS version 5.6.1 or greater but less than 5.9.1.
  • Veeam Backup for Nutanix AHV 1, 2, 2.1, 3, and 4.

Challenge

Veeam Backup for Nutanix AHV 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."

The Prism Element dashboard shows the following failed tasks:

prism error

This article is relevant when the following conditions are met:

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

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

To resolve this, upgrade to at least AOS 5.9.1, where ENG-163615 was resolved.

If upgrading is not feasible, an alternate solution is to disable the host affinity rules for the affected VMs.
 
Note: This issue does not affect the LTS (Long Term Support) release branch.
 

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

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

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.