Service announcements

Learn about Google Cloud VMware Engine changes such as upgrades, backward incompatible API changes, product or feature deprecations, mandatory migrations, or potentially disruptive maintenance.

Date published Description Instructions

November 20, 2020

Upgrade announcement for the following software:

  • Upgrade VMware stack from version 6.7 to 7.0
  • Upgrade NSX-T stack from version 2.5 to 3.0
See the Preparing for the upgrade section in this document.

November 20, 2020

The VMware Engine operations team will upgrade VMware components to newer versions beginning mid December 2020. You will receive an email with the planned maintenance dates and times of the upgrade.

Upgrade contents

We aim to provide you with access to the most up-to-date features and functions of vSphere. We will upgrade the VMware stack from version 6.7 to 7.0 and the NSX-T stack from version 2.5 to 3.0. The upgrade lets you use new features of vSphere, vSAN, and NSX-T and enjoy significant improvements in storage and networking performance.

Learn more about vSphere 7.0 features and NSX-T 3.0 features.

VMware component versions post-upgrade

VMware component Version Build
vCenter Server 7.0 U1a 17004997
ESXi 7.0.1 U1a 17119627
vSAN 7.0 U1 N/A
NSX-T 3.0.2 16887200

Upgrade schedule

This upgrade is scheduled between December 2020 and January 2021. You will receive an email notification with the planned maintenance dates and times of the upgrade for your private cloud. An hour before the upgrade starts, the VMware Engine operations team will send another email notice. Notifications are sent to all users of VMware Engine and any additional configured email IDs.

Upgrade actions

During the upgrade, VMware Engine will add a new node to your vSphere cluster and place an existing node in maintenance mode. The new node maintains availability and capacity of your private cloud during the upgrade process. When VMware components are upgraded, you might see alarms in vCenter Server. The alarms are a part of the maintenance operations performed by the VMware Engine operations team.

Depending on the size and complexity of your deployment, this upgrade might take from a few hours to a few days. The following actions will happen during the upgrade:

  • VMs configured with vSAN storage policy for Failures to Tolerate (FTT) of 0 are changed to vSAN storage policy for FTT of 1 to maintain the SLA.
  • CDs mounted on a VM using a datastore ISO file or client are disconnected.
  • Any in-progress VMware tool installations or upgrades are terminated.
  • VMs with SCSI bus sharing are powered off.
  • DRS rules are disabled during the upgrade and re-enabled after the upgrade.
  • Orphaned or inaccessible VMs are removed from vCenter inventory.

Preparing for the upgrade

  • Check storage capacity: Ensure your vSphere Cluster's storage space utilization is below 75% to maintain the SLA. If the utilization is above 75%, upgrades might take longer than normal or fail completely. If your storage utilization is higher than 70%, add a node to expand the cluster and avoid any potential downtime during upgrades.
  • Check solution compatibility: Ensure that any add-on solutions deployed on your private cloud vCenter are compatible with vSphere 7.0. Some examples are backup, monitoring tools, and disaster recovery orchestrator and tools. Check with the solution vendor and upgrade these solutions if necessary to avoid any incompatibility after upgrade.
  • Change vSAN storage policies with FTT of 0: Change VMs configured with a vSAN storage policy for Failures to Tolerate (FTT) of 0 to a vSAN storage policy with FTT of 1 to maintain the SLA.
  • Remove VM CD mounts: Remove any CDs mounted on your workload VMs.
  • Complete VMware tool installations: Complete any installations or upgrades of VMware tools before the scheduled upgrade begins.
  • Remove SCSI bus sharing on VMs: Remove SCSI bus sharing on VMs if you don't want the VMs to be powered off.
  • Remove inaccessible VMs and datastores: Remove orphaned and inaccessible VMs from vCenter inventory. Remove any inaccessible external datastores.
  • Disable DRS rules: DRS rules that pin a VM to a host prevent a node from entering maintenance mode. You can disable the DRS rules before the upgrade and enable them after the upgrade is complete.

Upgrade FAQs

Will it cost my organization anything to upgrade?
No, your organization is not charged for the upgrade. All new capabilities of vSphere are covered by your service.
How long will the upgrade take?
Upgrades can take anywhere from a few hours to a few days, depending on the complexity of your deployment, the number of clusters, and the amount of data present on your private cloud.
Will the upgrade break anything?
We don't expect downtime during the upgrade process. However, we recommend that you check with solution vendors of any deployed solutions on your private cloud for compatibility with vSphere 7.0 and ensure that you have enough free storage capacity—over 30%—for the upgrade to be performed.
Do I need to do anything after the upgrade?
No action is required from you after the upgrade. You can check the versions of VMware components and use all new features available with this upgrade.
How will I know when the upgrade has completed?
The VMware Engine operations team will send you an email at the start of the upgrade and again upon its completion. Ensure you have turned on email alerts to receive notifications from the VMware Engine team. You can configure additional email alerts to notify any other users who need to be notified.
How can I get help?
If you have any questions about the upgrade or need any help after the upgrade, contact Cloud Customer Care.