«

»

Dec 12 2017

Migrate Windows vCenter Server 6.0 to vCenter Server Appliance (VCSA) 6.5

A few weeks back I did my first production environment migration of VMware vCenter Server 6.0 Windows version to vCenter Server Appliance (VCSA) 6.5. I have tested this in customer lab and in my home lab before so it was not a new experience. Since the source vCenter Server used an Embedded Platform Service Controller (PSC) and I couldn’t find any reason for moving to an external PSC I decided to keep it simple and just continue with the embedded option.

The process can be divided into three sections according to:

Preparation

In this step you should read, understand and perform the necessary steps included in this official VMware documentation before you move on to the next section. In addition to do some reading you should also download the VCSA 6.5 image.

Stage I

The end state in Stage I is to have a VCSA VM up and running.

Two main steps in this stage:

  1. Start the VCSA Migration Assistant by mounting the downloaded ISO to the vCenter Server, go to folder migration-assistant and double-click the VMware-Migration-Assistant.exe file.
    1. Give the adminsitrator@vsphere.local (or what ever SSO domain you are using) password:
      Wait for connection
  2. Step through Stage 1 of the migration by running the vCenter Server UI Installer
    1. Start the vCenter Server Installation UI and click Migrate
    2. Accept license agreement
    3. Provide FQDN, SSO user name and SSO password for existing vCenter Server
    4. Accept SSL certificate
    5. You can select an ESXi hosts or a vCenter Server as target for your VCSA VM deployment. In my case I used an ESXi host
    6. Click Yes to the certificate warning
    7. Provide VM Name and a root password for the VCSA VM
    8. Select target Datastore (where your VCSA will be placed/running)
    9. Select and provide the following:
      1. Network, in my case an ESXi Virtual Standard Switch (VSS) port group called mignetwork
      2. Temporary IP information for the VCSA VM so it can be online same time as original vcenter Server
    10. Review the information and click Finish
    11. Wait until the process is finished.
    12. When the process is finished you can either click Close or Continue. If you select Continue you will automatically be taken to Stage 2

Stage II

In Stage II we will actually migrate the vCenter Server component including all its data to the VCSA and the  end state will be VCSA up and running and old Windows based vCenter Server turned off.

If you selected Close at the last step in Stage I you can start Stage II by loggin in to the VCSA VM admin interface which can be accessed via https//fqdn:5480

In my case I selected Continue and the below interface was started automatically.  Follow the below steps to complete the migration.

  • Click Next
  • The Pre-migration check results includes any potential issues you might run in to. In my case, just an outdated plugin.
  • Since the Windows based vCenter Server VM was a member of the domain we need domain credentials
  • Select what type of information you want to migrate. In my case I selected everything mening:
    • Configuration
    • Tasks & Events
    • Performance Metrics
  • I did not Join VMware Customer Experience Program (CEP)
  • Watch the migration happen via the Migration wizard or Migration Assistant cmd window which will be unavailable when the Windows based vCenter Server shut down as a step in the migration process.

When completed you are all good to go. Remember to login to the admin interface via https//fqdn:5480 to perform any additional configuration, take a manual backup or check out the blog post about how to Schedule vCenter Server Appliance backups via PowerCLI.

2 comments

  1. Thomas

    Hello, we run though the Migration process as Well and had the following Problems:
    – Import of vum data was not possible so we had to uninstall the update manager at first and Start the migration process again
    – during the First test Migration only the large appliance was selectable. So we cleaned up the sql database before the Migration and bring the dB size down from 100 gb to 20 gb. Afterward also Medium was selectable.

  2. magander3

    Thanks for sharing

    //Magnus

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">