Configurations

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.

Data Replication

Server Configuration

*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: Most Azure VMs contain a temporary disk (/dev/disk/cloud/azure_resource), which is not a managed Disk. The temporary disk provides short-term storage for applications and processes and is intended to only store data such as page or swap files. The temporary storage is automatically mounted on /mnt but in the examples below it is being mounted on /mnt/resource. The azure_resource is often the /dev/sdb device node but can be a different device node depending on the configuration. This temporary disk is NOT suitable to be used as a LifeKeeper protected device such as storage used with DataKeeper. Refer to the file /mnt/DATALOSS_WARNING_README.txt for more information.

*Note 3: Microsoft Azure shared disk requires the steeleye-lkSCSI3 recovery kit available starting with LifeKeeper 9.6.2.

Software Configuration

Monitored Items

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.