Administrator Guide vCenter Server Heartbeat 6.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
Administrator Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.
Contents About This Book 5 1 Introduction 9 vCenter Server Heartbeat Concepts 9 vCenter Server Heartbeat Protection Levels 10 vCenter Server Heartbeat Communications 13 vCenter Server Heartbeat Switchover and Failover Processes 15 2 Configuring vCenter Server Heartbeat 19 Launching the Configure Server Wizard 20 Configuring the Machine 21 Configuring the VMware Channel 22 Configuring Public IP Addressing 24 Managing vCenter Server Heartbeat License Keys 26 Configuring the Logs 27 3 Server Protection 29
Administrator Guide 6 Status and Control 55 About vCenter Server Heartbeat Console 55 Working with Groups 57 Working with Pairs in vCenter Server Heartbeat Groups 57 Reviewing the Status of vCenter Server Heartbeat Groups and Pairs 60 Exiting vCenter Server Heartbeat Console 60 Shutting Down Windows Without Stopping vCenter Server Heartbeat 60 Controlled Shutdown 61 vSphere Web Client Plug-in 61 Uninstalling vCenter Server Heartbeat 63 7 Performance Protection 65 Applications: Rules Tab 65 8 Data Protect
About This Book The Administrator Guide provides information about configuring VMware vCenter Server Heartbeat server network protection, application protection, data protection, Split-brain Avoidance, and more. To help you protect your VMware vCenter Server, this book provides an overview of the protection offered by vCenter Server Heartbeat and the actions that vCenter Server Heartbeat can take in the event of a network, hardware, or application failure.
Administrator Guide ■ Chapter 4 — Network Protection describes how vCenter Server Heartbeat protects against network failure and provides a way to monitor communication status. It also explains how to configure public network connection checks and maximum server time difference. ■ Chapter 5 — Application Protection discusses how vCenter Server Heartbeat maintains the protected application environment ensuring that applications and services stay alive on the network.
About This Book Support Offerings Go to www.vmware.com/support/services to find out how VMware support offerings can help meet your business needs. VMware Professional Services Go to www.vmware.com/services to access information about educational classes, certification programs, and consulting services. VMware Education Services courses offer extensive hands-on labs, case study examples, and course materials designed for use as on-the-job reference tools.
Administrator Guide 8 VMware, Inc.
Introduction 1 This chapter includes the following topics: ■ “vCenter Server Heartbeat Concepts,” on page 9 ■ “vCenter Server Heartbeat Protection Levels,” on page 10 ■ “vCenter Server Heartbeat Communications,” on page 13 ■ “vCenter Server Heartbeat Switchover and Failover Processes,” on page 15 vCenter Server Heartbeat Concepts vCenter Server Heartbeat is a Windows based service specifically designed to provide high availability protection for vCenter Server configurations without requiring any
Administrator Guide Managing the Primary and Secondary Servers To allow management of vCenter Server Heartbeat server pairs using standard network, domain policy, and domain management procedures, vCenter Server Heartbeat is deployed so that Primary and Secondary servers use unique domain names. Each domain name must differ from the fully qualified domain name used by the original vCenter or SQL Servers.
Chapter 1 Introduction vCenter Server Heartbeat provides all five protection levels continuously, ensuring all facets of the user environment are maintained at all times, and that vCenter Server continues to operate through as many failure scenarios as possible.
Administrator Guide If vCenter Server should fail, vCenter Server Heartbeat first tries to restart the application on the active server (1) in Figure 1-2. If the application does not successfully restart, vCenter Server Heartbeat initiates a switchover (2) in Figure 1-2. Refer to “vCenter Server Heartbeat Switchover and Failover Processes,” on page 15 for further information about the switchover process. Figure 1- 2.
Chapter 1 Introduction vCenter Server Heartbeat intercepts all file system I/O operations on the active server. If the intercepted write and update operations are within the protected set, these are placed in a queue on the active server referred to as the active server’s “Send Queue”, pending transmission to the passive server. Each request is numbered to maintain its order in the queue.
Administrator Guide Figure 1- 4. Single NIC Configuration Figure 1- 5. Multi-NIC Configuration The IP address a client uses to connect to the active server (the Principal (Public) IP address) must be configured as a static IP address and not DHCP (Dynamic Host Configuration Protocol) enabled. In Figure 1-4 and Figure 1-5, the Principal (Public) IP address is configured as 192.168.1.127.
Chapter 1 Introduction The NICs that support connectivity across the VMware Channel can be standard 100BaseT Ethernet cards providing a throughput of 100 Mbits per second across standard Cat-5 cabling. In its most basic form, a dedicated channel requires no hubs or routers, but the direct connection requires crossover cabling.
Administrator Guide 4 vCenter Server Heartbeat causes the newly passive server to begin accepting updates from the active server. 5 vCenter Server Heartbeat starts the same protected applications on the new active server. The protected applications become accessible to users.
Chapter 1 Introduction During the automatic failover, the passive server performs the following steps: 1 Apply any intercepted updates currently in the passive server’s receive queue as identified by the log of update records that are saved on the passive server but not yet applied to the replicated files. The amount of data in the passive server’s receive queue affects the time required to complete the failover process.
Administrator Guide 18 VMware, Inc.
Configuring vCenter Server Heartbeat 2 After installation of vCenter Server Heartbeat, initial operational configuration is performed using the vCenter Server Heartbeat Console. The VMware vCenter Server Heartbeat – Server Configuration wizard (Configure Server wizard) sets up and maintains communications between the vCenter Server Heartbeat servers. After the system is set up and is functioning correctly, you do not normally need to reconfigure the system.
Administrator Guide Launching the Configure Server Wizard The VMware vCenter Server Heartbeat - Server Configuration wizard (Configure Server wizard) is used to modify the communications between the Primary and Secondary servers and reconfigure other components of vCenter Server Heartbeat. When using the Configure Server wizard, vCenter Server Heartbeat must not be running. Procedure 1 Stop vCenter Server Heartbeat.
Chapter 2 Configuring vCenter Server Heartbeat Configuring the Machine The Machine tab is used to set the Server Identity, Active Server, and Client Connection Port. Configuring the Machine Identity The machine identity is either Primary or Secondary and once assigned does not change during the life of the server. Caution The machine Identity should only be changed when directed to do so by VMware Support or when instructed to do so by a knowledge base article.
Administrator Guide Configuring the Client Connection Port Clients such as the vCenter Server Heartbeat Console use the Client Connection Port to connect to vCenter Server Heartbeat. Do not change this port unless another application is using it. Procedure ◆ To change the Client Connection Port, click the Machine tab, edit the default entry (52267) and click Next or Finish.
Chapter 2 Configuring vCenter Server Heartbeat 4 To change the VMware Channel IP addresses, select and edit the entry in the table. 5 Click Next or Finish. Configuring the Default Channel Port VMware Channel uses the Default Channel Port to communicate between the Primary and Secondary server. Do not change this port unless another application is using it. Procedure ◆ To change the Default Channel Port, click the Channel tab, edit the default entry (57348), and click Next or Finish.
Administrator Guide Procedure ◆ To change Low Bandwidth Optimization after installation, select the Channel tab of the Configure Server wizard and use the HA/DR Topology drop-down to select the appropriate topology. Click Next or Finish to accept changes. Figure 2- 4. Configure Server wizard - Channel tab Configuring Public IP Addressing vCenter Server Heartbeat servers are typically configured with one shared Principal (Public) IP address in a LAN or two Principal (Public) IP address in a WAN.
Chapter 2 Configuring vCenter Server Heartbeat 3 In the NIC field, select the Principal (Public) network connection in the drop-down. Note Adjacent IP addresses should be reserved and used for the Principal (Public) IP address and the management IP addresses for the Primary and Secondary servers when installing vCenter Server Heartbeat on servers running Windows Server 2008. 4 Enter the Principal (Public) IP address in the Public IP field.
Administrator Guide Managing vCenter Server Heartbeat License Keys To manage vCenter Server Heartbeat license keys, select the License tab of the Configure Server wizard. Adding an Entry to the License Keys Table Procedure 1 Click the Add Row icon and enter your VMware vCenter Server Heartbeat serial number. 2 Manually type or paste (using Ctrl-V) your license key into the table. 3 Click Next or Finish. Figure 2- 6. Configure Server wizard — License tab 26 VMware, Inc.
Chapter 2 Configuring vCenter Server Heartbeat Configuring the Logs vCenter Server Heartbeat allows you to change the default location for the logs used for storing data in the queue. Configuring Message Queue Logs The server temporarily stores replication data received in the passive server’s receive queue and the replication data waiting in the active server’s send queue in message queue logs. This configuration only affects the local server.
Administrator Guide If using a dedicated disk for log files, consider disabling the quota. To do this, set the quota to zero. If vCenter Server Heartbeat runs out of disk space, it must be shut down before it can resume replication. Set the quota with sufficient overflow space so vCenter Server Heartbeat can stop replicating gracefully. Procedure ◆ 28 To configure Maximum Disk Usage, click the Logs tab, type the maximum dedicated disk space allocated for message queue log files, and click Finish.
3 Server Protection Protection against operating system or hardware failure affecting the active server is facilitated by two instances of the vCenter Server Heartbeat that monitor one another by sending “I’m alive” messages and reciprocating with acknowledgments over the VMware Channel. If the passive server detects that this process (the heartbeat) has failed, an automatic switchover is initiated.
Administrator Guide Table 3- 1. System Status Status Icon Description Not replicating File and registry replication is in the process of stopping and all protected applications may be closing down. Switching active server The system is in the process of performing a switchover. Connecting to peer server VMware Channel connections have been established between the two servers. Disconnecting from peer server VMware Channel connections have been lost between the two servers.
Chapter 3 Server Protection Monitoring the Status of Servers The Server: Monitoring page provides additional information about the status of communications between the servers within the pair. The graphical representation provides an overview of the status of communications between the servers. A green channel icon indicates that the channel is connected and healthy while a yellow dashed channel icon indicates that communications are not operational between the indicated servers.
Administrator Guide Procedure 1 Navigate to Server: Monitoring > Configure Failover to open the Server Monitoring: Failover Configuration dialog. 2 The Failover timeout can be customized by changing the default value (60 seconds) to a custom value.
Chapter 3 Server Protection 3 The passive server attempts to ping the configured waypoints on the Public network to determine if the it is still visible on the Public network. If pings to the waypoints on the Public network are unsuccessful, the passive server will remain passive and take no action. If the pings to the waypoints on the Public network are successful, the passive server will continue to the next step.
Administrator Guide Upon detection of missed heartbeats vCenter Server Heartbeat performs the following steps: 1 As soon as the active server detects that the VMware Channel is experiencing missed heartbeats, it will determine if a valid failover target (the passive server) is present. Simultaneously, once the passive server detects missed heartbeats, it will determine if it is a valid failover target.
Chapter 3 Server Protection Configuring Split-brain Avoidance Split-brain Avoidance ensures that only one server becomes active if the VMware Channel connection is lost, but both servers remain connected to the Principal (Public) network. Split-brain Avoidance works by pinging from the passive server to the active server across the Principal (Public) network. If the active server responds, the passive server does not failover, even if the VMware Channel connection is lost.
Administrator Guide Since a managed switchover cannot be performed during synchronization, it is important to review the queue information prior to attempting a managed switchover. If the queues are large, file operations on the active server are high and for this reason it may be prudent to delay a managed switchover due to the length of time required to completely clear the queue. Queue lengths can be viewed in the Data: Traffic/Queues page of the vCenter Server Heartbeat Console.
Chapter 3 Server Protection 5 Resolve the list of possible failures. 6 Restart this server and reconnect or enable the network card again. 7 After restart, check that the Taskbar icon now reflects the changes by showing P / – (Primary and passive). 8 On the Secondary active server or from a remote client, launch vCenter Server Heartbeat Console and confirm that the Secondary server is reporting as active.
Administrator Guide On the Secondary Server Procedure 1 Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the list. Note Before proceeding with the database upgrade, perform a backup of the database. 2 When asked, select Do not overwrite, leave the existing database in place. 3 Continue with vCenter Server installation and record all configuration settings used.
Chapter 3 Server Protection Procedure 1 Change the Role of the server to Primary/active: a Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. In the Active server section select Primary. b Using the Service Control Manager, start the VMware vCenter Server Heartbeat service. c Wait until all protected services are started. d Using the Service Control Manager, stop the VMware vCenter Server Heartbeat service.
Administrator Guide 40 VMware, Inc.
Network Protection 4 vCenter Server Heartbeat proactively monitors the network by polling up to three predefined nodes to ensure that the active server is visible on the network.
Administrator Guide Configuring Public Network Connection Checks The Network Monitoring page allows you to view the status of the network and make adjustments to the IP addresses used to ping multiple servers within the network. The Principal (Public) network monitoring feature, previously discussed, is enabled by default during the installation of VMware vCenter Server Heartbeat.
Chapter 4 Network Protection Setting Max Server Time Difference vCenter Server Heartbeat generates a warning if the Primary and Secondary server system clocks are not synchronized. The threshold for time difference can be configured on the Server: Summary page. Procedure 1 Select the Server: Summary tab and click Configure to display the Server: Summary Configure dialog.
Administrator Guide 44 VMware, Inc.
Application Protection 5 vCenter Server Heartbeat incorporates an Application Management Framework (AMFx) to manage vCenter Server Heartbeat plug-ins. The AMFx provides additional functions while maintaining the traditional stability of VMware software. Use the AMFx to install and remove plug-ins on the fly while vCenter Server Heartbeat continues to provide protection to currently installed applications. The AMFx also employs sponsorship for protected application files and services.
Administrator Guide Procedure ◆ After acknowledging the problem and solving it, click Clear in the Application Health pane of the Applications: Summary page to reset the Application Health status. The status updates to provide the actual current Application Health status. Viewing Application Status After an application starts and is running, you can view its status in the Applications pane of the Applications: Summary page.
Chapter 5 Application Protection Manually Stop and Start Applications Procedure ◆ To stop all protected applications or start the stopped applications, at the top of the Applications: Summary page, click the appropriate button. Option Description Stop Applications The protected applications set stops. You can view the progress of the stopping in the Applications Log pane. Start Applications The applications start. You can view the progress of starting in the Applications Log pane.
Administrator Guide Reviewing the State of an Application After an application successfully starts and is running, you can view the application state in the Applications: Summary page. If an application fails, right-click the event in the Applications Log and click on Properties to invoke the Event Properties dialog and investigate the failure. Reviewing the Applications Log The Applications Log helps troubleshoot the protected application environment.
Chapter 5 Application Protection Adding a Service To protect a service that was not automatically added by vCenter Server Heartbeat during installation, the service must be added through the vCenter Server Heartbeat Console and be in a Running state. Procedure 1 Right-click on a service and select Add from the menu or click Add on Applications: Services page to invoke the Add Service dialog. The Name drop-down list contains a list of all currently running services.
Administrator Guide Checking the Status of Services The Applications: Services page displays the status of all protected services. The status shows both the target and actual state for both the Primary and Secondary servers and the Failure Counts for both servers. Unprotecting User Defined Services and Stopping Monitoring To unprotect and stop monitoring user defined services: Procedure 1 Navigate to the Applications: Services page and select the user defined service. 2 Click Edit.
Chapter 5 Application Protection Applications: Tasks Tab Tasks are a generalization and extension of start, stop, and monitor scripts. Task types are determined by when the tasks run, and include the following: ■ Network Configuration – This is the first type of task that runs when applications start and is intended to launch dnscmd or DNSUpdate. The task can launch a batch script containing multiple dnscmd commands.
Administrator Guide Editing a Task You can edit the interval of a task or disable a task. To edit a task: Procedure 1 Right-click on an existing task and select Edit from the menu or select the task and click Edit at the top of the pane to invoke the Edit Task dialog. 2 Edit the parameters of the task. 3 Click OK. Removing a Task Procedure 1 To remove a task, select the task on the Applications: Task page and click Remove. A confirmation message is displayed. 2 Click Yes.
Chapter 5 Application Protection Viewing the User Accounts Procedure 1 On the Applications: Task page, click User Accounts to invoke the User Accounts dialog and view the current User accounts used to run tasks. 2 Click Close to exit the dialog. Adding a User Account Procedure 1 On the Applications: Tasks page, clickUser Accounts to invoke the User Accounts dialog. 2 Click Add to invoke the Add User dialog.
Administrator Guide 3 Type a path to the plug-in location or click Browse to navigate to the plug-in location. The path statement is case-sensitive. 4 Click OK. Editing a Plug-in vCenter Server Heartbeat allows you to edit the configuration of user installed plug-ins. Procedure 1 On the Applications: Plug-ins page, right-click on an existing plug-in from the Plugins list and select Edit from the menu or select the plug-in and click Edit at the top of the pane to invoke the Edit Plugin dialog.
Status and Control 6 vCenter Server Heartbeat operates over a Pair of vCenter Server Heartbeat servers and is administered in these Pairs. The vCenter Server Heartbeat Console is used to carry out the day-to-day administration of one or more Pairs of servers.
Administrator Guide Starting vCenter Server Heartbeat Console You can start vCenter Server Heartbeat Console from any server in the vCenter Server Heartbeat Pair. Procedure 1 Right-click the VMware vCenter Server Heartbeat interactive status icon on the Windows too tray (located on the right side of the Windows tool bar). The vCenter Server Heartbeat quick access menu opens. 2 Select Manage Server. The vCenter Server Heartbeat Console opens in a window and shows the Heartbeat Servers (overview) pane.
Chapter 6 Status and Control 4 Click OK. A confirmation message appears. 5 Click Yes to confirm the changes and restart vCenter Server Heartbeat Console to apply the new font settings. Click No to restart later; the changes will be applied the next time vCenter Server Heartbeat Console is started. Working with Groups vCenter Server Heartbeat allows you to Group server pairs based upon logical organization such as business function or category.
Administrator Guide Adding a New Connection The Add Connection feature in the vCenter Server Heartbeat Console allows you to add a new Pair Connection to an existing vCenter Server Heartbeat Group. Procedure 1 In the navigation panel, select the vCenter Server Heartbeat Group to receive the new connection. Click Add Connection in the tool bar, select Add Connection from the File menu, or right-click an existing group in the navigation panel and select Add Connection to invoke the Add Connection dialog.
Chapter 6 Status and Control Editing a Connection The Edit Connection feature in the vCenter Server Heartbeat Console allows you to change the Port Number for existing connections. Procedure 1 In the navigation panel, select the connection you want to change and select Edit Connection from the File menu or right-click an existing connection in the navigation panel and select Edit Connection from the menu to display the Edit Connection dialog.
Administrator Guide Editing User Name and Password Settings The Edit User Name and Password feature in vCenter Server Heartbeat Console allows you to change the User Name and Password settings used to connect to a given Pair. Procedure 1 Select a connection in the navigation panel and select Edit User Name and Password from the File menu or right-click on the Connection in the navigation panel and select Edit User Name and Password from the menu to display the Edit User Name and Password dialog.
Chapter 6 Status and Control Controlled Shutdown A Controlled Shutdown is the process where the VMware vCenter Server Heartbeat service is able to delay a system shutdown for a sufficient period to perform all of the necessary steps required to stop the applications and replication in a synchronized state. The Controlled Shutdown is intended for situations where an unattended planned shutdown of the server is necessary.
Administrator Guide 5 Select the Monitor tab of the vSphere Client. The Monitor sub-tabs are displayed. 6 Select the Heartbeat sub-tab of vSphere Web Client. The Heartbeat Plug-in content is displayed. Figure 6- 1. vSphere Web Client Heartbeat Plug-in Performing a Switchover Using vSphere Web Client Procedure 1 Navigate to the Heartbeat sub-tab in the vSphere Web Client. 2 Click either Make Primary Active or Make Secondary Active as appropriate. A confirmation dialog is displayed.
Chapter 6 Status and Control Starting or Stopping Replication Using vSphere Web Client Procedure 1 Select the Heartbeat tab of vSphere Web Client. 2 Click either Stop Replication or Start Replication as appropriate. Uninstalling vCenter Server Heartbeat Under normal conditions it is not necessary to uninstall vCenter Server Heartbeat. Should the need arise, vCenter Server Heartbeat can be uninstalled easily allowing you to retain current log information.
Administrator Guide 9 Click Finish. A restart is required to finish removing certain components and to apply new settings. When you are prompted to perform this restart, click Yes. 10 After the server has restarted, launch a web browser and navigate to http:///mob 11 Click Content. 12 Click ExtensionManager. 13 In the Properties pane, identify the values extensionlist[“com.vmware.heartbeat”] and extensionlist[“com.neverfail.
Performance Protection 7 Performance Protection describes how vCenter Server Heartbeat monitors system and application attributes to prevent an unexpected system or application failure. Applications: Rules Tab Rules are implemented by plug-ins (there are no user-defined rules). Configure rule actions to trigger the rule that performs specific tasks. Rules have two trigger properties: ■ Timed – They must evaluate as true continuously for the specified duration to trigger.
Administrator Guide Editing a Rule Rules are implemented by plug-ins and cannot be created by users. Each plug-in contains a default set of rules with options that may be modified by the user. Procedure 1 Right-click on the rule and select Edit from the menu or click Edit at the top of the pane. 2 Edit the parameters of the rule and click OK. Rules Installed by vCenter Server Heartbeat Plug-ins The following plug-ins implement the rules listed.
Chapter 7 Performance Protection ■ RedirectorBytesTotalPerSec ■ RedirectorNetworkErrorsPerSec ■ ServerBytesTotalPerSec ■ ServerWorkItemShortages >= 3 (if the rule for server work item shortages is triggered, consult Microsoft documentation on setting the registry values for InitWorkItems or MaxWorkItems accordingly) ■ ServerWorkQueueLength ■ SystemContextSwitches VMware, Inc.
Administrator Guide 68 VMware, Inc.
Data Protection 8 vCenter Server Heartbeat can protect many permutations or combinations of file structures on the active server by the use of custom Inclusion and Exclusion filters configured by the administrator. The filter driver identifies files to protect and disk I/O operations to intercept and replicate to the passive server. Use this driver to filter files for inclusion in or exclusion from the replication process.
Administrator Guide Table 8- 1. File and Registry Synchronization Status Icon Description The file is verified and successfully synchronized. The file is not synchronized on the active and passive servers. This state often follows a failover and requires manual synchronization and verification. The file or folder has not been checked because a full system check has not been performed or the system check has not yet reached the file or folder.
Chapter 8 Data Protection Initiating a Full System Check You can verify and synchronize the entire protected file set using the Full System Check feature of vCenter Server Heartbeat Console. A Full System Check performs the same block level check of all the files set by the file filters in the initial startup synchronization and verification. Procedure 1 Click Full System Check in the File Hierarchy pane to initiate a Full System Check.
Administrator Guide Initiating File Synchronization Manually The Data: Replication File Hierarchy pane displays files that were detected as out of synchronization. Procedure ◆ To initiate file synchronization manually, perform one of the following: ■ To synchronize the specified files, click Synchronize. ■ Select multiple files with the Shift or Ctrl keys and click Synchronize. ■ Select a folder and select Including Subdirectories to synchronize files within folders and click Synchronize.
Chapter 8 Data Protection Checking for Orphaned Files vCenter Server Heartbeat provides the opportunity to check the system for orphaned files and either notify the administrator or to delete the orphaned files. Orphaned files are those files in a protected set that exist on the passive server but do not exist in the protected set on the active server in a pair.
Administrator Guide File Filters File filters dictate which files are protected and the disk I/O operations to intercept and replicate to the passive server. File filters also allow you to customize the inclusion and exclusion of files from the replication process. The File Filters pane of the Data: File Filters page allows you to set up and manage Inclusion and Exclusion filters. The File Filters pane contains three columns: Table 8- 2.
Chapter 8 Data Protection Adding a User-Defined Exclusion Filter Exclusion filters create a subset of an Inclusion Filter to specify items to exclude from protection. Procedure 1 In the Data: File Filters pane, click Add Exclusion Filter to display the Add Exclusion Filter dialog. 2 Type the complete path and pattern, specify a pattern containing wildcards, or click Browse to locate the file or folder. 3 Click OK.
Administrator Guide 76 VMware, Inc.
Alerts and Events 9 vCenter Server Heartbeat can notify Administrators of potential problems or when specific events occur by sending a custom configured predefined alerts and route event logs to a remote Administrator as required.
Administrator Guide 4 If the SMTP servers require authentication to accept and forward SMTP messages, select Mail Server requires authentication and specify the credentials for an appropriate authenticated user account. 5 Click OK. Configuring Alert Email Triggers vCenter Server Heartbeat allows you to configure email recipients in the On Red Alert, On Yellow Alert, and On Green Alert tabs of the Configure Alerts dialog after configuring the trigger levels and the email server.
Chapter 9 Alerts and Events Configuring Alert Email Triggers (Alternate Method) vCenter Server Heartbeat allows an alternate method to configure sending an alert notification that allows the Administrator to create an event in the Application Event Log that can be customized to include vCenter Server Heartbeat specific information variables. Procedure 1 Select Run Command under the pertinent alert state. 2 Browse to the script to run or use a command line argument to run on the alert trigger.
Administrator Guide 3 Type a path and filename or click Browse and navigate to the file. 4 Adjust the length of the event list to meet your needs by increasing or decreasing the value (the default is 300 events) in the Record at most field. 5 Click OK. Configuring Log File Email Recipients Use vCenter Server Heartbeat to email the log to specified personnel at predetermined intervals.
Chapter 9 Alerts and Events Reviewing Event Logs The Event Log pane of the Logs page lists events logged chronologically by default. The Event Log shows the time an event happened, the type, the source, its importance, and its detail. The display order for events can be sorted either descending or ascending by clicking on the column heading. Since the detail in the data grid is truncated, it may be necessary to review the log in more detail.
Administrator Guide Filtering log events by date and time range Procedure 1 Select the Only show events from check box and adjust the start date, end date, and times. 2 Click OK. Table 9- 3. Event Log Buttons Icon Purpose To export the list to a comma-separated variable file, click Export event log at the top left of the Log Details data grid. You can configure the filename and path to export the data in the Configuration tab. To immediately email the list, click E-mail.
Troubleshooting 10 You can use a variety of procedures for diagnosing and fixing problems that you may encounter when using vCenter Server Heartbeat. You can use troubleshooting procedures to investigate the causes of such problems and attempt to correct them yourself, or you can obtain assistance from VMware Technical Support. The following unexpected behaviors illustrate Problems, Causes, and Solutions for a given scenario.
Administrator Guide ■ A name conflict occurs on a server pair running vCenter Server Heartbeat. In a WAN environment the Primary and Secondary servers connect to the network using different IP addresses. However, if the servers are running with the same name and are visible to each other across the WAN, a name conflict occurs ■ Clients (for example, VI Client, ESX, etc.
Chapter 10 Troubleshooting 11 Restart this server. As the server restarts, it connects to the passive server and starts replication. The active server overwrites data on the passive server. 12 Start vCenter Server Heartbeat, if required, and check that the Task bar icon now reflects the changes by showing P / A (Primary and active) or S / A (Secondary and active). 13 Start vCenter Server Heartbeat Console. 14 Check that the servers have connected and replication has started.
Administrator Guide 4 On the server to make passive, start the Server Configuration wizard, and confirm the passive server. Do not change the identity (Primary or Secondary). 5 Restart the passive server. All protected application services stop. 6 Start vCenter Server Heartbeat on both servers.
Chapter 10 Troubleshooting VMware Channel Incorrectly Configured If the VMware Channel is not properly configured, it cannot initiate the handshake to establish communications through the VMware Channel connection. Problem Failure to establish the VMware Channel connection prevents a full system check, thereby leaving the File System Status and Registry Status as Out-of-sync.
Administrator Guide Passive Server Has Less Available Space than Active Server Inadequate available disk space on the passive server can cause replication to cease. Problem Replication stops with the following error: [N27]Failed to write information for the file: {filename} to the disk. Either the disk is full or the quota (for the SYSTEM account) was exceeded. Cause The passive server has less available disk space than the active server, preventing updates from being replicated to the passive server.
Chapter 10 Troubleshooting Channel Drops When the VMware Channel loses connection between the servers, the following scenarios can occur. Performance Issues Poor performance can be experienced as a result of a channel loss. Problem The message java.io.IOException: An existing connection was forcibly closed by the remote host appears in the active server's NFLog.txt file, and the VMware Channel connection between the servers is lost.
Administrator Guide Hardware or Driver Issues on VMware Channel NICs NIC malfunctions and old or incorrect drivers can cause channel drops resulting in poor performance. Problem The VMware Channel intermittently drops or disconnects and reconnects. Cause The following are common causes of NIC problems.
Chapter 10 Troubleshooting Channel Fails to Connect After Configuring Firewall Ports Problem The VMware Channel fails to connect and does not allow traffic to pass between the Primary and Secondary servers. Cause If Microsoft Windows changed the connection type from Private network to Unidentified network after the user has configured the firewall port to allow channel communications, this may cause the firewall changes to be reset for the new network type.
Administrator Guide Solution The installation process manually assigns the correct IP addresses to each NIC on the Secondary server. If no VMware Channel connection occurs between the servers, verify the configuration of the IP addresses on the Secondary server's channel NICs. Check the settings for the Principal (Public) NIC. The configuration error can remain unrecognized until you perform a switchover or a failover occurs.
Chapter 10 Troubleshooting Subnet or Routing Issues In a LAN or WAN deployment, the following connection problems can occur. LAN Deployment Incorrectly configured subnets or routing can cause channel problems resulting in poor performance or failure to connect. Problem The Channel disconnects or fails to connect in a LAN deployment. Cause The Channel disconnects or fails to connect due to the Principal (Public) NIC and/or one or more channels sharing the same subnet.
Administrator Guide MaxDiskUsage Errors vCenter Server Heartbeat uses queues to buffer the flow of replication data from the active server to the passive server. This configuration provides resilience in the event of user activity spikes, VMware Channel bandwidth restrictions, or VMware Channel drops across a WAN deployment. Some types of file write activity also require buffering as they can cause a sharp increase in the amount of channel traffic.
Chapter 10 Troubleshooting 3 Configure the Maximum Disk Usage value and click Finish. 4 Start vCenter Server Heartbeat. Note vCenter Server Heartbeat is a symmetrical system and can operate with either server in the active role. For this reason, the queue size is always set to the same value for both servers. MaxDiskUsage Error Messages The following error messages display when available disk space on the servers is exceeded.
Administrator Guide [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server This message indicates that you have exceeded the amount of allocated disk space reserved for the passive server’s receive queue. Problem Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from the passive server. Cause Two of the most common causes are shown below: ■ The bottleneck lies between the VMware Channel NIC and the disk subsystem on the passive server.
Chapter 10 Troubleshooting 3 Configure the path for Message Queue Logs Location and click Finish. 4 Start vCenter Server Heartbeat on both servers. Note The selected path is applied to all vCenter Server Heartbeat queues on both servers. ■ Increase the amount of disk space allotted to the queues. However, if a hardware issue is the root of the problem, correct that problem at the source.
Administrator Guide The machines hosting vCenter Server Heartbeat must meet recommended hardware requirements and must be powerful enough to support the load, the protected applications, and any other critical applications running on the same server pair. Poor Application Performance When applications are competing for resources, one or more applications can perform poorly. Problem Neither server in the pair can accommodate the load placed upon it during normal operation.
Chapter 10 Troubleshooting Cause A large discrepancy occurs in the processing power between the Primary and Secondary servers. One server can handle the operational load while the other cannot. The load on a server is greater while in the active role when the protected application starts. Applications on the server pair run successfully when the Primary server is active, but experience performance issues when the Secondary is active (or the reverse).
Administrator Guide 100 VMware, Inc.
Glossary Active The functional state or role of a server when it is visible to clients through the network, running protected applications, and servicing client requests. Alert A notification provided by vCenter Server Heartbeat sent to a user or entered into the system log indicating an exceeded threshold.
Administrator Guide Cloned Servers Servers that have identical configuration settings, names, applications, Security Identifiers (SIDs) and IP addresses, following the installation of vCenter Server Heartbeat. Cloning Process The vCenter Server Heartbeat process whereby all installed programs, configuration settings, and the machine name, Security Identifier (SID), and IP address are copied to another server.
Glossary Global Catalog Server A global catalog is a domain controller that stores a copy of all Active Directory objects in a forest. The global catalog stores a full copy of all objects in the directory for its host domain and a partial copy of all objects for all other domains in the forest. Graceful (Clean) Shutdown A shutdown of vCenter Server Heartbeat based upon completion of replication by use of the vCenter Server Heartbeat Console, resulting in no data loss.
Administrator Guide Passive The functional state or role of a server when it is not delivering service to clients and is hidden from the rest of the network. Pathping A route-tracing tool that works by sending packets to each router on the way to a final destination and displays the results of each hop. Plug-and-Play (PnP) A standard for peripheral expansion on a PC. On starting the computer, PnP automatically configures the necessary IRQ, DMA and I/O address settings for the attached peripheral devices.
Glossary Rule A set of actions performed by vCenter Server Heartbeat when defined conditions are met. Secondary An identity assigned to a server during the vCenter Server Heartbeat installation process that normally does not change during the life of the server and usually represents the standby server prior to installation of vCenter Server Heartbeat. Security Identifier (SID) A unique alphanumeric character string that identifies each operating system and each user in a network of 2003/2008 systems.
Administrator Guide System State Data that comprises the registry, COM+ Class Registration database, files under Windows File Protection, and system boot file; other data may be included in the system state data. Task An action performed by vCenter Server Heartbeat when defined conditions are met. Time-To-Live (TTL) The length of time that a locally cached DNS resolution is valid. The DNS server must be re-queried after the TTL expires.
