Installation Guide VMware vCenter Server Heartbeat 6.3 Update 1 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.
Installation 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 © 2010 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 Getting Started 1 Introduction 9 Overview 9 vCenter Server Heartbeat Concepts 9 Architecture 9 Protection Levels 11 Communications 14 vCenter Server Heartbeat Switchover and Failover Processes 15 Installation 2 vCenter Server Heartbeat Implementation 21 Overview 21 Environmental Prerequisites 21 Common Requirements 22 Server Architecture Options 23 Virtual to Virtual (V2V) 23 Physical to Virtual (P2V) 23 Physical to Physical (P2P) 24 Cloning Technology Options 24 Supported Pre
Installation Guide Configuring VirtualCenter Plug-in with the Correct Credentials 45 When Deployed in a WAN Environment 46 vCenter Server 2.
About This Book The Installation Guide provides information about installing VMware vCenter Server Heartbeat, including implementation in a Local Area Network (LAN) or Wide Area Network (WAN) and using identical nodes or non-identical nodes. To help you protect your VMware vCenter Server, the book provides an overview of 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.
Installation Guide Document Feedback VMware welcomes your suggestions for improving our documentation and invites you to send your feedback to docfeedback@vmware.com. Abbreviations Used in Figures The figures in this book use the abbreviations listed in Table 1. Table 1.
Getting Started VMware, Inc.
Installation Guide 8 VMware, Inc.
1 Introduction 1 This chapter includes the following topics: “vCenter Server Heartbeat Concepts” on page 9 “vCenter Server Heartbeat Switchover and Failover Processes” on page 15 Overview vCenter Server Heartbeat is a Windows based service specifically designed to provide high availability protection for vCenter Server configurations without requiring any specialized hardware.
Installation Guide filter on the currently active server is enabled preventing communications on the Public network while the packet filter on the currently passive server is disabled thereby allowing the two servers to switch roles. From this point on, the previously passive server is now active and servicing the clients. The previously active server is now passive and hidden from the Public network.
Chapter 1 Introduction addresses for the Primary and Secondary servers separate from the shared Public (Principal) IP address. Clients connect to vCenter Server using a unique virtual service name configured in vCenter Server Heartbeat that resolves to the Public (Principal) IP address. When started, vCenter Server Heartbeat provides the passive server its unique Management IP address and provides the active server with the shared Principal (Public) IP address.
Installation Guide Figure 1-1. Failover A failover is similar to a switchover but is used in more urgent situations, such as when the passive server detects that the active server is no longer responding. This can occur when the active server hardware fails, loses its network connections, or otherwise becomes unavailable. Rather than the active server gracefully closing, the passive server determines that the active server has failed and requires no further operations.
Chapter 1 Introduction Figure 1-2. Switchover A switchover gracefully closes any protected applications that are running on the active server and restarts them on the passive server, including the application or service that caused the failure. In the example where the Primary server is active and the Secondary server is passive, the Primary server is demoted to a passive role and is hidden from the network when the Secondary server is promoted to an active role and is made visible to the network.
Installation Guide Figure 1-3. Apply Process The apply process running on the passive server’s receive queue applies all updates in strict sequence, duplicating an identical set of file operations on the passive server as illustrated in Figure 1-3. Communications The VMware Channel is a crucial component of the setup and can be configured in a number of ways. Both the Primary and Secondary servers must have two or more network interface connections (NICs). The Principal (Public) network requires one NIC.
Chapter 1 Introduction The Principal (Public) NICs on the passive server are configured to use the same IP address as that of the active server but are prevented from communicating with the live network through an IP packet filtering system installed with vCenter Server Heartbeat. This packet filter prevents traffic using the Principal (Public) address from being committed to the wire.
Installation Guide 3 Re-designate the Secondary server as the new active server. After this step, vCenter Server Heartbeat: Hides the previously active server from the network. Makes the newly active server visible on the network. The newly active server has the same identity as the previously active server, and begins to intercept and queue disk I/O operations for the newly passive server.
Chapter 1 Introduction This enables the public identity of the server. The active and passive servers both use the same system name and same Principal (Public) IP address. This Principal (Public) IP address can be enabled only on one system at anytime. When the public identity is enabled, any clients previously connected to the server before the automatic failover are able to reconnect. 3 Start intercepting updates to protected data.
Installation Guide To restore the previously failed server to the active role 1 Correct the conditions that caused the failover. 2 Verify the integrity of the disk data on the failed server. 3 Restart the failed, now passive, server after all issues are resolved. 4 Start vCenter Server Heartbeat on the passive server. At this point, the instances of vCenter Server Heartbeat running on the servers connect and begin to re-synchronize the data on the Primary server.
Installation VMware, Inc.
Installation Guide 20 VMware, Inc.
2 vCenter Server Heartbeat Implementation 2 This chapter includes the following topics: “Overview” on page 21 “Environmental Prerequisites” on page 21 “Common Requirements” on page 22 “Server Architecture Options” on page 23 “Cloning Technology Options” on page 24 “Application Component Options” on page 25 “Network Options” on page 26 “Antivirus Recommendations” on page 29 “Deployment Options Summary” on page 29 Overview vCenter Server Heartbeat is a versatile solution
Installation Guide Common Requirements The following requirements are in addition to those required for vCenter Server and SQL Server. NOTE If you are intending to deploy vCenter Server Heartbeat with non-identical nodes, you must use vCenter Server 4.0 Update 1 or later. Supported vCenter Server Versions VirtualCenter Server 2.5 VirtualCenter Server 2.5 Update 1 VirtualCenter Server 2.5 Update 2 VirtualCenter Server 2.5 Update 3 VirtualCenter Server 2.
Chapter 2 vCenter Server Heartbeat Implementation Verify that both Primary and Secondary servers have identical system date, time, and time Zone settings. Once configured, do not change the time zone. Verify that the Principal (Public) network adapter is listed as the first network adapter in the Network Connections Bind Order. (Network Connections > Advanced > Advanced Settings).
Installation Guide Physical to Physical (P2P) P2P architecture is used in environments where both the Primary and Secondary servers are physical servers. Use of P2P limits installation options as it requires use of the Install Clone technique. This architecture requires attention to detail when preparing for installation as both hardware and software must meet specific prerequisites. NOTE The P2P architecture is not supported when deploying vCenter Server Heartbeat with non-identical nodes.
Chapter 2 vCenter Server Heartbeat Implementation VMware vCenter virtual machine cloning for “Virtual to Virtual (V2V)” on page 23. Supported Install Clone Technologies Installation of vCenter Server Heartbeat provides support for NTBackup on Windows 2003 and Wbadmin on Windows Server 2008 for automated Install Cloning. This process is automated but requires meeting all prerequisites for the Secondary server specified in “Physical to Physical (P2P)” on page 24.
Installation Guide vCenter Converter Enterprise SQL Server Versions Microsoft SQL Server 2005 SP1-SP3 Microsoft SQL Server 2008 including SP2 NOTE Ensure that all VMware components are bound to the Principal (Public) IP address on the Principal (Public) network adapter and that the Principal (Public) network adapter is listed first in the bind order of the Network Connections > Advanced > Advanced Settings page.
Chapter 2 vCenter Server Heartbeat Implementation Microsoft DNS Server Updated During Switchover/Failover Microsoft DNS servers must be updatable to allow operation of the DNSUpdate.exe If using Microsoft Windows 2008 R2, the security level must be configured to permit changes to Windows Server 2008 R2 DNS servers.
Installation Guide WAN Deploying vCenter Server Heartbeat in a WAN environment requires additional considerations. Each server within the vCenter Server Heartbeat pair requires its own separate Principal (Public) IP address and a VMware Channel IP address in a separate dedicated subnet. NOTE Non-identical nodes are not supported in a WAN environment.
Chapter 2 vCenter Server Heartbeat Implementation Latency Latency has a direct effect on data throughput. Latency on the link should not fall below the standard defined for a T1 connection. Heartbeat Diagnostics can assist in determining the available bandwidth, required bandwidth, and server workload. For more information about Heartbeat Diagnostics, contact VMware Professional Services.
Installation Guide Installation Options Checklist Verify the prerequisites: Server architecture: ___ P2P ___ P2V ___ V2V Cloning technology option: ___ Pre-Clone Install ___ Install Clone Application components to protect: ___ vCenter Server with SQL Server on same host ___ vCenter Server with SQL Server on separate host ___ vCenter Server only Network environment type: ___ LAN ___ WAN Identity Mode: ___ Identical Nodes ___ Non-Identical Nodes (Only supported in LAN, using V2V or P2V, Pre-Cloned environmen
3 Installing vCenter Server Heartbeat on Identical Nodes 3 This chapter includes the following topics: “Overview” on page 31 “Installation Process” on page 31 “Primary Server” on page 32 “Secondary Server” on page 38 “vCenter Server Heartbeat Console” on page 44 “Post Installation Configuration” on page 45 “Installation of Client Tools” on page 47 Overview This chapter discusses the installation process used to implement vCenter Server Heartbeat on Windows Server 2003 and Wind
Installation Guide Primary Server Installation of vCenter Server Heartbeat begins on the Primary server. NOTE vCenter Server Heartbeat prompts you to enter a valid production serial number during the installation process. If you do not enter a valid production serial number during the installation process, vCenter Server Heartbeat installs in the evaluation mode.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 4 The Setup Type page appears. Because this is a new installation of vCenter Server Heartbeat, select Install vCenter Server Heartbeat and click Next. NOTE The left pane of each page in the setup wizard provides information about the setup process. 5 Select the physical identity of the server on the Physical Hardware Identity page. Select Primary as the server identity and click Next. NOTE If .Net 2.
Installation Guide NOTE The path of the VMware installation folder cannot contain Unicode characters. If vCenter Server Heartbeat is installed in a folder that has a path containing Unicode characters, this causes the Neverfail Server R2 service to fail to start. The path of the VMware installation folder can only contain lower and upper case letters A to Z, digits from 0 to 9, and the following special characters: space \ _ - ( ) .
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 19 For a LAN environment, click Add to specify the IP address. Click Next. If installing in a LAN or when the WAN uses the same subnet, go to Step 23. 20 For a WAN environment, specify IP addresses of the Secondary server and the Primary server. 21 Add each Principal (Public) network address until all addresses are present. Click Next.
Installation Guide 23 The vCenter Server Heartbeat server pair can be administered remotely on client machines using the vCenter Server Heartbeat Console. The vCenter Server Heartbeat Console connects to an IP address of the active server using the default client connection port of 52267. If this port is already in use, type an available client connection port in the text box. Click Next. 24 Select the applications to protect. All licensed vCenter Server Heartbeat features are listed.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 26 c Specify the path to an appropriate location for storing the backup file by either manually typing the path into Backup File Folder or click Browse to locate the folder or network mapping. Click Next. Go to Step 27. d Select a location to place the backup files through the Microsoft Windows Backup Configuration page. When installing into a Windows Server 2008 environment, you must specify a UNC path to the backup file location.
Installation Guide 32 The next page displays the Microsoft Windows Backup page. Click Proceed. The automated backup is saved in the previously defined location. NOTE When installing into a Windows Server 2008 environment, vCenter Server Heartbeat verifies that the Windows Server Backup Feature and Command Line Tools are installed. If they are not installed, you must install them now. You are not required to exit the installation to install the Windows Server Backup Feature.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 5 Identify the location of the folder containing the backup file from the Primary server. Manually type the location path in the text box. Click Next. NOTE For Windows Server 2003 installations you can alternatively click Browse and locate the folder. On Windows Server 2008 installations, you must use the UNC path. 6 The pre-install checks run. Click Next.
Installation Guide 40 12 Click Open Network Connections to change the static IP address of the Principal (Public) adapter to match that of the Primary server (LAN configuration only). 13 If in a WAN environment, verify the Secondary Principal (Public) adapter IP address configuration. Click Next and go to Step 15.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 19 Expand the file tree structure to see the System State file in the left pane. Click OK to build indexes where required. Select all items listed under the media created tree and click Next. 20 With Where to restore at the default Original location, click Next. Click Finish. 21 A warning message alerts you that the restore process is going to overwrite the existing System State files. Click OK.
Installation Guide 29 The Microsoft Windows Backup Restore page is displayed. The Microsoft Windows Backup Restore page shows the progress of unbinding the packet filter and disabling NetBIOS from the channel NIC(s). After this process completes, a caution message advises you that the restore process is initiating and upon completion of the restore process, the server requires a restart. After restarting, Plug-and-Play (PnP) can require you to restart the machine more than once. Click OK.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes 35 The Reconnect Network Cables page is displayed. Follow the instructions on this page to reconnect all of the previously disconnected network cables. After all network cables are connected, click Next. 36 The Channel Adapter Identification page is displayed. Use this opportunity to reconfigure the VMware Channel NICs.
Installation Guide NOTE The installation is complete if vCenter Server was installed with a local SQL Server or only vCenter Server was installed with no separate SQL Server. If vCenter Server only was installed and you want to install a separate SQL Server, repeat the installation process for the Primary and Secondary servers at the remote site and select SQL Server only.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes To add a vCenter Server Heartbeat Group 1 Open vCenter Server Heartbeat Console and click Add Group in the tool bar, select Add Group from the File menu, or right-click an existing group in the navigation panel and select Add Group form the menu. 2 Type the name for the new group into the text box and click OK. The newly created group appears in the navigation panel on the left of the vCenter Server Center Heartbeat window.
Installation Guide When Deployed in a WAN Environment When deployed in a WAN environment with VMware Orchestrator and the Primary and Secondary servers in different subnets, you must configure an Exclusion File Filter following the steps below: 1 Launch vCenter Server Heartbeat Console. 2 Click Data and click the File Filters tab. 3 Click Add Exclusion Filter and type the following path: $INSTALL_PATH_TO_ORCHESTRATOR/app-server/bin/boot.properties 4 Click OK.
Chapter 3 Installing vCenter Server Heartbeat on Identical Nodes IMPORTANT Do not configure the VMware Managed IP address using the Virtual Infrastructure Client. The Managed IP field from Administration > VirtualCenter Management Server Configuration > Runtime Settings must be clear. Installing the View Composer Plug-in Installation of the View Composer Plug-in can occur during the installation of vCenter Server Heartbeat as a part of the installation process or can be installed post-installation.
Installation Guide 48 8 Pre-install checks run to ensure that the installation can continue. The Report pane displays the results of the pre-install checks. If some pre-install checks are unsuccessful, go back through the wizard, make the necessary changes, and run the pre-install checks again. If the pre-install checks are successful, click Next. 9 The next page displays the progress of the installation.
4 Installing vCenter Server Heartbeat on Non-Identical Nodes 4 This chapter includes the following topics: “Overview” on page 49 “Installation Process” on page 49 “Installing vCenter Server Heartbeat on Non-Identical Nodes” on page 50 “Post Installation Configuration” on page 60 “vCenter Server Heartbeat Console” on page 58 “Installation of Client Tools” on page 61 Overview This chapter discusses the installation process used to implement vCenter Server Heartbeat on Windows Server
Installation Guide Installing vCenter Server Heartbeat on Non-Identical Nodes vCenter Server Heartbeat is installed on both the Primary and Secondary server of a vCenter Server Heartbeat cluster. NOTE When protecting SQL Server in a non-identical nodes environment, the SQL Server instance service must run under an account with administrator rights rather than the Network Service or Local System account. If required, change the Log On AS property by navigating to Start > Administrative Tools > Services.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes 12 Click Add to enter a valid production serial number for production mode or click Next to install in the evaluation mode. 13 Select LAN for the network topology and in the Deploy Heartbeat Cluster across pane, select either Non-identical (Updates MS DNS) if you are using an updatable Microsoft DNS server or Non-identical if you are using a non-updatable Microsoft DNS server or non-Microsoft DNS server. Click Next.
Installation Guide 17 The VMware Channel IP Configuration page prompts you to configure the VMware Channel(s) IP network addresses. Click Add for each available channel connection. For the Primary server, select from a drop-down menu that lists all local IP addresses. Type the reciprocal IP address on the Secondary server into the IP Address On Secondary text box.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes If installing SQL Server remotely, upon completion of the vCenter Server installation locally, repeat the installation procedure at the remote SQL Server location and select Protect SQL Server Only. NOTE When deploying with non-identical nodes, vCenter Server Heartbeat only supports SQL Sever installed on a separate server (remotely). Therefore the option Protect Virtual Center and SQL Server should not be selected.
Installation Guide 28 The next page displays the progress of the installation. During this process, Setup installs the necessary files and folders onto your system and applies the configuration you specified. Setup also installs Heartbeat Diagnostics and configures it with the default settings. NOTE If a previous version of Heartbeat Diagnostics is detected, vCenter Server Heartbeat Setup updates it to the current version.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes To install vCenter Server Heartbeat on the Secondary server 1 Before powering on the cloned image, edit the image settings. a Select the Principal (Public) virtual network adapter and clear the Connected and Connect at power on check boxes. b Repeat the process on the VMware Channel virtual network adapter. c Power on the Secondary (previously cloned) server image.
Installation Guide 7 The pre-install checks run. Click Next. NOTE The pre-install checks will return the message that the Primary and Secondary server’s names match. This is expected and installation will be allowed to continue. If some pre-install checks are unsuccessful, go back through the wizard, make the necessary changes, and run the pre-install checks again. 8 The next page displays the progress of the installation.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes 18 Enter the Service Name for the vCenter Server or SQL Server. NOTE The Service Name is the DNS name by which application clients connect to the application. Normally this is the original name of the vCenter Server or SQL Server. There is only one Service Name and it is the same on all servers in the cluster. 19 In the NIC drop-down, select the Principal (Public) NIC.
Installation Guide 5 Change the IP address to the match that of the Secondary management IP address previously entered in the Configure Server wizard. Click OK twice to close the dialogs. 6 Navigate to the server’s System Properties, select the Computer Name tab, and click Change to rename the Secondary server and join a Workgroup. When requested, restart the server. 7 Right-click the Secondary server image and select Edit Settings.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes The selection of Group or Pair you make in the navigation panel “points” the vCenter Server Heartbeat Console to that Group or Pair and vCenter Server Heartbeat Console provides information related to only the selected Group or Pair. To avoid confusion, pay particular attention to the selection in the navigation panel when you are managing more than one Group or Pair.
Installation Guide Post Installation Configuration Upon completion of installation, a series of tasks must be performed to ensure that vCenter Server Heartbeat is properly configured. 1 When protecting SQL Server, verify that the SetSPN.exe tool present on both the Primary and the Secondary servers at the following locations: On Windows Server 2003 environments, in Program Files\Support Tools. If Support Tools are not installed on your system, download them from http://support.microsoft.
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes Configuring SQL Server Plug-in to run with the Correct Credentials 1 Launch the vCenter Server Heartbeat Console and navigate to the Applications: Tasks page. 2 Click User Accounts. Verify that the user account under which you installed vCenter Server Heartbeat is present in the list of User Accounts.
Installation Guide 3 The WinZip Self-Extractor dialog appears. Click Setup to continue. 4 The Setup Type page appears. Because this is a vCenter Server Heartbeat Client Tools installation, select Install Client Tools Only and click Next. 5 Read the license agreement carefully and select I accept terms of the License Agreement. Click Next. 6 Configure the installation paths. The default installation location is C:\Program Files\VMware\VMware vCenter Server Heartbeat, but you can change it by manually
Appendix – Setup Error Messages Table A-1. Setup Error Messages Message Pri Sec Level Test 10 – ‘The pre install check data file does not have the correct format. Setup cannot continue’. No Yes Critical Stop Check that the file adheres to the correct formatting and structure for use in analysis on the Secondary. Setup has detected incompatible versions of the collector version $x and the analyzer version $y dll.
Installation Guide Table A-1. Setup Error Messages (Continued) 64 Message Pri Sec Level 113 - You do not have enough total memory to install vCenter Server Heartbeat on your #1# server. You must have at least 1GB. Yes Yes Critical Stop VMware recommend a minimum of 2GB. Note actual memory requirements depend on the application load; and may require more memory. Yes Yes Warning 117 - You do not have enough free disk space to install vCenter Server Heartbeat.
Glossary A Active The functional state or role of a server visible through the network by clients running protected applications and servicing client requests. Alert A notification sent to a user or entered into the system log indicating an exceeded threshold. Active Directory (AD) Presents applications with a single, simplified set of interfaces so users can locate and use directory resources from a variety of networks while bypassing differences among proprietary services.
Reference Guide Channel NIC (Network Interface Card) A dedicated subnet used by the VMware Channel. Cloned Servers Two servers in a pair with the same 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 applications, configuration settings, the machine name, security identifier (SID), and IP address are copied to a second server.
Glossary H Hardware Agnostic A key vCenter Server Heartbeat feature enabling the use of servers from different manufacturers, models, and processing power in a single vCenter Server Heartbeat server pair. Heartbeat The packet of information issued by the passive server across the VMware Channel, which the active server responds to, indicating its presence.
Reference Guide Pathping A route-tracing tool that sends 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. When starting the computer, Plug and Play (PnP) configures the necessary IRQ, DMA and I/O address settings for the attached peripheral devices. Plug-in An optional module that can be installed into a vCenter Server Heartbeat server to provide additional protection for a specific application.
Glossary Shared Nothing A key vCenter Server Heartbeat feature whereby hardware is not shared between the Primary and Secondary servers, thus preventing a single point of failure. SMTP A TCP/IP protocol used in sending and receiving e-mail between or among servers.
Reference Guide Unprotected Application An application that is not monitored or its data replicated by vCenter Server Heartbeat. V VMware Channel The IP communications link used by vCenter Server Heartbeat for heartbeat and replication traffic. VMware vCenter Server Heartbeat The core replication and system monitoring component. VMware vCenter Server Heartbeat Packet Filter The network component installed on both servers that controls network visibility.
