SolarWinds Orion Failover Engine Quick Start Guide

Transcription

1 SlarWinds Orin Failver Engine Quick Start Guide ORION FAILOVER ENGINE

2 Cpyright SlarWinds, Inc., all rights reserved wrldwide. N part f this dcument may be reprduced by any means nr mdified, decmpiled, disassembled, published r distributed, in whle r in part, r translated t any electrnic medium r ther means withut the written cnsent f SlarWinds. All right, title and interest in and t the sftware and dcumentatin are and shall remain the exclusive prperty f SlarWinds and its licensrs. SlarWinds, the SlarWinds lg, ipmnitr, LANsurveyr, and Orin are amng the trademarks r registered trademarks f the cmpany in the United States and/r ther cuntries. All ther trademarks cntained in this dcument and in the Sftware are the prperty f their respective wners. SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Micrsft, Windws 2000 Server, Windws 2003 Server, and Windws 2008 Server are either registered trademarks r trademarks f Micrsft Crpratin in the United States and/r ther cuntries. Graph Layut Tlkit and Graph Editr Tlkit Tm Sawyer Sftware, Oakland, Califrnia. All Rights Reserved. Prtins Cpyright CmpnentOne, LLC All Rights Reserved. Fluent is a trademark f Micrsft Crpratin and the Fluent user interface is licensed frm Micrsft Crpratin. SlarWinds Orin Failver Engine versin

3 SlarWinds Orin Quick Start Guide Abut SlarWinds SlarWinds, Inc develps and markets an array f netwrk management, mnitring, and discvery tls t meet the diverse requirements f tday s netwrk management and cnsulting prfessinals. SlarWinds prducts cntinue t set benchmarks fr quality and perfrmance and have psitined the cmpany as the leader in netwrk management and discvery technlgy. The SlarWinds custmer base includes ver 45 percent f the Frtune 500 and custmers frm ver 90 cuntries. Our glbal business partner distributr netwrk exceeds 100 distributrs and resellers. Cntacting SlarWinds Yu can cntact SlarWinds in a number f ways, including the fllwing: Team Cntact Infrmatin Sales Technical Supprt User Frums supprt.slarwinds.net/supprt Nte: Yu need a custmer accunt t access the Custmer Supprt area f the website. Cntents iii

4 SlarWinds Orin Failver Engine Dcumentatin Library The fllwing dcuments are included in the SlarWinds Orin Failver Engine dcumentatin library: Dcument Purpse Administratr Guide Installatin Guide Page Help Quick Start Guide Release Ntes Prvides cnfiguratin and cnceptual infrmatin. Prvides detailed setup infrmatin. Prvides help fr every windw in the Orin Failver Engine user interface Prvides installatin, setup, and cmmn scenaris fr which Orin Failver Engine prvides a simple, yet pwerful, slutin. Prvides late-breaking infrmatin, knwn issues, and updates. The latest Release Ntes can be fund at Cnventins The dcumentatin uses cnsistent cnventins t help yu identify items thrughut the printed and nline library. Cnventin Specifying Bld Italics Fixed fnt Straight brackets, as in [value] Curly braces, as in {value} Lgical OR, as in value1 value2 Windw items, including buttns and fields. Bk and CD titles, variable names, new terms File and directry names, cmmands and cde examples, text typed by yu Optinal cmmand parameters Required cmmand parameters Exclusive cmmand parameters where nly ne f the ptins can be specified iv Cntents

5 SlarWinds Orin Quick Start Guide Cntents Abut SlarWinds... iii Cntacting SlarWinds... iii SlarWinds Orin Failver Engine Dcumentatin Library... iv Cnventins... iv Chapter 1 Intrductin... 1 Orin Failver Engine Prtectin... 1 Server Prtectin... 1 Applicatin Prtectin... 2 Netwrk Prtectin... 3 Perfrmance Prtectin... 3 Data Prtectin... 3 Cmmunicatins... 4 Chapter 2 SlarWinds Orin Failver Engine Installatin... 7 Installatin Requirements... 7 Additinal Requirements... 8 Server Architecture Optins... 8 Virtual t Virtual (V2V)... 8 Physical t Virtual (P2V)... 9 Physical t Physical (P2P)... 9 Clning Technlgy Optins Supprted Pre-Clne Technlgies Supprted Install Clne Technlgies Applicatin Cmpnent Optins Netwrk Optins LAN WAN Installatin Prcess Installatin n the Primary Server Installatin n the Secndary Server Cntents v

6 Actins Required After an Installatin Cnfigure actins t take upn failure f a service When Additinal Pllers (AP)s are nt installed, create an Exclusin Filter t reduce replicatin traffic When IPAM 2.0 is installed, create an Inclusin Filter t replicate the IPAM.attributes.xml file Chapter 3 Installatin Verificatin Failver Simulatin Exercise Data Replicatin Exercise Switchver Exercise vi Cntents

7 SlarWinds Orin Quick Start Guide Chapter 1 Intrductin This chapter intrduces the Orin Failver Engine, prviding an verview f general cncepts related t the prtectin Orin Failver Engine prvides. Orin Failver Engine Prtectin The Orin Failver Engine (Orin Failver Engine) is a Windws-based service specifically designed t prvide high availability prtectin fr SlarWinds Orin installatins withut requiring any specialized hardware. The fllwing sectins describe the varius ways Orin Failver Engine prtects yur SlarWinds Orin installatin: Server Prtectin Applicatin Prtectin Netwrk Prtectin Perfrmance Prtectin Data Prtectin Server Prtectin The Orin Failver Engine prvides cntinuus availability t end users shuld a hardware failure r perating system crash ccur. Additinally, Orin Failver Engine prtects the netwrk identity f the prductin server, ensuring users are prvided with a replica server including server name and IP address shuld the prductin server fail. The Orin Failver Engine sftware is installed n bth a primary server and a secndary server. These names refer t the physical hardware (identity) f the servers. The secndary server has the same name, file and data structure, and netwrk address as the primary server, and runs the same applicatins and services as the primary server. Under nrmal perating cnditins in a nnfailver state the primary server functins as the active server, and the secndary server functins as the passive server. These tw Orin Failver Engine instances regularly send I m alive messages and acknwledgments t ne anther ver a netwrk cnnectin referred t as the SlarWinds Channel t detect interruptins in respnsiveness. If the passive server detects that the mnitring prcess has failed, it initiates a failver. The Orin Failver Engine is symmetrical in almst all respects, and either server primary r secndary can take the active rle, prviding prtected applicatins and services t users. Intrductin 1

8 A failver is used in mre urgent situatins, such as when the passive server detects that the active server is n lnger respnding. The active server can becme nn-respnsive due t hardware failure, lss f netwrk cnnectivity, r ther cmmunicatin failure. In a failver situatin, the passive server determines that the active server has failed and then immediately assumes the active server rle, as illustrated in the fllwing figure: Applicatin Prtectin The Orin Failver Engine enables yu t maintain yur applicatin envirnment by ensuring that netwrk applicatins and services stay alive. The Orin Failver Engine n the active server uses plug-ins t mnitr the applicatins and services it has been cnfigured t prtect. If a prtected applicatin fails, the Orin Failver Engine first tries t restart the applicatin n the active server (1). If restarting the applicatin fails, then the Orin Failver Engine can initiate a switchver (2) as illustrated in the fllwing figure. A switchver gracefully clses any prtected applicatins running n the active server, and then restarts all f them n the passive server, including the service r applicatin that initially caused the failure, as illustrated in the figure abve. 2 Intrductin

9 Netwrk Prtectin SlarWinds Orin Quick Start Guide The Orin Failver Engine practively mnitrs the netwrk by plling up t three ndes t ensure that the active server is visible n the netwrk. The Orin Failver Engine plls 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 r a lcal switch failure, the Orin Failver Engine can initiate a switchver, allwing the secndary server t assume a netwrk identity identical t that f the primary server. Perfrmance Prtectin The Orin Failver Engine practively mnitrs system perfrmance attributes t ensure that the system administratr is ntified f prblems and can take preemptive actin t prevent an utage. In additin t mnitring applicatin services, the Orin Failver Engine can mnitr specific applicatin attributes t ensure they remain within nrmal perating ranges. Similar t applicatin mnitring, varius rules can be cnfigured t trigger specific crrective actins when these attributes fall utside f their respective ranges. Data Prtectin The Orin Failver Engine intercepts all data written by users and applicatins, and it maintains a cpy f this data n the passive server that can be used in the event f a failure. The Orin Failver Engine cnfigures itself t prtect files, flders, and even the registry settings n the active server by mirrring these in realtime t the passive server. If a failver ccurs, all files prtected n the failed server are available after the failver, hsted n the secndary server. Orin Failver Engine cntinuusly prvides all five prtectin levels, ensuring all facets f the user envirnment are maintained at all times, and that the principal netwrk cntinues t perate thrugh as many failure scenaris as pssible. Intrductin 3

