Quick Start Guide. vcenter Server Heartbeat 5.5

Transcription

1 Quick Start Guide vcenter Server Heartbeat 5.5

2 Quick Start Guide Quick Start Guide Revisin: Item: Yu can find the mst up-t-date technical dcumentatin n the VMware Web site at: The VMware Web site als prvides the latest prduct updates. If yu have cmments abut this dcumentatin, submit yur feedback t: dcfeedback@vmware.cm 2009 VMware, Inc. All rights reserved. This prduct is prtected by U.S. and internatinal cpyright and intellectual prperty laws. VMware prducts are cvered by ne r mre patents listed at VMware, the VMware bxes lg and design, Virtual SMP, and VMtin are registered trademarks r trademarks f VMware, Inc. in the United States and/r ther jurisdictins. All ther marks and names mentined herein may be trademarks f their respective cmpanies. VMware, Inc Hillview Ave Pal Alt, CA VMware, Inc.

3 Cntents Cntents ABOUT THIS BOOK... 4 INTENDED AUDIENCE... 4 DOCUMENT FEEDBACK... 4 Abbreviatins Used in Figures... 4 TECHNICAL SUPPORT AND EDUCATION RESOURCES... 5 Online and Telephne Supprt... 5 Supprt Offerings... 5 VMware Prfessinal Services... 5 VCENTER SERVER HEARTBEAT INTRODUCTION... 6 VCENTER SERVER HEARTBEAT PROTECTION... 6 Server Prtectin... 6 Netwrk Prtectin... 7 Applicatin Prtectin... 7 Perfrmance Prtectin... 8 Data Prtectin... 8 COMMUNICATIONS... 8 VCENTER SERVER HEARTBEAT INSTALLATION OVERVIEW ENVIRONMENTAL PREREQUISITES COMMON REQUIREMENTS SERVER ARCHITECTURE OPTIONS Virtual t Virtual (V2V) Physical t Virtual (P2V) Physical t Physical (P2P) CLONING TECHNOLOGY OPTIONS Supprted Pre-Clne Technlgies Supprted Install Clne Technlgies APPLICATION COMPONENT OPTIONS vcenter Server with SQL Server n the Same Hst vcenter Server with SQL Server n a Separate Hst vcenter Server Only NETWORK OPTIONS LAN WAN INSTALLATION PROCESS Installatin Optins Checklist INSTALLATION Primary Server Secndary Server Pst Installatin Tasks INSTALLATION VERIFICATION VERIFYING VCENTER SERVER HEARTBEAT Exercise One Exercise Tw Exercise Three VMware, Inc. 3

4 Abut This Bk This Quick Start Guide prvides an intrductin t VMware vcenter Server Heartbeat. It guides yu thrugh the steps required t install vcenter Server Heartbeat and t perfrm basic cnfiguratin. It prvides a brief intrductin t basic administratin tasks and advanced cnfiguratin features. Fr mre infrmatin, the guide prvides pinters t ther manuals. Intended Audience The user guide assumes a wrking knwledge f netwrks including the cnfiguratin f the TCP/IP suite f prtcls, a sund knwledge f dmain administratin n the Windws 2003 platfrm ntably in Active Directry and DNS. Dcument Feedback VMware welcmes yur suggestins fr imprving ur dcumentatin. If yu have cmments, send yur feedback t dcfeedback@vmware.cm Abbreviatins Used in Figures The figures in this bk use the abbreviatins listed in Table 1. Table 1. Abbreviatins Abbreviatin Descriptin Channel VMware Channel NIC Netwrk interface card P2P Physical t physical P2V Physical t virtual V2V Virtual t virtual SAN Strage area netwrk type datastre 4 VMware, Inc.

5 Technical Supprt and Educatin Resurces The fllwing sectins describe the technical supprt resurces available t yu. T access the current versins f this bk and ther bks, g t Online and Telephne Supprt Use nline supprt t submit technical supprt requests, view yur prduct and cntract infrmatin, and register yur prducts. G t Custmers with apprpriate supprt cntracts shuld use telephne supprt fr the fastest respnse n pririty 1 issues. G t Supprt Offerings Find ut hw VMware supprt fferings can help meet yur business needs. G t VMware Prfessinal Services VMware Educatin Services curses ffer extensive hands-n labs, case study examples, and curse materials designed t be used as n-the-jb reference tls. Curses are available nsite, in the classrm, and live nline. Fr nsite pilt prgrams and implementatin best practices, VMware Cnsulting Services prvides fferings t help yu assess, plan, build, and manage yur virtual envirnment. T access infrmatin abut educatin classes, certificatin prgrams, and cnsulting services, g t VMware, Inc. 5

