VMware Engine is upgrading existing private clouds to use newer VMware components. See Service announcements for more details.

Private cloud maintenance and updates

Private cloud environments are designed to have no single point of failure.

  • ESXi clusters are configured with vSphere high availability (HA). Clusters are sized to have at least one spare node for resiliency.
  • vSAN provides redundant primary storage, requiring at least three nodes to provide protection against a single failure. For larger clusters, you can configure vSAN to provide higher resiliency.
  • vCenter, PSC, and NSX Manager virtual machines (VMs) are configured with RAID-10 storage to protect against storage failure. The VMs are additionally protected against node and network failures by vSphere HA.
  • ESXi hosts have redundant fans and NICs.
  • TOR and spine switches are configured in HA pairs to provide resiliency.

VMware Engine continuously monitors uptime, monitors availability, and provides availability SLAs for the following VMs:

  • ESXi hosts
  • vCenter
  • PSC
  • NSX Manager

VMware Engine continuously monitors the following for failures:

  • Hard disks
  • Physical NIC ports
  • Servers
  • Fans
  • Power
  • Switches
  • Switch ports

If a disk or node fails, VMware Engine immediately and automatically adds a new node to the affected VMware cluster to restore service operability.

The following VMware elements in private clouds are backed up, maintained, and updated:

  • ESXi
  • vCenter Platform Services Controller
  • vSAN
  • NSX

Backup and restore

Backup includes:

  • Nightly incremental backups of vCenter, PSC, and DVS rules.
  • vCenter native APIs to back up components at the application layer.
  • Automatic backup prior to update or upgrade of the VMware management software.


The following types of planned maintenance are included.

Backend and internal maintenance

Backend and internal maintenance typically involves reconfiguring physical assets or installing software patches. It doesn't affect normal consumption of the assets being serviced. With redundant NICs going to each physical rack, normal network traffic and private cloud operations aren't affected. You might notice a performance impact only if your organization expects to use the full redundant bandwidth during the maintenance interval.

Portal maintenance

Some limited service downtime is required when the control plane or infrastructure is updated. Maintenance intervals can be as frequent as once per month, and are expected to decline in frequency over time. VMware Engine notifies you about impending portal maintenance and makes an effort to keep the maintenance interval as short as possible. During a portal maintenance interval, the following services continue to function without any impact:

  • VMware management plane and applications
  • vCenter access
  • All networking and storage

VMware infrastructure maintenance

It's occasionally necessary to make changes to the configuration of the VMware infrastructure. These intervals can occur every one to two months, but the frequency is expected to decline over time. This type of maintenance can usually be done without interrupting normal private cloud consumption. During a VMware maintenance interval, the following services continue to function without any impact:

  • VMware management plane and applications
  • vCenter access
  • All networking and storage

Updates and upgrades

VMware Engine is responsible for lifecycle management of VMware software (ESXi, vCenter, PSC, and NSX) in private clouds.

Software updates include the following:

  • Patches: security patches or bug fixes released by VMware
  • Updates: minor version change of a VMware stack component
  • Upgrades: major version change of a VMware stack component

VMware Engine tests critical security patches as soon as they become available from VMware. Per SLA, VMware Engine targets a roll out of security patches to private cloud environments within one week of their availability.

When a new major version of VMware software is available, VMware Engine works with customers to coordinate a suitable maintenance window for applying the upgrade. VMware Engine applies major version upgrades at least six months after the major version is released and notifies customers two months in advance of applying major version upgrades.

VMware Engine also works with key industry vendors to ensure that they support the latest VMware software version before rolling out a major version upgrade. To get information about support for specific vendors, you can contact support.

What's next