10 Cmmunicatins The SlarWinds Channel is a crucial cmpnent f an Orin Failver Engine installatin, and it can be cnfigured in a number f ways, prvided the fllwing cnditins are met: Bth the primary and the secndary servers must have tw r mre netwrk interface cnnectins (NICs). The principal (public) netwrk requires ne NIC. The SlarWinds Channel uses a separate NIC fr the private cnnectin between the prtected servers that is used fr cntrl and data transfer. A secnd pair f NICs can be used t prvide a degree f redundancy fr the SlarWinds Channel. In this cnfiguratin, the SlarWinds Channel has a dual channel if mre than ne dedicated NIC is prvided fr the SlarWinds 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. The IP address a client uses t cnnect t the active server the principal IP address must be cnfigured as a static IP address that is nt DHCP- enabled (Dynamic Hst Cnfiguratin Prtcl). In the figure abve, the IP address is cnfigured as The principal NICs n the passive server are cnfigured t use the same IP address as the active server, but they are prevented frm cmmunicating with the live netwrk thrugh an IP packet filtering system installed with the Orin Failver Engine. This packet filter prevents traffic using the principal address frm being cmmitted t the wire. It als prevents NetBIOS traffic using ther IP addresses n the NIC frm being sent t prevent NetBIOS name reslutin cnflicts. Fllwing restre and after the Orin Failver Engine installatin cmpletes (runtime), NetBIOS is disabled acrss the SlarWinds Channel. This ccurs during installatin t prevent name cnflicts that ccur when bth servers have the same name. 4 Intrductin

11 SlarWinds Orin Quick Start Guide The NICs n the active and passive servers that supprt cnnectivity acrss the SlarWinds Channel can be standard 100BaseT Ethernet cards prviding a thrughput f 100Mbits per secnd acrss standard Cat-5 cabling, and are cnfigured s their IP addresses are utside the subnet range f the principal netwrk. These addresses are referred t as SlarWinds Channel addresses. Nte: Firewalls prtecting the SlarWinds Channel netwrk cnnectins must be disabled t allw uninterrupted cmmunicatins between the primary and secndary servers. When cnfigured fr a WAN deplyment, the SlarWinds Channel uses static rutes ver switches and ruters t maintain cntinuus cmmunicatins independent frm crprate r public traffic. 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 netwrk and serves the prtected applicatins; this is the active server. The ther server, referred t as the passive server, is hidden frm the principal netwrk, remaining as a ready standby server. Intrductin 5

12 6 Intrductin

13 SlarWinds Orin Quick Start Guide Chapter 2 SlarWinds Orin Failver Engine Installatin Prir t installing the Orin Failver Engine, select the deplyment ptins yu intend t use. The installatin prcess prmpts yu t select ptins thrughut the prcedure t create the cnfiguratin yu want. Installatin Requirements The fllwing table lists minimum requirements fr the SlarWinds Orin Failver Engine. Nte: These requirements are in additin t any ther requirements fr the perating system r installed applicatins. Orin Failver Engine Requirements Supprted SlarWinds Orin Mdules Supprted Operating Systems Memry Disk Space SlarWinds Orin NPM MP v10.0 SP1 and higher SlarWinds Orin IPAM v1.7.1 and higher SlarWinds Orin APM v3.5 and higher SlarWinds Orin APM MP v4.0.1 and higher SlarWinds Orin IPSLA Manager v3.5 and higher SlarWinds Orin NTA v3.6 and higher SlarWinds Orin NCM v6.0 and higher Nte: NCM v7.0 is supprted, but it must be updated t NCM v7.0.1 if additinal plling engines r additinal web sites are in use. SlarWinds Orin SEUM v1.0 and higher SlarWinds Orin UDT v1.0 and higher SlarWinds Orin EOC v1.2 and higher Windws Server 2003 x86 Standard r Enterprise, SP1 and SP2 Windws Server 2003 x64 Enterprise SP2 Windws Server 2003 R2 x86 Standard r Enterprise Windws Server 2003 R2 x64 Standard r Enterprise Windws Server 2008 x86 r x64, SP1 and SP2 Standard r Enterprise Windws Server 2008 R2 Standard r Enterprise Nte: SlarWinds recmmends installing all Micrsft security updates. 1 GB (2 GB is recmmended) Nte: During setup, Orin Failver Engine verifies that a minimum f 1GB RAM is available. T ensure prper peratin, 2GB is recmmended in additin t any ther memry requirements fr the perating system r SlarWinds Orin mdules. 2 GB f available disk space n the installatin drive fr Orin Failver Engine. SlarWinds Orin Failver Engine Installatin 7