6 vcenter Server Heartbeat Intrductin This chapter intrduces vcenter Server Heartbeat and prvides an verview f the cncepts. It cntains the fllwing sectins: vcenter Server Heartbeat Prtectin n page 6 Cmmunicatins n page 8 vcenter Server Heartbeat Prtectin vcenter Server Heartbeat is a Windws based system that has been specifically designed t prvide high availability t server cnfiguratins in ne prduct while nt requiring any specialized hardware. Server Prtectin vcenter Server Heartbeat prtects the active server s perating system r hardware frm failing. Tw instances f vcenter Server Heartbeat mnitr each ther by sending I m alive messages and reciprcating with acknwledgments ver a netwrk cnnectin termed the vcenter Server Heartbeat Channel. If the passive server detects that this prcess r heartbeat has failed, then a failver ccurs as illustrated in Figure 0-1. VMware, Inc. 6

7 Figure 0-1 Failver A failver is similar t a switchver but is used in mre drastic situatins. A failver happens when the passive server detects that the active server is n lnger respnding. This can ccur when the active server hardware crashes r lses its netwrk cnnectins. Rather than the active server gracefully clsing, the passive server determines that the active server has failed and requires n further peratins. In a failver, the passive server immediately takes n the rle f the active server. Netwrk Prtectin vcenter Server Heartbeat practively mnitrs the ability f the active server t cmmunicate with the rest f the netwrk by plling defined ndes arund the netwrk, including the default gateway, the primary DNS server, and the Glbal Catalg server at regular intervals. If all three ndes fail t respnd, fr example, in the case f a netwrk card failure r a lcal switch failure, vcenter Server Heartbeat can initiate a switchver, allwing the secndary server t assume an identical netwrk identity as the primary server. Applicatin Prtectin vcenter Server Heartbeat running n the active server lcally mnitrs the applicatins and services it has been cnfigured t prtect thrugh the use f plugins. If a prtected applicatin fails, vcenter Server Heartbeat first tries t restart the applicatin n the active server (1). If restarting the applicatin fails, then vcenter Server Heartbeat initiates a switchver (2). Figure 0-2 Switchver VMware, Inc. 7

8 A switchver gracefully clses any prtected applicatins that are running n the active server and restarts them n the passive server with the applicatin r service that caused the failure as illustrated in Figure 0-2. Perfrmance Prtectin vcenter Server Heartbeat mnitrs applicatin services as well as specific applicatin attributes t ensure that prtected applicatins are peratinal and nt in an unrespnsive r stpped state. This level f mnitring is fundamental in ensuring that applicatins are available t users. In additin t mnitring applicatin services, vcenter Server Heartbeat can als mnitr specific applicatin attributes t ensure that they remain within nrmal perating ranges. Similar t applicatin mnitring, varius rules can trigger specific crrective actins whenever these attributes fall utside f their respective ranges. Data Prtectin Once installed, vcenter Server Heartbeat cnfigures itself autmatically t prtect files, flders, and even the registry settings fr vcenter Server n the active server by mirrring them in realtime t the passive server. This means that if a failver ccurs, all the files prtected n the failed server are available after the failver, hsted n the secndary server. Figure 0-3 Apply Prcess Cmmunicatins The VMware Channel is a crucial cmpnent f the setup and can be cnfigured in a number f ways. Bth the Primary and Secndary servers must have tw r mre netwrk interface cnnectins (NICs). The Principal (Public) netwrk requires ne NIC. The vcenter Server Heartbeat Channel uses a separate NIC, a private cnnectin between the servers used fr cntrl and data transfer between the pair f servers. The vcenter Server Heartbeat Channel might use a secnd pair f NICs t prvide a degree f redundancy. In this case, the VMware Channel has a Dual Channel if mre than ne dedicated 8 VMware, Inc.

