Veritas™ Volume Manager 5.0.1 Migration Guide HP-UX 11i v3 HP Part Number: 5900-0088 Published: November 2009 Edition: 1.
© Copyright 2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Technical Support ............................................................................................... 4 Chapter 1 VxVM and LVM ...................................................................... 9 About VxVM and LVM .................................................................... 9 Introducing Veritas Volume Manager ................................................ 9 Notable features of VxVM .......................................................
8 Contents Example: displaying the vxvmconvert menu ............................... Example: listing disk information .............................................. Example: listing LVM volume group information ......................... Example: analyzing LVM volume groups .................................... Example: converting LVM volume groups to VxVM disk groups ...........................................................................
Chapter 1 VxVM and LVM This chapter includes the following topics: ■ About VxVM and LVM ■ Introducing Veritas Volume Manager ■ VxVM and LVM—conceptual comparison ■ Coexistence of VxVM and LVM disks About VxVM and LVM This chapter provides an overview of Veritas Volume Manager by Symantec (also referred to as VxVM) and its features. It includes a brief description of the benefits of migrating from the HP-UX Logical Volume Manager (LVM) to VxVM.
10 VxVM and LVM Introducing Veritas Volume Manager See the Storage Foundation Release Notes for additional details of the features that are supported in this release. ■ Veritas Volume Manager can be used instead of LVM to manage the root disk. Basic volume management capabilities are included in the operating system. ■ Veritas Volume Manager is integrated with HP ServiceGuard and ServiceGuard OPS Edition for High Availability, but requires a specific version of the ServiceGuard products.
VxVM and LVM Introducing Veritas Volume Manager ■ Task Monitor, which tracks the progress of system recovery by monitoring task creation, maintenance, and completion. The Task Monitor lets you pause, resume, and stop as desired to adjust the impact on system performance. ■ Multiple mirroring with up to 32 mirror copies of a volume’s address space. ■ Mirrored stripes (RAID-0 + RAID-1) and striped mirrors (RAID-1 + RAID-0) combine the benefits of striping and mirroring.
12 VxVM and LVM VxVM and LVM—conceptual comparison Note: Additional information is available on LVM and VxVM commands. See HP-UX Managing Systems and Workgroups See LVM manual pages in HP-UX Reference Volumes 2, 3, and 5. See the Veritas Volume Manager documentation. VxVM and LVM—conceptual comparison The following section compares the terminology that is used in LVM and VxVM at a conceptual level.
VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 A conceptual comparison of LVM and VxVM (continued) LVM term VxVM term Description Physical volume VxVM disk An LVM physical volume and a VxVM disk are conceptually the same. A physical disk is the basic storage device (media) where the data is ultimately stored. You can access the data on a physical disk by using a device name (devname) to locate the disk. In LVM, a disk that is initialized by LVM becomes known as a physical volume.
14 VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 A conceptual comparison of LVM and VxVM (continued) LVM term VxVM term Description Logical volume Volume An LVM logical volume and a VxVM volume are conceptually the same. Both are virtual disk devices that appear to applications, databases, and file systems like physical disk devices, but do not have the physical limitations of physical disk devices.
VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 A conceptual comparison of LVM and VxVM (continued) LVM term VxVM term Description Volume group Disk group LVM volume groups are conceptually similar to VxVM disk groups. An LVM volume group is the collective identity of a set of physical volumes, which provide disk storage for the logical volumes. A VxVM disk group is a collection of VxVM disks that share a common configuration.
16 VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 LVM term A conceptual comparison of LVM and VxVM (continued) VxVM term Unused physical extent Free space Description VxVM can place a disk under its control without adding it to a disk group. The VxVM Storage Administrator shows these disks as “free space pool”. LVM contains unused physical extents that are not part of a logical volume, but are part of the volume group.
VxVM and LVM Coexistence of VxVM and LVM disks Table 1-1 A conceptual comparison of LVM and VxVM (continued) LVM term VxVM term Description Import Import In LVM, import adds a volume group to the system and the volume group information to /etc/lvmtab but does not make the volumes accessible. The volume group must be activated by the vgchange -a y command to make volumes accessible. In VxVM, import imports a disk group and makes the disk group accessible by the system.
18 VxVM and LVM Coexistence of VxVM and LVM disks The System Management Homepage (SMH) and Veritas Enterprise Administrator (VEA) graphical administrative utilities also recognize and identify all disks on the system. See “About SMH and the VEA” on page 73. The vxvmconvert command is provided to enable LVM disks to be converted to a VxVM disk format without losing any data. See “Converting LVM volume groups to VxVM disk groups” on page 21.
Chapter 2 Converting LVM to VxVM This chapter includes the following topics: ■ About LVM to VxVM conversion ■ Converting unused LVM physical volumes to VxVM disks ■ Converting LVM volume groups to VxVM disk groups ■ Restoring the LVM volume group configuration ■ Examples ■ General information regarding conversion speed ■ Non-interactive conversion of volume groups About LVM to VxVM conversion This chapter explains how to convert your LVM configuration to a VxVM configuration.
20 Converting LVM to VxVM Converting unused LVM physical volumes to VxVM disks The former are disks that contain logical volumes and volume groups. Unused disks contain no user data, and are not used by any volume group, but have LVM disk headers written by pvcreate. Conversion is done differently for these two types of disks. For unused LVM disks you can use a combination of pvremove and vxdiskadm. For LVM disks in volume groups, the primary tool for conversion is the vxvmconvert command.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups If pvdisplay finds no valid group information associated with the disk, you can overwrite the LVM headers using pvcreate: # pvcreate disk_name Warning: If disk_name is an alternate path to a disk that does not appear in the lvmtab file for this system, or is a disk that is in use on another system, but not imported onto this system, then do not pvcreate -f the disk. Doing so will destroy the LVM headers.
22 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups The conversion process involves many steps. Though there are tools to help you with the conversion, some of these steps cannot be automated. You should be sure to understand how the whole conversion process works, and what you will need to do in the process before beginning a volume group conversion. The tool used for conversion is vxvmconvert.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Thevxvmconvertcommand does not convert any volume group that contains a rootable volume, identified by the presence of the LIF area as created by mkboot(1M). Not only is the current root volume off limits, but any volume that might be used as an alternate root volume is rejected as well. Note: VxVM rootability operations and rootability commands are currently not supported on the LVM version 2 volume groups.
24 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups root volume can be converted (as long as this volume is not in the same volume group as the root volume). ■ Volume group disks used in MC/ServiceGuard clusters. The conversion process does not support conversion of any volume group that is marked as a member of a MC/ServiceGuard or OPS Edition high availability cluster.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups conversion. Some of them (e.g. backing up user data) are left to you to accomplish through your regular administrative processes. The steps in the conversion process are: ■ Identifying LVM volume groups for conversion. ■ Analyzing an LVM group to see if conversion is possible. ■ Taking actions to make conversion possible if analysis fails. ■ Backing up your LVM configuration and user data.
26 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Analyzing an LVM volume group to see if conversion is possible After you have selected a volume group for conversion, you need to analyze it to determine if conversion for VxVM use is possible. Use the analyze option of vxvmconvert to check for problems that would prevent the conversion from completing successfully. Additional information is available on all the conditions that this option checks for.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Messages from vxvmconvert will explain the type of failure and any actions that can be taken before retrying the analysis. Complete details on specific error messages and actions are available. See “About conversion error messages” on page 79. Backing up your LVM configuration and user data After analysis you know which volume group or groups you want to convert to VxVM disk groups.
28 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Note: The vxvmconvert utility itself also saves a snapshot of the LVM metadata in the process of conversion for each disk. This data is saved in a different format from that of vgcfgbackup. It can only be used by the vxvmconvert program. With certain limitations, you can reinstate the LVM volumes after they have been converted to VxVM using this data.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Planning for new VxVM logical volume names When you change from LVM volumes to VxVM volumes, the device names by which your system accesses data are changed. LVM creates device nodes for its logical volumes in /dev under directories named for the volume group. VxVM creates its device nodes in /dev/vx/dsk and /dev/vx/rdsk.
30 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Warning: This method of resolving the naming problem has risks. The symbolic links can become stale. For example, if a database refers to /dev/vx/rdsk/vol1 through a symbolic link /dev/vg00/rvol1(“the old LVM name”), and if the underlying VxVM volume configuration is changed in any way, the database could refer to a missing or different volume. Note: You may want to use this symbolic link approach to ease the transition to VxVM.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups To unmount a file system, use the following command: # umount file-system Conversion and reboot During conversion, after the analysis phase is complete, the disks to be converted are deemed to be conversion ready. The vxvmconvert program asks if you are ready to commit to the conversion changes.
32 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups As described earlier, the volume groups selected for conversion are analyzed to ensure that conversion is possible. See “Analyzing an LVM volume group to see if conversion is possible” on page 26. After a successful analysis phase, vxvmconvertprompts you to commit to the change or abort the conversion. When you select to commit to conversion, the new VxVM metadata is written.
Converting LVM to VxVM Restoring the LVM volume group configuration names. When you started vxvmconvert, you may have left file systems mounted that are associated with the volumes you converted. vxvmconvert remounts these with the new VxVM volume names. Tailoring your VxVM configuration vxvmconvert provides a default name for naming the newly formed VxVM disk group during conversion only as an option. However, you will be given the choice of choosing your own VxVM disk group name.
34 Converting LVM to VxVM Restoring the LVM volume group configuration ■ If during a conversion only some of a set of volume groups converted successfully, then you may want to restore the LVM configuration for the entire set. It is possible to restore the original LVM configuration in one of two ways, but both have limitations and restrictions. The method you use depends on if any changes have been made to the VxVM configuration since the conversion occurred.
Converting LVM to VxVM Restoring the LVM volume group configuration Note: Restoring user data using the vgrestore and frecover method will result in the loss of all user data changes made since the conversion, and the loss of all new volumes created since the conversion. In other words, this method of restoring data will take you back to exactly where you were before the conversion was done.
36 Converting LVM to VxVM Restoring the LVM volume group configuration Note: In many cases, if you choose the rollback method and the configuration has changed, you receive an error and must use the full restore method.. If you used the workaround of creating symbolic links from the old LVM names to the new VxVM names, you must remove the symbolic links you created before beginning the rollback. Additional information is available on creating symbolic links.
Converting LVM to VxVM Examples To use this method, you must have backed up data located on all the volume groups’ logical volumes before conversion to VxVM. Restoration of LVM volume groups is a two-step process consisting of a restoration of LVM internal data (metadata and configuration files), and restoration of user or application data. The process is limited to restoring the state of the logical volumes as they existed before conversion to VxVM disks.
38 Converting LVM to VxVM Examples 3 list listvg ? ?? q Roll back from VxVM to LVM List disk information List LVM Volume Group information Display help about menu Display help about the menuing system Exit from menus Example: listing disk information The list option of vxvmconvert displays information about the disks on a system. Select the list option from the vxvmconvert Main Menu: Menu: Volume Manager/LVM_Conversion/list # list Use this menu option to display a list of disks.
Converting LVM to VxVM Examples LVM VOLUME GROUP INFORMATION NAME VERSION TYPE PHYSICAL VOLUME vg00 1.0 ROOT disk10 vg09 2.0 Non-Root disk11 vg08 1.0 Non-Root disk12 Volume Group to list in detail [
,none,q,?] (default: none) none To display detailed information about a volume group, select any of the volume groups from the above list.40 Converting LVM to VxVM Examples Current LE Allocated PE Used PV --- Physical volumes --PV Name PV Status Total PE Free PE 125 125 1 /dev/disk/disk12 available 250 0 List another LVM Volume Group? [y,n,q,?] (default: n) Select an operation to perform: Note: The volume groups you want to convert must not be a root volume group or have bootable volumes in the group.
Converting LVM to VxVM Examples More than one volume group or pattern may be entered at the prompt.
42 Converting LVM to VxVM Examples list listvg ? ?? q List disk information List LVM Volume Group information Display help about menu Display help about the menuing system Exit from menus Select an operation to perform: 1 Analyze one or more LVM Volume Groups Menu: Volume Manager/LVM_Conversion/Analyze_LVM_VGs Use this operation to analyze one or more LVM volume groups for possible conversion using the VxVM Volume Manager.
Converting LVM to VxVM Examples SMALLEST VGRA space = 176 RESERVED space sectors = 78 PRIVATE SPACE/FREE sectors = 98 AVAILABLE sector space = 49 AVAILABLE sector bytes = 50176 RECORDS neededs to convert = 399 MAXIMUM records allowable = 392 The smallest disk in the Volume Group (vg08) does not have sufficient private space for the conversion to succeed.
44 Converting LVM to VxVM Examples one or more VxVM disk groups. This adds the disks to a disk group and replaces existing partitions with volumes. LVM-VxVM Volume Group conversion may require a reboot for the changes to take effect. For this release, only Non-root LVM Volume Groups are allowed to be converted. More than one Volume Group or pattern may be entered at the prompt.
Converting LVM to VxVM Examples process will not be able to complete without a reboot.You would then be given the choice to either abort the conversion, or finish the conversion by rebooting the system. The conversion process will update the /etc/fstab file so that volume devices are used to mount the file systems on this disk device. You will need to update any other references such as backup scripts, databases,or manually created swap devices.
46 Converting LVM to VxVM Examples The system reconfiguration will now be done without rebooting. The Volume Manager is now reconfiguring (initialization phase)... Volume Manager: Adding dg0801 (disk12) as a converted LVM disk. Adding volumes for disk12... Starting new volumes... Updating /etc/fstab... The system will now Convert the LVM Volume Groups over to VxVM disk groups.
Converting LVM to VxVM Examples Select Volume Groups to convert : [,all,list,listvg,q,?] listvg LVM VOLUME GROUP INFORMATION NAME VERSION TYPE PHYSICAL vg00 1.0 vg05 1.0 vg03 2.0 vg08 1.
48 Converting LVM to VxVM Examples RESERVED space sectors = 78 PRIVATE SPACE/FREE sectors = 98 AVAILABLE sector space = 49 AVAILABLE sector bytes = 50176 RECORDS neededs to convert= 399 MAXIMUM records allowable = 392 The smallest disk in the Volume Group (vg08) does not have sufficient private space for the conversion to succeed. There is only enough private space for 392 VM Database records and the conversion of Volume Group (vg08) would require enough space to allow 399 VxVM Database records.
Converting LVM to VxVM Examples 49 Enter Volume Group (i.e.- vg04) or "all" [
,all,q,?] (default:all) LVM VOLUME GROUP INFORMATION Name Version Type Physical Volumes vg00 vg01 c2t0d0 c9t3d4 1.0 2.50 Converting LVM to VxVM Examples listvg: list: vg_name: : list all LVM Volume Groups list all disk devices a single LVM Volume Group, named vg_name for example: vg04 vg08 vg09 Select Volume Groups to convert : [,all,list,listvg,q,?]vg01 Convert LVM Volume Group vg01 Convert this Volume Group? [y,n,q,?] (default:y) VxVM NOTICE V-5-2-0 LVM Volume Group vg01 reports a version 2.0 LVM Volume Group other than version 1.0 is not supported for conversion. Hit RETURN to continue.
Converting LVM to VxVM Examples What does vxvmconvert list display? The device indicates a physical disk, a disk with a name indicates if the disk is under VxVM control, a group shows the disk group name, and the status indicates if it is an LVM disk. If the status is online, that means VxVM acknowledges the disk but doesn’t have it under its control. Example vxprint output before conversion The list and listvg output is from within the vxvmconvert command. vxprint is a command line command.
52 Converting LVM to VxVM Examples v dg08lv1 fsgen ENABLED 102400 pl dg08lv1-01 dg08lv1 ENABLED 102400 sd dg0801-01 dg08lv1-01 ENABLED 102400 - ACTIVE ACTIVE - - The vxprint output provides the following information: ■ The disk group dg08 contains the VxVM disk dg0801 and the volume dg08lv1. The VxVM disk dg0801 is associated with disk device c0t8d0 and is 2080768 blocks in length.
Converting LVM to VxVM General information regarding conversion speed Warning: If the VxVM configuration has changed since the conversion you should NOT use this operation. Additional information is available on restoring configuration. See “Restoring the LVM volume group configuration” on page 33. More than one Volume Group or pattern may be entered at the prompt.
54 Converting LVM to VxVM Non-interactive conversion of volume groups The first and simple logical volume takes less time to convert than the striped volume. However, for the striped volume, 50 disks need to be checked. Also, the complexity of reproducing the VxVM commands to set up the striped volumes requires more VxVM commands to be generated to represent more smaller sub-disks representing the same amount of space.
Converting LVM to VxVM Non-interactive conversion of volume groups Analyzing volume groups for conversion The vxautoanalysis utility analyses one or more LVM volume groups, and reports on their suitability for conversion to VxVM disk groups. Only analysis of the suitability of the volume groups for conversion is performed. The actual conversion can be performed by using the vxautoconvert utility or the vxvmconvert utility.
56 Converting LVM to VxVM Non-interactive conversion of volume groups To convert volume groups to disk groups ◆ Run the vxautoconvert command: # /usr/sbin/vxautoconvert [-f] [vgname ...] The volume groups may be specified by their names or full pathnames. If no volume groups are specified, conversion of all volume groups on the system is attempted. If the value of the system tunable, nproc, is too low, the analysis will report that the conversion of the volume groups cannot be performed in parallel.
Chapter 3 Command differences This chapter includes the following topics: ■ About LVM and VxVM command differences ■ LVM and VxVM command equivalents ■ Comparison of LVM and VxVM tasks ■ Tasks with no direct LVM equivalents ■ Existing features in LVM not supported in VxVM About LVM and VxVM command differences This chapter describes the differences between LVM and VxVM commands, and tasks.
58 Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM lvchange Changes the characteristics of logical vxedit volumes. or Description/action Creates, removes, and modifies Volume Manager records. vxvol set There is no single equivalent LVM command. lvlnboot Creates root, primary and secondary swap and dump volumes. It also creates boot areas on the disk. lvcreate Creates a logical volume.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison (continued) LVM Description/action VxVM lvremove Removes one or more logical volumes vxedit from a volume group. vxassist Description/action Removes volumes with the -rf rm parameters. Example: vxedit -rf rm vol_name Removes a volume with the remove volume parameters. Example: vxassist remove volume vol_name lvsplit Splits a mirrored logical volume into two logical volumes.
60 Command differences LVM and VxVM command equivalents Table 3-1 Command comparison (continued) LVM Description/action VxVM Description/action pvcreate Makes a disk an LVM disk. vxdisksetup Brings a disk under VxVM control. Example: vxdisksetup c0t3d0 Option 1 in the vxdiskadm menu adds or initializes one or more disks. pvdisplay Displays information about physical volumes in a volume group. vxdisk list Lists information about VxVM disks.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison (continued) LVM Description/action VxVM Description/action vgdisplay Displays information on all volume groups. vxdg list Displays the contents of a disk group. vxprint Displays information about all objects or a subset of objects. vgchange Activates or deactivates one or more volume groups. vgextend Extends a volume group by adding one vxdiskadd or more disks to it. vxdiskadm Adds a disk to the disk group.
62 Command differences Comparison of LVM and VxVM tasks Table 3-1 Command comparison (continued) LVM Description/action VxVM Description/action lvchange, lvextend, lvcreate, lvreduce Performs operations on logical volumes. vxvol Operates on volume objects. No LVM command vxsd Operates on subdisk objects. No LVM command vxmend Fixes simple misconfigurations.
Command differences Comparison of LVM and VxVM tasks Table 3-2 63 LVM and VxVM task comparisons Task type Description Example LVM Create an LVM disk.
64 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example LVM Import and activate a volume group. vgimport -v /dev/vol_grp\ /dev/ dsk/disk_name vgchange -a y /dev/vol_grp VxVM Import a disk group to make the specified disk vxdg -tfC -n newname import group accessible on the local machine.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example LVM Extend a volume group by adding LVM disks to the volume group. vgextend /dev/vol_grp/\ /dev/dsk/disk_name VxVM Add one or more disks to the disk group. vxdiskadd disk_name Option 1 in the vxdiskadm main menu performs this task.
66 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example VxVM Mirroring the VxVM root disk. vxrootmir [-v] [-t tasktag] disk_access_name | disk_media_name LVM Create a logical volume in LVM volume group.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example VxVM Remove disks from a disk group. vxdisk rm disk_group vxdg rmdisk disk_name vxdg -g group_name rmdisk disk_name LVM Remove an entire volume group. vgremove /dev/vol_grp Before attempting to remove the volume group, you must remove the logical volumes using lvremove, and all physical volumes except the last one using vgreduce. VxVM Deport a disk group.
68 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example VxVM Remove mirrors or reduce the number of plexes/mirrors. vxplex -o rm dis plex_name vxedit -rf rm vol_name Remove a volume with the plexes associated with it. LVM Increase the number of mirror copies. lvextend -m 2 /dev/vol_grp/lvol_name VxVM Add mirrors to a volume or increase the number of plexes.
Command differences Tasks with no direct LVM equivalents Table 3-2 LVM and VxVM task comparisons (continued) Task type Description Example VxVM Resynchronize operations for the named vxrecover -s vol_name volumes, or for volumes residing on the named disks. If no medianame or volume operands are specified, then the operation applies to all volumes. LVM Start a volume. lvchange -a y /dev/vol_grp/lvol_name VxVM Start a volume. vxrecover -s vol_name vxvol start vol_name LVM Stop a volume.
70 Command differences Tasks with no direct LVM equivalents Table 3-3 Task descriptions Additional VxVM tasks with no LVM equivalents Examples Hot-relocation: in addition to using disks as hot spares, No action needed for hot relocation. the hot relocation facility can also use any available free To move hot-relocated subdisks back to the original disk: space in the disk group.
Command differences Existing features in LVM not supported in VxVM Table 3-3 Additional VxVM tasks with no LVM equivalents (continued) Task descriptions Examples Remove a log from a volume. vxassist remove log vol_name Move a subdisk. vxsd mv old_subdisk new_subdisk Join subdisks. vxsd join subdisk1 subdisk2 new_subdisk Existing features in LVM not supported in VxVM Some of the existing features in LVM are not supported in the current release of VxVM.
72 Command differences Existing features in LVM not supported in VxVM
Chapter 4 SMH and the VEA This chapter includes the following topics: ■ About SMH and the VEA ■ Displaying disk devices in SMH ■ Displaying volume groups and disk groups in SMH ■ Displaying logical volumes in SMH About SMH and the VEA This chapter describes the Veritas Enterprise Administrator (VEA) graphical user interface (GUI), and its relationship with the System Management Homepage (SMH). SMH and the VEA coexist as independent entities.
74 SMH and the VEA Displaying disk devices in SMH Displaying disk devices in SMH To display disk devices in SMH, select Tools > Disks and File Systems > Disks. The Disks tab of the HP-UX Disks and File Systems Tool screen lists the system’s disk devices. To switch between legacy device names and new agile device names, click on Toggle Global Device View. In the legacy view, all paths to a device are listed using the old-style c#t#d# naming convention that is used in the /dev/dsk and /dev/rdsk directories.
SMH and the VEA Displaying volume groups and disk groups in SMH Figure 4-1 Displaying disk devices in SMH Displaying volume groups and disk groups in SMH To display volume groups and disk groups in SMH, select Tools > Disks and File Systems > Volume Groups. The Volume Groups screen lists all the LVM volume groups and VxVM disk groups that are on the system.
76 SMH and the VEA Displaying logical volumes in SMH Figure 4-2 Displaying LVM volume groups and VxVM disk groups in SMH Displaying logical volumes in SMH To display logical volumes in SMH, select Tools > Disks and File Systems > Logical Volumes. The Logical Volumes screen lists the LVM logical volumes and VxVM volumes on the system. The “Type” column indicates whether a volume is controlled by LVM or VxVM. The “Use” column shows whether a volume is in use and if so, what it is used for.
SMH and the VEA Displaying logical volumes in SMH Figure 4-3 shows an example Logical Volumes screen. The LVM logical volumes in the vg00 volume group are being used for HFS and VxFS file systems and for swap and dump. The myvol1 and myvol2 VxVM volumes in the mydg disk group are being used for VxFS and HFS file systems. The remaining VxVM volume, myvol3, is not currently in use.
78 SMH and the VEA Displaying logical volumes in SMH
Appendix A Conversion error messages This appendix includes the following topics: ■ About conversion error messages About conversion error messages This appendix lists the error messages that you may encounter when conversting LVM volume groups to VxVM disk groups and volumes. For each error message, a description is provided of the problem, and the action that you can take to troubleshoot it. Table A-1 shows the error messages that you may encounter during conversion.
80 Conversion error messages About conversion error messages Table A-1 Conversion error messages (continued) Message Description Device device_name has the following bad blocks... Cannot convert LVM Volume Group Unlike LVM, VxVM does not support bad block revectoring at the physical volume level. If there appear to be any valid bad blocks in the bad block directory (BBDIR) of any disk used in an LVM volume group, the group cannot be converted.
Conversion error messages About conversion error messages Table A-1 Conversion error messages (continued) Message Description This Volume Group contains one or more logical volumes with mirrored data If you attempt to convert a Mirrored LVM Volume Group without a valid VxVM license installed, the conversion is not allowed. Install the required license before attempting the conversion.
82 Conversion error messages About conversion error messages Table A-1 Conversion error messages (continued) Message Description WARNING!: The LVM Volume Group name is too long for longvGname. VxVM will not allow such long name for VxVM Disk Group. Default VxVM Volume group will have only first 31 characters of LVM Volume Group name. If you convert an LVM volume group with more than 31 characters in the volume group name, VxVM will retain only the first 31 characters of the LVM volume group name.
Glossary block A unit of space for data on a disk, typically having a size of 1024-bytes. Dirty Region Logging Dirty Region Logging (DRL) is an optional property of a volume, used to provide a speedy recovery of mirrored volumes after a system failure. DRL keeps track of the regions that have changed due to I/O writes to a mirrored volume. file system The organization of files on storage devices.
84 Glossary private region A region of a physical disk used to store private, structured VxVM information. The private region contains a disk header, a table of contents, and a configuration database. The table of contents maps the contents of the disk. physical extent A set of physical disk blocks on a physical volume that forms a basic unit of access in LVM. This also forms the allocation unit for logical volumes. snapshot A temporary extra copy (plex/mirror) created in a volume.
Index A alternate links 67 B back up volume group 64 Backup vgcfgbackup 27 C coexistence VxVM and LVM disks 17 commands vxedit 58 configuration LVM 19 configuration VxVM 19 conversion errors 79 non-interactive 54 speed 53 vxvmconvert 21 D deactivate disk group 64 volume group 64 deport disk group 64 destroy disk group 64 disable mirror 70 disk evacuate 70 offline 70 online 70 recover\x09 70 rename 70 replace 70 disk group 63 rename 70 disk groups 9 disk headers 21 disks 9 coexistence 17 mirroring 65 di
86 Index Example analyze LVM groups 38 conversion 38 failed conversion 38 list 38 list disk information 38 list LVM volume group information 38 listvg 38 LVM to VxVM 38 vxprint output 38 example Failed Analysis 38 export volume group 64 extend volume group 65 F File System 28 file system 63 G GUI SMH 62, 73 VERITAS Volume Manager Storage Administrator 73 H Hot Relocation 62 I import disk group 64 volume group 64 increase disk group 64 swap 64 J join subdisk 71 L list LVM 38 Logical Volume 14–15 logi
Index Private Region 15 pvchange 60 pvcreate 60 pvdisplay 60 pvmove 60 tools vxdiskadm 19 vxvmconvert 19 troubleshoot errors 79 R V RAID-5 62 reduce 63 volume group 65 remove disk 66 volume 66 volume group 64, 67 rename disk group 70 repair mirror 70 restore volume group 64 resynchronize volumes 68 root disk configuring for VxVM 23 reconfiguring for LVM 23 root disks mirroring 65 rootability configuring a VxVM root disk 23 restoring a LVM root disk 23 root disk 23 root volume 23 Veritas Volume Manager
88 Index VxVM volumes resynchronize 68 vxvol 59, 62
