vSphere 7.0 Migration Process with Screenshots

vSphere 7.0 Migration Process with Screenshots


vSphere 7.0 Converge & Migration Process

 

Glad that you are seeking options to upgrade to our brand new offering vSphere 7.0

Please note that starting from vCenter 7.0, it will be only appliance based no options for integrating with any external database.

 

Community Support:

Did you know that VMware has a dedicated Install/Upgrade community ?

This sub community has an active user base and helps on common queries/errors during upgrade.

If you ever encounter any errors during the upgrade, feel free to post in our official install/upgrade forum - vSphere Upgrade & Install

 

This article focuses on migrating 6.5 Windows vCenter with external PSC to 7.0 vCenter Server

The steps are more or less same for migrating 6.7 windows to 7.0 vCenter Server

 

What has been deprecated in vCenter 7.0:

  • No option provided for deployed external PSC
  • No option provided for deploying Windows based vCenter
  • No inclusion of flash based Web client

 

Who can upgrade:

Source vCenter (Appliance or Windows) Destination vCenter Upgrade/Migrate
vCenter 5.5 & 6.0 (any version) vCenter 7.0 Not Supported
vCenter 6.5 & 6.7 (any version) vCenter 7.0 Supported

 

Click here to check the vCenter Server version upgrade compatibility

Click here to get update sequence for vSphere 7.0

Don't forget to read the vSphere Back-in-time release upgrade restriction

Licensing:

For vSphere 7.0, the existing license needs to be upgraded and you can contact VMware licensing team for upgrade options specific to your existing license.

Click here to learn more about licensing requirement for vCenter Server 7.0

 

Download:

Click here to download the latest version of vCenter 7.0

 

What you require:

  • A jump box, preferably windows 10 or any windows server 2008/20212/2016
  • It is advised to keep the jump box and the destination vCenter 7.0 on the same subnet, same port group/VLAN as the source vCenter appliance that you are planning to upgrade

          This way we can eliminate most of the network related errors during the upgrade phase.

  • User has access to windows based external PSC and vCenter
  • Make sure you have taken complete backup of the vCenter database

 

A quick summary of actions we will be performing for this migration process:

 

The migration task is split into stage 1 and stage 2.

Stage 1

Deploy a new 7.0 vCenter VM with active network connection set to communicate via the temporary IP address

 

Stage 2

The installer exports the data from the existing 6.5 vCenter to the new 7.0 vCenter using temporary IP

Performs convergence, shuts down source vCenter and reverts the network back to the same IP as the source vCenter

Performs First-Boot of vCenter 7.0 services and then imports copied data to the 7.0 vCenter

Steps with Screenshot :

___________________________________________________________________________________________

 

Stage 1

___________________________________________________________________________________________

 

Once you have read the above documents proceed to mount the downloaded image on the jump box

Inside the mounted directory, copy the "migration-assistant" folder

Log into the source windows vCenter server and paste the "migration-assistant" folder

___________________________________________________________________________________________

 

B.png

<On the source 6.5 windows vCenter>

Navigate to the folder and Run the migration assistant as Administrator

___________________________________________________________________________________________

 

E.png

Enter the SSO password and wait for the installer to perform pre-checks and shows prompt "waiting for migration to start"

DO NOT CLOSE THIS WINDOW - KEEP IT RUNNING

___________________________________________________________________________________________

2.png

<Login back to the Jump Box where you have mounted the installer ISO>

Navigate to the following directory and run the installer as Administrator and Select "Migrate"

___________________________________________________________________________________________

 

Once the installer starts, on the Introduction page, we have a quick recap of the two stage process which we had discussed earlier

Click "Next" and accept the EULA (End User License Agreement)

___________________________________________________________________________________________

6.png

Here you need to enter the FQDN of the source vCenter server

Also your local SSO administrator username and the password and click "Next"

(Make sure to correct the domain vsphere.local in case if you have set a different local SSO domain)

 

The installer gives prompt "Converge to an embedded Platform Services Controller"

This is to let users know that it has read the underlying vCenter configuration.

It automatically detects that the source vCenter has external SSO and will perform a converge operation during Migration

___________________________________________________________________________________________

8.png

 

Enter the host/vcenter name or IP on which the new 7.0 VM is going to get deployed

Since I have set the host IP address, I have set the username as root

If you had entered vCenter name, you should be entering the SSO admin user which is administartor@vsphere.local

___________________________________________________________________________________________

9.png

 