14 Additinal Requirements The fllwing additinal requirements als apply: The Orin Failver Engine cannt prtect any server cnfigured as a dmain cntrller, glbal catalg, r dmain name server. Yu must use an accunt with lcal administratr rights t cmplete an Orin Failver Engine installatin. All applicatins yu intend t prtect must be installed and cnfigured n the primary server prir t installing an Orin Failver Engine. Verify that bth primary and secndary servers have identical system date, time, and time zne settings. Once cnfigured, d nt change the time zne. Verify that the principal netwrk adapter is listed as the first netwrk adapter in the netwrk cnnectins bind rder. (Netwrk Cnnectins > Advanced > Advanced Settings). Firewalls prtecting the SlarWinds Channel netwrk cnnectins must be disabled t allw uninterrupted cmmunicatins between the primary and secndary servers. Cnsult the SlarWinds Knwledge Base fr additinal infrmatin. SQL Server shuld nt be installed n the same machine as Orin Failver Engine. Server Architecture Optins The server architecture yu select affects bth hardware requirements and the technique used t clne the primary server. The fllwing server architecture ptins are available: Virtual t Virtual (V2V) Physical t Virtual (P2V) Physical t Physical (P2P) Virtual t Virtual (V2V) The V2V architecture is supprted if the Orin Failver Engine is already installed n a primary prductin server running n a virtual machine. The secndary virtual machine must als meet the minimum requirements. Fr mre infrmatin abut minimum Orin Failver Engine requirements, see Installatin Requirements n page 7. 8 SlarWinds Orin Failver Engine Installatin

15 SlarWinds Orin Quick Start Guide The specificatins f the secndary virtual machine must match the specificatins f the primary virtual machine as fllws: Similar CPU (including resurce management settings) Apprpriate resurce pl pririties Same memry cnfiguratin, perating system versin, and service pack (including resurce management settings) Each virtual machine used in the V2V pair must be n a separate 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 Identical Memry Operating system versin and service pack The secndary virtual machine must have pririty in resurce management settings t ensure that ther virtual machines d nt impact its perfrmance. Each virtual NIC must use a separate virtual switch. Physical t Physical (P2P) P2P architecture is used in envirnments where bth the primary and secndary servers are physical servers. Nte: Using P2P limits installatin ptins as it requires using the Install Clne technique. This architecture requires attentin t detail when preparing fr installatin as bth hardware and sftware must meet specific prerequisites. Fr mre infrmatin abut the Install Clne technique, see Clning Technlgy Optins n page 10. Primary Server The primary server must meet the hardware and sftware requirements specified in Installatin Requirements n page 7. SlarWinds Orin Failver Engine Installatin 9

16 Secndary Server The secndary server perates as a near-clne f the primary server and must meet the fllwing requirements. Secndary server hardware must meet the fllwing requirements: Similar CPU and memry. Identical number f NICs as the primary server. Drive letters must match thse n the primary server. Available disk space must be greater than r equal t the space available n the primary server. Advanced Cnfiguratin and Pwer Interface (ACPI) cmpliance must match the primary server. If nt, cntact SlarWinds supprt fr further infrmatin. Sftware n the secndary server must meet the fllwing requirements: Operating system versin and service pack versin must match the primary server. The perating system must be installed t the same driver letter and directry as n the primary server. The machine name must be different frm the primary server prir t installing the Orin Failver Engine. The secndary server must be cnfigured in a wrkgrup. System date, time, and time zne settings must be cnsistent with the primary server. Clning Technlgy Optins Clning the primary server t create a near identical secndary server invlves different techniques depending n the selected server architecture. Supprted Pre-Clne Technlgies Orin Failver Engine supprts mst third-party clning technlgies fr creating pre-clned images fr use as a secndary server in the fllwing cnfiguratins: Physical t virtual. Fr mre infrmatin, see Physical t Virtual (P2V) n page 9. Virtual t virtual. Fr mre infrmatin, see Virtual t Virtual (V2V) n page SlarWinds Orin Failver Engine Installatin

17 Supprted Install Clne Technlgies SlarWinds Orin Quick Start Guide The Orin Failver Engine prvides supprt fr NTBackup n Windws 2003 and Wbadmin n Windws Server 2008 fr autmated install clning. This prcess is autmated, but it requires that all prerequisites fr a Physical t Physical architecture are met. Fr mre infrmatin, see Physical t Physical (P2P) n page 9. Applicatin Cmpnent Optins The Orin Failver Engine can accmmdate any supprted SlarWinds Orin installatin with the fllwing SlarWinds Orin mdules: SlarWinds Orin NPM MP v10.0 SP1 and higher SlarWinds Orin IPAM v1.7.1 and higher SlarWinds Orin APM v3.5 and higher SlarWinds Orin APM MP v4.0.1 and higher SlarWinds Orin IPSLA Manager v3.5 and higher SlarWinds Orin NTA v3.6 and higher SlarWinds Orin NCM v6.0 and higher Nte: NCM v7.0 is supprted, but it must be updated t NCM v7.0.1 if additinal plling engines r additinal web sites are in use. SlarWinds Orin SEUM v1.0 and higher SlarWinds Orin UDT v1.0 and higher SlarWinds Orin EOC v1.2 and higher Tmcat v5.5.6 Netwrk Optins Netwrking requirements are cntingent upn hw yur Orin Failver Engine is deplyed. T deply an Orin Failver Engine as a high availability slutin, a LAN cnfiguratin is required. Fr mre infrmatin, see LAN n page 11. T deply an Orin Failver Engine fr Disaster Recvery (DR), a WAN cnfiguratin is required. Fr mre infrmatin, see WAN n page 12. LAN When deplyed in a LAN envirnment, the Orin Failver Engine requires that bth servers use the same principal IP address. Each server als requires a separate SlarWinds Channel IP address n a separate dedicated subnet. SlarWinds Orin Failver Engine Installatin 11

