LogRhythm HA DR Install Guide 10.1 RevD

Install a LogRhythm HA + DR Combined
Solution
March 23, 2023

© LogRhythm, Inc. All rights reserved.
This document contains proprietary and confidential information of LogRhythm, Inc., which is protected by copyright
and possible non-disclosure agreements. The Software described in this Guide is furnished under the End User License
Agreement or the applicable Terms and Conditions (“Agreement”) which governs the use of the Software. This Software
may be used or copied only in accordance with the Agreement. No part of this Guide may be reproduced or transmitted
in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other
than what is permitted in the Agreement.
Disclaimer
The information contained in this document is subject to change without notice. LogRhythm, Inc. makes no warranty of
any kind with respect to this information. LogRhythm, Inc. specifically disclaims the implied warranty of
merchantability and fitness for a particular purpose. LogRhythm, Inc. shall not be liable for any direct, indirect,
incidental, consequential, or other damages alleged in connection with the furnishing or use of this information.
Trademark
LogRhythm is a registered trademark of LogRhythm, Inc. All other company or product names mentioned may be
trademarks, registered trademarks, or service marks of their respective holders.
LogRhythm
385 Interlocken Crescent, Suite 1050
Broomfield, CO 80021
(303) 413-8745
www.logrhythm.com
Phone
Support (7am - 6pm, Monday-Friday)
Toll Free in North America
(MT) +1-866-255-0862
Direct Dial in the Americas
(MT) +1-720-407-3990
EMEA (GMT) +44 (0) 844 3245898
META (GMT+4) +971 8000-3570-4506
APAC (SGT) +65 31572044
Table of Contents
Prerequisites .................................................................................................................... 5
High Availability .......................................................................................................................................5
IP Addresses ..................................................................................................................... 5
HA Host Records............................................................................................................... 5
Ports.................................................................................................................................. 5
Backup.............................................................................................................................. 5
Outages............................................................................................................................. 5
Power Supply ................................................................................................................... 6
LogRhythm Software Version.......................................................................................... 6
Installation Environment................................................................................................. 6
LogRhythm Infrastructure Installer Considerations for HA ........................................... 6
Dual Site Additional Requirements................................................................................. 6
DNS Records..................................................................................................................... 7
Disaster Recovery.....................................................................................................................................7
Install the High Availability Software for HA + DR ........................................................ 10
Run the High Availability Setup Tool ....................................................................................................10
Install the High Availability Software....................................................................................................15
Run the Install Script..............................................................................................................................15
Configure HA on the Secondary HA Node.............................................................................................15
(Optional) Import the XML Configuration File ......................................................................................15
Configure the High Availability Software for HA + DR .................................................. 16
Configure the New HA Deployment ......................................................................................................16
Build the Appliance Resource Hierarchy ..............................................................................................24
Update SQL Credentials in LifeKeeper..................................................................................................27
Extend the Resource Hierarchy to the Secondary Node......................................................................27
Associate the DX Cluster ID on Both Nodes ..........................................................................................31
LogRhythm, Inc. | Contents 3

Update Mirror Settings ..........................................................................................................................32
Setup and Configure Disaster Recovery for HA + DR .................................................... 33
Add the DR Shared IP to LifeKeeper......................................................................................................33
Prepare Lifekeeper for DR Install ..........................................................................................................33
Configure the Primary Platform Manager.............................................................................................33
Transfer Database Files to Secondary Site ...........................................................................................34
Configure the Secondary Platform Manager ........................................................................................34
Complete the Setup on the Primary Platform Manager.......................................................................35
Put Lifekeeper Back in Service ..............................................................................................................36
Install the HA_DR_Setup........................................................................................................................36
Register LogRhythm Databases for SQL ...............................................................................................36
Complete Additional HA + DR Installation Tasks.......................................................... 38
Configure LogRhythm for HA+DR ..........................................................................................................38
LogRhythm, Inc. | Contents 4

Install a LogRhythm HA + DR Combined Solution
This guide is for LogRhythm Professional Services to prepare, install, and configure LogRhythm's combined HA + DR
solution.
Prerequisites
All requirements and prerequisites for both HA and DR must be met before deploying HA + DR.
High Availability
IP Addresses
For each HA system, three static IP Addresses are needed on the Public Network. One IP Address is needed for each of
the nodes of the cluster, and one IP Address is Shared. This Shared IP address can only be active on one node of the
cluster at any time.
HA Host Records
In the Entities tab of the LogRhythm Client Console's Deployment Manager, a shared host record must be created for HA
which includes identifiers for the SHARED IP and the SHARED HOSTNAME.
Ports
The following ports are required for the LogRhythm HA solution.
Component Ports
Windows File and Print 135/TCP, 137/UDP, 138/UDP, 139/TCP, 445/TCP
LifeKeeper 81/TCP, 82/TCP, 1500/TCP, 1510/TCP, 3278/TCP, 3279/TCP
DataKeeper 9999/TCP, 10003/TCP, 10011/TCP
Additional ports required for the LogRhythm installation are not included in the above list.
Backup
Prior to starting the HA installation, back up critical data.
Outages
For new installations, outages are usually not an issue. However, the DataKeeper component installs a driver that
requires a reboot. For this reason, you will not be able to create mirrored volumes until the system has been rebooted
following the SPS installation.
Prerequisites 5
Constant changes on the source volume will delay the completion of the replica to the target volume. The
recommended approach is to minimize or eliminate any changes to the D: and L: volumes until the source and target
volumes are synchronized and in a Mirroring State.
Power Supply
LogRhythm recommends that all LogRhythm systems be connected to an uninterruptible power supply. A power cut
may cause an Elasticsearch failure that leads to a loss of indices.
LogRhythm Software Version

LogRhythm version 7.8+ and HA software version 10.1 are required.
Installation Environment
 Cloud infrastructure is not supported in High Availability (HA) environments.
HA is intended to provide redundancy for hardware failure, which is not applicable to a cloud (shared infrastructure)
environment. In a cloud environment, the virtual IP created by the SIOS SteelEye software cannot be appropriately
moved between hosts in the event of failover. If HA functionality is required in a cloud environment, consider using
Disaster Recovery (DR) or database backups. For more information, see the Disaster Recovery Installation Guide.
LogRhythm Infrastructure Installer Considerations for HA

