VMware vCenter Server Heartbeat - How to Restart the Primary (active) Server

Follow

Summary

This Knowledgebase article provides information on how to restart a Primary (active) server running vCenter Server Heartbeat.


More Information

When restarting a server running vCenter Server Heartbeat, it is important to follow the VMware recommended procedure to prevent an Unclean shutdown of vCenter Server Heartbeat, which may result in some data loss.

The following procedure assumes that the vCenter Server Heartbeat server pair is running with the Primary server as active and the Secondary server as passive.

Procedure

To restart the Primary (active) server, follow the steps below:

  1. Launch the vCenter Server Heartbeat Console , by right-clicking the vCenter Server Heartbeat system tray icon and selecting Manage Server , or by selecting the same option from Start -> All Programs -> VMware -> VMware vCenter Server Heartbeat .
  2. Login at the prompt. Select the server pair you wish to manage.
  3. On the Server: Summary page, check that the Files and Registry are both shown as Synchronized , and then click Shutdown .
  4. At this point, the Shutdown Options dialog is displayed. Select the Primary server to shutdown and select the option Do not stop protected applications and click OK . This will leave the application(s) running on the active server as vCenter Server Heartbeat exits.  If you would like to troubleshoot the server with vCenter Server Heartbeat and the protected application(s) offline, you should continue to step 5, and later follow the instructions below to restore default vCenter Server Heartbeat startup settings. If not please skip the next step and continue to step 6.
  5. Set the VMware vCenter Server Heartbeat service to Manual , and restart the server. This will prevent vCenter Server Heartbeat , and the protected applications, from starting as the server boots. Continue to step 6.
  6. Restart both the Primary and Secondary servers. If you followed step 5 above, continue to Section 2, if not continue to step 7 below.
  7. The servers will restart, reconnect, and perform a Full System Check. This may take some time to complete depending on the amount of protected data and bandwidth available. If this does not happen, you may need to contact your VMware Support representative for further instructions.

To restore the default vCenter Server Heartbeat startup settings:

Note: All protected applications will still be unavailable at this point. Troubleshooting can now be initiated with vCenter Server Heartbeat and the protected applications offline. Once finished follow the steps below to restore default settings.

  1. Check that the server role on the Primary (active) server is correctly set. Note: To do this, the vCenter Server Heartbeat service must not be running.
  2. Right-click the vCenter Server Heartbeat system tray icon and select Server Configuration wizard.
  3. From the Machine tab, check that the Primary server is selected as active. If not, this should be changed so the Primary server is the active server. This should already be the case if the server was active before stopping vCenter Server Heartbeat . However, if the service failed to stop cleanly, it may be set to passive.
  4. Click Finish .
  5. Check that the server role on the Secondary (passive) server is correctly set. Note: To do this, the vCenter Server Heartbeat service must not be running.
  6. Right-click the vCenter Server Heartbeat system tray icon and select Server Configuration wizard.
  7. From the Machine tab, check the Primary server is selected as the active server. If not this should be changed to reflect the Primary server as active. This should already be the case if the server was passive before stopping vCenter Server Heartbeat .
  8. Click Finish .
  9. On the Primary (active) server, start vCenter Server Heartbeat . Right-click the vCenter Server Heartbeat system tray icon and select Start vCenter Server Heartbeat . Ensure that the application services have started on the Primary (active) server. The Services that are protected by vCenter Server Heartbeat are listed in the Applications: Services page of vCenter Server Heartbeat Console.
  10. On the Secondary (passive) server, start vCenter Server Heartbeat . Right-click the vCenter Server Heartbeat system tray icon and select Start vCenter Server Heartbeat . Note: Application services should NOT start on this server, as it is passive, and not servicing client requests. Ensure that all protected services are stopped. The Services that are protected by vCenter Server Heartbeat are listed in the Application: Services page of the vCenter Server Heartbeat Console.
  11. Check using the Windows Services Management Console that the VMware vCenter Server Heartbeat service is set to Automatic and Started on both servers. If the service is not set to Automatic set this now.
  12. Login to the server pair, and check that the servers have connected and started replication.
  13. Launch the vCenter Server Heartbeat Console, by right-clicking the vCenter Server Heartbeat system tray icon and selecting Manage Server , or by selecting the same option from Start -> All Programs -> VMware -> VMware vCenter Server Heartbeat .
  14. Login at the prompt. Select the server pair you wish to manage.
  15. On the Server: Summary page, check that the File System Status and Registry Status are both replicating and the direction is from Primary (active) server to the Secondary (passive) server. The Registry Status should quickly display as Synchronized . The File System Status may take much longer depending on the amount of protected data.
  16. Logout of the vCenter Server Heartbeat C onsole by clickin the "X" in the top right corner of the page and following the on-screen prompts.
  17. The server pair has now been restored to its default startup settings, and should be replicating normally. If this does not happen, you may need to contact your VMware Support representative for further instructions.


Applies To

VMware vCenter Server Heartbeat 6.3 and later


Related Information

None

KBID-1667

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.