Neverfail ClusterProtector Installation Guide for SQL Server 2005, … · 2018. 8. 22. ·...

Neverfail ClusterProtector InstallationGuide

ForSQL Server 2005, 2008 and 2008 R2

Clusters v2.1

You can find the most up-to-date technical documentation on the Neverfail Extranet at:

http://extranet.neverfailgroup.com.

The Neverfail Extranet also provides the latest product updates. If you have comments about thisdocumentation, submit your feedback to:

[email protected]

Artisan Infrastructure has taken all reasonable care to ensure the information in this document is accurate at the date ofpublication. In relation to any information on third party products or services, Artisan Infrastructure has relied on the bestavailable information published by such parties. Artisan Infrastructure is continually developing its products and services,therefore the functionality and technical specifications of Artisan Infrastructure’s products can change at any time. For thelatest information on the Artisan Infrastructure’s products and services, please contact us by email ([email protected] or visit our Web site www.artisaninfrastructure.com ).

Heartbeat is a product trade mark of Artisan Infrastructure, LLC. Artisan Infrastructure products are protected, in wholeor in part by U.S. and foreign patents, which include US. Patent No. 7,409,577 and 7,788,524 and European Patent No.1,397,744.

All third party product names referred to in this document are acknowledged as the trade marks for their respective ownerentities.

Copyright © 2015 Artisan Infrastructure, LLC All rights reserved.

http://extranet.neverfailgroup.commailto:[email protected]:[email protected]://www.artisaninfrastructure.com

ContentsPreface: About This Book...........................................................................v

Chapter 1: Requirements................................................................................................9Supported Network Configurations....................................................................................................................9Prerequisites..........................................................................................................................................................10

Software..........................................................................................................................................................10Hardware........................................................................................................................................................11Networking....................................................................................................................................................11

Chapter 2: Pre-Installation Tasks..................................................................................13Primary Cluster Tasks..........................................................................................................................................13

Channel IP Address Resource.....................................................................................................................13Configure the Channel IP Address Resource on MSCS 2003.................................................................13Configure the Channel IP Address Resource on WSFC 2008.................................................................17Configure the Channel IP Address Resource on WSFC 2012.................................................................20

Secondary / Standby Server Tasks......................................................................................................................24Add a Management IP Address to the Secondary Server.......................................................................24Rename the Secondary Server and Join the Domain...............................................................................24Disk Requirements........................................................................................................................................25Install the Protected Application on the Secondary Server.....................................................................25Configure Protected Application Services on the Secondary Server.....................................................25

Chapter 3: Installing Neverfail Heartbeat.....................................................................27Installing Neverfail Heartbeat on the Production Cluster.............................................................................27Installing Neverfail Heartbeat on the Secondary / Standby Server..............................................................41

Chapter 4: Post Installation Tasks................................................................................43Configure Neverfail Heartbeat Licenses...........................................................................................................43Set the 'Neverfail Service' Resource to Depend on Clustered Data Disk Resources..................................43Configure DR Server as Secondary / Passive...................................................................................................43Configure ClusterProtector Scripts....................................................................................................................44Obtain and Place SetSPN.exe Utility on DR Server.........................................................................................45Start Neverfail Heartbeat.....................................................................................................................................45Configure Credentials for ClusterProtector and Clustered SQL Server Plug-ins.......................................46Disable Auto-configured DNSUpdate Tasks (WAN Installation Only).......................................................46Configuring Neverfail Heartbeat.......................................................................................................................47

Configuring the Neverfail Heartbeat Failover..........................................................................................47Configuring the Neverfail Heartbeat Failover Timeout..........................................................................47

Glossary..........................................................................................................................49

iiiArtisan Infrastructure, LLC

Artisan Infrastructure, LLCiv

Neverfail ClusterProtector Installation Guide

About This Book

Overview

This guide explains how to install and configure Neverfail Heartbeat on an existing Microsoft Cluster toprovide disaster recovery protection for the clustered applications. The following diagram illustrates theproposed disaster recovery solution for Microsoft Clusters using Neverfail products to replicate data to asingle node cluster at a remote location.

Figure 1: Neverfail ClusterProtector Overview

Intended Audience

This document is designed for use by Neverfail Certified Implementation Engineers (NCIE) who possessdetailed knowledge of both Microsoft clustering and the Neverfail product suite. Although this documentprovides detailed steps to assist with the implementation of this solution, there are some areas that requiretechnical knowledge beyond the scope of this document and are not covered within this document.

Technical Experience

Engineers using this guide to implement the above-described solution should have the following qualifications/ experience:

• NCIE (Neverfail Certified Implementation Engineer)• MCP (Microsoft Certified Professional) - This should be in a windows server operating system• 1 Years working experience with Microsoft Clustering solutions

vArtisan Infrastructure, LLC

Related Documents

Additional information can be found in the Neverfail Heartbeat Installation Guide andNeverfail HeartbeatAdministrators Guides available on the Neverfail Extranet. The Neverfail Heartbeat Administrator's Guideprovides detailed instructions about the use of Neverfail Heartbeat in general

Overview of Content

This guide is designed to give guidance on the configuration and administration of Neverfail Heartbeat,and is organized into the following sections:

• Preface — About This Book (this chapter) provides an overview of this guide and the conventions usedthroughout.

• Chapter 1 — Requirements presents an overview of the minimum requirements to successfully installthe Neverfail ClusterProtector solution.

• Chapter 2 — Pre-installation Tasks discusses those tasks that must be accomplished prior to installingNeverfail ClusterProtector.

• Chapter 3 — Installing Neverfail Heartbeat describes the step-by-step procedure to install NeverfailClusterProtector.

• Chapter 4 — Post Installation Tasks discusses tasks to be performed after installing NeverfailClusterProtector including DNS tasks, scripts, and configuring timeouts.

Document Feedback

Neverfail welcomes your suggestions for improving our documentation and invites you to send yourfeedback to [email protected].

Abbreviations Used in Figures

The figures in this book use the abbreviations listed in the table below.

Table 1: Abbreviations

DescriptionAbbreviation

Neverfail ChannelChannel

Network Interface CardNIC

Physical to PhysicalP2P

Physical to VirtualP2V

Virtual to VirtualV2V

Storage Area Network type datastoreSAN

Technical Support and Education Resources