9 NIC is prvided fr the vcenter Server Heartbeat Channel n each server. T prvide added resilience, the cmmunicatins fr the secnd channel must be cmpletely independent frm the first channel they must nt share any switches, virtual switches, ruters r the same WAN cnnectin. Figure 0-4 Cmmunicatin between Primary and Secndary Servers The IP address used by a client t cnnect t the active server (the Principal (Public) IP address) must be cnfigured t use a static IP address (Nt DHCP enabled). In the example in Figure 0-4, the IP address is cnfigured as The passive server s Principal (Public) NICs are cnfigured t use the same IP address as that f the active server but are prevented frm cmmunicating with the live netwrk thrugh an IP packet filtering system installed with vcenter Server Heartbeat. This packet filter prevents traffic using the Principal (Public) address frm being cmmitted t the wire. It als prevents NetBIOS traffic utilizing ther IP addresses n the NIC frm being sent t prevent NetBIOS name reslutin cnflicts. Cnfigure the NICs n the active and passive servers used fr the vcenter Server Heartbeat Channel s that their IP addresses are utside f the Principal (Public) netwrks subnet range. These addresses are termed the vcenter Server Heartbeat Channel addresses. Yu must switch ff NetBIOS fr the vcenter Server Heartbeat Channel(s) n the active and passive servers as this cnnectin remains live, and bth the passive and active machines have the same NetBIOS name. After restre and after the vcenter Server Heartbeat installatin cmplete (runtime), NetBIOS is disabled acrss the channel(s). This ccurs autmatically during installatin. If NetBIOS was nt disabled, a name cnflict ccurs as bth servers nw have the same name. The NICs that allw the cnnectivity acrss the vcenter Server Heartbeat Channel can be standard 100BaseT Ethernet cards prviding a thrughput f 100Mbits per secnd acrss standard Cat-5 cabling. When cnfigured fr a WAN deplyment, vcenter Server Heartbeat Channel uses static rutes ver switches and ruters t maintain cntinuus cmmunicatins independent frm crprate r public traffic. vcenter Server Heartbeat sftware is installed n a Primary server and a Secndary server. These names refer t the physical hardware (identity) f the servers. VMware, Inc. 9

10 The Secndary server has the same name, same file and data structure, same netwrk address, and can run all the same applicatins and services as the Primary server. Only ne server name and netwrk address can be visible n the same netwrk at any ne time. One f these tw servers is live n the Principal (Public) netwrk and serves the prtected applicatins. This is the active server. The ther server is hidden frm the Principal (Public) netwrk, remains as a ready standby server, and is the passive server. The vcenter Server Heartbeat sftware is symmetrical in almst all respects, and either the Primary Server r the Secndary server can take the active rle and prvide the prtected applicatin t users. 10 VMware, Inc.

11 vcenter Server Heartbeat Installatin This chapter discusses the installatin f vcenter Server Heartbeat and prvides an verview f the prerequisites fr successful installatin. It cntains the fllwing sectins: Overview n page 11 Envirnmental Prerequisites n page 12 Cmmn Requirements n page 12 Server Architecture Optins n page 12 Clning Technlgy Optins n page 14 Applicatin Cmpnent Optins n page 14 Netwrk Optins n page 15 Installatin Questins n page 17 Installatin n page 18 Pst Installatin Tasks n page 19 Overview vcenter Server Heartbeat prvides a versatile slutin that deplys multiple cnfiguratins in either a LAN r WAN envirnment with the prtected applicatins n either a single server r multiple servers. When deplyed with SQL Server, vcenter Server Heartbeat allws vcenter Server t be installed n a lcal server while SQL server is installed n a remte server. Additinally, vcenter Server Heartbeat can be deplyed with vcenter Server alne. Prir t installing vcenter Server Heartbeat, yu must identify the desired deplyment ptins. The installatin prcess requires yu t select ptins thrughut the prcedure t achieve the desired cnfiguratin. 11 VMware, Inc.