18 Primary Server Three NICs (1 x principal; 2 x channel) are recmmended fr redundancy in the event that any single channel fails. A minimum f tw NICs (ne fr the SlarWinds Channel, and ne fr the principal cnnectin) are required in this cnfiguratin. Split-brain avidance shuld be cnfigured. The principal netwrk cnnectin is cnfigured with the fllwing: Static IP address Crrect netwrk mask Crrect Gateway and preferred and secndary DNS server addresses NetBIOS enabled Channel netwrk cnnectins are cnfigured with the fllwing: Static IP address in a different subnet than the principal netwrk with a different IP address than the secndary server channel NIC Crrect netwrk mask N Gateway IP address r DNS server address NetBIOS enabled (disabled during the installatin prcess) Secndary Server Netwrking cmpnents n the secndary server must be cnfigured as fllws: Same number f NICs as the primary server Principal 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 netwrk with a different IP address than the primary server channel NIC. Crrect netwrk mask N Gateway r DNS IP address NetBIOS enabled (disabled during the installatin prcess) File and print sharing enabled WAN Deplying an Orin Failver Engine in a WAN envirnment requires additinal cnsideratins as indicated in the fllwing sectin. 12 SlarWinds Orin Failver Engine Installatin

19 WAN Requirements SlarWinds Orin Quick Start Guide When deplying an Orin Failver Engine in a WAN envirnment, the fllwing cmpnents must be cnfigured: Persistent static ruting cnfigured fr the channel cnnectin(s) where ruting is required Tw NICs (1 x principal; 1 x SlarWinds Channel) recmmended At least ne dmain cntrller at the disaster recvery site If the primary and disaster recvery site use the same subnet: During install, fllw the steps fr a LAN r VLAN n the same subnet Bth servers in the Orin Failver Engine pair use the same principal IP address If the primary and disaster recvery site use different subnets: During install, fllw the steps fr a WAN Bth servers in the Orin Failver Engine pair require a unique principal, public IP address in a subnet separate frm the SlarWinds Channel Additinally, each server requires separate NIC with a SlarWinds Channel IP address assigned and static ruting cnfigured between the primary and secndary servers Prvide a user accunt with rights t update DNS using the DNSUpdate utility prvided as a cmpnent f the Orin Failver Engine when prmpted during the setup prcess Recmmend integrating Micrsft DNS int AD s that DNSUpdate can identify all DNS Servers that require updating At least ne dmain cntrller at the disaster recvery site Refer t the fllwing articles in the SlarWinds Knwledge Base: Cnfiguring DNS with Orin Failver Engine in a WAN Envirnment. Search SWREFID 1425 in the SlarWinds Knwledge Base. Cnfiguring Orin Failver Engine t Update BIND9 DNS Servers Deplyed in a WAN. Search SWREFID 1599 in the SlarWinds Knwledge Base. SlarWinds Orin Failver Engine Installatin 13

