This section describes the steps required to protect a cluster of NFS servers.
Before Beginning
This section assumes that the following 2 resources are configured on the cluster.
- IP Resource
- Data Replication at /datakeeper
The LifeKeeper GUI should look like the following prior to installing the NFS software.
Install NFS Server Software
Install nfs-utils on both node-a and node-b.
Configure the NFS Server
Edit /etc/exports to define the NFS export. We are using the shared storage (/datakeeper) that is protected by DataKeeper. Create /datakeeper/nfs/data and use it as the location of the export.
Once the /etc/exports file is edited it should look like the following:
Start the NFS process on node-a.
Confirm Access to the NFS Server from a Client
On the client machine (e.g., node-c), complete the following steps to install the NFS software. Mount the NFS export from node-a to a local folder (e.g., mount to /local/nfsclient).
Now the content on the NFS server should be visible. Disconnect (unmount) from the NFS server to configure the NFS cluster.
Protecting an NFS Resource using LifeKeeper
- Select on the LifeKeeper user interface.
- The Create Resource Wizard at node-a screen will appear. Select the NFS Recovery Kit as the Recovery Kit.
- Select the following parameters.
Switchback Type | intelligent |
Server | node-a |
Export Point | /datakeeper/nfs/data |
IP Tag | ip-10.10.10.10 |
NFS Tag | nfs-/datakeeper/nfs/data |
The wizard checks these values. Once “nfs-/datakeeper/nfs/data” is successfully created on node-a, continue to the next steps.
- Select the following values on Pre-Extend Wizard @ node-a.
Target Server | node-b |
Switchback Type | intelligent |
Template Priority | 1 |
Target Priority | 10 |
The wizard checks these values. Once the Pre-Extend Check is completed, move on to the next steps.
- Select the following values on the Extend gen/nfs Resource Hierarchy @ node-a wizard.
NFS Tag | nfs-/datakeeper/nfs/data |
The NFS resource hierarchy is now defined in LifeKeeper. The wizard automatically defines a dependency between the NFS resource and required resources (IP resource and /datakeeper resource).
Post your comment on this topic.