When installing LogRhythm software, the LogRhythm Infrastructure Installer should be run as a single host deployment
for XM deployments. In this scenario, no special configuration is needed.
For HA installations of a PM or any distributed LogRhythm deployment, such as an XM + separate Web Console, the
LogRhythm Infrastructure Installer will need to be run twice. The initial installation can be run as a single-host
deployment in order to continue the LogRhythm Software installation. After completing the HA installation, run the
Infrastructure Installer again on the Primary HA node as a multihost deployment, and create a single entry for the HA
systems by using the shared IP address created during HA Install. Next, perform a failover to the Secondary HA node
and run the deployment package that was generated on the Primary node.
Dual Site Additional Requirements

Dual Site deployments provide greater protection from disasters. However, they also have a number of additional
requirements to deliver an appropriate level of performance across a distance.
The private and public network connections between cluster nodes must appear as a single, nonrouted LAN that uses
technologies such as virtual LANs (VLANs). In these cases, the network must be able to provide a guaranteed, maximum
round-trip latency between nodes of 15 milliseconds. The NICs carrying Public data and Private data must each appear
as a standard LAN to support a shared IP Address between cluster nodes.
Network bandwidth is also a key consideration.
In order to characterize the network traffic, a Search Optimized configuration is presented.
• 20% of logs are stored in the Online database are Events and are stored in LogMart.
• 100% of logs are archived.
• The total log rate is 250 logs per second.
Power Supply 6
The following table provides examples of the results when varying compression levels.
Active Public NIC Active Private NIC Active Private NIC Active Logical Disk Average CPU
Bytes In/sec Bytes Out/sec Compression Level (0-9) Write Bytes/sec Utilization
60,000 3,500,000 0 (no compression) 3,300,000 26%
60,000 1,800,000 1 3,300,000 31%
60,000 1,600,000 2 3,300,000 33%
60,000 1,550,000 3 3,300,000 36%
60,000 1,350,000 9 3,300,000 39%
The results indicate that the most benefit can be gained from using a compression level of 1 for all replicated volumes
without significant negative impact on the CPU. Additional compression increases the load on the CPU without offering
notable gain in terms of bandwidth saved.
Measuring the sum of the Total Write Bytes on the D: and L: volumes divided by the optimal compression factor
provides a guide for network sizing.
((Write Bytes / Sec for D:) + (Write Bytes / Sec for L:)) / (Compression Factor) =
Minimum required Network Bandwidth
To summarize, site-to-site configurations require:
• Low latency connections – less than 15 ms ping times between nodes of the cluster
• The network connecting both the Public and Private adapters must appear as a single subnet
• Network bandwidth equal to half the total write bytes of the replicated volumes
DNS Records
Microsoft automatically creates a DNS record for each HA node that is added to a domain. The DNS record for the
Shared Machine Name and Shared Public IP address are not created automatically and should be added manually. Use
the DNS snap-in of the Microsoft Management Console to create these. Include a pointer record (PTR) for each by
selecting the Create associated pointer (PTR) record check box. For more information on managing DNS records, see
the Microsoft Developer Network library.
Disaster Recovery
LogRhythm SIEM The LogRhythm SIEM must be deployed on both the Primary and
Secondary sites using the same LogRhythm software version.
DNS Records 7
SQL Server, SQL Server Agent, and LogRhythm Configure the SQL Server, SQL Server Agent, and LogRhythm Service
Service Registry configuration Registry services to run under the same account on both the Primary and
Secondary sites. This should be a named, privileged account that is not
the sa account. The account can be either:
• A domain account
• Identical local user accounts
Network recommendations Configure the network so that:

• A dedicated network is used for data replication from the
Primary to Secondary sites, so that replication traffic is
isolated from other network traffic — recommended.
• The IP addresses are configured on the dedicated interfaces,
but they do not need to be on the same subnet.
• The network supports:o Bandwidth: 10 Mb/secondo Latency:
150 milliseconds (maximum)
Ports/Firewall Ensure that the SQL Server port (1433) and the ports used for replication
between the two sites (default is 5022) are open (not blocked by a
firewall) at both sites. The DR setup automatically opens ports secured
by Windows Firewall, but not by other types of firewalls.
Domain Name Server (DNS) requirements A common DNS A record needs to be provisioned within the DNS zone
the Disaster Recovery systems are deployed to. This operation is not
performed automatically by DR Setup and requires manual intervention
by a network administrator.
Configure DNS so that:
• It can point to either the IP address of the Primary Platform
Manager or the IP address of the Secondary Platform
Manager.
• The Data Indexers and AI Engines point to the Platform
Manager using a DNS name rather than an IP address. The
Data Indexers and AI Engines can optionally have a shared
name, but it is not necessary.
• DNS Zones should span the Primary and Secondary sites.
• DNS Address records should be configured with a TTL (Time
to Live) of two minutes so that failover occurs relatively
quickly.
DNS Records 8
Disk space requirements on Platform Managers During the DR setup, you must back up the Primary Platform Manager’s
databases and copy them to the Secondary system. The DR installation
program will check your database sizes and give you an estimate for the
disk space requirements. You can also use a network drive for the
backup, provided that the SQL Agent service account has write access to
the share.
 The database backup may take hours to complete, depending

on the data size and the write-speed of the backup media.
DNS Records 9
Install the High Availability Software for HA + DR

Run the High Availability Setup Tool
 Before continuing with the installation, please verify that the Physical Configuration portion above is
completed on both servers.
The HA Setup tool allows you to complete the necessary information for SIOS to work properly. You must enter the
Domain Name (Optional), Public and Private IP Addresses, and Machine Names. The tool validates the input and
prompts the user to start the installation of SIOS HA software.
The HA Setup tool can be found in the root of the HA installation directory (LogRhythm High Availability Setup.exe).
Two Ways to Use the HA Setup Tool

• On-site configuration and testing. Run HA Setup on the Primary and Secondary servers to test that all values work
in the given environment.
• Off-site configuration. The HA Setup can be run on any system (requires .NET 4.0) and allows for exporting the
XML configuration file for future use on an HA pair. Once on-site, the configuration file can be imported to the
tool and tested.
Install the High Availability Software for HA + DR 10

Configure the Primary or Secondary Machine

Select the radio button for a primary or secondary machine. This step is optional if you are doing an offsite
configuration. The program detects and populates the name and IP information for the corresponding section.
 You may see the following message if you have not already configured your Public and Private Network
