Veeam Backup & Replication 12.1.2 Compatibility with vSphere 8.0 U3

Veeam's RnD team has extensively tested 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.

Update #2: Due to unforeseen complications, the testing of NSX-T 4.2.0 with Veeam Backup & Replication 12.3 is taking longer than initially expected. This article will be updated once further information is available. Thank you for your patience.

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