VMware vCenter Server Heartbeat - Upgrading vCenter Server 4.0 and its Updates to vCenter Server 4.1 With a Remote SQL Database With 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 and its updates to vCenter Server 4.1 with a remote SQL database and vCenter Server Heartbeat 5.5 Update 2 and 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 vCenter Server Heartbeat, leaving the protected applications running on Secondary (active) server.
  3. Using the Service Control Manager, configure Neverfail Server R2 service Startup Type to Manual on both Primary and Secondary servers.

On the 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 4.1 and select vCenter Server from the list.

    Important: Before proceeding with the database upgrade, perform a backup of the existing vCenter Server database and SSL certificates.
  2. On the Database Upgrade page, select the option Yes, I want to upgrade the vCenter Server database .
  3. Continue with vCenter Server installation and record all configuration settings used.
  4. If asked, do not reboot the server.
  5. Once the vCenter Server upgrade process successfully completes, 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 upgraded 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 server Current Role to Passive :
    1. Launch the Configure Server wizard and click the Machine tab. In the Current Role section select Passive and click Finish .
    2. Reboot the server.

On the Primary Server

Note: Continuation of the upgrade process assumes the upgrade of the Secondary server completed successfully

  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. Open a command prompt and navigate to <install_directory>\VMware\VMware vCenter Server Heartbeat\R2\Bin
    3. Execute the following command:

      Nfpktfltr.exe setfilter PassThru
    4. Verify the packet filter’s state to be passthru by running the command:

      nfpktfltr.exe getstate
  2. Start VMware vCenter Installer 4.1 and select vCenter Server from the list.
  3. On the Database re-initialization warning page, select the Do not overwrite, leave my existing database in place option and proceed with the installation process.
  4. Continue with vCenter Server installation, using the same configuration settings used for installation on the Secondary server.
  5. Once the vCenter Server upgrade process successfully completes, upgrade the existing extensions on the server. Details for each component upgrade can be found below.
  6. Verify that vCenter Server and all upgraded extensions are operational.
  7. Using the Service Control Manager, configure Neverfail Server R2 service Startup Type to Automatic on both Primary and Secondary servers.
  8. Start vCenter Server Heartbeat on both servers.
  9. Launch the vCenter Server Heartbeat Console and connect to the server pair.
  10. Verify that the Full System Check has completed and that the system replicating.

If vCenter Server fails to start on the Secondary Server:

  1. Shutdown vCenter Server Heartbeat.
  2. Launch the Configure Server wizard and click on the Machine tab. In the Current Role section, select Passive .
  3. Start vCenter Server Heartbeat on the Secondary server.
  4. Start the Configure Server wizard on the Primary server and click on the Machine tab. In the Current Role section, select 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.
  8. If the vCenter Server upgrade was successful on both servers, then the upgrade process for vCenter authorized extensions, if any, can be performed.

Upgrading Update Manager 4.0 Update 2 to Version 4.1 With a Remote SQL Database

On the Secondary Server:

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

During the vCenter Update Manager upgrade process, record all configuration settings used (vCenter Server information, Database information, port settings) as these will be required when upgrading the Primary server.

  1. Start VMware vCenter Installer 4.1 and select vCenter Update Manager from the list.

    Important: Perform a backup of the existing Update Manager database before proceeding with the next step.
  2. On the Database Upgrade page, select the option Yes, I want to upgrade the Update Manager database.
  3. Continue with the install process.
  4. Once the upgrade is complete, verify that vCenter Update Manager is operational.

On the Primary Server

Note: Continuation of the upgrades process assumes that the upgrade of the Secondary server completed successfully and that you have already upgraded vCenter Server on Primary server.

  1. Using the Service Control Manager, start VMware VirtualCenter Server service.
  2. Start VMware vCenter Installer version 4.1 and select vCenter Update Manager from the list.
  3. During the vCenter Update Manager upgrade, provide the same configuration settings used during the upgrade process on the Secondary server.
  4. On the Database re-initialization warning page, select Do not overwrite, leave my existing database in place option and proceed with the installation process.
  5. Once the upgrade is complete, verify that vCenter Update Manager is operational.


Applies To

vCenter Server 4.0 upgraded to vCenter Server 4.1 with a remote SQL database
vCenter Server 4.0 Update 1 upgraded to vCenter Server 4.1 with a remote SQL database
vCenter Server 4.0 Update 2 upgraded to vCenter Server 4.1 with a remote SQL database


Related Information

vCSHB-Ref-2120

KBID-2120

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.