Defining shared LVM components

These topics describe how to define the LVM components shared by the nodes in a PowerHA® SystemMirror® cluster.

Creating the volume groups, logical volumes, and file systems shared by multiple nodes in a PowerHA SystemMirror cluster requires that you perform steps on all those nodes. In general, you define the components on one node (referred to in the text as the source node) and then import the volume group onto each of the other nodes that will be part of the resource group (referred to as destination nodes). This ensures that the definitions in the PowerHA SystemMirror configuration database for the shared components are the same on all the nodes that may access them.

Using SMIT, you can collect information about all volume groups available either on a local node, or on all nodes in the cluster defined to the resource group. Later, you can automatically import these volume groups onto all the destination nodes, if needed. As you configure shared resources in SMIT, when you add a volume group to a resource group, you can select the option to automatically import the volume group onto all the destination nodes in the participating resource group.

PowerHA SystemMirror nonconcurrent access environments typically use journaled file systems to manage data, while concurrent access environments use raw logical volumes. This topic provides instructions for both types of environments.

While configuring file systems for a resource group, you can select one or more individual file systems to be mounted in the particular resource group. In addition, you can specify that all file systems in the specified shared volume groups are mounted at run time. Using this option allows you to add or delete file systems in the particular shared volume group without resynchronizing the cluster resources after each update.