20 Bandwidth Determine the available bandwidth and estimate the vlume f data thrughput t determine acceptable latency fr the thrughput. Available bandwidth can affect the queue size required t accmmdate the estimated vlume f data. SlarWinds recmmends making a minimum f 1Mbit f spare bandwidth available t the Orin Failver Engine. The Orin Failver Engine ffers autmatic bandwidth ptimizatin in WAN envirnments. This feature cmpresses data transferred ver the SlarWinds Channel, ptimizing the traffic fr lw bandwidth cnnectins while placing 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. Specifically, FE Latency must nt exceed 100ms fr a WAN/DR cnfiguratin. Nte: Mirrring is nt supprted in an autmatic failver scenari. When Failver ccurs, yu must run the Cnfiguratin Wizard and pint yur installatin t the new database befre plling can resume. This is a manual peratin. Installatin Prcess After selecting implementatin ptins, begin the installatin prcess. The installatin prcess fr all scenaris fllws the same basic prcedure. Ntes: If the primary and secndary site subnet is the same, an IP address is required fr this subnet. If Active Directry-integrated DNS is enabled, a dmain accunt with rights t update DNS is required. If Active Directry-integrated DNS is nt enabled, see the fllwing knwledge base articles: Cnfiguring DNS with Orin Failver Engine in a WAN Envirnment. Search SWREFID 1425 in the SlarWinds Knwledge Base. Cnfiguring Orin Failver Engine t Update BIND9 DNS Servers Deplyed in a WAN. Search SWREFID 1599 in the SlarWinds Knwledge Base. Fr mre detailed infrmatin abut Orin Failver Engine installatin, see the Orin Failver Engine Administratr Guide. 14 SlarWinds Orin Failver Engine Installatin

21 Installatin n the Primary Server SlarWinds Orin Quick Start Guide After reviewing the setup prerequisites t ensure the servers in the pair (either physical r virtual) meet the minimum requirements and cmpleting the preinstallatin tasks (Pre-Clning fr V2V and P2V envirnments and cnfiguring the SlarWinds Channel), yu can begin the setup prcess. Ntes: Fr mre infrmatin abut minimum installatin requirements, see Installatin Requirements n page 7. If yu need help during the setup prcess, the left panel f the setup windw explains each step r ptin. When installing n Windws Server 2008, yu must specify a universal naming cnventin (UNC) path t the backup file lcatin. T set up the primary server 1. Duble-click the WinZip Self-Extracting file n the primary server. 2. The Setup Intrductin dialg is displayed. Click OK. 3. The WinZip Self-Extractr dialg is displayed. Click Setup t pen the Install SlarWinds Orin Failver Engine windw. 4. The first installatin ptin t cnfigure is the Setup Type. Select Install SlarWinds Orin Failver Engine. 5. On the fllwing step, select Primary as the Server Identity. During the setup prcess, yu have the pprtunity t identify the fllwing: The prgram Installatin lcatin SlarWinds Channel IP addresses The principal IP addresses A single IP fr a LAN installatin Tw IPs fr a WAN installatin The lcatin t stre the clne files Setup runs a pre-install check t verify that the server meets the minimum requirements befre installing Orin Failver Engine. The next ptin t cnfigure is the clning technique. When yu select the clning ptin, the subsequent setup screens display the setup prcess fr the selected clning technlgy. SlarWinds Orin Failver Engine Installatin 15

22 When using the Install Clne technique, setup makes a backup. When using the Pre-Clne setup, setup cpies tw small files t the strage lcatin cnfigured n the secndary server. A Packet Filter is installed n the principal NIC and the setup prcess cmpletes n the primary server. Installatin n the Secndary Server After reviewing the setup prerequisites t ensure the servers in the pair (either physical r virtual) meet the minimum requirements and cmpleting the preinstallatin tasks (Pre-Clning fr V2V and P2V envirnments and cnfiguring the SlarWinds Channel), yu can begin the setup prcess. Ntes: If the primary and secndary site subnet is the same, an IP address is required fr this subnet. If Active Directry-integrated DNS is enabled, a dmain accunt with rights t update DNS is required. If Active Directry-integrated DNS is nt enabled, see the fllwing knwledge base articles: Cnfiguring DNS with Orin Failver Engine in a WAN Envirnment. Search SWREFID 1425 in the SlarWinds Knwledge Base. Cnfiguring Orin Failver Engine t Update BIND9 DNS Servers Deplyed in a WAN. Search SWREFID 1599 in the SlarWinds Knwledge Base. Fr mre detailed infrmatin abut Orin Failver Engine installatin, see the Orin Failver Engine Administratr Guide. T set up the secndary server 1. Duble-click the WinZip Self-Extracting file t start the setup prcess fr the secndary server (physical r virtual). 2. The Setup Intrductin dialg is displayed. Click OK. 3. The WinZip Self-Extractr dialg is displayed. Click Setup t pen the Install SlarWinds Orin Failver Engine windw. 4. The first installatin ptin t select is the Setup Type. Select Install SlarWinds Orin Failver Engine. 5. Select Secndary fr the Server Identity ptin. 16 SlarWinds Orin Failver Engine Installatin