The following sections describe the technical support resources available to you. To access the current versionof this book and other books, go to http://extranet.neverfailgroup.com.

Online and Telephone Support

Use online support to view your product and contract information, and to submit technical support requests.Go to http://extranet.neverfailgroup.com/support.

Artisan Infrastructure, LLCvi


mailto:[email protected]://extranet.neverfailgroup.comhttp://extranet.neverfailgroup.com/support

Support Offerings

To find out how Neverfail Support offerings can help meet your business needs, go tohttp://www.neverfailgroup.com/services/technical-support.html.

Neverfail Professional Services

Neverfail Professional Services courses offer extensive hands-on labs, case study examples, and coursematerials designed for use as on-the-job reference tools. Courses are available on site, in the classroom, andlive online. For the day-to-day operations of Neverfail Heartbeat, Neverfail Professional Services providesofferings to help you optimize and manage your Neverfail Heartbeat servers. To access information abouteducation classes, certification programs, and consulting services, go tohttp://www.neverfailgroup.com/services/professional-services.html.

viiArtisan Infrastructure, LLC

http://www.neverfailgroup.com/services/technical-support.htmlhttp://www.neverfailgroup.com/services/professional-services

Artisan Infrastructure, LLCviii


Chapter1Requirements

Supported Network Configurations

WAN Implementation

When the primary and secondary sites are configured in different subnets, there is a requirement tohave a dedicated subnet on the primary site for the channel network. Below is an example of a typicalnetwork configuration.

Figure 2: WAN Implementation

LAN / Stretched LAN Implementation

When using a LAN\stretched LAN with layer 3 VLAN's you must have a dedicated VLAN for thechannel network that operates on a different subnet range than the Principal (Public) network trafficon each site. Following diagram shows a stretched LAN (for LAN implementation, the Public IP isthe same on both Primary and Secondary servers)

9Artisan Infrastructure, LLC

Figure 3: LAN / Stretched LAN

Prerequisites

This section describes the prerequisites for successfully installing this solution and describes theenvironment into which the product should be installed. This section also discusses the applicationsthat can be protected using this guide.

SoftwareThis section describes the software prerequisites required to install this solution.

Clustering ConfigurationThis documentation only supports Microsoft Clusters that are configured in an Active / Passiveconfiguration.

Note: Active / Active cluster solutions ARE NOT supported by this documentation or solution type.

The cluster should be split into two or more groups. The default cluster group should contain only aCluster IP, name, and quorum disk. There should also be a group for the protected application withits affected resources.

Neverfail Heartbeat VersionsThis documentation is compatible with the following versions of Neverfail:

• Neverfail Heartbeat v6.6.0 and later

Windows VersionsThis documentation is compatible with the following versions of Microsoft Windows:

• Windows 2003 Server Enterprise Edition• Windows 2008 Server Enterprise Edition• Windows 2008 R2 Enterprise Edition up to SP1

Artisan Infrastructure, LLC10


• Windows 2012 Enterprise Edition

Clustering Technologies• MSCS available on Windows 2003 Server• WSFC available on Windows 2008 Server• WSFC available on Windows 2012 Server

Application VersionsThis documentation is compatible with the following applications running on a Microsoft cluster:

• Microsoft SQL Server 2005 and SP4• Microsoft SQL Server 2008 SP2 and SP3• Microsoft SQL Server 2008 R2 SP1 and SP2

Utilities• Microsoft SetSPN.exe tool• The Failover Cluster Command Interface (FCCI) feature must be installed when deploying Windows

Server 2012 Failover Cluster

HardwareThis section describes the hardware prerequisites required to install this solution. Please refer to theMicrosoft Hardware Compatibility List to ensure the actual Cluster Hardware meets Microsoftspecifications.

Primary ClusterThis solution requires an existing Microsoft Cluster providing protection for one of the supportedapplications listed in the Application Versions section above. The Microsoft cluster should be in anActive / Passive configuration.

Secondary / Standby ServerA standalone server with an identical disk configuration to the Primary server is required on thedisaster recovery site.

NetworkingThis section describes the network prerequisites required to implement Neverfail ClusterProtector forSQL Server solution on a Microsoft Cluster with a Secondary / Standby Server.

Primary / Production ClusterEach node in the cluster must have a dedicated network adapter for the Neverfail Channel. (For acorrect implementation, the Production Cluster should have at least 3 separate networks adaptors: 1Principal (Public), 1 Cluster Private, and 1 NF Channel).

The dedicated Neverfail Channel network adapter on each node must be configured with a uniqueIP address in a subnet range that is different than any other Principal (Public) or Private Subnet rangein the network.


Requirements

Secondary / Standby ServerThe Secondary / Standby server must meet the following prerequisites:

• A unique network name and Principal (Public) IP address.• A standalone server with membership in a standalone workgroup (must not be a member of a

domain).• A dedicated Neverfail Channel network adapter that has been configured in either a separate

subnet range from the corporate network connection or in the same subnet range with static routesto the Cluster Neverfail Channel IP. (For a correct implementation, the DR server should have atleast 2 different NICs: 1 Principal (Public), 1 NF Channel)



Chapter2Pre-Installation Tasks

Primary Cluster Tasks

Before installing Neverfail ClusterProtector, a number of tasks must be performed to prepare theenvironment.

Note: The Failover Cluster Command Interface (FCCI) feature must be installed when deploying WindowsServer 2012 Failover Cluster

Channel IP Address ResourceThe Neverfail Channel IP is used for all communications between the Primary and Secondary server.As you are installing onto a Microsoft Cluster, the channel IP address must be shared between thecluster nodes. To do this a virtual IPAddress Resourcewill be createdwithin the protected applicationgroup on theMicrosoft Cluster. The procedure for creating theNeverfail Channel IPAddress Resourceis shown below.

Configure the Channel IP Address Resource on MSCS 2003

Procedure

Prior to installing Neverfail, the Neverfail Channel IP Address Resource must be configured.

To configure the Neverfail Channel IP Address Resource, follow the steps below:

1. Launch theMicrosoft Cluster Administrator console.2. Right-click the Protected Application Group as shown and then select theNew > Resource.


Figure 4: Protected Application Group

3. When the followingdialog is presented, enter a valid resource name (see note below) anddescription.Additionally, ensure that IP Address is selected as the Resource type . When all information has beenentered into the dialog, clickNext to continue.

