vCenter Server upgrades with the reduced downtime

Products

• VMware vCenter Server

Issue/Introduction

1. Description

Reduced Downtime Upgrade (RDU) is a new mechanism introduced for upgrading the self-managed vCenter Servers with decreased downtime. Self-managed vCenter Server is one that manages its own ESXi host and its own virtual machine. This does not require a jump host to mount the ISO but the vCenter ISO needs to be mounted on the CD-ROM device of the vCenter Server Virtual Machine. The Workflow is integrated inside the vCenter Server itself.

2. Supported upgrade paths

Source Version	Target Version
8.0 GA	8.0 U2 or later releases
8.0 U1	8.0 U2 or later releases
8.0 P02	8.0 U2 or later releases
8.0 U2	Releases later than 8.0 U2

3. Known issues

• An error might be encountered which says "Update 8.0.x.xxxxxx for component vlcm is not found". To remediate this error, follow Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found".

Environment

VMware vCenter Server 8.0.2

Resolution

Workflow

 

Disclaimers:

i. Users should not be using multiple lifecycle operations at the same time. For example, they should not use Reduced downtime upgrade and VAMI at the same time. This may interfere with already running lifecycle events and may lead to a corrupt vCenter Server.

ii. If the ISO is mounted from the Reduced downtime upgrade workflow, VAMI (vCenter Server Appliance Management Interface) should not be used to upgrade the vCenter Server, as it is not the patch iso that is used to update the vCenter Server to the minor version update.

iii. Only a single administrator should be performing the Reduced downtime upgrade workflow at any given point in time

 

1. Download and mount ISO

1. The VCSA ISO needs to be downloaded in the Content Library/Datastore, which is connected to the vCenter Virtual Machine, or in the content library of the Managing vCenter.

2. Go to the properties of the vCenter Server Virtual Machine.
   

3. Connect the VCSA ISO to CD-ROM by browsing the datastore/content library.

4. Select the Connected checkbox and click OK.

2. Flow 1: Upgrade from version 8.0 GA, 8.0 U1, 8.0 P02 to 8.0 U2

1. Set the target in VAMI (vCenter Server Appliance Management Interface) while using the offline custom repository. If the online repository is used, make sure that the Default Repository URL is selected.

2. Go to Update Planner

 

3. Select the Target 8.0 U2 version.

4. Ensure the backup of the vCenter Server has been taken, then Perform Update Plugin from the Upgrade Planner page.

Note: An error might be encountered, which says "Update 8.0.x.xxxxxx for component vlcm is not found". To remediate this error, follow Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found"



Once the plugin is upgraded, the page will refresh to load the new UI.

5. The new UI should reload with ISO options

 

6. There is a discard functionality in the workflow. This can be used to discard all information that has been currently entered in the workflow.

Note: This does not revert the "Upgrade Plugin"

 

7. Mount the Target 8.0 U2 ISO on the vCenter. Please refer to Download and mount ISO for more information.

 

8. On the Update planner page, the ISO File gets updated with the current version, proceed to "next

 

9. Ensure the backup is completed. 

 

10. No Update Plugin required and Prepare Target should be enabled

 

11. Please read and accept the License Agreement.

 

12. Join the Customer Experience Improvement Program (CEIP)

13. Target location ( Deploy in same location as source).

 

14. The configuration with which you can deploy the target vCenter, which can be the same configuration as the source, or the user can select the detailed configuration.

 

15. Select the datacenter or Virtual Machine Folder where the target vCenter Server needs to be deployed

 

16. Select the Compute Resource to deploy the target vCenter Server.

 

17. This contains the Virtual Machine name and temporary root password. However, post-upgrading, the same root password as the source will be applied.

 

18. The source machine deployment size is displayed here; based on this, the user can select the Deployment Size for the target.

Note: The Deployment size configuration can be the same or greater than the source.

19. Select the target Datastore location where the vCenter Server will be deployed.

 

20. Network Settings

 

21. Review and proceed with Finish.

22. The configuration for the target (upgraded) vCenter server is now saved. Proceed to the upgrade steps.

 