23 SlarWinds Orin Quick Start Guide 6. Specify the lcatin f the flder cntaining the backup file frm the primary server. Type the lcatin path in the text bx r click Brwse and lcate the flder. 7. Click Next. 8. Setup identifies the backup file lcatin and runs pre-install checks befre installing Orin Failver Engine n the secndary server. 9. The next step installs the Packet Filter and identifies the SlarWinds Channel and principal NICs. 10. When using an Install Clne setup in a LAN envirnment, cnfigure the principal NIC with the same IP address as the primary server. 11. After recnfiguring the principal NIC, if necessary, start the restre prcess. 12. Fllwing cmpletin f the restre prcess, if the secndary server is a physical server, Windws Plug and Play might run multiple times t detect hardware differences. As a result, ne r mre system restarts may be required. 13. After Plug and Play cmpletes detectin, the setup prcess displays the Finish windw. Actins Required After an Installatin After a successful installatin f the Orin Failver Engine, cmplete the fllwing tasks: 1. Activate the Orin Failver Engine license. 2. Ensure that the Orin Failver Engine is shut dwn. 3. Verify that the date, time, and time zne n the secndary server are identical t the same n the primary server. 4. Start the Orin Failver Engine n the primary server. 5. Start the Orin Failver Engine n the secndary server. 6. Right-click the System Tray icn and select Abut SlarWinds Orin Failver Engine t verify v6.4 (5984) is displayed. Cnfigure actins t take upn failure f a service Orin Failver Engine assigns three sequential tasks t perfrm in the event a mnitred service fails. Task ptins include Recver Service, Applicatin Restart, Lg Warning, Switchver, and any additinal user-defined tasks previusly created. By default, Orin Failver Engine assigns Recver Service t each f the three actins. T cause a switchver in the event f service failure, cnfigure the 3 rd ptin t Switchver. SlarWinds Orin Failver Engine Installatin 17

24 T cnfigure tasks t perfrm upn service failure: 1. Navigate t Applicatins: Services. 2. Select the intended service. 3. Click Edit and assign a task t each f the three failure ptins, and then click OK. Imprtant: Fr dependent services, failure actins must match the failure actins fr any prtected service n which thse services depend, in bth type and rder. Fr example: Service X is autmatically prtected by Orin Failver Engine Service Y is autmatically prtected by Orin Failver Engine and has a dependency n service X The system administratr sets custm recvery actins fr service X as fllws: First Failure = Recver Service Secnd Failure = Applicatin Restart Third Failure = Switchver In this situatin, the system administratr shuld als set the service recvery actins fr service Y t: First Failure = Recver Service Secnd Failure = Applicatin Restart Third Failure = Switchver Nte that if service X fails, the dependent service Y must als fail. If the service recvery actins fr service Y are different t thse fr service X, they may take precedence, fr example service X requires a switchver but the failure f service Y has already triggered a service restart actin. This advice applies nly t services which are autmatically prtected by Orin Failver Engine and dependent upn ne anther. These dependencies may be examined via the Windws Service Cntrl Manager, under Prperties > Dependencies. Fr services which are shwn in the Prtected services depend n: pane f the Orin Failver Manager Applicatins: Services page, this advice is nt applicable, because: 1. These services d nt depend n prtected services; rather, prtected services are dependent upn them; and 18 SlarWinds Orin Failver Engine Installatin

25 SlarWinds Orin Quick Start Guide 2. These services are nt directly managed by Failver Engine and therefre have n cnfigurable recvery actins. Nte: If an applicatin with the failure ptin set t Applicatin Restart fails, nly the services that have failed are restarted. Dependent services d nt stp and restart as a result f the failure. When Additinal Pllers (AP)s are nt installed, create an Exclusin Filter t reduce replicatin traffic T prevent needless replicatin f temprary files created when Additinal Pllers are nt used, create an Exclusin Filter. T create the Exclusin Filter: 1. Launch SlarWinds Orin Failver Manger. 2. Navigate t the Data: File Filters pane, and click Add Exclusin Filter t pen the Add Exclusin Filter dialg. 3. Type the cmplete path t r brwse t lcate the file at the fllwing lcatins: Windws Server 2003: C:\Dcuments and Settings\All Users\Applicatin Data\SlarWinds\JbEngine\*.sdf r 4. click OK. Windws Server 2008: C:\PrgramData\Applicatin Data\SlarWinds\JbEngine\*.sdf When IPAM 2.0 is installed, create an Inclusin Filter t replicate the IPAM.attributes.xml file T create the Inclusin Filter: 1. Launch the Orin Failver Manager n the active server. 2. Navigate t Data: File Filters. 3. Click Add Inclusin Filter. 4. Type the path belw r brwse t the file lcatin. <installatin_dir>\orin\infrmatin Service\2.0\Schemas\IPAM.attributes.xml 5. Click OK. SlarWinds Orin Failver Engine Installatin 19

26 20 SlarWinds Orin Failver Engine Installatin