Note: Please ensure that the Neverfail Channel resource name contains one of the terms "NF", "Neverfail"or "Channel". This is mandatory for a correct ClusterProtector installation. The Neverfail Channel resourcename is case sensitive and must be in the format specified

Figure 5: New Resource dialog

4. In the following dialog, ensure that all cluster nodes are listed as Possible owner of the resource, andthen clickNext to continue.



Figure 6: Possible Owners dialog

5. In the following dialog, since theNeverfail Channel IPAddress does not have dependent resourceswithin the cluster, click theNext button leaving the information unchanged.

Figure 7: Dependencies dialog

6. In the following dialog, enter the IP address and subnet mask for the selected Neverfail ChannelIP address to be used on the Primary nodes and then click Finish to complete the process.

Note: This is created as a cluster resource to ensure that all nodes within the cluster will have access tothe same Neverfail Channel IP address when the protected application group moves between cluster nodes.


Pre-Installation Tasks

Figure 8: TCP/IP Address Parameters dialog

7. A notification dialog is presented stating that the cluster resource Neverfail Channel IPwas createdsuccessfully. ClickOK to acknowledge the notification.

Figure 9: Notification dialog

8. Once the resource has been created, the resource behaviormust bemodified in the event the resourcefails. Right-click on the newly created resource and select Properties. When the tabbed NeverfailChannel IP Properties dialog is displayed, select the Advanced tab.

Figure 10: Neverfail Channel IP Properties dialog



9. Ensure that the Affect the group check box is cleared. This will ensure that, if the resource fails andis unable to come back online, the SQL group on the cluster will not be affected. ClickOK to closethe dialog.

10. Right-click the newly created IP address resource and select Bring online.

Figure 11: Bring Online

Configure the Channel IP Address Resource on WSFC 20081. Open theMicrosoft Failover Cluster Management Console.2. Right-click the protected application group as shown, and then click the Add a resource option

and select Add IP Address.

Figure 12: Add a Resource Navigation



Note: The purpose of creating this as a cluster resource is to ensure that all nodes within the cluster canhave access to the same channel IP address when the protected application group moves between clusternodes.

3. For the Neverfail Channel Adapter IP addresses to be available to the new IP Address Resource,navigate toNetworks and select the network corresponding to the Neverfail Channel subnet. Clickon Properties and select the Allow clients to connect through this network check box.

Figure 13: Cluster Network Properties

4. Right-click the newly added resource and selectProperties. Enter a valid resource name (for example,Neverfail Channel IP) and IP Address (for example, 9.1.1.10) for the Resource.



Figure 14: IP Address Properties

5. Select the Policies tab and clear the If restart is unsuccessful, fail over all resources in this service orapplication field. This will ensure that should this resource fail and is unable to come back online,that the cluster SQL group will not be affected on the cluster. Then clickOK.



Figure 15: IP Address Policies dialog

6. Right-click the newly created IP Address Resource and then select the Bring this resource onlineoption.

Configure the Channel IP Address Resource on WSFC 20121. Open theMicrosoft Failover Cluster Management Console.2. Right-click the protected application group as shown, and then click the Add a resource option

and select Add IP Address.



Figure 16: Add a Resource Navigation

Note: The purpose of creating this as a cluster resource is to ensure that all nodes within the cluster haveaccess to the same channel IP address when the protected application group moves between cluster nodes.

3. For the Neverfail Channel Adapter IP addresses to be available to the new IP Address Resource,navigate toNetworks and select the network corresponding to the Neverfail Channel subnet. Clickon Properties and select the Allow clients to connect through this network check box.



Figure 17: Cluster Network Properties

4. Right-click the newly added resource and selectProperties. Enter a valid resource name (for example,Neverfail Channel IP) and IP Address (for example, 9.1.1.10) for the Resource.



Figure 18: IP Address Properties

5. Select the Policies tab and clear the If restart is unsuccessful, fail over all resources in this service orapplication field. This will ensure that should this resource fail and is unable to come back online,that the cluster SQL group will not be affected on the cluster. Then clickOK.



Figure 19: IP Address Policies dialog

6. Right-click the newly created IP Address Resource and then select the Bring this resource onlineoption.

Secondary / Standby Server Tasks

Add a Management IP Address to the Secondary ServerAfter Neverfail installation is completed on the Secondary server, the Secondary server’s Principal(Public) IP address will be filtered by Neverfail. To allow access to the Secondary server, an additionalIP address (Management IP) is recommended. The Management IP address should be positioned asthe first IP address on the Principal (Public) network interface.

Rename the Secondary Server and Join the DomainFor this solution to work correctly, the Secondary server must have a unique name and must also bea member of the existing domain. Rename the Secondary server and make it a member of the correctdomain.

Procedure

To rename the Secondary server and join the domain:



1. While a member of a local workgroup, rename the Secondary server.2. Reboot the Secondary server to apply the network name change.3. Join the Secondary server to the domain and reboot it to complete the domainmembership process.

Disk RequirementsOn the Secondary/Stand-alone Server, the drive lettering schememust match the Primary/ProductionCluster node(s).

Youmust ensure that all disk volumes that will be used to hold protected application data are availableon the Secondary/Stand-alone Server.

Install the Protected Application on the Secondary ServerInstall the same versions of protected applications with identical service packs using the sameconfiguration as the Primary server. Ensure the correct paths to the protected application data are set(same as on Primary Cluster) – this is required by Neverfail in order to replicate data correctly.

Note: Install the protected application as a user with Domain Administrative rights.

Note: It is vital that the application being installed on the Secondary /Standby server is installed with anidentical configuration to that of the Primary / Cluster server installation. The application installation anddata locations must be the same to ensure that switchover / failover works.

Configure Protected Application Services on the Secondary ServerOnce the protected applications have been installed and configured on the Secondary server, navigateto Start > Administrative Tools > Services and on the Properties dialog of each of the protectedapplication services, set the application services toManual startup type. All protected applicationservices on the Secondary server will need to be in a stopped state to allow for Neverfail replication towork correctly.



Chapter3Installing Neverfail Heartbeat

The following steps should be performed on each cluster node and standby server.

Note:

• Neverfail Heartbeat installation folderMUST be identical on all servers, both Primary(s) and Secondary.• Before beginning installation of Neverfail, ensure that the Cluster Protected Application is owned and online

