A Communication Path is a mechanism that allows the three nodes to communicate with each other and to transfer the data (for data replication purposes) between nodes. In a typical setup and especially in an on-premise environment, multiple communication paths are required to avoid a single point of failure. In this example, the network card in each node, or network routers switching between these nodes can be a point of failure.

In a cloud environment, however, having one communication path between nodes may be good enough as the underlying network layer is abstracted (we don’t have visibility of these layers).

The next step is to define communication paths between all pairs of nodes.

  1. Click “Add communication path”.

  1. Select the following values. In most cases, these values should already be filled and selected.
Local Server node-a
Remote Server(s) node-b
Device Type TCP
Local IP Address(es)
Remote IP Address
Priority 1
  1. The summary of what has been configured will be displayed. Select “Next”.

  1. A communication path has now been defined.

Once the communication path has been defined, you may notice a yellow triangle ( ) on each node. This is because we have only defined a single communication path. If a second communication path is defined, this changes to a green checkmark ( ).

Turn off the Comm Path Redundancy Warning

This warning may be ignored if you are deploying in the cloud. The warning sign can be turned off by unchecking the “Comm Path Redundancy Warning” check box in the View menu of the LifeKeeper GUI.

Once unchecked, the icon will change from to .



はい いいえ