27 SlarWinds Orin Quick Start Guide Chapter 3 Installatin Verificatin Installatin verificatin tests and validates yur installatin. The fllwing exercises are examples that must be perfrmed in rder. SlarWinds recmmends perfrming a switchver rather than a failver t test the peratin f the passive server. Warning: SlarWinds des nt recmmend attempting t test a failver n a prperly perating server pair using methds such as unplugging a pwer crd. When pwer is lst, any data nt written t the passive server is lst. Failver Simulatin Exercise 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, yu will stp the primary server frm prviding service and hide it frm the netwrk, then intrduce the secndary server t the netwrk and allw it t prvide service. Nte: Using the System Tray icn, verify that the primary server displays P/A indicating that it is the active server. On the secndary server, repeat the prcess and verify that the secndary server displays S/ indicating that it is passive. Using the SlarWinds Orin Failver Manager, navigate t the Data: Replicatin tab. Verify that bth the File System and the Registry status display as Synchrnized. Ntify any lcal users that the service will be unavailable fr the duratin f the exercise. Machine Activity Result Primary Shut dwn the Orin Failver Engine. Select Stp SlarWinds Orin Failver Engine and all prtected applicatins, and then click OK. With Orin Failver Engine shut dwn, n the primary server, click Start > All Prgrams > SlarWinds Orin > Orin Failver Engine > Cnfigure Server t launch the Cnfigure Server wizard. In the wizard, change the primary server s rle t passive. Start Orin Failver Engine, and then shut it dwn. Select Stp Orin Failver Engine and all prtected applicatins, and then click OK. Orin Failver Engine stps all mnitred services and exits. Primary server becmes passive This activates the netwrk filter hiding the primary server frm the netwrk. Installatin Verificatin 21

28 Machine Activity Result Secndary Client Click Start > All Prgrams > SlarWinds Orin > Orin Failver Engine > Cnfigure Server t launch the Cnfigure Server wizard. In the wizard, change the secndary server rle t active, and then start the Orin Failver Engine. Cmpare applicatin functinal status t defined criteria fr availability and perfrmance. The secndary server starts as the active server. The secndary server acts as the primary. Data Replicatin Exercise The Data Replicatin exercise fllws the Failver Simulatin exercise perfrmed previusly. The bjective is t take a wrking active server (the secndary server) and synchrnize it with the passive (primary server). This exercise als demnstrates that all the crrect services stpped when the primary server became passive. Ntes: Orin Failver Engine is running n the secndary active server. Using the System Tray icn, verify that the server status displays S/A. Orin Failver Engine is nt running n the primary server which is set t passive. Using the System Tray icn, verify that the server status displays / t indicate that Orin Failver Engine is nt running. Ntify any lcal users that the service will be unavailable fr the duratin f the exercise. Machine Activity Result Start Orin Failver Engine. Orin Failver Engine starts. The Orin Failver Engine shws the cnnectin between the secndary (active) and primary (passive) servers. Primary Wait fr bth the Registry and the File System t becme Synchrnized. Access the Orin Failver Engine lgs and cnfirm that n exceptin errrs ccurred during synchrnizatin. Data replicatin resumes frm the secndary server back t the primary server. Bth the File System & Registry becme Synchrnized. Bth machines are resynchrnized. All data changed n the secndary machine while the primary was running Orin Failver Engine is updated nt the primary machine. The secndary (active) machine cntinues t prvide service. 22 Installatin Verificatin

29 Switchver Exercise SlarWinds Orin Quick Start Guide This exercise demnstrates the ability t switch the functinality and peratins f the active server n cmmand t the ther server in the pair using SlarWinds Orin Failver Manager. Perfrm this exercise nly after successfully cmpleting the Failver Simulatin and Data Replicatin Exercises. Ntify any lcal users that the service will be unavailable fr the duratin f this exercise. Ntes: Using the System Tray icn, verify that the secndary server is active (S/A) and servicing clients. On the primary server, verify that the server is passive using the System Tray icn status (P/ ). On the secndary server, launch SlarWinds Orin Failver Manager and select the Data: Replicatin tab. Verify that bth the File System and Registry status are Synchrnized. Machine Activity Result Orin Failver Engine Any Click Make Active and cnfirm. Cnfirm applicatin perfrmance and availability meets previusly defined criteria. Verify that client applicatins are running as expected after the switchver prcess. The Orin Failver Engine 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 Orin Failver Engine shws the services starting n the newly active server. Bth the File System and the Registry are Synchrnized. Service as usual. Yu might have t refresh r restart sme client applicatins as a result f a switchver. Applicatin service transferred frm the riginally active machine t the riginally passive machine. Dcument the applicatin-client behavir fr future reference. Installatin Verificatin 23