by/on the node where Neverfail is being installed.

Installing Neverfail Heartbeat on the Production Cluster

Procedure

The following steps should be performed on each cluster node and standby server.

Note: Before beginning installation of Neverfail, ensure that the Cluster Protected Application is owned andonline by/on the node where Neverfail is being installed.

1. To install Neverfail Heartbeat, launch Neverfail Setup by double-clicking the Setup.exe andfollow the steps below:

2. When the Setup Type page is displayed, select Install Neverfail Heartbeat as shown below and clickNext.


Figure 20: Setup Type page

3. When the Physical Hardware Identity page is presented, select Primary as shown below and clickNext.

Figure 21: Physical Hardware Identity page

4. When the License Agreement page is presented, select I accept terms of the License Agreement as shownbelow and clickNext.



Figure 22: License Agreement page

5. Neverfail presents the License Configuration page. Click the Add button and enter a valid licensekey(s) that corresponds to the HBSIG of the server, clickOK and then click onNext.

Figure 23: License Configuration page

Note: A valid license key based uponHardware HBSIG is required for each cluster node within theMicrosoftCluster, and also for the Secondary server.

The Select Topology page is displayed.

6. Select the appropriate topology between the pair, LAN orWAN. Then clickNext.


Installing Neverfail Heartbeat

Figure 24: Select Topology page

The Cloning Option page is displayed.

7. Select Pre-cloned as the cloning option. Then clickNext.

Figure 25: Cloning Option page

The Installation Paths page is displayed.

8. Specify the installation path. Choose to Create icons on Desktop if desired, and then clickNext.



Figure 26: Installation Paths page

The Channel Adapter Identification page is displayed.

9. Select the network card to be used for the Neverfail Channel and clickNext.

Figure 27: Channel Adapter Identification page

10. When theNeverfail Channel Configuration screen is displayed, clickAdd to add a Neverfail Channelpair.



Figure 28: Neverfail Channel IP Configuration page

11. Ensure that the IP Address on Primary drop down shows the IP address previously configured forthe Neverfail Channel IP Address resource. Type the Secondary server’s Neverfail Channel IPaddress into the IP Address On Secondary field and clickOK to continue.

12. If installing on Secondary: Ensure that the IP Address on Primary drop down shows the currentSecondary server Channel IP. Type the clustered Neverfail Channel IP into the IP Address OnSecondary field and clickOK to continue. They will be corrected after the installation.

Figure 29: Add Neverfail Channel Link dialog

13. When the Add Neverfail Channel Link dialog is dismissed, the Neverfail Channel Configuration pageis displayed with the current configuration data for the Neverfail Channel. ClickNext to continue.



Figure 30: Neverfail Channel IP Configuration page

14. Neverfail Setup displays the Public Adapter Identification page as shown below. Select the networkadapter configured for use with the Principal (Public) network and clickNext.

Figure 31: Public Adapter Identification page

15. The next screen displays the Principal (Public) IP Address Configuration. If installing into a LANenvironment, select the Use same IP addresses for Secondary radio button or if installing into a WANenvironment, select the Use different IP addresses for Secondary radio button. Add the correct IPaddresses then clickNext.

Note: Ensure that it used the Clustered SQL Server IP address as the Principal (Public) IP address andnot one of the individual cluster nodes.



16. If installing on Secondary:a) For LAN installs, the Principal (Public) IP address of the DR server will be configured with the

Management IP address. (for example, the only IP address set on the Principal (Public) NIC).It will be corrected after the installation.

b) For WAN / Stretch-LAN installations, the Principal (Public) IP address of the DR server will bespecified as Primary Principal (Public) IP and the Clustered SQL Server IP address will be setas the Secondary Principal (Public) IP address. These will be corrected after the installation.

Figure 32: Principal (Public) IP Address Configuration page

17. If configuring different IP addresses for Primary and Secondary servers, Neverfail displays theUser Details page. Enter the credentials for a valid Domain Administrator account. This account isused to run select tasks during a failover/switchover. Once complete, clickNext to continue.

Figure 33: User Details page



18. The following screen displays the default Client Connection Port. Unless this port is already in use,leave the default settings and clickNext.

Figure 34: Client Configuration page

The Licensed Feature Configuration page is displayed.

19. The next screen displays the licensed features that can be installed. Select (if possible) the checkboxes for the desired features, and then clickNext.

Figure 35: Licensed Feature Configuration page

20. Neverfail displays theAM(X) Configuration page. Click theAdd button and navigate to the plug-infiles location.

21. Add in sequence, first ClusterProtectorNFPlugin, and then ClusteredSQLServerNFPlugin. ClickNextto continue.



Note: It is mandatory that the installation order is ClusterProtectorNFPlugin, and thenClusteredSQLServerNFPlugin.

Figure 36: AM(X) Configuration page

22. On the following screen, select a folder that will store the pre-synchronization data configurationfiles. ClickNext.

Note: Neverfail ClusterProtector solutions do not use pre-synchronization data configuration files but afolder must be selected to allow setup to continue.

Figure 37: Pre-Synchronization Data Configuration page



23. At this point, Neverfail Setup displays the Installation Summary page. After reviewing the content,clickNext to continue.

Figure 38: Installation Summary page

The Validate Collector Installation page is displayed.

24. Click Install to install the Validate Collector on the local server.

The results of the Validate Collector installation are displayed in the Report pane. If the ValidateCollector is not successfully installed, click Back to reattempt installation.

Figure 39: Validate Collector Installation page

25. After Validate Collector is successfully installed on the local server, clickNext.



Figure 40: Validate page

Validate Collector gathers required information from the local server and provides the status ofthe gathering operation. Upon completion of information gathering, high level results are displayedin the lower pane of the page with the color green and a check mark for success, a blue trianglewith an exclamationmark for informational, a yellow triangle with exclamationmark for warning,or the color red and an "X" for failure. To re-run Validate, click Retry. To change the location of theValidate report, type a new path or click Browse and select a new location for the Validate report.

26. Click the View link at the lower left of the Validate pane and review the detailed report providedby Validate.A web browser is launched and the detailed contents of the Validate are displayed. Review thecontents for failures, warnings, or recommendations.

Figure 41: Validate Report



27. After reviewing the Validate report, clickNext to continue the installation.Neverfail Setup performsa pre-installation check to ensure the prerequisites have been met.

