1-800-691-1991 | 9am - 8pm ET

Veeam Backup & Replication support for VMware vSphere


This article describes list of VMware vSphere versions currently supported by Veeam Backup & Replication.

IMPORTANT: It is recommended to always use the latest Veeam version to ensure modern platforms support and security compliance.


vSphere versionMinimum Veeam Backup & Replication versionVeeam GA date
710 Cumulative Patch 2 (build P2)2020-05-28
6.7 Update 39.5 Update 4b (build
6.7 Update 29.5 Update 4a (build
6.7 Update 19.5 Update 4 (build
6.79.5 Update 3a (build
6.5 Update 39.5 Update 4b (build
6.5 Update 2

9.5 Update 4 (build

IMPORTANT: Official Support for 6.5u2 starting from ESXi patch level ESXi650-201811002

9.5 Update 3a (build


  • Supported for 9.5 U3a with the exception of issues caused by a regression introduced in ESXi 6.5 U2 that causes its API to fail randomly under heavy host load.
  • There is a known issue where a Veeam Proxy running on a VM may become listed as (invalid) in vSphere. More information here:
6.5 Update 19.5 Update 2 (build
6.59.5 Update 1 (build
6.08.0 Update 2 (build
5.57.0 R2 (build

More information

A list of Veeam Backup & Replication version and build numbers can be found on Veeam KB 2680
A list of VMware ESX(i) versions and their respective build numbers can be found on VMware KB 2143832.

Veeam Product Lifecycle: 
VMware Lifecycle Product Matrix:

The latest Veeam updates can be found at:
Veeam Backup & Replication
Last Modified:
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