VMware vSphere Upgrade Policies
search cancel

VMware vSphere Upgrade Policies

book

Article ID: 316386

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

This article provides a description of the ways in which vSphere is bundled and distributed, provides definitions of the terms used, and provides general guidance on upgrade paths.

Environment

VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 6.0.x
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.0
VMware vSphere ESXi 6.5
VMware vCenter Server Appliance 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server Appliance 6.0.x
VMware vCenter Server Appliance 5.1.x
VMware vSphere ESXi 6.0
VMware vCenter Server 5.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server Appliance 5.5.x
VMware vCenter Server 6.5.x

Resolution

vSphere uses various mechanisms to deliver software functionality, enhancements, and bug fixes. These are summarized on the Upgrade and Update Policy page, and are described here in more detail.
  • Major release (for example vSphere 5.0)
    • Major releases generally contain new features and functionality. Major releases may also include significant changes in architecture, deployment, and operations of vSphere and vSphere components including vCenter Server. Each major release has a support lifecycle that is described the VMware Lifecycle Product Matrix.
    • There is no standard cadence for major releases but generally there are multiple years between releases.
       
  • Minor release (for example vSphere 5.1)
    • Minor releases generally contain new features in functionality but also may focus on enhancing existing capabilities from both technical and user experience perspectives. A minor release inherits its lifecycle from the parent major release. For example, vSphere 5.1 inherits the same end of sale and end of support dates of the vSphere 5.0 release. For more information on product lifecycle, see the VMware Lifecycle Product Matrix.
    • There is no standard cadence for minor releases but they generally occur more quickly than major releases.

      Note: vSphere 5.5 was an exception; this version is considered a Major release, and its support lifecycle is that of a major release.
       
  • Update release (for example vSphere 5.5 U3)
    • Update releases, sometimes called Maintenance releases generally contain bug fixes, compatibility enhancements, and user experience improvements. In some cases, update releases may contain minor new features and functionality. An update release inherits its lifecycle from its parent release. For example, vSphere 5.5 U3 inherits the same end of sale and end of support dates as vSphere 5.5. For more information on product lifecycle, see the VMware Lifecycle Product Matrix.
    • The typical timeline for update releases follows a 6-9-9 model, that is, Update 1 is usually released 6 months after the release of the major or minor release, and subsequent updates follow every 9 months. Note that this is not a policy, but only a general guideline. For example, Update 1 might come more than 6 months after the initial release.
       
  • Patch and Express Patch release (for example vSphere 6.5a or vCenter Server 5.5 Update 3e)
    • Patches and Express patch releases contain critical bug fixes that cannot wait for a full update release. Sometimes, for extremely time-sensitive issues, an express patch may be issued very quickly. An example of this may be a patch for a security vulnerability. A patch may also be issued for bug fixes that are deemed critical. Patches and express patches inherit their lifecycle from their parent release. For example, vSphere 5.5 Update 3e inherits the same end of sale and end of support dates as vSphere 5.5 Update 3. For more information on product lifecycle, see the VMware Lifecycle Product Matrix.
    • There is no standard timeline for patches and express patches.
    • Patches and Express Patches may be issued independently for ESXi (also known as vSphere Hypervisor) and vCenter Server. For example, at a given time, the most recent patch release for ESXi could be ESXi 5.5.0 Update 3b while the most recent patch release for vCenter Server could be vCenter Server 5.5 Update 3e.

Supported Upgrade Paths Policy

Generally, VMware supports upgrades to vSphere from releases that are several versions prior. For example:
  • Upgrades to vSphere 5.5 from prior major or minor versions of vSphere starting with vSphere 4.0 is supported.
    • The starting version can be a General Availability , Update or, a Patch release.
    • The upgraded version can be the General Availability release or an updated release of vSphere 5.5.
    • The starting version must not have been released after the end version.
    • It is NOT supported to upgrade from vSphere 5.0 U3 to vSphere 5.5, because vSphere 5.0 U3 was published after the release of vSphere 5.5.
    • It IS supported to upgrade from vSphere 5.0 U3 to vSphere 5.5 U1, because vSphere 5.0 U3 was published before the release of vSphere 5.5 U1.
Note: For the purpose of upgrade supportability, any patch release is treated the same as its parent release. In the above example, even if there was a patch release of vSphere 5.5 that was published after the release of vSphere 5.0 U3, this upgrade path is still not supported. Only upgrading to vSphere 5.5 U1 and higher is supported.
 
For the latest information on supported upgrade paths, see the Upgrade Path section of the VMware Product Interoperability Matrices. After selecting vSphere or vCenter Server, the resulting table will show which paths are supported. A Patch release should be referenced by removing the patch letter from the release name and looking at the parent release.


Additional Information

简体中文：VMware vSphere 升级策略

Powered by Wolken Software