VMware vCenter Server Heartbeat - Upgrading and Applying Service Packs to SQL Server Protected by VMware vCenter Server Heartbeat



This Knowledgebase article provides procedures for upgrading or applying Service Packs to a SQL Server protected by vCenter Server Heartbeat where the vCenter Server database is remote from the vCenter Server.

More Information

Prior to attempting this upgrade you should read the entire procedure.

The procedure assumes that the SQL database is installed on a remote server and not installed on the same server as vCenter Server.

Supported Applications and Versions

  • SQL Server
    • For Service Packs on SQL Server 2005 or 2008
    • For upgrades from SQL Server 2005 or 2008


Prior to upgrading SQL Server with vCenter Server Heartbeat installed, check with VMware for the latest version of SQL Server plug-in and verify that the plug-in supports the new application version or Service Pack. To upgrade SQL Server with vCenter Server Heartbeat installed, perform the following steps:

On the Primary (active) Server

  1. Uninstall the existing version of the SQL Server plug-in using the procedure in vCSHB-Ref-2067 - How to Uninstall Plug-ins in vCenter Server Heartbeat .
    1. Wait for the plug-in to uninstall completely and remove all protection.
    2. Check the Application Event Log events to ensure this process has completed on the passive server.
  2. Install the latest plug-in for SQL Server.
    1. Wait for the plug-in installation process to complete.
    2. Verify that all services and filters are added.
  3. Shutdown vCenter Server Heartbeat, opting to leave the protected applications running.
  4. Upgrade the SQL Server or apply the Service Pack by running Setup.exe .
  5. Restart the server if requested.
    1. vCenter Server Heartbeat will return as active, with heartbeat in the started state.
    2. SQL Server will start.
    3. The SQL Server upgrade / Service Pack will resume.
  6. If the server was restarted at Step 5, shutdown vCenter Server Heartbeat opting to leave the protected application running. If the server was not restarted, continue to Step 7.
  7. Allow the SQL Server upgrade / Service Pack to complete.
  8. Once complete, start SQL Server services.

On Secondary (passive) Server

NOTE: Use identical Setup program upgrade parameters on both servers.
  1. Upgrade SQL Server by running Setup.exe .
  2. Restart the server if required.
    1. The server will return as passive with vCenter Server Heartbeat in the stated state.
    2. The SQL Server services will be stopped.
    3. The SQL Server upgrade will resume.
  3. If server was restarted at Step 2, stop vCenter Server Heartbeat.
  4. Allow the SQL Server upgrade to complete.

    NOTE: Do not start SQL Server services when the upgrade has completed.

Finalize Installation and Synchronize vCenter Server Heartbeat

  1. On Secondary (passive) server, start vCenter Server Heartbeat.
  2. On Primary (active) server, start vCenter Server Heartbeat.
  3. In Service Control Manager window, on the Primary (active) server, verify that all protected application services are started and set to 'Manual'.
  4. In Service Control Manager window, on the Secondary (passive) server, verify that all protected application services are stopped and set to 'Manual'.
  5. On Primary (active) server, launch the vCenter Server Heartbeat Console.
    1. Manually run the 'Protected Service' and 'Registry' discovery task for the SQL Server sponsor
    2. Verify that all newly installed components and services are protected.
    3. Allow vCenter Server Heartbeat to complete the full system check.

Applies To

vCenter Server Heartbeat All Versions
SQL Server v2005 or 2008

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.