Connections.
(Optional) Set Domain Name

In Active Directory domain environments, the HA Setup attempts to detect the domain name. If it is unable to find the
domain name, the field is empty and you need to add the correct domain name. For workgroup environments, the
Domain Name field may be left empty. Example: mytestdomain.com
Enable AIE
 The AIE Enabled box is irrelevant on an AI Engine system. This control is only used on XM and PM systems.
Newer LogRhythm systems may include the AIE services, providing customers the option of running AIE on their PM/XM,
or on a dedicated AIE system. The default setting for AIE Enabled is true, meaning that HA is configured to protect AIE on
the box. If the customer has a dedicated AIE system, or does not wish to use AIE, then clear the AIE Enabled check box.

Configure Public Network Connections

The Public section represents the names and IP addresses that will be visible to the production network and contains
three columns: Primary, Secondary, and Shared.
• Primary. The main server in the HA pair.
• Secondary. The failover or secondary server in the HA pair.
• Shared. The shared Machine Name and IP Address that moves between systems depending on which node is
active.

Enter the Machine Name and Public IP Address for Primary, Secondary, and Shared.
 The Shared Machine Name and Shared Public IP should be unique and not found anywhere else on the
network.
Configure Private Network Connections

The Private section represents the private physical connection to the other HA system (usually a crossover cable).

Enter the Private IP Address for the Primary and Secondary systems.
Test the Configuration

After you have entered the required information, click Test. The test button first validates the required fields. If the
fields are blank or have invalid information, the error icon appears next to the item that needs to be fixed. Hover over
the error icon for additional information about the error.
After all the fields are verified, the test validates that the Primary and Secondary IP addresses are accessible, and then
verifies that the Shared IP address and Shared Name are unique on the network.
Configuration problems discovered during the test are displayed in the Error Report section at the bottom of the
window. The program advises which fields need to be modified, and why. The test can be run as many times as needed
until all items have passed.
After the program has successfully completed a test, the Install button is enabled.
 Before running the install process, you can export an XML configuration file for a faster deployment on the
secondary machine.
Export
Exporting provides the capability of creating an XML file that can be imported into another HA Setup tool. For instance,
once the validation steps have passed successfully on the primary system, the configuration can be exported as an XML
file, which can then be imported on the secondary node.
To export a file, click File, Export, XML, and choose a location to save the file.

Import
Importing a file is a fast and easy way to configure the HA setup.
To Import a file, click File, Import, XML, and then browse to the location of the HA_Config.xml file.
Edit
Editing provides the capability to go back and modify field values after testing.
To enable editing after a test, click File and Edit.
Install the High Availability Software
Run the Install Script

1. To launch the installation script, click Install.
The HA Setup tool closes and a PowerShell window displays the appropriate script for an XM, PM, or DP.
2. Press Enter to continue.
3. If prompted, supply the password for the SQL sa account. If the script is able to connect to SQL via LogRhythm
default or Windows credentials, you are not prompted for credentials.
The script runs for several minutes.
4. When complete, review the output for any errors. Then press Enter to reboot the system.
Configure HA on the Secondary HA Node

Repeat the same steps on the secondary node of the HA pair.
 Do not reboot the secondary system until the primary system has completed rebooting, and do not reboot the
primary system until the secondary system has completed rebooting.
(Optional) Import the XML Configuration File

1. Click File, Import, XML, and then locate the XML file that was exported from the primary node.
2. To validate the configuration, click Test.
3. To launch the installation script, click Install.

Configure the High Availability Software for HA + DR

Configure the New HA Deployment
Verify the Installation

To confirm the installation was successful, look in Programs and Features for the following new programs:
• LifeKeeper for Windows v8 Update 7
• LifeKeeper Microsoft SQL Server Recovery Kit v8 Update 7
• SIOS DataKeeper for Windows v8 Update 7
• Microsoft Visual C++ 2015 Redistributable (x64) – 14.0.23026
• Microsoft Visual C++ 2015 Redistributable (x86) – 14.0.24215
Additionally, you can review the log file from the script in the \Logs directory to check for any error messages.
Verify the Initial LifeKeeper Configuration

1. Run the LifeKeeper GUI on the primary system (Start, All Programs, SIOS, LifeKeeper, and then LifeKeeper
(Admin Only)) as an Administrator
2. Log on using local admin credentials. An IP and Name resource should be displayed, and the primary server icon
should contain a yellow triangle.
The yellow triangle on the server icon indicates that communication paths were setup from Node 1 to Node 2,
but not in the other direction. Once the install process has run on the secondary server, the yellow icon should
change to a green check. The same interface, viewed from the secondary server after a completed installation,
looks like this:
Configure the High Availability Software for HA + DR 16

Configure LifeKeeper and DataKeeper Service Accounts
The following steps must be performed on both nodes.

In order to function properly, the LifeKeeper and SIOS DataKeeper services should be set up to run as an account with
local administrator credentials on the systems. These can either be domain accounts, or local accounts as long, as the
same accounts and passwords are created on both systems.
1. Open the Services console, right-click the LifeKeeper service, and click Properties.
2. Select the Log On tab and enter the credentials for the account you wish to use.
3. Repeat for the SIOS DataKeeper service, and then for both services on the other node.
Start Elasticsearch on XM Nodes

1. Open the Services Console, right click the LogRhythm DX – Elasticsearch Service and select Start, if the
service is not already started.
2. Perform this step on each XM node in the deployment.
Configure LogRhythm
Before the rest of the HA configuration can be done, LogRhythm needs to be configured on the primary node to work
with the shared Name and IP.
1. Click Start, All Programs, LogRhythm, and then open the Local Configuration Managers (LCM) for each
LogRhythm service.
The Server field for each should contain the Shared Name or IP of the HA pair.
For a PM/DP configuration, configure Job Manager, Alarming and Response Manager, and the System Monitor
Agent on the PM system. On the DP system, configure the Mediator and the System Monitor Agent. Make sure
that the DP shared IP is used for the Data Processor Connection Settings, and the PM shared IP is used for the
Platform Manager Connection Settings. For XM configurations, all services are configured on the same system,
using the same shared IP.

