Use this option to protect a file system only (for example, if you have shared files that need protection).
On the Edit menu, select Resource, then Create Resource Hierarchy. A dialog box entitled Create Resource Wizard will appear with a list of all recognized recovery kits installed within the cluster.
Select File System Resource and click Next.
Select either intelligent or automatic for Switchback Type and click Next.
Select the Server on which you want to create the hierarchy, and click Next. The Create gen/filesys Resource dialog box appears.
Select the Mount Point for the file system resource hierarchy.
Note:
In order for a mount point to appear in the choice list, the mount point must be currently mounted. If an entry for the mount point exists in the /etc/fstab file, LifeKeeper will remove this entry during the creation and extension of the hierarchy. When the hierarchy is deleted, an entry will be placed in the /etc/fstab file only on the primary server (i.e. the server that is set to the AUTORES_ISP state) so that the file system will be automatically mounted at boot time on that server. An entry will NOT be placed in the /etc/fstab file when a hierarchy is unextended.
If your wish to create a File System resource that is built on a logical volume, then you must first have the LVM Recovery Kit installed. Otherwise, the mount point for the file system will not appear in the choice list.
LifeKeeper creates a default Root Tag for the file system resource hierarchy.(This is the label used for this resource in the status display). You can select this root tag or create your own, then click Next.
Click Create Instance. A window will display a message indicating the status of the instance creation.
Click Next. A window will display a message that the file system hierarchy has been created successfully.
At this point, you can click Continue to move on the extending the file system resource hierarchy, or you can click Cancel to return to the GUI. If you click Cancel, you will receive a warning message that your hierarchy exists on only one server, and it is not protected at this point.