VMware vCenter Server Heartbeat - Upgrading vCenter Server 4.0, vCenter Server 4.0 Update 1, or vCenter Server 4.0 Update 2 to a Later Update or vCenter Server 4.1 With a Local SQL Database and vCenter Server Heartbeat 5.5 Update 2 or Earlier Installed

Follow

Summary

This Knowledge Base article provides the procedure to upgrade vCenter Server 4.0, vCenter Server 4.0 Update 1, or vCenter Server 4.0 Update 2 to a Later vCenter Server Update or vCenter Server 4.1 with a local SQL database and vCenter Server Heartbeat 5.5 Update 2 or Earlier installed.

More Information

When using this procedure to upgrade your existing vCenter Server installation with vCenter Server Heartbeat installed, VMware recommends that you review the entire procedure before starting the upgrade process.

Procedure

Note: If the Secondary server is the active server, skip step 1.

  1. Using the vCenter Server Heartbeat Console on the Secondary server, click System on the left navigation panel to open the Status and Control page and then click Switchover. Wait for the operation to complete successfully. 
  2. Shutdown the vCenter Server Heartbeat, leaving protected applications running on Secondary (active) server.
  3. Using the Service Control Manager, configure the Neverfail Server R2 service Startup Type to Manual on both Primary and Secondary. servers.

On Secondary Server

Note: If vCenter Guided Consolidation 4.0 or any of its updates are installed and you plan to upgrade it to vCenter Guided Consolidation 4.1, you must uninstall the old version of vCenter Guided Consolidation before proceeding with the vCenter Server upgrade.

  1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the list.
  2. Proceed with the setup, selecting the correct ODBC data source and database server credentials.
  3. If other components are installed, vCenter Server Setup will warn about the need to upgrade them as well.
  4. On the Database re-initialization warning page, select the Do not overwrite, leave my existing database in place option if you want to retain your existing data and proceed with the installation process.
  5. Once the vCenter Server upgrade process ends successfully, VMware recommends that you upgrade the existing extensions on the server. Details for each component upgrade can be found below.
  6. Verify that vCenter Server and all updated extensions are operational.
  7. If the upgrade on the Secondary server fails:
    1. Research the cause of the upgrade failure.
    2. If the issue can be resolved, then it is safe to proceed with upgrade procedure. Otherwise, revert to a previous version.
    3. To revert to a previous version:
      1. Uninstall the upgraded components.
      2. On the Secondary server, launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. Change the Current Role to Passive.
      3. Reboot the server. vCenter Server Heartbeat starts and vCenter Server is stopped.
      4. On the Primary server, launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. Change the Current Role to Active.
      5. Restart vCenter Server Heartbeat on the Primary Server and allow the system to synchronize.
      6. Start the vCenter Server Heartbeat Console and verify that the system completes the Full System Check.
  8. Change the Current Role to Passive:
    1. Launch the Configure Server wizard and click the Machine tab. In the Current Role section choose Passive and click Finish.
    2. Reboot the server.

On the Primary Server

Note: Continuation of this procedure assumes that the Secondary server upgrade process was successful.

If vCenter Guided Consolidation 4.0 or any of its updates are installed and you plan to upgrade it to vCenter Guided Consolidation 4.1, you must uninstall the old version of vCenter Guided Consolidation before proceeding with the vCenter Server upgrade.

  1. Change the Current Role to Active:
    1. Launch the Configure Server wizard and click the Machine tab. In the Current Role section select Active and click Finish.
    2. Using the Service Control Manager, start the Neverfail Server R2 service. 
    3. Wait until all protected services are started. 
    4. Using the Service Control Manager, stop the Neverfail Server R2 service.
  2. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the list.
  3. Proceed with the setup, selecting the correct ODBC data source and database server credentials.
  4. If other components are installed, vCenter Server Setup will warn about the need to upgrade them as well.
  5. On the Database re-initialization warning page, select the Do not overwrite, leave my existing database in place option if you want to retain your existing data and proceed with the installation process.
  6. Once the vCenter Server upgrade process ends successfully, VMware recommends that you upgrade the existing extensions on the server. Details for each component upgrade can be found below.
  7. Verify that vCenter Server and all updated extensions are operational on Primary server. 
  8. Using the Service Control Manager, configure Neverfail Server R2 service Startup Type to Automatic on both Primary and Secondary servers.
  9. Start vCenter Server Heartbeat on both servers.
  10. Launch the vCenter Server Heartbeat Console and connect to the server pair.
  11. Verify that the system completes the Full System Check and is replicating.

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 Current 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 Current 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.