For the System Monitor LCM, the Data Processor IP and System Monitor IP should both be the Shared IP of the
HA pair.
If you plan to enable AIE on this system, make sure to configure it before continuing. If you do not plan to enable
it, the services can be disabled in the services console.
2. After all services are configured, open the LogRhythm Console. Log on using the Shared Name or IP.
3. On the New Deployment Wizard, use the Shared Name and IP.
4. Continue through the Knowledge Base Import Wizard and the License Wizard, and then select the appropriate
platform from the platform selector in Platform Manager Properties and Data Processor Properties.
For a PM/DP pair, a Data Processor record and an Agent record needs to be manually created using the Shared
Name and Shared IP of the DP.
5. Set the active and inactive archive locations to the D: drive (Gen4) or the S: drive (Gen5) in the Data Processor
properties, and the values of NetflowServerNIC, sFlowServerNIC, and SyslogServerNIC to the Shared IP in the
agent properties.
LogRhythm Configuration for AIE or Collector

If you have an AIE system or an XM or PM running the AI Engine service, the following steps must be completed before
the rest of the High Availability configuration can be done.
Configure LogRhythm on the Primary Node to Work with the Shared Name and IP
1. Click Start, All Programs, LogRhythm, and then LogRhythm System Monitor Configuration Manager.
2. Enter the Data Processor IP.
3. In the System Monitor IP Address field, enter the Shared IP of the HA pair.
Create Host and System Monitor Records for the Shared Agent
1. From the LogRhythm Console, click Deployment Manager on the main toolbar, and then click the Entities tab.
2. Select the Entity where the shared agent should go. The default is Primary Site.
3. Right-click the Entity Hosts area and click New Host.
4. Enter the name for the shared agent and then click the Identifiers tab.
5. Enter the shared IP and each of the system IPs for IP Address identifiers.
6. Enter the shared name and each of the system names for Windows Name identifiers.
7. Click OK.
8. Click the System Monitors tab, right-click in the lower pane, and click New.
9. Choose the host record from the previous step that the Host Agent is installed on.
10. Enter the System Monitor Agent name.
11. On the Data Processor Settings tab, select the Data Processor this agent will use, and enter the shared IP for the
Agent IP/Address Index.
12. If any syslog or flow collection will be performed by this agent, select Advanced and change the value of
SyslogServerNIC, NetflowServerNIC, and sFlowServerNIC to the shared IP.
Configure the AI Engine Service

1. Click Start, All Programs, LogRhythm, and then open the local Configuration Manager (LCM) for the LogRhythm
AI Engine service.
2. On the General tab, in the Platform Manager Connection Settings, enter the information for the PM.

Create a New AIE Record

1. From the LogRhythm Console, click Deployment Manager on the main toolbar and then click the AI Engine tab.
2. Click the Servers tab.
3. Right-click and select New.
4. Choose the host record from the previous step.
5. Enter the AI Engine Name.
6. Select a workload and click OK.
Use the LogRhythm Install Wizard to install or upgrade LogRhythm components in your deployment. You must run the
Install Wizard on each appliance or server in your deployment, and select the appliance configuration that you want to
install or upgrade.
 • The LogRhythm Install Wizard requires .NET Framework version 4.7.2 or above.
• If you are installing or upgrading the Data Indexer or Web Console, ensure that Windows Firewall
Service is running before starting the Install Wizard to allow firewall rules to be created.
• Do not try to run the wizard from a network share. Run the wizard locally on each appliance.
• For systems with UAC (Vista and later), always run installers as a Local Administrator with elevated
privileges. The person performing the installation must be in the Local Admin group, unless the
domain is managed and the Group Policy Object dictates that only Domain Administrators can run
installers.
• When installing the Web Console, it is recommended that you run the LogRhythm Install Wizard to
install all Web Console services. You may choose to install the Web Console as a stand-alone
installation or as part of the XM Appliance or Platform Manager (PM) configurations.
• Before installing or upgrading the Web Console, ensure that Windows Firewall is running so the
Common installer can open port 8300.
 When the Client Console is installed on a fresh system, additional software packages must be installed such as
Microsoft Visual C++ Redistributable packages, SAP Crystal Reports runtime engine, and .NET Framework
4.7.2. For this reason, the Client Console installer may take 30 minutes or more to complete.
1. Log in as an administrator on the appliance or server where you are installing or upgrading LogRhythm software.
2. Copy the entire LogRhythm Install Wizard directory to a new directory on the local server.
3. Open the Install Wizard directory, right-click LogRhythmInstallWizard.exe, and then click Run as
administrator.
The Welcome screen appears.
4. Click Next to proceed.
The wizard asks you to confirm that you have prepared the LogRhythm databases for the upgrade.
5. Click one of the following:
• If you have run the Database Install or Upgrade Tool on each Platform Manager or XM server, click Yes to
continue.
• If you have not prepared the LogRhythm databases on all required appliances, click No to cancel the
wizard, install or upgrade all of the required databases, and then continue with this procedure.
The End User License Agreement appears.
6. Read the agreement carefully. By accepting the terms in the agreement, you agree to be bound by those terms.

7. If you accept the terms of the agreement, select the I accept the terms in the license agreement check box, and
then click Next.
The configuration selector appears. Depending on the selected configuration, the wizard upgrades or installs a
specific application or set of applications.
 For certain configurations, you can optionally select to install or upgrade the AI Engine.
 If you select the Web Console, it is installed to the default location, C:\Program
Files\LogRhythm\LogRhythm Web Services. For instructions on how to install the Web Console to a
custom location, see Install and Configure the Web Console.
8. For each appliance that you install, select the target appliance configuration, according to the following table.
If you are upgrading an existing PM + DP appliance or another configuration that is not represented in the Install
Wizard, select one of the available configurations and then run the wizard again to install the next configuration.
7.x.x Configuration Select…
XM XM
Platform Manager PM
Data Processor DP
Client Console Client Console
Web Console Web Console
AI Engine AIE
Data Collector/System Monitor DC
LogRhythm Diagnostics Tool LRD Tool
LogRhythm Diagnostics Tools Agent LRD Agent
 If you are upgrading the LogRhythm Web Console, pay attention to the following:

• Upgrades from Web Console 6.1.x and 6.2.x are not supported. Uninstall your Web Console and
complete a fresh installation.
• If you have a 7.2.0 deployment, close the Web Services Configuration Manager prior to
beginning the upgrade.
 If you are running the Install Wizard on an XM or DP/DX appliance, ensure that the Elasticsearch service