Figure 42: Pre-Install Checks page

If the pre-installation check fails, click the Back button, find and resolve the issue, and then onceagain, run the pre-installation check. Once the pre-installation check has successfully completed,clickNext.

28. Neverfail starts installation of program files. The progress of the installation is displayed on thecurrent screen. Once the file installation is complete, clickNext to continue.

Figure 43: Install page

Neverfail Setup starts to install theNeverfail Packet Filter and displays the progress of theNeverfailPacket Filter configuration on the screen below.



Note: Only for Primary installation(s) : The installation of the packet filter may cause the clustergroup to failover from the currently active cluster node to the next available passive node. The cluster groupshould be left failed over to allow for the installation of Neverfail Heartbeat on the second cluster node. Ifthe cluster group does not failover, move the cluster group to the passive node before beginning the installationon the next node.

Figure 44: Packet Filter Installation page

29. Upon completion of the Neverfail Packet Filter installation, clickNext to continue.At this point, Neverfail Setup displays that the Primary server installation is complete. Do notselect Start Neverfail Heartbeat. Click the Finish button to complete the installation process.

Figure 45: Primary Installation Complete page



30. Navigate to Start > Control Panel > Network Connections and verify that the Neverfail PacketFilter was enabled only for the Principal (Public) network adapter. If it is enabled on other networkadapters, then disable it.

Installing Neverfail Heartbeat on the Secondary / Standby Server

The installation process on the Secondary server follows the steps for the Production cluster above.Where necessary, additional notes or comments are inserted, starting with If installing on Secondary

Note: Neverfail Heartbeat installs on Secondary as a Primary server. The identity, role and networkconfiguration will be corrected at the end of the installation.



Chapter4Post Installation Tasks

The following tasks should be performed in the order they are presented, immediately after the installationis finished and BEFORENeverfail Heartbeat is started on all three servers.

Configure Neverfail Heartbeat LicensesNeverfail Heartbeat licenses are required for each node including Secondary Cluster nodes andStandalone DR nodes.

1. Obtain separate licenses for each node.A separate license is required for each node because the license is based upon the HBSIG which isunique for each node.

2. Using the Configure Server wizard, install all licenses on each node.This is required to ensure a valid license is available to Neverfail Heartbeat in the event of aswitchover or failover.

Set the 'Neverfail Service' Resource to Depend on Clustered DataDisk Resources

On the Primary active node, configure the Neverfail Service cluster resource to depend also on all ofthe clustered data disk resources (by default it depends on the Neverfail Channel resource).

Configure DR Server as Secondary / PassiveThe DR server was installed as a Primary server. The following procedure describes how to configureit as Secondary - Passive.

Procedure

On the Secondary Server:

1. Launch theNeverfail Configure Serverwizard and click on theMachine tab. Select Secondary for thePhysical Hardware Identity. The Active Server should show Primary as selected (if not, select Primaryfor the Active Server). ClickNext.


Figure 46: Server Configuration Machine tab

2. Click on the Channel tab and ensure that the Neverfail Channel IP resource created on theProduction cluster is assigned to the Primary server and the one created on the Disaster Recoveryserver is assigned to the Secondary server. Make corrections if necessary. ClickNext, and then clickFinish to save the changes.

3. Click on the Public tab and ensure that the Secondary Principal (Public) IP address is configured.If not, make corrections by choosing the correct one from the drop-down list. Click Finish to savethe changes.

Configure ClusterProtector Scripts

During Heartbeat setup, the scripts used by the ClusterProtector were automatically generated andplaced in the \R2\Scripts folder of each Primary active node.Some of the scripts require manual editing. It is recommended to edit the scripts only (once) on theactive node, then copy them on the other Primary node and Secondary servers. For each script, readcarefully the indications (rem comments) and provide the required input.

ClusterProtector Scripts

setSpnDel.bat and setSpnAdd.bat

• Edit the log on account for the SQL Server service, or the machine name if the account is LocalSystem.

• Edit the SQL Server port number, if different than default.• For Windows 2012 installs delete or comment the following command cd /d C:\Program

Files\Neverfail\R2\Scripts

startPrimary.bat



• If this is a WAN install, edit the Secondary Public IP address in the DNSUpdate command, andremove rem’ from the beginning of the line (un-comment the line); also un-comment the ‘echoDNSUpdate […]’ command.

• Edit from SC command with either the FQDN or Management IP address ofthe Secondary server.

stopPrimary.bat

• Nothing to edit.

startSecondary.bat

• If this is a LAN / Stretched LAN install, edit the Public NIC name of the Secondary server in theNFIP command.

• If this is a WAN install, edit the Secondary Public IP address in the DNSUpdate command, andremove rem from the beginning of the line (un-comment the line); also un-comment the echoDNSUpdate […] command and comment the NFIP command by placing rem at the beginning ofthe line.

stopSecondary.bat

• If this is a LAN install/Stretched LAN, edit the Public NIC name of the Secondary server in theNFIP command.

• If this is a WAN install, comment the NFIP command by placing rem at the beginning of the line

Optionally, the user can choose to control other application services (if present), by placing the correctcommands into the scripts.

After all the scripts are edited, copy them to the \R2\Scripts>folder, on the other Primary cluster node (mandatory) and the Secondary server (optional, since theywill be replicated by Neverfail).

Note: Any script changes should be performed only on the Primary ACTIVE cluster node, and theyMUSTbe immediately copied to the other (passive) cluster node.

Obtain and Place SetSPN.exe Utility on DR Server

Obtain and place SetSPN.exe utility on Production cluster nodes and place it on each of theProduction/Primary nodes, in the \R2\Scripts> folder. Thisutility is required by the Secondary tasks.

Start Neverfail Heartbeat

During installation, the Neverfail Servicewas automatically configured as a resource within the SQLcluster group. This way Neverfail Heartbeat/ClusterProtector is controlled by the cluster, ensuringthat data replication always occurs between Primary active node and Secondary servers.

For replication to work correctly, ensure the Neverfail Channel IP and SQL cluster disk(s) resources(where appropriate) are online on the Primary Cluster. Also, create permissions in the WindowsFirewalls to allow Neverfail to communicate over the channel.


Post Installation Tasks

In order to start Neverfail Heartbeat – ClusterProtector, the following actions should be performed:

1. On Primary active cluster node, bring the Neverfail Service resource online.2. On Secondary server, start Neverfail Heartbeat (if not already started).

Configure Credentials for ClusterProtector and Clustered SQLServer Plug-ins

In order to run the associated pre start/stop tasks, ClusterProtector and Clustered SQL Server plug-insneeds to be configured with appropriate credentials (they are configured by default with Local Systemcredentials). To do that:

1. Open a Neverfail Heartbeat Management Client connection to Primary/Active server.2. Navigate to Applications > Plug-ins.3. HighlightClusterProtectorNFPlugin.dll, clickEdit, and then enter the appropriate domain,

username, password (usually the domain administrator credentials are used). ClickOK.4. Highlight ClusteredSQLServerNFPlugin.dll, click Edit, and then enter the appropriate

domain, username, password (usually the domain administrator credentials are used). ClickOK.The above steps must be performed on each Primary cluster node, when active.

Note: The user configured in the ClusterProtector and ClusteredSQLServer plug-ins must have thefollowing permissions:

• Read All SPN• Write All SPN• All Validated SPN

Disable Auto-configured DNSUpdate Tasks (WAN Installation Only)This task should be only performedwhenNeverfail Heartbeat is installed in aWAN. It is not requiredfor LAN deployments.

Procedure

The following steps should be performed only on currently active cluster node:

1. Using theNeverfail Heartbeat Management Client, connect to the Primary/active Neverfail Heartbeatserver.

2. Navigate to Applications > Tasks.3. Highlight the DNSUpdate (Primary) task, click Edit, and then clear the Enabled check box. Click

OK.4. Highlight the DNSUpdate (Secondary) task, click Edit, and then clear the Enabled check box. Click

OK.



Figure 47: Edit Task dialog

Note: The custom DNSUpdate command is executed from the ClusterProtector start scripts.

Configuring Neverfail Heartbeat

Configuring the Neverfail Heartbeat FailoverOn LAN installations, auto-failover is enabled by default. Neverfail strongly recommends disablingauto-failover and configuring manual failover to avoid split-brain if the communication channel failsbetween Primary and Secondary servers. Administrators can then control failover bymanuallymakingthe Secondary/DR server active.

Procedure

To disable auto-failover:

1. Launch the Neverfail Heartbeat Management Client and navigate to the Server: Monitoring.2. Clear option Failover from Primary server to Secondary server if channel Heartbeat is lost for failover

timeout.3. Clear option Failover from Secondary server to Primary server if channel Heartbeat is lost for failover

timeout.4. ClickOK to save the settings.

Configuring the Neverfail Heartbeat Failover TimeoutThe default Failover timeout is set to 60 seconds. For deploymentswhere the clustermove node/failovernormally takesmore time (than 60 seconds), theNeverfail Heartbeat Failover timeout should be increasedto a value which ensures avoidance of false failover. This must be done on both cluster nodes, whileactive.

Procedure

To configure Failover timeout:

1. Open the Neverfail Heartbeat Management Client and navigate to the Server: Monitoring.2. Click the Configure Failover button.

The following dialog appears:


Post Installation Tasks

Figure 48: Server Monitoring: Failover Configuration dialog

3. Configure the Failover timeout to the new value, and then clickOK.



Glossary

ActiveThe functional state or role of a server when it is visibleto clients through the network, running protectedapplications, and servicing client requests.

Active Directory (AD)Presents applications with a single, simplified set ofinterfaces so users can locate and use directory resourcesfrom a variety of networks while bypassing differencesbetween proprietary services. Neverfail Heartbeatswitchovers and failovers require no changes to ADresulting in switchover/failover times typicallymeasuredin seconds.

Active Server QueueThe staging area of the active server used to storeintercepted data changes before being transported acrossthe Channel to the passive server.

Active–PassiveThe coupling of two servers with one server visible toclients on a network and providing application servicewhile the other server is not visible and not providingapplication service to clients.

Advanced Configuration and PowerInterface (ACPI)A specification that dictates how the operating systemcan interact with the hardware especially where powersaving schemes are used. The Primary, Secondary, andTertiary servers must have identical ACPI compliance.

AlertA notification provided by Neverfail Heartbeat sent toa user or entered into the system log indicating anexceeded threshold.

AsynchronousA process whereby replicated data is applied (written)to the passive server independently of the active server.

Basic Input/Output System (BIOS)The program a personal computer'smicroprocessor usesto get the computer system started after you turn it on.It also manages data flow between the computer'soperating system and attached devices such as the harddisk, video adapter, keyboard, mouse, and printer.

Cached CredentialsLocally stored security access credentials used to log intoa computer system when a Domain Controller is notavailable.

Channel DropAn event in which the dedicated communications linkbetween servers fails, often resulting in the passive serverbecoming active and consequently creating a split-brainsyndrome.

Channel NIC (Network Interface Card)A dedicated subnet used by the Neverfail Channel.

CheckedThe status reported for user account credential(username/password) validation.

Cloned ServersServers that have identical configuration settings, names,applications, Security Identifiers (SIDs) and IP addresses,following the installation of Neverfail Heartbeat.


Cloning ProcessThe Neverfail Heartbeat process whereby all installedprograms, configuration settings, and themachine name,Security Identifier (SID), and IP address are copied toanother server.

ClusterAgeneric term for aNeverfail Heartbeat Pair or Trio andthe set of machines (physical or virtual) involved insupporting a single protected server. A NeverfailHeartbeat Cluster can include the machines used in aVMware or Microsoft cluster.

ConnectionAlso referred to as Cluster Connection. Allows theNeverfail HeartbeatManagementClient to communicatewith a Neverfail Heartbeat Cluster, either on the samemachine or remotely.

Crossover CableA network cable that crosses the transmit and receivelines.

Data ReplicationThe transmission of protected data changes (files andregistry) from the active to the passive server via theNeverfail Channel.

Data Rollback ModuleANeverfail Heartbeatmodule that allows administratorsto rollback the entire state of a protected application,including files and registry settings, to an earlierpoint-in-time. Typically used after some form of dataloss or corruption.

DegradedThe status reported for an application or service that hasexperienced an issue that triggered a Rule.

Device DriverA program that controls a hardware device and links itto the operating system.

