Upgrade vCenter Server for VMware Cloud Foundation 5.2.x
The upgrade bundle for VMware
vCenter Server
is used to upgrade the vCenter Server instances managed by SDDC Manager. Upgrade vCenter Server
in the management domain before upgrading vCenter Server
in VI workload domains.- Download the VMwarevCenter Serverupgrade bundle. See downloading-vmware-cloud-foundation-bundles.dita.
- Take a file-based backup of thevCenter Serverappliance before starting the upgrade. See manually-back-up-vcenter-server.dita.After taking a backup, do not make any changes to thevCenter Serverinventory or settings until the upgrade completes successfully.
- If your workload domain contains Workload Management (vSphere with Tanzu) enabled clusters, the supported target release depends on the version of Kubernetes (K8s) currently running in the cluster. Older versions of K8s might require a specific upgrade sequence. See KB 92227 for more information.
- In the navigation pane, click.
- On the Workload Domains page, click the domain you are upgrading and then click theUpdatestab.
- ClickPrecheckto run the upgrade precheck.Resolve any issues before proceeding with the upgrade.
- Upgrading toVMware Cloud Foundation5.2:
- In the Available Updates section, clickUpdate NoworSchedule Updatenext to the VMware Software Update forvCenter Server.
- ClickConfirmto confirm that you have taken a file-based backup of the vCenter Server appliance before starting the upgrade.
- If you selectedSchedule Update, click the date and time for the bundle to be applied and clickSchedule.
- If you are upgrading fromVMware Cloud Foundation4.5.x, enter the details for the temporary network to be used only during the upgrade. The IP address must be in the management subnet.
- Review the upgrade settings and clickFinish.
- Upgrading toVMware Cloud Foundation5.2.1 fromVMware Cloud Foundation5.x:
- In the Available Updates section, clickConfigure Update.
- Select the upgrade mechanism and clickNext.OptionDescriptionvCenter Reduced Downtime UpgradeThe reduced downtime upgrade process uses a migration-based approach. In this approach, a new vCenter Server Appliance is deployed and the current vCenter data and configuration is copied to it.During the preparation phase of a reduced downtime upgrade, the source vCenter Server Appliance and all resources remain online. The only downtime occurs when the source vCenter Server Appliance is stopped, the configuration is switched over to the target vCenter, and the services are started. The downtime is expected to take approximately 5 minutes under ideal network, CPU, memory, and storage provisioning.To perform a vCenter Reduced Downtime Upgrade, the target vCenter version must be theVMware Cloud Foundation5.2.1 BOM version or later.vCenter Regular UpgradeDuring a regular upgrade, the vCenter Server Appliance is offline for the duration of the upgrade.
- Select a backup option and clickNext.
- For an RDU update, provide a temporary network to be used only during the upgrade and clickNext.AutomaticAutomatically assign network information.StaticEnter an IP address, subnet mask, and gateway. The IP address must be in the management subnet.
- Schedule the update and clickNext.For vCenter Reduced Downtime UpgradeSelect scheduling options for the preparation and switchover phases of the upgrade.If you are scheduling the switchover phase, you must allow a minimum of 4 hours between the start of preparation and the start of switchover.For vCenter Regular UpgradeSelect anUpgrade NoworSchedule Update.
- Review the upgrade settings and clickFinish.
- Upgrading toVMware Cloud Foundation5.2.1 fromVMware Cloud Foundation4.5.x:
- In the Available Updates section, clickConfigure Update.
- Enter the details for the temporary network to be used only during the upgrade. The IP address must be in the management subnet.
- Select a backup option and clickNext.
- Schedule the update and clickNext.
- Review the upgrade settings and clickFinish.
- Monitor the upgrade progress. See monitor-update.dita.
- After the upgrade is complete, remove the old vCenter Server appliance (if applicable).Removing the old vCenter is only required for major upgrades. If you performed a vCenter RDU patch upgrade, the old vCenter is automatically removed after a successful upgrade.If the upgrade fails, resolve the issue and retry the failed task. If you cannot resolve the issue, restorevCenter Serverusing the file-based backup. See restore-vcenter-server.dita. vCenter RDU upgrades perform automatic rollback if the upgrade fails.
Once the upgrade successfully completes, use the vSphere Client to change the vSphere DRS Automation Level setting back to the original value (before you took a file-based backup) for each vSphere cluster that is managed by the
vCenter Server
. See KB 87631 for information about using VMware PowerCLI to change the vSphere DRS Automation Level.