is running before you continue. You can start all services by running the following command in an
Administrative PowerShell prompt: Start-Service lr-*
If this service is not running, the Data Indexer installer will fail. After ensuring the service is running,
you can run the Install Wizard again, or run the LRDataIndexer executable in the wizard's Installers
subfolder by right-clicking it, and then clicking Run as Administrator.
9. When you have selected the target configuration, click Install.

The LogRhythm Deployment Tool appears.
10. Select from the following options, depending on the type of deployment you are running:
• For Disaster Recovery upgrades, follow the procedure for a multi-host upgrade in the LogRhythm
Infrastructure Installer. The Deployment Properties modal asks whether your deployment includes
Disaster Recovery. Be sure to select Yes and provide the FQDN of the DR Cluster and select OK.
i. Add the Management IP address of each DR server as two separate hosts in the deployment tool.
ii. If applicable, add the IP addresses of other participating hosts in your LogRhythm deployment,
and then click Create Deployment Package.
iii. After the deployment package is created, click Run Host Installer on This Host. Leave this
window open until the final step of this section.
iv. Copy the deployment package from previous steps—both the Windows executable and the plan
file—to a location the secondary host of the DR pair.
v. Log in to the Secondary host, run cmd as an administrator, and change the directory to the
location where you copied the LRII executable and plan file.
vi. From the command prompt, run lrii_windows.exe /dr-secondary, and verify that the command
finishes without any errors.

vii. Run the LRII exe from the deployment package on each additional LogRhythm host in the
deployment.
viii. Return to the Primary DR server and select Verify Status to confirm that all LogRhythm Host
Installers have completed successfully. Exit when confirmation is complete.
ix. Through services.msc, verify that the LogRhythm Service Registry service is using the appropriate
service account after re-running the Infrastructure Installer.
• For High Availability upgrades, the following instructions apply.
i. Select Upgrade Deployment.
ii. The HA shared IP should be supplied as the IP address representing both nodes in the HA cluster.
Do not add other IP addresses from the HA nodes.
iii. If applicable, add the IP addresses of other participating hosts in your LogRhythm deployment,
and then click Create Deployment Package.
iv. On the primary node, select Run Host Installer on This Host.
v. Copy the resulting deployment package (executable and plan file) to a location on the secondary
node in the HA cluster.
vi. On the secondary node, open an elevated command prompt (Run as administrator) and change
directory to the location of the LRII_Windows.exe copied in the previous step. For example: cd "C:
\Users\Administrator\Desktop\Deployment Package"
vii. Run the following command: ".\LRII_Windows.exe /ha-secondary=<HA shared IP address>" and
press Enter.
Additional help is available by clicking the question mark icon in the upper-right of the tool.
When you are finished preparing your deployment, you will be returned to the Install Wizard.
11. Observe for any failures as the wizard installs or upgrades the applications according to the selected
configurations.
 When the Client Console is installed on a fresh system, additional software packages must be installed
such as Microsoft Visual C++ Redistributable packages, SAP Crystal Reports runtime engine, and .NET
Framework 4.7.2. For this reason, the Client Console installer may take 30 minutes or more to
complete.
Progress in the installation screen is indicated as follows:
Color Meaning
Green The application was installed successfully. A message about the application and
installed version
is also printed below the status indicators.
Blue The application is being installed.
Yellow The current or a newer version of the application is already installed.

Color Meaning
Red Something went wrong and the application was not installed. Additional details will be
printed
below the status indicators. If something went wrong, check the installer logs located in
the following location:
C:\LogRhythm\Installer Logs\<install date and time>\
 During the Web Console installation or upgrade, if you receive a message that notifies you of an error
with your Windows Installer package, go into each folder in C:\Program Files\LogRhythm\LogRhythm
Web Services and run the unzip.bat file as an administrator. For other failures, run a Repair.
12. Configure your deployment using the LogRhythm Configuration Manager that appears after the installation or
upgrade is complete.
The LogRhythm Configuration Manager has two modes: Basic and Advanced. The most commonly edited
settings are shown in Basic mode. Advanced mode displays all settings, including those shown in Basic mode,
grouped according to which service they affect. You can filter the settings that are displayed by clicking one of
the options on the left — All (no filtering), Authentication, or Web Services. When settings are filtered, you should
enable the Advanced view to ensure you can see all settings. For more information, see Use the LogRhythm
Configuration Manager.
 While the Configuration Manager is still open, review your previous Web Console configuration values
(backed up before starting the upgrade), turn on the advanced view, and validate or set all of the
values in the Configuration Manager, especially the following:
• Global, Database Server. This is the IP address of your Platform Manager where the EMDB is
installed.
• Web Global, Database Password. This is the password for the LogRhythmWebUI user, used by
the Admin API for connecting to the EMDB. If the password is not correct, the Admin API will
display an error.
• Web Console UI values. Verify all settings for all Web Console instances.
When finished, click Save, back up your current configuration to file, and then close the Configuration
Manager.
 After you validate and save your configuration, it is strongly recommended that you make a new back
up. Save the file in a safe location in case you need to restore it later.
13. To close the LogRhythm Install Wizard, click Exit.

14. Run the Install Wizard on the secondary node. When the LogRhythm Deployment Tool (LRII) launches, click Exit
and allow the installation to complete.

 If you need to install additional components that were not included in the selected configuration, run the
Install Wizard again and select the necessary components.
Build the Appliance Resource Hierarchy
The following steps need to be performed on the primary node only. For a PM/DP pair, this step should always be
performed first on the primary PM node and then on the primary DP node.
Each of the LogRhythm services will be protected by LifeKeeper by using the Generic Services Recovery Kit. The Generic
Services Recovery Kit makes use of a set of scripts to communicate with the Windows Service Control Manager with the
“sc.exe” command.
Run 2_HA_Build.cmd
1. On the primary node, right-click the 2_HA_Build.cmd file and click Run as administrator.
A PowerShell window opens with the build script.
2. Press Enter to continue. If prompted, supply the password for the SQL sa account. If the script is able to connect
to SQL via LogRhythm default credentials, you are not prompted for credentials.
The script builds the SQL hierarchy, adds the monitored services, and adds each of the monitored databases
before proceeding on to create the hierarchies for the LogRhythm services. When finished, the script displays a
Setup Complete message and allows you to review the output before closing the window.
3. Switch back to the LifeKeeper GUI and verify that you have a completed resource hierarchy that looks like the
following:
On a Gen5 appliance, the Vol.S_ResTag replaces the Vol.D_ResTag for the following:
LogRhythmApIGateway_ResTag
LRAIEComMgr_ResTag
LRAIEEngine_ResTag
scmedsvr_ResTag
scsm_ResTag