12 Envirnmental Prerequisites The server prtected by vcenter Server Heartbeat can NOT be cnfigured as a dmain cntrller / glbal catalg r DNS. Cmmn Requirements The fllwing requirements are in additin t thse required fr vcenter Server and SQL Server. Supprted vcenter Server Versins 2.5.0, 2.5.1, 2.5.2, Operating System Windws Server 2003 x86 Sp1 r SP2 Additinal 512 MB (minimum), 1 GB RAM (recmmended) 2 GB f disk space available n the drive where vcenter Server Heartbeat is installed Lcal administratr rights fr vcenter Server Heartbeat installatin Latest Micrsft security updates All applicatins t be prtected by vcenter Server Heartbeat must be installed and cnfigured n the Primary server prir t installing vcenter Server Heartbeat. The primary and secndary servers must be set t identical System Date / Time and Time Zne. Once cnfigured, d nt change the Time Zne. Primary Server Hardware and sftware as specified in the Cmmn Requirements sectin. Secndary Server Hardware Hardware must match the Primary server t ensure adequate perfrmance when the server is in the active rle: Similar CPU Memry Identical number f NICs t the Primary server. Drive letters must match the Primary server. Available disk space must be greater than r equal t the Primary server. ACPI cmpliance must match the Primary server. The vcenter Server Heartbeat Standard implementatin prcess assumes that the Advanced Cnfiguratin and Pwer Interface (r ACPI) cmpliance f bth machines are the same. If this is nt the case, cntact VMware Supprt at fr further infrmatin. Sftware OS versin and Service Pack versin must match the Primary server. OS must be installed t same driver letter and directry as n the Primary server. Machine name must be different frm the Primary server prir t installing vcenter Server Heartbeat. 12 VMware, Inc.

13 Set up a Wrkgrup prir t installing vcenter Server Heartbeat. System Date / Time and Time Zne must be cnsistent with Primary server. Server Architecture Optins The selected server architecture determines the requirements fr hardware and impacts the technique used t clne the Primary server. Virtual t Virtual (V2V) V2V is the supprted architecture if vcenter Server is already installed n the prductin (Primary) server running n a virtual machine. The Secndary virtual machine must meet the minimum requirements. The specificatins f the Secndary Virtual Machine must match that f the Primary Virtual Machine as fllws: Similar CPU (including resurce management settings) Memry cnfiguratin (including resurce management settings) Apprpriate resurce pl pririties Each virtual machine used in the V2V pair must be n a separate ESX hst t guard against failure at the hst level. Each virtual NIC must use a separate virtual switch. Physical t Virtual (P2V) The P2V architecture is used when the envirnment requires a mix f physical and virtual Machines. The Secndary virtual machine must meet the minimum requirements. The specificatins f the Secndary Virtual Machine must match the Primary physical server as fllws: Similar CPU Memry The Secndary Virtual Machine must have enugh pririty in resurce management settings s that ther virtual machines d nt impact its perfrmance. Each virtual NIC must use a separate virtual switch. Physical t Physical (P2P) The P2P architecture is used in an envirnment where it is necessary t have bth the Primary and Secndary servers as physical servers. Use f P2P limits the installatin ptins as it requires using the Install Clne technique. Additinally, this architecture requires attentin t detail when preparing fr installatin as bth current hardware and sftware must meet the specific prerequisites listed. Clning Technlgy Optins Clning the Primary server t create a near identical Secndary server invlves different techniques depending n the chsen server architecture ptin. VMware, Inc. 13

14 Supprted Pre-Clne Technlgies T create Pre-Clned images fr use as a Secndary server, use the fllwing clning technlgies: VMware Cnverter fr Physical T Virtual (P2V) VMware vcenter virtual machine clning fr Virtual T Virtual (V2V) Supprted Install Clne Technlgies vcenter Server Heartbeat supprts NTBackup n Windws 2003 fr autmated Install Clning. This autmated prcess requires meeting all prerequisites fr the Secndary server specified in the Physical t Physical (P2P) sectin. Applicatin Cmpnent Optins vcenter Server Heartbeat can accmmdate any f the supprted vcenter Server cnfiguratins and prtect the fllwing cmpnents: VMware vcenter Server VMware Capacity Planner VMware Cnverter Enterprise VMware Update Manager VMware License Server vcenter Server with SQL Server n the Same Hst T ensure adequate perfrmance in 20+ hst r 200+ VM envirnments, VMware recmmends installing SQL Server and vcenter Server n separate physical disk drives. VMDKs must be n separate datastres t avid ptential disk bttlenecks. vcenter Server with SQL Server n a Separate Hst When installing vcenter Server Heartbeat in an envirnment where SQL Server is n a separate hst frm vcenter Server, repeat the installatin prcess fr the Primary and Secndary server specifically fr the SQL Server. T ensure prper failver, increase the default Heartbeat interval fr the vcenter Server frm 20 t 30 secnds. vcenter Server Only The vcenter Server Only ptin requires a single iteratin f the installatin prcess because the database is nt prtected. T ensure prper failver, increase the default interval frm 20 t 30 secnds n the server running vcenter Server. This cnfiguratin is required when SQL Server is nt n the same hst as vcenter Server. 14 VMware, Inc.