The VM name is the name on which the new VM will be deployed on the inventory

Also here you are given option to set the root password for the 7.0 vCenter

___________________________________________________________________________________________

 

10.png

 

Set the appliance deployment size based on your environmental requirement

You can refer the table in the above screenshot to size it accordingly

___________________________________________________________________________________________

11.png

 You select the Datastore where the new VM will be deployed

12.png

 

It is advised you select the same port-group where the source vCenter VM resides

Provide the temporary IP address, subnet, gateway and DNS server

All these steps are mandatory and cannot be skipped

13.png

 

You are given one final view of all the network settings provided

Once confirming the details, click on Finish to start Stage1 deployment

 

14.png

 

The deployment of the new vCenter 7.0 VM starts

You can check its progress by logging into the ESXi host and check the tasks pane

The installer might freeze at 80% but do not panic as this is common

At 80% is where it installs the RPM packages for the appliance

___________________________________________________________________________________________

15.png

Once completed, you should see the screen as above

___________________________________________________________________________________________

 

At this point, it is advised to take a snapshot of the newly deployed vCenter 7.0 appliance

If by any chance if the installer fails, you can revert back to the end of Stage1 installation and retry the upgrade again

 

To restart the upgrade from this point, you just simply enter the temporary IP address with port 5480

Example: If my temporary IP is 192.168.0.111

Then I restart the upgrade process from browser https://192.168.0.111:5480

___________________________________________________________________________________________

 

Stage 2

 

Click continue to go to Stage 2 Introduction page where the process is explained

Click "Next" to take you to the "Connect to source vCenter" page

 

___________________________________________________________________________________________

17.png

The installer detects the existing vCenter details which were provided earlier

Click "Next" to run the pre-migration checks for Stage 2

___________________________________________________________________________________________

21.png

This is the new option introduced

You can select the default option in case if you have single PSC and vCenter like we used in this guide

___________________________________________________________________________________________

21a.png

Optional - Only for reference purpose

This is how you can select to manage convergence in case if the PSC has multiple vCenter registered

___________________________________________________________________________________________

22.png

You are given option to enter the username which has privilege to add machines to the Domain

This step automatically adds vCenter appliance to the AD domain

___________________________________________________________________________________________

23.png

You can choose to keep tasks, events and performance charts data

You can also skip and go only with the configuration data of the source vCenter

___________________________________________________________________________________________

24.png

You can check this box to join VMware customer experience improvement program

Click "Next" to continue

___________________________________________________________________________________________

25.png

You are given options to validate your inputs

You have to check the "I have backed up..." to continue

If all the entered data is correct, start the final step by clicking on "Finish"

___________________________________________________________________________________________

27.png

Stage 2 starts and it will power off the source vCenter

The new vCenter 7.0 VM will take the same IP as the source and the temporary IP will be deleted

Once complete you will see installation successful 100% complete.

___________________________________________________________________________________________

This marks the end of Stage 2 and completion of the migration process

Additional Notes:

Only the source windows vCenter is only powered off

If you notice the source PSC is still powered on

Also if you check the replication partner, you will still see the source PSC registered with the new vCenter 7.0 appliance

This is kept so that customers can continue the migrate paths for other vCenter which are connected to the same PSC

Once the entire environment is migrated, you can decommission the source windows PSC following this link

- Jonathan Ebenezer 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Labels (3)
Comments

By your first step of stage 1, "Log into the source windows vCenter server and paste the "migration-assistant" folder," It looks like these procedures assume that you are upgrading a source vCenter running on a windows platform.  What about a linux based appliance?

@perryblalock The VCSA appliances come in .ISO format and on them are EXEs that are launched from a Windows environment. This doesn't mean he is actually installing/upgrading the Windows version of vCenter Server.

 

@jonastro - Nice documentation! Kudos for that.

Thanks pdirmann01.  I must not be reading the instructions correctly then because the first step of Stage 1 clearly states "Log into the source windows vCenter server and paste the "migration-assistant" folder."  That does say "Log into the source windows vCenter server," right?  To me that means he's telling us to grab the executable off the "ISO" that is "mounted" on the Jumphost and then copy them to the "source windows vCenter server."  Perhaps I'm not able to follow the flow on these steps, but that what it looks like to me.

I keep getting an error saying it couldnt authenticate. And i know the vcenter password is correct.

Version history
Revision #:
25 of 25
Last update:
‎09-11-2023 03:09 PM
Updated by:
 
Contributors