Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Upgrading vCenter Server 2.5 to a later update or to vCenter Server 4.0 when protected by vCenter Server Heartbeat 5.5 Update 2 and earlier protecting vCenter Server and SQL Server Database (1010483)

Purpose

This article provides steps to upgrade an instance of vCenter Server 2.5 and its updates to a more recent update or to vCenter Server 4.0 protected by vCenter Server Heartbeat 5.5 Update 2 and earlier where the vCenter Server database is installed on the same server.

Warning: Prior to attempting this upgrade, read this entire article. 

Note: This steps in this article assume that the SQL database is installed on the same server as vCenter Server and that it is protected.

Resolution

On the Primary Active Server, shutdown vCenter Server Heartbeat, opting to leave the protected application running.
 
On the Secondary Passive Server:
  1. Before proceeding with the upgrade, add a Management IP address to the Secondary server.
    1. Add a temporary Management IP address on the Principal (Public) IP NIC from the same subnet as the Principal (Public) IP address.

      This is needed because the Principal (Public) IP address is filtered on the passive (standby) server and vCenter Server needs it to access Active Directory. The temporary Management IP address is removed after completion of the upgrade process on the Secondary server.

    2. Start the SQL Server and SQL Server Agent services.

  2. If upgrading vCenter Server 2.5 to a more recent update:

    1. Install the vCenter Server 2.5 Update by running the VMware-VIMSetup.exe. This upgrades the VI Client, vCenter Server, and all the installed extensions.
    2. Upgrade the database.
    3. If asked, do not reboot the server at this point. A reboot is required later in the process.

      Note: During the upgrade process, the login account may be reset to the default (Local/System).

    4. Open the Service Control Manager and verify that the vCenter Server service login account is correct. If necessary, make corrections.
    5. Remove the temporary Management IP address.

      If the upgrade procedure was successful proceed to step 4.

  3. If upgrading vCenter Server 2.5 to vCenter Server 4.0:

    1. Install vCenter Server 4.0 running the Setup.exe.
    2. Upgrade the database.

      Important: Before proceeding with the database upgrade, perform a database backup.

    3. If asked, do not reboot the server. A reboot is required later in the process.
    4. Upgrade all existing components.
    5. Install all new components.
    6. Configure and install the vCenter Orchestrator Server service:

      Note: This step is not mandatory, but it should be performed at this point if this component is going to be used.
      Important: Make sure that the vCenter Orchestrator database name is the same on both servers.

      1. Using the Service Control Manager, start the vCenter Orchestrator Configuration service.
      2. Using the vCenter Orchestrator Web Configuration, install and start the vCenter Orchestrator Server service.

    7. Remove the temporary Management IP address.
    8. If the upgrade procedure is successful, proceed to step 4.

  4. Reboot the server. The server returns as passive with vCenter Server Heartbeat started and vCenter Server services are stopped.
  5. If the upgrade on the Secondary server fails:
    1. Research the cause of the upgrade failure.
    2. If the failure can be resolved, it is safe to proceed with upgrade procedure. Otherwise, you can revert to the previous version. To revert to the previous version:
      1. Uninstall the upgraded components on the Secondary server.
      2. Reboot the Server Secondary server. vCenter Server Heartbeat starts and vCenter Server is stopped.
      3. Restart vCenter Server Heartbeat on the Primary server.
      4. Launch the vCenter Server Heartbeat Console and verify that the system completes the Full System Check.

On the Primary Server (assuming a successful upgrade of the Secondary Server)

  1. If upgrading vCenter Server 2.5 to a more recent update:

    1. Install the vCenter Server 2.5 Update by running the VMware-VIMSetup.exe. This upgrades the VI Client, vCenter Server, and all installed extensions.
    2. Upgrade the database.
    3. If asked, do not reboot the server. It is rebooted in step 3.
    4. Open the Service Control Manager, and verify that the vCenter Server service login account is the correct. If necessary, make corrections.

      Note: During the upgrade process, the login account might be reset to the default (Local/System).

  2. If upgrading vCenter Server 2.5 to vCenter Server 4.0:

    1. Install vCenter Server 4.0 by running the Setup.exe.
    2. Upgrade the database.

      Important: Before proceeding with the database upgrade, perform a database backup.

    3. If asked, do not reboot the server. 
    4. Upgrade all existing components.
    5. Install all new components.
    6. Configure and install vCenter Orchestrator Server service:

      Note: This is not mandatory but it should be performed at this point if this component will be used.
      Important: Make sure that the vCenter Orchestrator database name is the same on both servers.

      1. Using the Service Control Manager, start the vCenter Orchestrator Configuration service.
      2. Using the vCenter Orchestrator Web Configuration, install and start the vCenter Orchestrator Server service.

  3. Reboot the Server. The server returns as active with vCenter Server Heartbeat and vCenter Server services started.
  4. Verify vCenter Sever is operational.
  5. If this is a WAN installation, remove the Managed IP address from the vCenter Server settings.
    1. Open vSphere Client.
    2. Navigate to Administration > vCenter Server Settings > Runtime settings.
    3. Clear the vCenter Server Managed IP field in Managed IP Address pane.
    4. Click OK.

  6. Launch the vCenter Server Heartbeat Console.
    1. If upgrading vCenter Server 2.5 to vCenter Server 4.0, from the vCenter Server Heartbeat Console, manually run the Protected Service Discovery task.
    2. Verify that the system completes the Full System Check.

Testing the vCenter Server Upgrade on the Secondary Server  

To test the success of the vCenter Server upgrade on the Secondary server:
  1. Trigger an auto-switchover so that the Secondary server becomes active.
    1. Launch the vCenter Server Heartbeat Console.
    2. Navigate to Application > Services.
    3. Select a protected service and click Edit.
    4. In the Edit Service dialog, set On First Failure to Switchover.
    5. Click OK.
    6. Open the Service Control Manager and stop the service that was previously configured in steps c and d.

      vCenter Server starts and replication is stopped.

  2. If vCenter Server starts successfully, click Start Replication.
  3. When the system is synchronized, perform a switchover to make the Primary server active.

If vCenter Server fails to start on the Secondary server:

  1. Shutdown vCenter Server Heartbeat.
  2. Start the Configure Server wizard and set the Secondary server Role to passive.
  3. Start vCenter Server Heartbeat on the Secondary server.
  4. Start the Configure Server wizard on the Primary server and set the server Role to active.
  5. Start vCenter Server Heartbeat on the Primary server.
  6. Launch the vCenter Server Heartbeat Console and verify that the system completes the Full System Check.
  7. Investigate the cause of the vCenter Server failure on the Secondary server.

Additional Information

vCSHB-Ref-1765

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

  • 3 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)
  • 3 Ratings
Actions
KB: