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 and applying Service Packs to SQL Server protected by vCenter Server Heartbeat when the vCenter Server database is remote from the vCenter Server (1034077)

Purpose

This article provides steps to install an upgrade or apply Service Packs to SQL Server protected by vCenter Server Heartbeat when the vCenter Server database is remote from the vCenter Server.

Resolution

Notes:
  • Prior to attempting this upgrade, 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.
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:
 
On the Primary (active) Server:
  1. Uninstall the existing version of the SQL Server plug-in using the steps in Uninstalling Plug-ins in vCenter Server Heartbeat (1034078).
    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.
    • vCenter Server Heartbeat returns as active, with heartbeat in the started state.
    • The SQL Server starts.
    • The SQL Server upgrade / Service Pack resumes.

  6. If the server was restarted in 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 the 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.
    • The server returns as passive with vCenter Server Heartbeat in the stated state.
    • The SQL Server services stop.
    • The SQL Server upgrade resumes.

  3. If server was restarted in 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.
To finalize the installation and synchronize vCenter Server Heartbeat:
  1. On the Secondary (passive) server, start vCenter Server Heartbeat.
  2. On the 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 that they are set to Manual.
  4. In Service Control Manager window on the Secondary (passive) server, verify that all protected application services are stopped and that they are set to Manual.
  5. On the 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.

Additional Information

vCSHB-Ref-1998

Update History

03/14/2013 - Added vCenter Server Heartbeat 6.5.x to Products

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

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