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
Configuring OPS Clusters with MC/LockManager: > Chapter 7 Cluster and Package Maintenance

Making Changes to Shared Volume Groups (HP-UX Commands Only)

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

You may need to change the volume group configuration of OPS shared logical volumes to add capacity to the data files or to add log files. No configuration changes are allowed on shared volume groups while they are activated. The volume group must be deactivated first on all nodes, and marked as non-shareable. Use the following procedure (examples assume the volume group is being shared by node 1 and node 2, and they use the volume group vg_ops):

  1. Ensure that the OPS database is not active on either node.

  2. From node 2, use the vgchange command to deactivate the volume group:

    # vgchange -a n /dev/vg_ops 
  3. From node 2, use the vgexport command to export the volume group:

    # vgexport -m /tmp/vg_ops.map.old /dev/vg_ops 

    This dissociates the volume group from node 2.

  4. From node 1, use the vgchange command to deactivate the volume group:

    # vgchange -a n /dev/vg_ops 
  5. Use the vgchange command to mark the volume group as unshareable:

    # vgchange -S n -c n /dev/vg_ops 
  6. Prior to making configuration changes, activate the volume group in normal (non-shared) mode:

    # vgchange -a y /dev/vg_ops 
  7. Use normal LVM commands to make the needed changes. Be sure to set the raw logical volume device file's owner to oracle and group to dba, with a mode of 660.

  8. Next, still from node 1, deactivate the volume group:

    # vgchange -a n /dev/vg_ops 
  9. Use the vgexport command with the options shown in the example to create a new map file:

    # vgexport -p -m /tmp/vg_ops.map /dev/vg_ops 

    Make a copy of /etc/lvmpvg in /tmp/lvmpvg, then copy the file to /tmp/lvmpvg on node 2. Copy the file /tmp/vg_ops.map to node 2.

  10. Use the following command to make the volume group shareable by the entire cluster again:

    # vgchange -S y -c y /dev/vg_ops 
  11. On node 2, issue the following command:

    # mkdir /dev/vg_ops 
  12. Create a control file named group in the directory /dev/vg_ops, as in the following:

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

    The major number is always 64, and the hexadecimal minor number has the form

    0xhh0000

    where hh must be unique to the volume group you are creating. Use the next hexadecimal number that is available on your system, after the volume groups that are already configured.

  13. Use the vgimport command, specifying the map file you copied from the configuration node. In the following example, the vgimport command is issued on the second node for the same volume group that was modified on the first node:

    # vgimport -v -m /tmp/vg_ops.map /dev/vg_ops /dev/dsk/c0t2d0  \
    /dev/dsk/c1t2d0
  14. Activate the volume group in shared mode by issuing the following command on both nodes:

    # vgchange -a s -p /dev/vg_ops 

    Skip this step if you use the OPS runhalt script to activate and deactivate the shared volume group as a part of OPS startup and shutdown.

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