Creating a Storage Infrastructure with LVM

Select the Volume Groups subarea.

From the Actions menu, choose Create or Extend.

Choose the first physical disk you wish to use in the volume group by selecting it from the list of available disks.

Enter the volume group name, e.g., vgdatabase.

Choose Create or Extend Volume Group.

Choose Add New Logical Volumes.

When adding logical volumes to the volume group, ensure that you are creating mirrored logical volumes with PVG strict allocation.

Specify the file system that is to be mounted on the volume group, for example, /mnt1.

Repeat the procedure for additional volume groups, logical volumes, and file systems.

Create the file system on the newly created logical volume:

# newfs -F vxfs /dev/vgdatabase/rlvol1 

Note the use of the raw device file for the logical volume.

Create a directory to mount the disk:

# mkdir /mnt1 

Mount the disk to verify your work:

# mount /dev/vgdatabase/lvol1 /mnt1 

Note the mount command uses the block device file for the logical volume.

Verify the configuration:

# vgdisplay -v /dev/vgdatabase 

On ftsys9, copy the mapping of the volume group to a specified file.

# vgexport -p -s -m /tmp/vgdatabase.map  /dev/vgdatabase 

Still on ftsys9, copy the map file to ftsys10:

# rcp /tmp/vgdatabase.map ftsys10:/tmp/vgdatabase.map 

On ftsys10, create the volume group directory:

# mkdir /dev/vgdatabase 

Still on ftsys10, create a control file named group in the directory /dev/vgdatabase, as follows:

# mknod /dev/vgdatabase/group c 64 0xhh0000 

Use the same minor number as on ftsys9. Use the following command to display a list of existing volume groups:

# ls -l /dev/*/group 

Import the volume group data using the map file from node ftsys9. On node fsys10, enter:

# vgimport -s -m /tmp/vgdatabase.map /dev/vgdatabase  

Note that the disk device names on ftsys10 may be different from their names on ftsys9. You should check to ensure that the physical volume names are correct throughout the cluster.

When the VG can be activated on this node, perform a vgcfgbackup in the unlikely event that a vgcfgrestore must be performed on this node because of a disaster on the primary node and an LVM problem with the volume group. Do this as shown in the example below:

# vgchange -a y /dev/vgdatabase
# vgcfgbackup /dev/vgdatabase
# vgchange -a n /dev/vgdatabase

If you are using mirrored individual disks in physical volume groups, check the /etc/lvmpvg file to ensure that each physical volume group contains the correct physical volume names for ftsys10.

	NOTE: When you use PVG-strict mirroring, the physical volume group configuration is recorded in the /etc/lvmpvg file on the configuration node. This file defines the physical volume groups which are the basis of mirroring and indicate which physical volumes belong to each PVG. Note that on each cluster node, the /etc/lvmpvg file must contain the correct physical volume names for the PVG’s disks as they are known on that node. Physical volume names for the same disks may not be the same on different nodes. After distributing volume groups to other nodes, you must ensure that each node’s /etc/lvmpvg file correctly reflects the contents of all physical volume groups on that node. Refer to the following section, “Making Physical Volume Group Files Consistent.”

Make sure that you have deactivated the volume group on ftsys9. Then enable the volume group on ftsys10:

# vgchange -a y /dev/vgdatabase 

Create a directory to mount the disk:

# mkdir /mnt1 

Mount and verify the volume group on ftsys10:

# mount /dev/vgdatabase/lvol1 /mnt1 

Unmount the volume group on ftsys10:

# umount /mnt1

Deactivate the volume group on ftsys10:

# vgchange -a n /dev/vgdatabase 

Copy /etc/lvmpvg from ftsys9 to /etc/lvmpvg.new on ftsys10.

If there are volume groups in /etc/lvmpvg.new that do not exist on ftsys10, remove all entries for that volume group from /etc/lvmpvg.new.

If /etc/lvmpvg on ftsys10 contains entries for volume groups that do not appear in /etc/lvmpvg.new, then copy all PVG entries for that volume group to /etc/lvmpvg.new.

Adjust any physical volume names in /etc/lvmpvg.new to reflect their correct names on ftsys10.

On ftsys10, copy /etc/lvmpvg to /etc/lvmpvg.old to create a backup. Copy /etc/lvmvpg.new to /etc/lvmpvg on ftsys10.