Disaster Recovery (DR)A term indicating how you maintain and recover datawith Neverfail Heartbeat in event of a disaster such as ahurricane or fire. DR protection can be achieved byplacing the Secondary server (in a Pair) or the Tertiaryserver (in a Trio) at an offsite facility, and replicating thedata through a WAN link.

DNS (Domain Name System) ServerProvides a centralized resource for clients to resolveNetBIOS names to IP addresses.

DomainA logical grouping of client server basedmachineswherethe administration of rights across the network aremaintained in a centralized resource called a domaincontroller.

Domain Controller (DC)The server responsible for maintaining privileges todomain resources; sometimes called AD controller inWindows 2003 and above domains.

DualedA way to provide higher reliability by dedicating morethan one NIC for the Neverfail Channel on each server.

FailoverFailover is the process by which the 1st passive serverassumes the active role when it no longer detects thatthe active server is alive as a result of a criticalunexpected outage or crash of a server.



First PassiveThe passive server in a Neverfail Heartbeat Pair or Triocommunicating with and receiving replicated datadirectly from the active server.

Full System Check (FSC)The internal process automatically started at the initialconnection or manually triggered through the ManageServer GUI to perform verification on the files andregistry keys and then synchronize the differences.

Fully Qualified Domain Name (FQDN)Also known as an absolute domain name, a FQDNspecifies its exact location in the tree hierarchy of theDomain Name System (DNS). It specifies all domainlevels, including the top-level domain, relative to the rootdomain. Example: somehost.example.com., where thetrailing dot indicates the root domain.

Graceful (Clean) ShutdownA shutdown of Neverfail Heartbeat based uponcompletion of replication by use of the NeverfailHeartbeat Neverfail Heartbeat Management Client,resulting in no data loss.

GroupAn arbitrary collection of Neverfail Heartbeat Clustersused for organization.

Hardware AgnosticA key Neverfail Heartbeat feature allowing for the useof servers with different manufacturers, models, andprocessing power in a singleNeverfail Heartbeat Cluster.

HeartbeatThe packet of information issued by the passive serveracross the Channel, which the active server responds toindicating its presence.

High Availability (HA)Keeping users seamlessly connected to their applicationsregardless of the nature of a failure. LAN environmentsare ideally suited for HA.

HotfixA single, cumulative package that includes one or morefiles that are used to address a problem in a product.

IdentityThe position of a given server in the Neverfail HeartbeatCluster: Primary, Secondary, or Tertiary.

Install CloneThe installation technique used by Neverfail Heartbeatto create a replica of the Primary server usingNTBackupor Wbadmin and to restore the replica to the Secondaryand/or Tertiary servers.

Low Bandwidth Module (LBM)A Neverfail Heartbeat module that compresses andoptimizes data replicated between servers over a WANconnection. This deliversmaximumdata throughput andimproves application response time on congestedWANlinks.

Machine NameThe Windows or NETBIOS name of a computer.

Management IP AddressAn additionally assigned unfiltered IP address used forserver management purposes only.

Many-to-OneThe ability of one physical server (hostingmore than onevirtual server) to protect multiple physical servers.


Glossary

Network MonitoringMonitoring the ability of the active server to communicatewith the rest of the network by polling defined nodesacross the network at regular intervals.

Neverfail ChannelThe IP communications link used by theNeverfail systemfor the heartbeat and replication traffic.

Neverfail ExtranetThe Neverfail web site dedicated to supporting partnersand customers by providing technical information,software updates, and license key generation.

Neverfail HeartbeatThe core replication and system monitoring componentof the Neverfail solution.

Neverfail Heartbeat Packet FilterThe network component, installed on all servers, thatcontrols network visibility.

Neverfail License KeyThe key obtained from theNeverfail extranet that allowsthe use of components in the Neverfail suite; entered atinstall time, or through the Configure Server Wizard.

Neverfail PairDescribes the coupling of the Primary and Secondaryserver in a Neverfail solution.

Neverfail Plug-insOptional modules installed into a Neverfail Heartbeatserver to provide additional protection for specificapplications.

Neverfail ReplicatorA functionally limited version of theNeverfail Heartbeatproduct.

Neverfail SCOPEThe umbrella name for the Neverfail process and toolsused to verify the production servers health andsuitability for the implementation of aNeverfail solution.

Neverfail SCOPE ReportA report provided upon the completion of the NeverfailSCOPE process that provides information about theserver, system environment, and bandwidth.

Neverfail Switchover/Failover ProcessAprocess unique toNeverfail inwhich the passive servergracefully (switchover) or unexpectedly (failover)assumes the role of the active server providingapplication services to connected clients.

Neverfail TrioDescribes a set of three coupled servers (Primary,Secondary, and Tertiary) in a Neverfail solution.

PairSee Neverfail Heartbeat Pair above.

PassiveThe functional state or role of a server when it is notdelivering service to clients and is hidden from the restof the network. For a Neverfail Heartbeat Trio, see alsoFirst Passive and Second Passive.

Passive Server QueueThe staging area on the passive server used to storechanges received from the active server before they areapplied to the disk/registry on the passive server.



PathpingA route-tracing tool that works by sending packets toeach router on theway to a final destination and displaysthe results of each hop.

Plug-and-Play (PnP)A standard for peripheral expansion on a PC.On startingthe computer, PnP automatically configures the necessaryIRQ, DMA and I/O address settings for the attachedperipheral devices.

Plug-inAn application specific module that adds NeverfailHeartbeat protection for the specific application.

Pre-CloneAn installation technique whereby the user creates anexact replica of the Primary server using VMwarevCenter Converter or other 3rd party utility prior to theinitiation of installation and uses the replica as aSecondary and or Tertiary server.

Pre-Installation ChecksA set of system and environmental checks performed asa prerequisite to the installation of Neverfail Heartbeat.

PrimaryAn identity assigned to a server during the NeverfailHeartbeat installation process that normally does notchange during the life of the server and usuallyrepresents the production server prior to installation ofNeverfail Heartbeat.

Principal (Public) IP AddressAn IP address used by clients to contact the serverthrough drive mappings, UNC paths, DNS resolvedpaths, etc., to gain access to the server's services andresources.

Principal (Public) NetworkThe network used by clients to connect to serverapplications protected by Neverfail Heartbeat.

Principal NICThe network card which hosts the Principal IP address.

Protected ApplicationAn application protected by the Neverfail Heartbeatsolution.

