Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Managing Serviceguard Fifteenth Edition > Appendix G Migrating from LVM to VxVM Data Storage

Customizing Packages for CVM


Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

NOTE: Check the Serviceguard, SGeRAC, and SMS Compatibility and Feature Matrix and the latest Release Notes for your version of Serviceguard for up-to-date information about support for CVM and CFS: http://www.docs.hp.com -> High Availability -> Serviceguard.

After creating the CVM disk group, you need to customize the Serviceguard package that will access the storage. Use the following procedure to modify a legacy package to use Cluster Volume Manager (CVM) disk groups. If you are using the Veritas Volume Manager (VxVM), use the procedure in the previous section. If you decide to create a new package, see Chapter 6 “Configuring Packages and Their Services”.

  1. Rename the old package control script as follows:

    # mv Package.ctl Package.ctl.bak

  2. Create a new package control script with the same name as the old one:

    # cmmakepkg -s Package.ctl

  3. Edit the new script to include the names of the new CVM disk groups and logical volumes.

    The new portions of the package control script that are needed for CVM use are as follows:

    • The CVM_DG[] array. This defines the CVM disk groups that are used for this package. The first CVM_DG[] entry should be in index 0, the second in 1, etc. For example:

    • The LV[], FS[] and FS_MOUNT_OPT[] arrays are used the same as they are for LVM. LV[] defines the logical volumes, FS[] defines the mount points, and FS_MOUNT_OPT[] defines any mount options.

      For example lets say we have two volumes defined in each of the two disk groups from above, lvol101 and lvol102, and lvol201 and lvol202. These are mounted on /mnt_dg0101 and /mnt_dg0102, and /mnt_dg0201 and /mnt_dg0202, respectively.

      /mnt_dg0101 and /mnt_dg0201 are both mounted read-only. The LV[], FS[] and FS_MOUNT_OPT[] entries for these would be as follows:



      FS_MOUNT_OPT[0]="-o ro"
      FS_MOUNT_OPT[1]="-o rw"
      FS_MOUNT_OPT[2]="-o ro"
      FS_MOUNT_OPT[3]="-o rw"

  4. Be sure to copy from the old script any user-specific code that may have been added, including environment variables and customer defined functions.

  5. Be sure to uncomment the appropriate CVM_ACTIVATION_CMD statement to specify the kind of import you wish the package to perform on the disk group.

  6. Distribute the new package control scripts to all nodes in the cluster.

  7. Enter each disk group into the package ASCII configuration file immediately following the HALT_SCRIPT_TIMEOUT parameter. Add one STORAGE_GROUP definition for each disk group. For the two disk groups in the previous example, you would enter the following lines:


    Then re-apply the package configuration:

    # cmapplyconf -P PackageName.ascii

  8. Test to make sure the disk group and data are intact.

  9. Deport the disk group:

    # vxdg deport DiskGroupName

  10. Start the cluster, if it is not already running:

    # cmruncl

    This will activate the special CVM package.

  11. When CVM starts up, it selects a master node, and this is the node from which you must issue the disk group configuration commands. To determine the master node, issue the following command from each node in the cluster:

    # vxdctl -c mode

    One node will identify itself as the master.

  12. Make the disk group visible to the other nodes in the cluster by issuing the following command on the master node:

    # vxdg -s import DiskGroupName

  13. Restart the package.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.