15 Netwrk Optins LAN Netwrking requirements are cntingent based upn hw vcenter Server Heartbeat is deplyed. If deplyed as a High Availability slutin then a LAN cnfiguratin is required. If vcenter Server Heartbeat is deplyed fr Disaster Recvery, then a WAN cnfiguratin is required. vcenter Server Heartbeat deplyed in a LAN envirnment requires the same Principal (Public) IP address used by bth servers. Additinally, each server requires a separate VMware Channel IP address n a separate dedicated subnet. Nte: When installing vcenter Server Heartbeat in a LAN envirnment, d nt enable the Lw Bandwidth Mdule as this is designed fr WAN deplyments. Primary Server Three NICs (1 x Public; 2 x Channel) fr redundancy in the event ne channel fails. A minimum f tw NICs (ne fr the Channel, and ne fr the Public) are required in this cnfiguratin. Cnfigure split brain avidance. Principal (Public) Netwrk cnnectin cnfigured with the fllwing: Static IP address Crrect Netwrk Mask Crrect Gateway address Crrect Preferred and Secndary (if applicable) DNS Server address NetBIOS enabled Channel Netwrk cnnectin(s) cnfigured with the fllwing: Secndary Server Static IP address in a different subnet than the Principal (Public) netwrk with a different IP address than the Secndary server channel NIC Crrect Netwrk Mask N Gateway IP address N DNS Server address NetBIOS enabled Same number f NICs as the Primary Server. Principal (Public) Netwrk cnnectin cnfigured with temprary netwrk settings Channel Netwrk cnnectin(s) cnfigured with the fllwing: Static IP address (in a different subnet than the Principal (Public) netwrk with a different IP address than the Primary server channel NIC) Crrect Netwrk Mask N Gateway IP address N DNS IP address NetBIOS Enabled VMware, Inc. 15

16 File and Print Sharing enabled WAN Deplying vcenter Server Heartbeat in a WAN envirnment requires additinal cnsideratins. Each server within the vcenter Server Heartbeat pair requires its wn separate Principal (Public) IP address as well as a VMware Channel IP address in a separate dedicated subnet. WAN Requirements Bandwidth A persistent static rute cnfigured t the channel cnnectin n the Secndary server where ruting is required Tw NICs (1 x Public; 1 x Channel) recmmended If the Primary and Disaster Recvery (DR) site use the same subnet: During install, fllw the steps fr a LAN / VLAN (same subnet). Each server within the vcenter Server Heartbeat pair uses the same Public IP address. If the Primary and DR site use different subnets: During install, fllw the steps fr a WAN. Each server within the vcenter Server Heartbeat pair requires its wn separate Principal (Public) IP address as well as a VMware Channel IP address in a separate dedicated subnet. Prvide a user accunt with rights t update DNS using the DNSUpdate utility prvided as a cmpnent f vcenter Server Heartbeat. Recmmend Micrsft DNS t be integrated int AD s that DNSUpdate autmatically identifies all DNS Servers that require updating. Refer t the fllwing articles in the Knwledge base: VMware Knwledge Base article VMware Knwledge Base article At least ne Dmain Cntrller at the Disaster Recvery site Determine the available bandwidth and estimate the vlume f data fr which thrughput is required t determine acceptable latency fr the thrughput. Additinally, the bandwidth may affect the required queue size t accmmdate the estimated vlume f data. VMware recmmends a minimum f 1Mb f spare bandwidth be available fr vcenter Server Heartbeat. vcenter Server Heartbeat includes a Lw Bandwidth Mdule fr use in WAN envirnments. When enabled, the VMware Channel cmpresses the data, ptimizing the traffic fr lw bandwidth cnnectins causing sme additinal CPU lad n the active server. Latency Latency has a direct effect n data thrughput. Latency n the link must nt fall belw the standard defined fr a T1 cnnectin. 16 VMware, Inc.