Quality of Service (QoS)An effort to provide different prioritization levels fordifferent types of traffic over a network. For example,Neverfail Heartbeat data replication may have a higherpriority than ICMP traffic, as the consequences ofinterrupting data replication are more obvious thanslowing down ICMP traffic.

Receive QueueThe staging area on a server used to store changesreceived from another server in the replication chainbefore they are applied to the disk/registry on the passiveserver.

Remote Desktop Protocol (RDP)A multi-channel protocol that allows a user to connectto a computer running Microsoft Terminal Services.

ReplicationThe generic term given to the process of interceptingchanges to data files and registry keys, transporting thechanged data across the Channel, and applying them tothe passive server(s) so the servers are maintained in asynchronized state.

RoleThe functional state of a server in theNeverfail HeartbeatCluster: active or passive.


Glossary

RuleA set of actions performed byNeverfail Heartbeat whendefined conditions are met.

Second PassiveThe passive server in a Neverfail Heartbeat Triocommunicating with and receiving replicated datadirectly from the 1st passive server.

SecondaryAn identity assigned to a server during the NeverfailHeartbeat installation process that normally does notchange during the life of the server and usuallyrepresents the standby server prior to installation ofNeverfail Heartbeat.

Security Identifier (SID)A unique alphanumeric character string that identifieseach operating system and each user in a network of2003/2008 systems.

Send QueueThe staging area on a server used to store intercepteddata changes before being transported across to a passiveserver in the replication chain.

Server MonitoringMonitoring of the active server by the passive server,using a heartbeatmessage, to ensure that the active serveris functional.

Shared NothingA key feature of Neverfail Heartbeat in which nohardware is shared between the Primary, Secondary, andTertiary servers. This prevents a single point of failure.

SMTPA TCP/IP protocol used in sending and receiving e-mailbetween servers.

SNMPSimple Network Management Protocol (SNMP) is anInternet-standard protocol for managing devices on IPnetworks.

Split-Brain AvoidanceA unique feature of Neverfail Heartbeat that prevents ascenario inwhichPrimary and Secondary servers attemptto become active at the same time leading to anactive-active rather than an active-passive model.

Split-Brain SyndromeA situation in whichmore than one server in a NeverfailHeartbeat Cluster are operating in the active mode andattempting to service clients, resulting in the independentapplication of different data updates to each server.

Storage Area Network (SAN)A high-speed special-purpose network or (subnetwork)that interconnects different kinds of data storage deviceswith associated data servers on behalf of a larger networkof users.

SubnetDivision of a network into an interconnected butindependent segment or domain, intended to improveperformance and security.

SwitchoverThe graceful transfer of control and application serviceto the passive server.

SynchronizeThe internal process of transporting 64KB blocks ofchanged files or registry key data, through the NeverfailChannel, from the active server to the 1st passive serveror from the 1st passive server to the 2nd passive serverto ensure the data on the passive server is amirror imageof the protected data on the active server.



System Center Operations Manager(SCOM)System Center Operations Manager is a cross-platformdata center management server for operating systemsand hypervisors.

System StateData that comprises the registry, COM+ ClassRegistration database, files under Windows FileProtection, and system boot file; other data may beincluded in the system state data.

TaskAn action performed by Neverfail Heartbeat whendefined conditions are met.

TertiaryAn identity assigned to a server during the NeverfailHeartbeat installation process that normally does notchange during the life of the server and usuallyrepresents the disaster recovery server prior toinstallation of Neverfail Heartbeat.

Time-To-Live (TTL)The length of time that a locally cached DNS resolutionis valid. TheDNS servermust be re-queried after the TTLexpires.

TracerouteA utility that records the route through the Internetbetween your computer and a specified destinationcomputer.

TrioSee Neverfail Heartbeat Trio above.

Ungraceful (Unclean) ShutdownA shutdown of Neverfail Heartbeat resulting from acritical failure or by shutting down Windows withoutfirst performing a proper shutdown of NeverfailHeartbeat, resulting in possible data loss.

Unprotected ApplicationAn application not monitored nor its data replicated byNeverfail Heartbeat.

Virtual Private Network (VPN)A private data network that makes use of the publictelecommunication infrastructure, maintaining privacythrough the use of a tunneling protocol and securityprocedures.

WindowsManagement Instrumentation(WMI)A management technology allowing scripts to monitorand controlmanaged resources throughout the network.Resources include hard drives, file systems, operatingsystem settings, processes, services, shares, registrysettings, networking components, event logs, users,clusters, and groups.


Glossary



ContentsAbout This BookRequirementsSupported Network ConfigurationsPrerequisitesSoftwareClustering ConfigurationNeverfail Heartbeat VersionsWindows VersionsClustering TechnologiesApplication VersionsUtilities

HardwarePrimary ClusterSecondary / Standby Server

NetworkingPrimary / Production ClusterSecondary / Standby Server

Pre-Installation TasksPrimary Cluster TasksChannel IP Address ResourceConfigure the Channel IP Address Resource on MSCS 2003Configure the Channel IP Address Resource on WSFC 2008Configure the Channel IP Address Resource on WSFC 2012

Secondary / Standby Server TasksAdd a Management IP Address to the Secondary ServerRename the Secondary Server and Join the DomainDisk RequirementsInstall the Protected Application on the Secondary ServerConfigure Protected Application Services on the Secondary Server

Installing Neverfail HeartbeatInstalling Neverfail Heartbeat on the Production ClusterInstalling Neverfail Heartbeat on the Secondary / Standby Server

Post Installation TasksConfigure Neverfail Heartbeat LicensesSet the 'Neverfail Service' Resource to Depend on Clustered Data Disk ResourcesConfigure DR Server as Secondary / PassiveConfigure ClusterProtector ScriptsObtain and Place SetSPN.exe Utility on DR ServerStart Neverfail HeartbeatConfigure Credentials for ClusterProtector and Clustered SQL Server Plug-insDisable Auto-configured DNSUpdate Tasks (WAN Installation Only)Configuring Neverfail HeartbeatConfiguring the Neverfail Heartbeat FailoverConfiguring the Neverfail Heartbeat Failover Timeout

Glossary

Neverfail ClusterProtector Installation Guide for SQL Server 2005, … · 2018. 8. 22. ·...

Documents

Transcript of Neverfail ClusterProtector Installation Guide for SQL Server 2005, … · 2018. 8. 22. ·...