*LifeKeeper does not support Windows Restore. Using Windows Restore may result in shared storage becoming locked and in a RAW state.

Supported Cloud Platforms

• AWS
• AWS Outposts
• Microsoft Azure
• Google Cloud
• Oracle Cloud Infrastructure
• Red Hat OpenShift Virtualization

AWS Outposts

AWS services generally offered as cloud services are referred to as Region, and AWS Outposts are referred to as Outposts.
Additionally, clients on Outposts or in a region under the same account are referred to as internal clients, and clients on-premise or on a different account are referred to as external clients.

Available configurations

With the exception of some ARKs, features available on Regions can also be used on Outposts by meeting the equivalent requirements.
The ARKs that have Outposts-specific restrictions are as follows:

• Recovery Kit for EC2 (RK for EC2)
• Recovery Kit for Route53 (RK for Route53)
• LB Health Check Kit (LBHC Kit)

When connecting from an external client, the use of these ARKs is restricted by the Outposts routing mode.

For availability reasons, it is recommended that each LifeKeeper cluster node be located on a different Outposts server.

Configuration notes for using the Recovery Kit for Route53 in CoIP mode

To communicate with the LifeKeeper cluster from external clients in CoIP mode, use RK for Route53.
Please make the OS recognize CoIP in order for RK for Route53 to rewrite the IP address corresponding to the A record of the Route53 Hosted Zone.
CoIP is not recognized by the OS even if it is assigned to an EC2 instance or ENI on the AWS console. Therefore, a private IP address equivalent to CoIP must be statically assigned on the OS. However, if a static IP address is assigned on the OS that is not assigned in the AWS console, it may cause problems with other communications using the corresponding NIC. Therefore, you should either assign a dedicated ENI that is not used for actual communications or create a dummy NIC, and then statically assign the CoIP to the NIC.

Red Hat OpenShift Virtualization

Available OpenShirft Virtualization Features

• Live Migration
• Snapshot
  1. Precautions when taking snapshots
     1. When using DataKeeper, snapshots must be taken in a manner that prevents data inconsistencies between the source and target nodes. To ensure this, stop all target nodes before taking snapshots, and make sure to take snapshots on all nodes at the same point in time.
  2. Precautions when restoring
     1. Stop all LifeKeeper cluster nodes before restoring.
     2. When restoring from a snapshot, the Persistent Volume Claim (PVC) is replaced by a different PVC. If a shared disk is attached, you need to manually specify the same PVC for all virtual machines except the first one restored, as their PVCs will either remain as the old PVC or be left unspecified.
     3. For Windows VMs, if a virtual Trusted Platform Module (vTPM) device is assigned, you must remove the vTPM device from the VM. In the OpenShift Virtualization Web console, go to the Configuration tab for the VM, set the boot mode to UEFI, and disable the vTPM setting from the YAML tab.
        (This step is not necessary for OpenShift Virtualization v4.18 and later.)

■ Before
spec:
..(snip)..
        devices:
          tpm:
            persistent: true
■ After
spec:
..(snip)..
        devices:
          tpm: {}

Configuration Requirements

Storage Requirements
The requirements for disks on which LifeKeeper is installed and those protected by LifeKeeper are as follows:

• Storage class is ocs-storagecluster-ceph-rbd-virtualization
• Type is Disk
• When protecting a shared disk with LifeKeeper, use the same Disk name on both nodes
• Interface is virtio
  

Network Requirements

• Networks used for LifeKeeper communication paths and IP resources must meet the following requirements.
  1. It is a Linux bridge network
  2. The network interface controller model is virtio

Client Requirements

• The intended clients are VMs and containers on the same OpenShift Virtualization.
  

Restrictions

• The following ARKs are not available for use.
  1. LB Health Check Kit
  2. ARKs for other virtualization platforms
     1. Recovery Kit for EC2
     2. Recovery Kit for Route 53
• Migration of a virtual machine with LifeKeeper installed between other virtualization platforms and OpenShift Virtualization is not supported.
• In the event of a failure related to OpenShift Data Foundation, LifeKeeper may not function as expected. We recommend implementing sufficient redundancy and preparing a solution other than LifeKeeper.