VMWare vCenter Server Heartbeat - Upgrading or Applying Updates to VirtualCenter Server 2.5 or vCenter Server 4.0 When Protected by vCenter Server Heartbeat - Local SQL Database

Follow

Summary

This Knowledge Base article provides the procedure to upgrade or apply updates to vCenter Server protected by vCenter Server Heartbeat when a local SQL database is used.


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.

The procedure below provides instructions for all supported vCenter Server components and plug-ins; omit steps for those components that do not need to be upgraded or do not apply to your deployment of vCenter Server.

Procedure

On the Primary Active Server

  1. Shutdown vCenter Server Heartbeat, opting to leave the protected application running.

On Secondary Passive Server

  1. If a Management IP does not already exist, add a Management IP address to the Secondary Server.
    1. Add a Management IP address on the Principal (Public) NIC from the same subnet as Principal (Public) IP address.

      This is needed because the Principal (Public) IP address is filtered on the passive (standby) server and vCenter Server will need it to access Active Directory. The temporary Management IP address will be removed after completion of the upgrade process on the Secondary server.
  2. Start the SQL Server, and SQL Server Agent services
  3. Install vCenter Server 4.0 running the Setup.exe

    Note: If upgrading from VirtualCenter Server 2.5 run VMware-VIMSetup.exe to upgrade the VI Client, vCenter Server, and vCenter Server and all installed extensions.

    Important: Before proceeding with the database upgrade, perform a database backup.
  4. Upgrade the database.
  5. If asked, Do NOT reboot the server at this point, it will be rebooted at step 10.

    Note: During upgrade process, the logon account might be reset to the default (Local/System).
  6. Open the Service Control Manager, and verify that the vCenter Server service logon account is correct. If necessary, make corrections.
  7. Remove the temporary Management IP address.
  8. If the upgrade procedure was successful proceed to step 10. If the upgrade procedure fails, go to step 9.
  9. If the upgrade on the Secondary server fails:
    1. Research the cause of the upgrade failure.
    2. If this can be resolved, then it is safe to proceed with upgrade procedure. Otherwise, you can revert to the previous version.
    3. To revert to the previous version:
      1. Uninstall the upgraded components on the Secondary server.
      2. Reboot the Server Secondary server. vCenter Server Heartbeat will start and vCenter Server will be 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.
  10. Reboot the server. The server will return as passive with vCenter Server Heartbeat started and vCenter Server services will be stopped.
  11. Upgrade all existing components

On the Primary Server (Assuming a Successful Upgrade of the Secondary Server)

  1. Install vCenter Server 4.0 running the Setup.exe

    Note: If upgrading from VirtualCenter Server 2.5 run VMware-VIMSetup.exe to upgrade the VI Client, vCenter Server, and vCenter Server and all installed extensions.

    Important: Before proceeding with the database upgrade, perform a database backup.
  2. Upgrade the database.
  3. If asked, Do NOT reboot the server at this point as it will be rebooted at step 5.

    Note: During the upgrade process, the logon account might be reset to the default (Local/System).
  4. Open the Service Control Manager, and verify that the vCenter Server service logon account is the correct. If necessary, make corrections.
  5. Reboot the Server. The server will return as active with vCenter Server Heartbeat and vCenter Server services started.
  6. Verify vCenter Server is operational.

    Note: If this is a WAN installation, the Managed IP address needs to be removed from the vCenter Server settings. To do this:
    1. Open the 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 .
  7. Launch the vCenter Server Heartbeat Console.
    1. Using the vCenter Server Heartbeat Console, manually run the Protected Service Discovery task.
    2. Verify that the system completes the Full System Check.
  8. Upgrade all existing components.

Testing the vCenter Server Upgrade on the Secondary Server

To test the success of the vCenter Server upgrade on the Secondary server, follow the steps below.

  1. Trigger an auto-switchover so that the Secondary server becomes active.
    1. Launch the vCenter Server Heartbeat Console.
    2. Navigate to Applications: 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.
  2. vCenter Server should start and replication should be stopped.
  3. If vCenter Server starts successfully click Start Replication .
  4. When the system is synchronized, perform a switchover to make the Primary server active.

If vCenter Server Fails to Start on the Secondary Server

If vCenter Server fails to start on the Secondary server, follow the steps below.

  1. Shutdown vCenter Server Heartbeat.
  2. Start the Configure Server wizard on the Secondary server, select the Machine tab, and select Primary as the Active server (setting the Secondary's role to passive).
  3. Start vCenter Server Heartbeat on the Secondary server.
  4. Start the Configure Server wizard on the Primary server, select the Machine tab, and select Primary as the Active server (setting the Primary's 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.

Testing the vCenter Server Upgrade on the Secondary Server

To test the success of the vCenter Server upgrade on the Secondary server, follow the steps below.

  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.
  2. vCenter Server should start and replication should be stopped.
  3. If vCenter Server starts successfully press the Start Replication button.
  4. When the system is synchronized, perform a switchover to make the Primary server active.

If vCenter Server Fails to Start on the Secondary Server

If vCenter Server fails to start on the Secondary server, follow the steps below.

  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.


Applies To

VirtualCenter Server 2.5
vCenter Server 4.0
vCenter Server Heartbeat 5.5, 6.3, 6.4


Related Information

vCSHB-Ref-1765

KBID-1765

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.