The LRAIEComMgr_ResTag and LRAIEEngine_ResTag resource hierarchies are only displayed if you selected the
AIE Enabled check box in the HA configurator.

Update SQL Credentials in LifeKeeper

The build script is unable to properly supply the SQL credentials to LifeKeeper, so the credentials must be manually
updated.
1. Right-click the SQL_ResTag hierarchy and click Properties. Verify that the services and databases are all
monitored, and then click Admin Actions.
2. Click Next to Manage User, select Change User and Password in the drop-down menu, and then click Next
again.
3. Enter a SQL admin account (sa) and password to complete the wizard.
Extend the Resource Hierarchy to the Secondary Node
 The following steps need to be performed on the primary node.

• Extending the hierarchy is the process that LifeKeeper uses to copy identical configuration and
resource details to the other node in the cluster.

• This section assumes that you have been performing all configurations on the system that has current
customer active data on it, and these volumes will be the source of the replica.
• The steps in this section may not always come in the order displayed. Expect to create two
volume resources, as well as one IP resource.
 This document assumes that all LifeKeeper Resource Hierarchies built thus far have been on the Active node.
Take great care to choose the source volume which contains customer data, and the target volume which will
contain empty LogRhythm databases. The Target Volume will ALWAYS be overwritten and no data will remain
on this volume. If you fail to get this correct, you will overwrite the customer’s data.
 Before you continue, ensure that File and printer sharing is turned on under Control Panel, All Control Panel
Items, Network and Sharing Center, and Advanced sharing settings.
1. In the Hierarchies Pane, right-click XM_ResTag, PM_ResTag, AIE_ResTag, or DC_ResTag, and then click Extend
Resource Hierarchy.
2. In the Extend Wizard, select the secondary system and click Next.
3. Make sure all the pre-extend checks were successful, and then click Next.
4. In the Volume Type menu for D:, select Create Mirror, and then click Next.
5. In the Network end points menu, select Private, and then click Next.
6. Select the default, and then click Create to create the mirror for the D: drive (Gen4) or the S: drive (Gen5)
volume.
7. After the mirror is successfully created, click Next.
8. Select the subnet mask that is on the Public interface and click Next.
9. In the Network Connection menu, select Public, and then click Next three times, accepting the defaults on the
next two screens.
 If on a Gen5 appliance, repeat steps 4-7 to create a mirror for the S: drive.
10. In the Volume Type menu for L:, select Create Mirror, and then click Next.
11. In the Network end points menu, select the Private network, and then click Next.
12. Select the default on the next screen, and then click Create to create the mirror for the L: volume.
13. Once the mirror is created successfully, click Next.
14. Leave the default Backup Priority on the next screen then click Extend.
15. Wait until the hierarchy is extended, then click Finish.
The extended resource hierarchy should look like this with HA1 Active and HA2 on Standby or Mirroring:
 On a Gen5 appliance, the Vol.S_ResTag replaces the Vol.D_ResTag for the following:
LogRhythmApIGateway_ResTag
LRAIEComMgr_ResTag
LRAIEEngine_ResTag
scmedsvr_ResTag
scsm_ResTag



 The LRAIEComMgr_ResTag and LRAIEEngine_ResTag resource hierarchies are only displayed if you
selected the AIE Enabled check box in the HA Setup tool.
16. New mirrors require time to synchronize. Failover is not possible until both L: and the D: drive (Gen4) or the S:
drive (Gen5) are in a Mirroring state. A Resync state means the data is being duplicated to this volume from the
active volume.
Right-click the active volume and click Properties to view the sync progress.
17. After the status is Mirroring for all volumes, you may proceed with outage tests. Failure to wait for the sync to
complete may result in data corruption.
Associate the DX Cluster ID on Both Nodes

To associate the DX cluster ID on the Primary Node, do the following:
1. Right-click PowerShell, and then click Run as administrator.
2. Issue the following command and record the value that is returned: $env:DXCLUSTERID
 You use the returned value to associate the cluster ID using PowerShell on the Secondary Node in the
next set of steps.
3. Press Enter to continue.

To associate the DX cluster ID on the Secondary Node, do the following:
1. Right-click PowerShell, and then click Run as administrator.
2. Issue the following command: Set-ItemProperty –Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment" –Name DXCLUSTERID –Value <DXCLUSTERID value obtained on Primary node>

 The DXCLUSTERID is case-sensitive and must match between both servers exactly for searches to
succeed after a failover.
3. Close the PowerShell window.
Update Mirror Settings

The default mirror settings created by LifeKeeper Volume Mirroring uses a flag called the LK Delete Mirror Flag, which is
set to True by default. The product documentation describes this flag as follows:
The LifeKeeper Delete Mirror Flag controls the behavior during delete of the LifeKeeper resource for the replicated
volume. When deleting the LifeKeeper volume resource, if the flag is set to True, then LifeKeeper deletes the mirror;
otherwise, the mirror remains.
• If you want the mirror deleted when the volume resource is unextended or removed from LifeKeeper, select
True.
• If you want the mirror to remain intact, select False.
The default is True if the mirror is created using LifeKeeper GUI. The default is False if the mirror is created outside of
LifeKeeper GUI.
To preserve data, the LifeKeeper Delete Mirror flag must be changed to False.
1. Right-click the active volume and select Properties.
2. Click the Mirror Settings button.
3. On the first page of the Volume Mirror Settings wizard, click Next, and then select Set LifeKeeper Delete Mirror
Flag in the dropdown menu.
4. Set the value to False and complete the wizard. Repeat the process for the other protected volume.
5. Confirm the setting on the Properties page.

Setup and Configure Disaster Recovery for HA + DR

Add the DR Shared IP to LifeKeeper
1. In LifeKeeper, right click the active server and select Create Resource Heirarchy.
2. Follow the screens in the wizard:
a. In the Application to protect field, select IP Address for the Application to protect, and then click Next.
b. Enter a valid IP address on the same subnet as the replication interfaces. This should be the Shared IP
Address for the DR Replication, which is separate from the previously created HA Shared Management IP.
Click Next.
c. Select the Subnet Mask, and then click Next.
d. Select or enter the name for the IP Resource Tag, and then click Next.
e. Select the Network Connection for the Resource (replication interface), and then click Next.
f. In the Local Recovery field, select No, and then click Next. The resource is created and then automatically
starts the Extend Wizard to extend the hierarchy to the standby node.
3. Right-click the SQL resource and click Add Dependency to add the newly created resource as a dependency for
the SQL resource.
4. Follow the screens in the wizard, making sure to select the newly created IP resource as the Child Resource.
Accept all other defaults.
Prepare Lifekeeper for DR Install