Upgrading Update Manager 4.0 to any of its updates or Update Manager 4.1 with a Local SQL Database 

On Secondary Server

Note: This procedure assumes you have already updated vCenter Server on Secondary server.

  1. Start VMware vCenter Installer for the version you want to upgrade to (should be the same installer used for vCenter Server upgrade) and select vCenter Update Manager from the list.
  2. Provide vCenter Server and database information, and record all configuration settings used.

    Important: Before proceeding with the database upgrade, perform a backup of the existing vCenter Update Manager database.
  3. On the Database Upgrade page, select the option Yes, I want to upgrade my Update Manager database.
  4. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure, otherwise revert to previous version.

On Primary Server

Note: This procedure assumes you have already updated vCenter Server on your Primary Server.

  1. Start VMware vCenter Installer for the version you want to upgrade to (should be the same installer used for vCenter Server upgrade) and select vCenter Update Manager from the list.
  2. Provide vCenter Server and database information (provide the same information used during the upgrade on the Secondary server).

    Important: Before proceeding with the database upgrade,perform a backup of the existing vCenter Update Manager database.
  3. On the Database Upgrade page, select the option Yes, I want to upgrade my Update Manager database.
  4. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure.

Upgrading vCenter Converter from 4.0 to any of its Updates or vCenter Converter 4.1

On Secondary Server

Note: This procedure assumes you have already upgraded vCenter Server on Secondary server.

  1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Converter from the list.
  2. Provide vCenter Server, vCenter Converter Server information and record all configuration settings used.
  3. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure.

On Primary Server

Note: This procedure assumes you have already upgraded vCenter Server on your Primary Server. If you haven’t done so, refer to the appropriate Knowledge Base article that applies to your environment and upgrade vCenter Server before continuing.

  1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Converter from the list.
  2. Provide vCenter Server, vCenter Converter Server information (provide the same information used during the upgrade on the Secondary server).
  3. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure.

Upgrading vCenter Guided Consolidation from 4.0 to any of its Updates

On Secondary Server

Note: This procedure assumes you have already upgraded vCenter Server on Secondary server.

  1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Guided Consolidation from the list.
  2. Proceed with the installation.
  3. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with upgrade procedure.

On Primary Server

Note: This procedure assumes you have already upgraded vCenter Server on your Primary Server. If you haven’t done so, refer to the appropriate Knowledge Base article that applies to your environment and upgrade vCenter Server before continuing.

  1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Guided Consolidation from the list.
  2. Proceed with the installation.
  3. In the event errors are encountered during the installation, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with upgrade procedure.

Upgrading vCenter Guided Consolidation to Version 4.1

On Secondary server

Note: This procedure assumes you have manually uninstalled the previous version of vCenter Guided Consolidation before vCenter Server was upgraded to version 4.1 on Secondary server.

  1. Start VMware vCenter Installer 4.1 and select vCenter Guided Consolidation from the list.
  2. Provide required information and record all configuration settings used. The same settings will be required when installing on Primary server.

On Primary server

Note: This procedure assumes you have manually uninstalled the previous version of vCenter Guided Consolidation before vCenter Server was upgraded to version 4.1 on Primary server.

  1. Start VMware vCenter Installer 4.1 and select vCenter Guided Consolidation from the list.
  2. Provide required information (provide the same information used during the upgrade on the Secondary server).

Applies To

vCenter Server 4.0 upgraded to vCenter Server 4.0 Update 1, vCenter Server 4.0 Update 2 or vCenter Server  4.1
vCenter Server 4.0 Update 1 upgraded to vCenter Server 4.0 Update 2 or vCenter Server 4.1
vCenter Server 4.0 Update 2 upgraded to vCenter Server 4.1

Related Information

vCSHB-Ref-2118 

 

KBID-2118 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.