Search the VMware Knowledge Base (KB)
View by Article ID

Reverting a vCenter Server 5.5 or 6.0 to Appliance 6.x migration (2146453)

  • 2 Ratings
Language Editions

Purpose

This article provides steps to roll back a migration of vCenter Server 5.5 or 6.0 on Windows to vCenter Server Appliance 6.x.

Note: The rollback procedure restores your environment to the state before running the migration.

Resolution

Before preforming the preceding steps, create a log bundle of the failed system for troubleshooting purposes. For more information, see  Collecting diagnostic information for VMware vCenter Server 4.x, 5.x and 6.x (1011641).

Prerequisites:
  • Back up all vCenter Server and vCenter Single Sign-On instances.
  • Ensure that migration of the vCenter Server and vCenter Single Sign-On instances was completed in sequence starting with the vCenter Single Sign-On instance.
  • Back up the vCenter Server database.

Rolling Back a Migration of a vCenter Server 5.5 Environment with an Embedded Single Sign-On

This procedure applies to a vCenter Server 5.5 or 6.0 with an embedded Single Sign-On or Platform Services Controller server that was migrated to a vCenter Server Appliance 6.0 with an embedded Platform Service Controller.
  1. Power off the newly deployed vCenter Server Appliance 6.x.
  2. Bring the old vCenter Server instance online:
    1. If the old vCenter Server instance is powered off, power on the instance.
    2. If the old vCenter Server instance is powered on, restart the instance.
  3. If the vCenter Single Sign-On server was joined to an Active Directory domain, it may need to be joined again.
  4. Wait for all vCenter Server services to start and log in to the vSphere Web Client to verify the vSphere inventory.

Rolling back a migration of a vCenter Server environment with a single external vCenter Single Sign-On or Platform Services Controller instance


This procedure applies to environments that were migrated from vCenter Server with an external Single Sign-On or Platform Services Controller server that was migrated to a vCenter Server Appliance 6.x with an external Platform Service Controller. This can include environments that have multiple vCenter Servers that are connected to a Single Platform Service Controller. 

Prerequisites:
 
Ensure that these prerequisites are completed during the upgrade:
  • The Single Sign-On server was migrated first and a backup was created after the successful migration to a Platform Service Controller.
  • Subsequent backups were created for the Platform Service controller and vCenter Server after each vCenter Server migration.
In the case of a single failed vCenter Server migration, the restore point created prior to the migration can be used to bring the environment back to a working state.

Roll back a failed migration of the Single Sign-On or Platform Services Controller instance
  1. Power off the newly deployed Platform Services Controller Appliance.
  2. Restore the Single Sign-On or Platform Services Controller instance from backup.

    Note: If the Single Sign-On server or Platform Services Controller was joined to an Active Directory domain, it may need to be joined again.

  3. Wait for all Single Sign-On or Platform Services Controller services to start and log in to the vSphere Web Client to verify your vSphere inventory.
Roll back a failed migration of the first vCenter Server instance
  1. Power off the new Platform Service Controller Appliance.
  2. Restore the Platform Service Controller to the latest known backup in a working state.

    Note: If the Single Sign-On or Platform Services Controller server was joined to an Active Directory domain, it may need to be joined again.

  3. Verify that all Single Sign-On services are up and running.
  4. Power off the vCenter Server Appliance.
  5. Ensure the vCenter database is available if using an external database.
  6. Restore the failed vCenter Server instance from the latest known backup in a working state.

    Note: If the vCenter Server was joined to an Active Directory domain, it may need to be joined again.

  7. Wait for all vCenter Server services to start and log in to the vSphere Web Client to verify your vSphere inventory.
Roll back a failed migration of a subsequent vCenter Server instance
  1. Power off the newly deployed Platform Services Controller Appliance.
  2. Restore the Platform Service Controller prior to the latest known backup in a working state.

    Note: If the Single Sign-On or Platform Services Controller server was joined to an Active Directory domain, it may need to be joined again.

  3. Verify that all Single Sign-On or Platform Services Controller services are up and running.
  4. Power off the vCenter Server Appliance.
  5. Ensure the vCenter database is available if using an external database.
  6. Restore the vCenter Server instance that failed to from the latest known backup in a working state.

    Note: If the vCenter Server was joined to an Active Directory domain, it may need to be joined again.

  7. Wait for all vCenter Server services to start and log in to the vSphere Web Client to verify your vSphere inventory.

Rolling back a migration of a vCenter Server environment with multiple external vCenter Single Sign-On or Platform Services Controller instances


This backup process covers migrating multiple vSphere Single Sign-On or Platform Services Controller (N1, N2, and so on) and multiple vCenter Server (M1, M2, and so on) nodes.

For the preceding roll back procedure to succeed, ensure that all vCenter Server and Single Sign-On or Platform Services Controller nodes are backed up before the migration process.
  1. Backup all the vCenter Server (M) and Single Sign-On or Platform Services Controller (N) nodes prior to migration. For example the backups would be labeled as M1S1, M2S1, N1S1, N2S1 in a M2N2 environment.
  2. Migrate the first Single Sign-On node or Platform Services Controller (N1).
  3. Verify logins and inventory view from all nodes.
    If there are inconsistencies, turn off N1 and N2 and revert to N1S1 and N2S1 and exit the migration process.
  4. Migrate the second Single Sign-On node or Platform Services Controller (N2).
  5. Verify logins and inventory view from all nodes.
    If there are inconsistencies,  turn off N1 and N2 and revert to (N1S1, N2S1)  and exit the migration process.
  6. Migrate the first vCenter Server node or Platform Services Controller (M1).
  7. Verify logins and inventory view from all nodes
    If there are inconsistencies, turn off M1, N1 and N2 and revert to (M1S1, N1S1, N2S1)  and exit the migration process.
  8. Migrate the second vCenter Server or Platform Services Controller (M2).
  9. Verify logins and inventory view from all nodes
    If there are inconsistencies, turn off M1, M2, N1 and N2 and revert to (M1S1, M2S1, N1S1, N2S1) and exit the migration process.
  10. If there are additional Single Sign-On or Platform Services Controller or vCenter Server nodes, follow the same process for each node.
Note: After reverting to the original backups, if the Single Sign-On or Platform Services Controller and vCenter Server was joined to an Active Directory domain, it may need to be joined again.

See Also

Language Editions

ja,2148146;zh_cn,2148226

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 2 Ratings
Actions
KB: