Azure is a public cloud service provided by Microsoft that enables users to utilize hardware, networks, disks and storage. The service can be used on Windows and Linux operating systems, web servers, RDBMS, and other middleware, groupware, server applications, and application runtime environments such as .Net framework on demand over a network. With Azure, users can easily create, deploy, and manage server applications over the Internet in Microsoft-managed data centers around the world. You can use only the required amount of computing resources, such as memory and disk without having your own servers or infrastructure. Pricing is grouped by resource and usage is based on hourly pay-as-you-go
Azure provides a web browser-based management portal that allows users to operate intuitively.
This document describes how LifeKeeper for Windows is deployed on virtual machines and introduces methods for increasing availability.
The configuration described below uses LifeKeeper for Windows to build an active/standby cluster.
VM Configuration (Cluster Nodes)
|Active System (lknode01)||Standby System (lknode02)|
|Virtual Machine Size||Standard B2ms (cpu/mem/disk=2/8g/4) *|
|Data Disk||30GB (for application use) *|
|Private IP Address||10.20.1.11||10.20.1.12|
|[VIP Protected by IP Resource]||10.20.1.200|
|[VIP Configured by ILB]||10.20.1.200|
|Ports Forwarded by ILB (i.e. ports on which Oracle listens)||(if using Oracle) 1521
(if using PostgreSQL) 5432
|ILB Load Balancing|| (if using Oracle)
(if using PostgreSQL)
|(if using Oracle)10.20.1.12:1521
(if using PostgreSQL) 10.20.1.12:5432
|Software||Windows Server 2019 Datacenter Edition
LifeKeeper for Windows v8.7.0
Oracle Database 19c (19.3) for Microsoft Windows x64 (64-bit)
- Ensure that your instance size and virtual machine disks meet the installation requirements for applications (Oracle, PostgreSQL, etc.) you want to protect.
VM Configuration (Client)
|Virtual Machine Siza||Standard A2m_v2 (2/16g/4)|
|Private IP Address||10.20.1.50|
|Software||Microsoft Windows 10
Oracle Database 19c Client (19.3) for Microsoft Windows x64 (64-bit)
Azure is used to create a virtual network (VNET) to enable communication between virtual machines (VMs). VNET enables communication between VMs within this subnet by specifying a subnet.
When configuring a network for VMs in Azure, it is common to create a VNET beforehand and specify this VNET for the VM. With VNET you can provide a virtual private network (VPN) to your VMs. Optionally, you can connect your VPN to your on-premises environment to implement hybrid and cross-premises solutions. VNETs can be used to control network topologies, including DNS and IP address range configurations, through the management portal site and Azure PowerShell.
Post your comment on this topic.