This chapter describes how to configure a highly available active/passive NFS server on a two-node Red Hat Enterprise Linux High Availability Add-On cluster using shared storage. The procedure uses
pcs to configure Pacemaker cluster resources. In this use case, clients access the NFS file system through a floating IP address. The NFS server runs on one of two nodes in the cluster. If the node on which the NFS server is running becomes inoperative, the NFS server starts up again on the second node of the cluster with minimal service interruption.
This use case requires that your system include the following components:
Two nodes, which will be used to create the cluster running the Apache HTTP server. In this example, the nodes used are
A power fencing device for each node of the cluster. This example uses two ports of the APC power switch with a host name of
A public virtual IP address, required for the NFS server.
Shared storage for the nodes in the cluster, using iSCSI, Fibre Channel, or other shared network block device.
Configuring a highly available active/passive NFS server on a two-node Red Hat Enterprise Linux High requires that you perform the following steps.
3.1. Creating the NFS Cluster
Use the following procedure to install and create the NFS cluster.
Create the two-node cluster that consists of
, using the procedure provided in Section 1.2, “Cluster Creation”
. As in that example procedure, this use case names the cluster
Configure fencing devices for each node of the cluster, using the procedure provided in Section 1.3, “Fencing Configuration”
. This example configures fencing using two ports of the APC power switch with a host name of