17 Installatin Prcess After selecting implementatin ptins, begin the installatin prcess. The installatin prcess fr all scenaris fllws the same basic prcedure. Installatin Optins Checklist Server architecture: P2P P2V V2V Clning technlgy ptin: Pre-Clne Install Install Clne Applicatin cmpnents t prtect: vcenter Server with SQL Server n same hst vcenter Server with SQL Server n separate hst vcenter Server nly Install in netwrk envirnment type: LAN WAN Is the subnet the same at the Secndary site? If Yes, yu need an IP address fr this subnet Active Directry Integrated DNS? If Yes, yu need a Dmain Accunt with rights t update DNS. If N, then refer t the Knwledge Base articles in the Netwrking Sectin. VMware, Inc. 17

18 Installatin Primary Server After reviewing the setup prerequisites t ensure the servers in the pair (either physical r virtual) meet the minimum requirements and cmpleting the pre-installatin tasks (Pre-Clning fr V2V and P2V envirnments and cnfiguring the VMware Channel), yu can begin the setup prcess. 1. Run setup.exe n the Primary server. 2. The first ptin is the Server Identity. Select Primary. Nte: If yu need help during the setup prcess, the left panel f the setup dialg explains each step r ptin. 3. The next ptin is the clning technique. When yu chse the clning ptin the subsequent setup screens display the setup prcess fr the selected clning technlgy. 4. During the setup prcess, yu have the pprtunity t identify: The Prgram Installatin lcatin VMware Channel IP addresses The Principal (Public) IP addresses A single IP fr a LAN installatin Tw IPs fr a WAN installatin The applicatins t prtect (vcenter Server and SQL Server, vcenter Server nly, r SQL nly) The lcatin t stre the clne files 5. The setup prcess runs a Pre-Install Check t ensure that the server meets the apprpriate requirements. 6. The setup installs vcenter Server Heartbeat. 7. When using an Install Clne setup, the setup makes a backup. When using a Pre-Clne setup, the setup cpies tw small files t the strage lcatin setup n the Secndary server. 8. A Packet Filter n the Principal (Public) NIC cmpletes the setup prcess n the Primary server. Secndary Server T set up the Secndary server, cmplete the fllwing steps: 1. Run setup.exe t start the setup prcess fr the Secndary server (physical r virtual). 2. The first ptin is the Server Identity. Select Secndary. 3. The setup identifies the backup file lcatin and runs Pre-Install checks befre installing vcenter Server Heartbeat n the Secndary server. 4. The next step installs the Packet Filter and identifies the VMware Channel and Principal (Public) NICs. 5. When using an Install Clne setup in a LAN envirnment, cnfigure the Principal (Public) NIC t the same IP address as the Primary server. 6. After recnfiguring the Principal (Public) NIC (if necessary), initiate the restre prcess. 18 VMware, Inc.

19 7. Once the restre is cmplete, if the secndary server is a physical server, Windws Plug and Play runs multiple times t detect hardware differences. Allw it t cmplete and if prmpted, rebt. 8. When Plug and Play is cmplete, the setup prcess displays the Finish dialg. 9. D NOT start vcenter Server Heartbeat n the Secndary server. Pst Installatin Tasks After installatin and prir t starting vcenter Server Heartbeat, cmplete the fllwing tasks: 1. Verify that the Date and Time and Time Zne n the Secndary server are identical t that f the Primary server. 2. Lg in t the vcenter Server Heartbeat Cnsle and add a Username and Passwrd with rights t Virtual Infrastructure fr the vcenter Plug-in. 3. If SQL Server is nt installed n the same hst as vcenter Server, in the Heartbeat Cnsle, navigate t the Advanced -> Cmmunicatin -> Cnfiguratin screen and cnfigure the Heartbeat Interval frm 20 secs t 30 secs. After successfully installing vcenter Server Heartbeat n the server pair, if SQL Server is nt n the same hst as vcenter Server, repeat the setup prcess at the lcatin where SQL Server is hsted. VMware, Inc. 19

