This guide provides the steps to deploy LifeKeeper for virtual machines and increase their availability. It is based on actual work procedures to help you use SIOS Protection Suite for Linux (LifeKeeper) with Microsoft Azure (Azure) Resource Manager. It will guide you through the steps to configure the following examples of a cluster environment on an Azure VM.
- LifeKeeper cluster (2-node cluster) *Multi-NIC configuration
- Data mirror type shared data area with DataKeeper replication
- IP resources, Oracle resources
The information contained in this document is based on the results of validation performed on Azure as of March 2020. We do not guarantee any changes in the specifications of Azure and LifeKeeper in the future. Please refer to the most recent documentation and make the appropriate settings if necessary.
- Multi-NIC configurations are supported only on RHEL7 and CentOS7 where “Predictable Network Interface Name” can be used.
- RHEL5, CentOS5, RHEL6, CentOS6 only support single NIC configurations, not multi-NIC configurations.
- Active/Active configurations are not supported.
- Services that use multiple ports or configurations that provide multiple services are not supported.
- Internal Load Balancing or ILB – This is a function that enables load balancing between virtual machines that reside inside Azure cloud services or virtual networks with limited regions.
- [VIP protected with IP resources] – A virtual IP address created with LifeKeeper.
- [VIP configured by ILB] – A virtual IP address of the Internal Load Balancing created in Azure.
- [Azure private IP address] – A private address used in Azure Virtual Network.
Thanks for your feedback.
Post your comment on this topic.