#1 Global Leader in Data Resilience

Veeam Backup & Replication 12.1.2 Compatibility with vSphere 8.0 U3

KB ID: 4641
Product: Veeam Backup & Replication | 12.1
Published: 2024-08-12
Last Modified: 2024-10-22
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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.

Update 2024-08-28

Veeam Backup & Replication 12.2 is now available.

This release resolves the "Automatic vCLS VM Exclusion" limitation detailed below.

Testing with NSX-T 4.2.0 is still in progress and is expected to be completed in time for the Veeam Backup & Replication 12.3 release.

Support Statement

Veeam's RnD team has performed extensive testing with Veeam Backup & Replication 12.1.2 (build 12.1.2.172) and has determined that it is functional with vSphere 8.0 U3; however, the following limitations apply:
 

Automatic vCLS VM Exclusion Broken

The automatic exclusion of vCLS VMs does not occur after upgrading to vSphere 8.0 U3. This automatic exclusion feature, first introduced in Veeam Backup & Replication 10, fails to function because vSphere 8.0 U3 changed the VM type identifier for vCLS VMs.

Update: Veeam Backup & Replication 12.2 was released on 2024-08-28 and includes a new method for identifying and automatically excluding vCLS VMs.

Advice: Use the provided workaround until Veeam Backup & Replication 12.2 is available.

  • Challenge: If a container object (e.g., Folder, Cluster, Datacenter, Host) has been added to a job, that job will attempt to process the vSphere Cluster Services (vCLS) VMs. The tasks for those vCLS VMs will fail.
  • Cause: In vSphere 8.0 U3, the vCLS VM type was changed.
  • Workaround: Add the vCLS VMs to the Global VM Exclusions list to prevent the jobs from attempting to process them.
    *Note: The vCLS VMs can only be seen by Veeam Backup & Replication and added to the Global VM Exclusion list after upgrading to vSphere 8.0 U3.
  • Resolution: This issue will be addressed in the upcoming Veeam Backup & Replication 12.2 release.
     

NSX-T 4.2.0 Compatibility Untested

Due to a lack of access to NSX-T 4.2.0, compatibility of NSX-T 4.2.0 and vSphere 8.0.3 has not been tested with Veeam Backup & Replication.

Update: Testing of NSX-T 4.2.0 and Veeam Backup & Replication 12.2 is underway and expected to be completed before the release of Veeam Backup & Replication 12.3.

Advice: Customers are advised to wait for final testing results before deploying NSX-T 4.2.0 in production environments.

 

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.