1. Running LifeKeeper GUI as an Administrator, right click the top-level RestTag and select Out of Service.
2. Select defaults to take the resource out of service.
Configure the Primary Platform Manager

To run the setup for the Primary site:
 Use only static IPs for the replication interface. Do not use DHCP.
1. Download the DR zip file from the LogRhythm Community and extract it to a new local directory on the Primary
Platform Manager.
2. Browse to the newly extracted DR directory.
3. Right-click DR_Setup and select Run as administrator. Enter your local system administrator credentials.
4. In the first DR Setup dialog, enter credentials for a SQL Sysadmin or enable the Windows Authentication check
box, and then click Next.
 The user entered here MUST have Sysadmin permissions in Microsoft SQL Server Management
Console. To check permissions, open and connect to the MS SQL SMC. In the main tree, expand the
Security > Logins folder. Select the user you want or create a new one. Right-click the user and click
Properties. Click Server Roles and make sure that the Sysadmin Server role is checked for this user.
5. Select Primary and Next.
Setup and Configure Disaster Recovery for HA + DR 33

6. Under Primary, select the DR Shared IP created as a ResTag for the Primary site by using the arrow to select from
discovered IPs. Under Secondary, enter the Replication IP address of the Secondary DR site. You can also select
a different port number, if necessary, as long as that port is not used by other systems. The port used for the
Primary site and the port used for the Secondary site can be different. Click Next.
7. Select the databases that you want to replicate on the Secondary site and click Next.
 The DR solution does not replicate the LogRhythm Archives.
8. Select a folder for temporarily storing the database backup, and then click Next.
 After you select the folder, the DR Setup shows the free space available. If the system does not have
enough free space for the backup, an error message appears at the bottom of the dialog. If necessary,
you can select a network drive or external drive. If you want to change your database selections, click
Back to return to the previous screen.
9. Select the minutes for your Recovery Point Objective (RPO).
 The RPO is the maximum tolerable period in which data from the Primary system can be lost due to
system disruption. If the data replication falls behind this time limit, the LogRhythm SIEM generates an
alert. The default is 60 minutes.
10. To backup the Platform Manager databases and to install DR solution on the Primary system, click Install.
 The DR setup launches a script that shows its progress. Depending on the size of the databases, this process
could take several hours. When it’s done, the following prompt appears: Press Enter when the setup is
complete on the secondary system. Keep this progress window open. You will return to it later, after
completing the setup on the secondary Platform Manager.
Transfer Database Files to Secondary Site

When the setup completes on the Primary system, copy the database backup files to the Secondary system.
1. Open the folder where the backup files are stored on the Primary system.
2. Select and copy all the database files and the logins file.
3. Access the Secondary Platform Manager server. Paste the files into a folder.
You will load the files from this folder when you configure the Secondary Platform Manager.
Configure the Secondary Platform Manager

To run the setup for the Secondary site:
1. Extract the DR zip file into a new local directory on the Secondary Platform Manager.
2. Browse to the newly extracted DR folder.

3. Right-click DR_Setup and click Run as administrator. Enter the local system administrator credentials.
4. In the first DR setup dialog, enter credentials for a SQL Sysadmin or select the Windows Authentication check
box, and then click Next.
 The user entered here MUST have Sysadmin permissions in Microsoft SQL Server Management
Console. To check permissions, open and connect to the MS SQL SMC. In the main tree, expand the
Security > Logins folder. Select the user you want or create a new one. Right-click the user and click
Properties. Click Server Roles and make sure that the Sysadmin Server role is checked for this user.
5. Select Secondary and click Next.
 If you accidentally leave this setting at Primary, the DR setup will fail. If this happens, you need to run
the DR Setup on the Secondary system again and choose Secondary.
6. Under Primary, enter the IP address of the Primary site. Make sure the Primary Port number is the same one you
selected during the Primary site configuration. Under Secondary, select the IP address for the Secondary site by
using the arrow to select from discovered IPs. Make sure the Secondary Port number is the same one you
selected during the Primary site configuration. Click Next.
7. Select the folder where you copied the Platform Manager databases, and then click Next.
8. Select the minutes for the Recovery Point Objective (RPO) on the Secondary Platform Manager.
 The default is 60 minutes. This value does not need to be the same RPO selected for the Primary
Platform Manager.
9. Click Install.
10. When you see the "Step Complete" message, press Enter to exit.
You are now done with setup on the Secondary site.
 Do not start the Platform Manager’s services (Job Manager and ARM) on the Secondary site. The Job Manager
and ARM services should remain on Manual unless you need to perform a failover to the Secondary site, as
described in the LogRhythm Disaster Recovery Administration Guide.
Complete the Setup on the Primary Platform Manager

After completing the setup on the Secondary site, follow these steps:
1. On the Primary Platform Manager, return to the DR Setup progress window.
2. To complete the setup on the Primary system, press Enter.
 If problems with the setup occur, you can view log files in the Logs subdirectory.
When the DR Setup Complete message appears, you are finished with the DR configuration.

3. (Optional) Remove the backup files you created on both the Primary and Secondary Platform Managers. The files
are no longer needed.
4. Restart all LogRhythm services running on AI Engines, Data Indexers, and the Platform Manager on the Primary
site (not the Secondary site). These services include:
• Platform Manager. Job Manager service and ARM service
• Data Indexers. Mediator service
• AI Engine (if integrated). AI Engine service and AI Engine Communication Manager service
Put Lifekeeper Back in Service

1. Running LifeKeeper GUI as an Administrator, right click the top-level RestTag and select In Service.
2. Select defaults options to bring the resource back into service.
Install the HA_DR_Setup