Once the prepare target is complete, the user can click on switchover. This operation will result in approximately 10 minutes of downtime.

Note: 8.0 U3 onwards supports Automated Switchover.
 

 

23. There is an option to “Cancel upgrade”. Once clicked on, the upgrade will be cancelled and can be triggered again.

24. Switchover: Do not close this window, as the progress of the upgrade will be unknown. The switchover is the step where the source vCenter Server configuration is applied to the target vCenter Server, and the target vCenter Server starts all the services on it to start accepting requests.

3. Flow 2: Upgrade from version 8.0 U2 to later than 8.0 U2

1. Go to Update Planner, The new UI should load with the ISO options

2. Continue to Backup, Update Plugin steps

3. Mount the Target 8.0 U2 ISO on the VC. Please refer to ISO downloading and mounting for more information.

4. Update the Plugin to a version later than 8.0 U2 from the ISO, page gets refreshed post this.

 

5. Prepare Target should be enabled

 

6. Please read and accept the license agreement.

 

7. Join the Customer Experience Improvement Program

 

8. Target Location

 

9. The configuration with which you can deploy the target vCenter, which can be the same configuration as the source, or the user can select the detailed configuration.

10. Select the datacenter or Virtual Machine Folder where the target vCenter Server needs to be deployed

 

 

11. Select the Compute Resource to deploy the target vCenter Server.

12. This contains the Virtual Machine name and temporary root password. However, post-upgrading, the same root password as the source will be applied.

 

13. The source machine deployment size is displayed here; based on this, the user can select the Deployment Size for the target.
    
    Note: The Deployment size configuration can be the same or greater than the source.

 

14. Select the target Datastore location where the vCenter Server will be deployed.

15. Network Settings

 
Note: Mac Changes is set to 'Reject' on portgroups VM Network used by the vCenter. Forged Transmits is set to 'Reject' on portgroups VM Network used by the vCenter. This could prevent from a successful upgrade.

16. Review and confirm the data

17. The configuration for the target (upgraded) vCenter server is now saved. Proceed to the upgrade steps

Once the prepare target is complete, the user can click on switchover. This operation will result in approximately 10 minutes of downtime.

18. There is an option “Cancel upgrade” as well. Once clicked on, the upgrade will be cancelled and can be triggered again.

19. Switchover: Do not close this window, as the progress of the upgrade will be unknown. The switchover is the step where the source vCenter Server configuration is applied to the target vCenter Server, and the target vCenter Server starts all the services on it to start accepting requests.

 

4. Cancellation

After a failed upgrade

• If the upgrade fails, the upgrade will automatically revert to the source machine and bring it to the state it was in before the upgrade. There is no action required from the user.
• The logs should be collected using Collecting diagnostic information for VMware vCenter Server 7.x and 8.x and send to VMware Support to open a ticket.

After a successful upgrade

• It is important to note that upon canceling the upgrade, the target vCenter Server machine, which is deployed, is automatically deleted.
• If, for any reason, the user wants to revert to the source machine, they will need to power on the source machine, which will trigger the cancellation on the source machine and will delete the target machine.

Miscellanous

1. Important

Disconnect the network adapter of the source VCSA VM after the successful upgrade. This is required because of the current functionality of the source VM that, if powered on, deletes the target VM.

 

2. Unsupported topologies

   Topology	Source Version	Target Version	User Visible Behavior	Support ETA
   VCHA	8.0, 8.0u1	8.0 u2		8.0 U3 and above supports VCHA with basic deployment type.
   Uber Managed	8.0, 8.0u1	8.0 u2		8.0 U3 and above supports Uber managed VCs.
   ELM	8.0, 8.0u1	8.0 u2		8.0 U3 and above supports ELM.
   DUAL IP Stack	8.0, 8.0u1, 8.0u2			8.0 U3 and above support dual IP stack with IPv6.
   Deploy on ESXi	8.0, 8.0u1, 8.0u2	8.0u2 and 8.0 u2+		Future Patch Release.

 

 

 

Additional Information

Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found"