20 Installatin Verificatin The Installatin Verificatin prcess validates the installatin and tests the sftware peratin. Verifying vcenter Server Heartbeat The fllwing exercises are examples and must be perfrmed in rder. VMware des nt recmmend attempting t test a failver n a prperly perating server pair by methds such as unplugging a pwer crd. When pwer is lst, any data nt written t the passive server is lst. VMware recmmends a switchver rather than a failver t check the peratin f the passive server. Exercise One This exercise demnstrates that the Secndary server can functin as the Primary Server withut the test data being immediately replicated back t the riginal server. During the exercise, stp the Primary server frm prviding service and hide frm the netwrk, then intrduce the Secndary t the netwrk and allw it t prvide service. Starting Cnditins The Primary server is active. The Secndary server is passive. Bth the File System and the Registry Status are Synchrnized. Lcal users are aware that the service is unavailable fr the duratin f this exercise. VMware, Inc. 20

21 Actins Table 2 Exercise One Actins Machine Activity Result Primary Secndary Client Shut dwn vcenter Server Heartbeat. Select Stp VMware vcenter Server Heartbeat and all prtected applicatins, then click OK. With vcenter Server Heartbeat shut dwn, n the Primary server, g t Start -> All Prgrams -> VMware -> VMware vcenter Server Heartbeat ->Cnfigure Server t launch the Cnfigure Server wizard. In the wizard, change the Primary server s rle t passive. Start vcenter Server Heartbeat. Then shut dwn Heartbeat and select Stp VMware vcenter Server Heartbeat and all prtected applicatins, and then click OK. G t Start -> All Prgrams -> VMware -> VMware vcenter Server Heartbeat -> Cnfigure Server t launch the Cnfigure Server wizard. In the wizard, change the Secndary server s rle t active. Then start vcenter Server Heartbeat. Check the Applicatin functinality against the acceptance criteria. vcenter Server Heartbeat stps all mnitred services and exits. Primary server becmes passive This activates the netwrk filter hiding the Primary server frm the netwrk. The Secndary server starts as the active server. Secndary server behaves as the Primary server. Results The Secndary server prvides the expected functinality f the Primary server. VMware, Inc. 21

22 Exercise Tw This exercise fllws Exercise One. The bjective is t take a wrking active server (Secndary) and synchrnize it with the passive (Primary). This exercise demnstrates that all the crrect services stp when the Primary server is passive. Starting Cnditins vcenter Server Heartbeat is running n the Secndary Server, which is active. vcenter Server Heartbeat is nt running n the Primary server and is set t passive withut starting vcenter Server Heartbeat. Lcal users are aware that the service is unavailable fr the duratin f this exercise. Actins Table 3 Exercise Tw Actins Machine Primary Activity Start vcenter Server Heartbeat. Check the vcenter Server Heartbeat lgs t cnfirm n exceptin errrs during the synchrnizatin. Allw the Status f bth the Registry and File System t becme Synchrnized. Result vcenter Server Heartbeat starts. The vcenter Server Heartbeat Cnsle shws the cnnectin frm the Secndary (active) t Primary (passive). Data replicatin resumes frm the Secndary server back t the Primary server. Bth the File System & Registry status becme Synchrnized. Results Bth machines are resynchrnized. All the data changed n the Secndary machine while the Primary was nt running vcenter Server Heartbeat is updated nt the Primary machine. The Secndary (active) machine cntinues t prvide service. 22 VMware, Inc.

23 Exercise Three Perfrm a switchver using vcenter Server Heartbeat Cnsle. Perfrm this exercise after cmpleting Exercises One and Tw. Lcal users are aware that the service is unavailable fr the duratin f this exercise. Starting Cnditins Bth the File System and Registry Status are Synchrnized. Actins Table 4 Exercise Three Actins vcenter Server Heartbeat Cnsle Any Machine Activity Result Click Switchver and cnfirm. Cnfirm functinality per previusly defined acceptance criteria. Check the behavir f client applicatins after the switchver prcess. The vcenter Server Heartbeat Cnsle displays the services stpping n the active server. Once all services are stpped, the active server becmes passive and the passive server becmes active. The Cnsle shws the services starting n the newly active server. Bth the File and Registry status are Synchrnized. Service as usual. Yu might have t refresh r restart sme client applicatins as a result f a switchver. Results Applicatin service transferred frm the riginally active machine t the riginally passive machine. Dcument the applicatin client behavir fr future reference. VMware, Inc. 23