All the Installation and Configuration steps above should be performed, using the active HA node as the primary DR
system. Use the DR Shared IP as the DR Primary IP Address.
1. After the DR setup is complete, use the LifeKeeper GUI to fail over the resource hierarchy to the HA secondary
system. On that system, extract the DR zip file and browse to the DR\bin directory.
2. Right-click HA_DR_Setup.ps1 and click Run with PowerShell.
3. When the DR Setup Complete message appears, press Enter to close the window and use the LifeKeeper GUI to
failback to the HA primary system.
Register LogRhythm Databases for SQL

To use the SQL Database Mirroring Monitoring tool for viewing data replication status, you must register the LogRhythm
databases first.
1. From the Primary Platform Manager server, click Start, All Programs, LogRhythm, and Disaster Recovery.
2. Double-click DR_Status to open the Database Mirroring Monitor.
3. Click Action, and then and Register Mirrored Database.
4. In the Register Mirrored Database dialog, click Connect.
5. Enter credentials for the SQL Server administrator, and then click Connect.
6. In the Register Mirrored Database dialog, select the check boxes for all databases, select Show the Manage
Server Connections dialog box when I click OK, and then click OK.
7. At the next prompt regarding Server Instance Connections, click OK.
8. In the Database Mirroring Monitor panel, click the plus sign to expand the list of mirrored databases.
The LogRhythm databases now appear in the Database Mirroring Monitor.
9. Go to the HA Secondary and DR Secondary Platform Manager and follow steps 1-8 to register the mirrored
databases for each node.
When you’re done registering the Primary and Secondary databases, you can view the status of a LogRhythm
database by selecting it in the left panel.
10. For the Data Indexer configuration, specify the DNS name for the AllConf EMDB location on the DR side.
 For more information about the Database Mirroring Monitor, see Administer a LogRhythm Disaster
Recovery Deployment.

 You can also see replication status by running LogRhythm’s DR Control from Start, All Programs,
LogRhythm, Disaster Recovery, right-click DR Control, and click Run as administrator. For more
information about this program, see Administer a LogRhythm 8.0.1 Disaster Recovery Deployment.

Complete Additional HA + DR Installation Tasks

Configure LogRhythm for HA+DR
Perform the following to complete HA + DR setup:
1. Apply a license for each DP on an XM deployment, including one for each DR server. If you do not have a license,
contact LogRhythm Fulfillment.
2. Use the Agent on the DR side to point to DR Secondary machine IP.
3. Use the DNS name for the EMDB location on the HA side.
4. Use the shared IP for the Public IP.
5. Use the HA shared name and IP for the new deployment wizard in the console.
6. Configure the Platform Manager on the HA side to point to the shared IP.
7. Configure the Platform Manager on the DR side to point to the DR IP.
8. Configure the Data Processor on the HA side to point to the DNS name.
 For more information on configuring DNS names, see the prerequisites.
9. Configure the Data Processor on the DR side to point to the DNS name.
10. Configure AIE on the HA side to point to the DNS name.
11. Configure AIE on the DR side to point to the DNS name.
12. Configure the Agent on the HA side to point to the shared IP.
13. Use the DNS name for the EMDB location on the DR side.
14. Change the ElasticSearch clustername value on the DR side to logrhythmdr.
 The ES Cluster Name configuration is currently done through windows environment settings, this will
be moving to the Configuration Manager in a later release.
You can change the cluster name by updating the environment system variable
DX_ES_CLUSTER_NAME and restarting DX services.
15. Add the DR secondary machine entity on entity tab of Deployment Manager and create a Data Indexer for DR
secondary machine.
16. Point the DP on the HA side to the logrhythm cluster.
17. Point the DP on the DR side to the logrhythmdr cluster.
Complete Additional HA + DR Installation Tasks 38

LogRhythm HA DR Install Guide 10.1 RevD

Uploaded by

Copyright:

Available Formats

LogRhythm HA DR Install Guide 10.1 RevD

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LogRhythm HA DR Install Guide 10.1 RevD

Uploaded by

Copyright:

Available Formats

Install a LogRhythm HA + DR Combined

March 23, 2023

LogRhythm, Inc. | Contents 3

LogRhythm, Inc. | Contents 4

Windows File and Print 135/TCP, 137/UDP, 138/UDP, 139/TCP, 445/TCP

LifeKeeper 81/TCP, 82/TCP, 1500/TCP, 1510/TCP, 3278/TCP, 3279/TCP

DataKeeper 9999/TCP, 10003/TCP, 10011/TCP

LogRhythm Software Version

 Cloud infrastructure is not supported in High Availability (HA) environments.

LogRhythm Infrastructure Installer Considerations for HA

Dual Site Additional Requirements

60,000 3,500,000 0 (no compression) 3,300,000 26%

60,000 1,800,000 1 3,300,000 31%

60,000 1,600,000 2 3,300,000 33%

60,000 1,550,000 3 3,300,000 36%

60,000 1,350,000 9 3,300,000 39%

Network recommendations Configure the network so that:

 The database backup may take hours to complete, depending

Install the High Availability Software for HA + DR

Two Ways to Use the HA Setup Tool

Install the High Availability Software for HA + DR 10

Configure the Primary or Secondary Machine

(Optional) Set Domain Name

Install the High Availability Software for HA + DR 11

Configure Public Network Connections

Install the High Availability Software for HA + DR 12

Configure Private Network Connections

Install the High Availability Software for HA + DR 13

Test the Configuration

Install the High Availability Software for HA + DR 14

Install the High Availability Software

Run the Install Script

Configure HA on the Secondary HA Node

(Optional) Import the XML Configuration File

Install the High Availability Software for HA + DR 15

Configure the High Availability Software for HA + DR

Verify the Installation

Verify the Initial LifeKeeper Configuration

Configure the High Availability Software for HA + DR 16

Configure LifeKeeper and DataKeeper Service Accounts

The following steps must be performed on both nodes.

Start Elasticsearch on XM Nodes

Configure the High Availability Software for HA + DR 17

LogRhythm Configuration for AIE or Collector

Configure the AI Engine Service

Configure the High Availability Software for HA + DR 18

Create a New AIE Record

Configure the High Availability Software for HA + DR 19

7.x.x Configuration Select…

Client Console Client Console

Web Console Web Console

Data Collector/System Monitor DC

LogRhythm Diagnostics Tool LRD Tool

LogRhythm Diagnostics Tools Agent LRD Agent

Configure the High Availability Software for HA + DR 20

9. When you have selected the target configuration, click Install.

Configure the High Availability Software for HA + DR 21

Progress in the installation screen is indicated as follows: