#1 Global Leader in Data Protection & Ransomware Recovery

Virtual Machine is unavailable and will be skipped from processing.  

KB ID: 1299
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1
Published: 2011-10-15
Last Modified: 2021-10-15
Languages: IT | FR | ES
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.

Challenge

One or more virtual machines in a VMware Backup job fail with the following error:
Virtual Machine <VMname> is unavailable and will be skipped from processing.  
Image showing what the error looks like in the Veeam GUI

Cause

This error occurs when a virtual machine's unique inventory reference identification number (MoRef or Managed Object Reference) changes within the virtual infrastructure, or the virtual machine is deleted. The virtual machine is still in the Backup Job, and when the job starts, the job is still attempting to find the VM by its old reference ID.

Note: The most common events that cause a VM MoRef ID to change are:

  • A VM is removed from inventory and then added back to inventory.
  • In rare cases, a host crash, which prompts the host to be removed and added back to the VC, may cause the VMs on that host to get new MoRef-IDs.
  • Reinstallation or creation of a new vCenter server where the old VC database is not reused. (If this occurs and all VM's MoRef IDs have changed, it may be possible to resolve this en masse using the vCenter Migration tool here: https://vee.am/kb2136)

 

Solution

New MoRef-ID is treated as New VM
Veeam Backup & Replication tracks every VMware VM by its unique MoRef ID. If the MoRef ID for a machine changes, it is treated by Veeam Backup & Replication as a different machine. If the VM is added to a job where it was backed up previously, the existing restore point chain will not continue with the re-added VM because the VM now has a different MoRef ID.

If the VM was removed from the infrastructure and no longer exists, remove it from the backup job.

If the VM exists in the environment, and the Backup job is throwing the error "Virtual Machine is unavailable and will be skipped from processing." The VM must be re-added to the Backup job.  

Re-add the VM to the Job

  1. Edit the Job
Edit job option in context menu
  1. Navigate to the Virtual Machines tab.
  2. Select the VM whose MoRef has changed.
  3. Click Remove
On Virtual Machines tab vm selected, click remove Note that the VM having this issue will be listed with 0 B in the size column. 
  1. Click Add...
Clicking add..
  1. Click Refresh (Infrastructure information is cached, the refresh function must be used when resolving this issue.)
  2. Add the VM removed in step 4.
Refresh and readd the VM
  1. Click [Finish] to save the Job settings.
Click finish to complete the editing of the job

More Information

  • Resolution can be confirmed without running the job. Edit the job, navigate to the "Virtual Machines" tab, and click the [Recalculate] button. Note that the VM's whose MoRefs changed now report as having the correct size.
  • Please be aware that VM's are tracked by their unique MoRef ID. When the MoRef changes, the VM is considered an entirely different VM. As such, Veeam Backup & Replication will treat them accordingly and create a Full restore point for the "new" VM.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.