Use this option to protect a file system only (for example, if you have shared files that need protection).

  1. There are four ways to begin creating a file system resource hierarchy.
  • º Right-click on a server icon to bring up the
server context menu, then click on Create Resource Hierarchy.
  • º On the
global toolbar, click on the Create Resource Hierarchy button.
  • º On the
server context toolbar, if displayed, click on the Create Resource Hierarchy button.
  • º On the
Edit menu, select Server, then click on Create Resource Hierarchy.
  1. A dialog entitled Create Resource Wizard will appear with a Recovery Kit list. Select File System Resource and click Next.
  1. Select the Switchback Type and click Next.
  1. Select the Server and click Next. Note: If you began from the server context menu, the server will be determined automatically from the server icon that you clicked on, and this step will be skipped.
  1. The Create gen/filesys Resource dialog will now appear. Select the Mount Point for the file system resource hierarchy and click Next. The selected mount point will be checked to see that it is shared with another server in the cluster by checking each storage kit to see if it recognizes the mounted device as shared. If no storage kit recognizes the mounted device, then an error dialog will be presented:

<file system> is not a shared file system

Selecting OK will return to the Create gen/filsys Resource dialog.


    • 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. It is advisable to make a backup of /etc/fstab prior to using the NAS Recovery Kit, especially if you have complex mount settings. You can direct that entries are re-populated back into /etc/fstab on deletion by setting the /etc/default/LifeKeeper tunable REPLACEFSTAB=true|TRUE.
    • Many of these resources (SIOS DataKeeper, LVM, Device Mapper Multipath, etc.) require LifeKeeper recovery kits on each server in the cluster in order for the file system resource to be created. If these kits are not properly installed, then the file system will not appear to be shared in the cluster.
  1. 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.
  1. Click Create Instance. A window will display a message indicating the status of the instance creation.
  1. Click Next. A window will display a message that the file system hierarchy has been created successfully.
  1. At this point, you can click Continue to move on to 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.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment