In this configuration, LifeKeeper is used to build an active/standby cluster as shown below. LifeKeeper is deployed on an Azure VM with a multi-NIC configuration.

Server Configuration

Virtual Machine size

Cluster node: Standard_A1 (1 core, 1.75 GB memory)

Client/Witness ServerはBasic_A0

(0.25 core, 0.75GB memory)

*Note 1

Data Disk

30GiB (for Oracle DB)

10GiB (for swap area)

(sdb is not user for the verification *Note 2)

*Note 1

[VIP protected with IP resources] 10.3.1.200
[IP to set in ILB] 10.3.1.200
ILB forwarding port 1521
ILB load balancing target hosts and ports 1521 port for each lk4lnode01/lk4lnode02
[Azure private IP address]

Cluster node (Active) 10.3.1.11 / 10.3.2.11

Cluster node (Standby) 10.3.1.12 / 10.3.2.12

Client and Witness server 10.3.1.50

*Note 1: Prepare the instance size and virtual machine disks to satisfy Oracle installation requirements (1 GB of memory, Oracle database installation disk size, and swap area size).

*Note 2: The disk ID of the /mnt/resource data disk that Azure mounts and starts with the initial configuration changes every time it is rebooted. Therefore, it cannot be used for disks that are used as shared disks for SIOS Protection Suite for Linux. We have added more disks separately in this document.

Software Configuration

OS RedHat Enterprise Linux 7.5 64bit
LifeKeeper SIOS Protection Suite for Linux v9.3.2
Oracle Oracle Database 12c Enterprise Edition

Monitored Items

Monitored items VIP PROTECTED WITH IP RESOURCES / File system / DataReplication / Oracle DB / Oracle Listener

Network Configuration

In Azure, a “virtual network” (VNET) is created to enable communication between virtual machines (VMs). The VNET enables communication between VMs within this subnet by specifying a subnet.

When configuring a network on a VM on Azure, it is common to create a VNET beforehand and specify this VNET for the VM. VNET allows you to provide a virtual private network (VPN) to the VM. Optionally, a VPN can be connected to the on-premises environment to enable hybrid or cross-premises solutions. VNET can control network topology, including DNS and IP address range configuration, through the management portal and Azure PowerShell.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment