VERITAS Volume Manager 5.0 Migration Guide HP-UX 11i v2 First Edition Manufacturing Part Number: 5991-5513 September 2006 Printed in the United States © Copyright 2006 Hewlett-Packard Development Company L.P.
Legal Notices 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 Chapter 1 VxVM and LVM Introducing Veritas Volume Manager ........................................................................7 Notable features of VxVM .................................................................................8 VxVM and LVM—conceptual comparison .............................................................10 Coexistence of VxVM and LVM disks ....................................................................
6 Contents Listing disk devices in SAM .....................................................................................68 Listing volume groups and disk groups in SAM ......................................................69 Listing logical volumes in SAM ...............................................................................
Preface The VERITAS Volume Manager 5.0 Migration Guide provides information on the August 2006 release of the VERITAS Volume Manager. Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service.
• http://itrc.hp.com For technical support visit: • http://welcome.hp.com/country/us/en/support.html Typographic Conventions Table 1 describes the typographic conventions used in this document. Table 1 Typographic Conventions Typeface Usage Examples monospace Computer output, files, directories, software elements such as command options, function names, and parameters Read tunables from the /etc/vx/tunefstab file.
• VERITAS 5.0 Installation Guide • VERITAS File System 5.0 Release Notes • VERITAS File System 5.0 Administrator’s Guide • VERITAS Volume Manager 5.0 Release Notes • VERITAS Volume Manager 5.0 Adminstrator’s Guide • VERITAS Volume Manager 5.0 Troubleshooting Guide • VERITAS Enterprise Administrator (VEA 500 Series) Getting Started HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs.
Chapter 1 VxVM and LVM This chapter provides an overview of Veritas Volume Manager by Symantec (also referred to as VxVM) and its features. A brief description of the benefits of migrating from the HP-UX Logical Volume Manager (LVM) to VxVM, and the coexistence of VxVM disks with LVM disks is also given.
8 VxVM and LVM Introducing Veritas Volume Manager ServiceGuard products. Refer to the Release Notes for details about the required version number, as well as the availability of specific features in your release. Notable features of VxVM The Veritas Volume Manager provides many features, some of which are not available with LVM or MirrorDisk/UX. Notable VxVM features are described in the list below.
VxVM and LVM Introducing Veritas Volume Manager across multiple disks, and mirroring to provide redundancy of data. Striped mirror volumes are more tolerant of disk failure and have a shorter recovery time than mirrored stripe volumes. Refer to the Veritas Volume Manager Administrator’s Guide for more detailed information on these layouts.
10 VxVM and LVM VxVM and LVM—conceptual comparison VxVM and LVM—conceptual comparison The following section compares the terminology used in LVM and VxVM at a conceptual level. For more information, refer to the glossary of this Guide for precise and detailed definitions of these terms. Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term LVM VxVM Both LVM and VxVM enable online disk storage management. They both build virtual devices, called volumes, on physical disks.
VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term 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.
12 VxVM and LVM Coexistence of VxVM and LVM disks Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term Mirrors Mirrors (plexes) Both LVM and VxVM support mirrors. Mirrors can be used to store multiple copies of a volume’s data on separate disks. In LVM, you can create mirrors using the MirrorDisk/UX product. Mirrors allow duplicate copies of the extents to be kept on separate physical volumes. MirrorDisk/UX supports up to 3 copies of the data. A VxVM mirror consists of plexes.
VxVM and LVM Coexistence of VxVM and LVM disks administrative utilities (SAM and VEA) recognize and identify all disks on the system (see “SAM and the VEA” on page 67, for details). The vxvmconvert command is provided to enable LVM disks to be converted to a VxVM disk format without losing any data. For more information, see “Converting LVM to VxVM” on page 15.
14 VxVM and LVM Coexistence of VxVM and LVM disks
Chapter 2 Converting LVM to VxVM This chapter explains how to convert your LVM configuration to a VxVM configuration and presents the following main topics: ■ Converting unused LVM physical volumes to VxVM disks ■ Converting LVM volume groups to VxVM disk groups ■ Restoring the LVM volume group configuration ■ Examples The basic tools for conversion are the VxVM commands, vxvmconvert and vxdiskadm, and the LVM administrative utilities such as pvremove and vgcfgbackup.
16 Converting LVM to VxVM Converting unused LVM physical volumes to VxVM disks Converting unused LVM physical volumes to VxVM disks LVM disks which are not part of any volume group, and contain no user data, are simply cleaned up, so that there are no LVM disk headers. Then the disks are given over to VxVM through the normal means of initializing disks. Caution: Exercise caution while using this procedure to give disks over to VxVM.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Initializing disks for VxVM use To initialize the disk for VxVM use, use the vxdiskadm command, selecting the option: 1) Add or initialize one or more disks Or use the command: # vxdisk init disk_name VxVM utilities will not tamper with disks that are recognized as owned by LVM (by virtue of the LVM disk headers).
18 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Volume group conversion limitations There are certain LVM volume configurations that cannot be converted to VxVM. Some of the reasons a conversion could fail are: ■ A volume group with insufficient space for metadata. In the conversion of LVM to VxVM, the areas of the disks used to store LVM metadata are overwritten with VxVM metadata.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups For this release, a volume group containing the /usr file system cannot be converted because vxvmconvert needs access to files in /usr. ■ Volume groups with any dump or primary swap volumes. vxvmconvert will not convert any volume group with dump or primary swap volumes. These are volumes known to the boot process.
20 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Conversion process summary Several steps are used to convert LVM volume groups to VxVM disk groups. Most of these steps can be done with the vxvmconvert utility. All the steps are not compulsory, and some may have to be followed only if there are problems during conversion. Some of them (e.g. backing up user data) are left to you to accomplish through your regular administrative processes.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Conversion steps explained 1. Identifying LVM disks and volume groups for conversion The obvious first step in the conversion process is to identify what you want to convert. The native LVM administrative utilities like vgdisplay and SAM can help you identify candidate LVM volume groups as well as the disks that comprise them. You can also use the vxvmconvert and vxdisk commands to examine groups and their member disks.
22 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Sample examples of the analyze option are shown in “Examples” on page 31. 3. Taking actions to make conversion possible if analysis fails Analysis may fail for any of the reasons listed in the section “Volume group conversion limitations”. Messages from vxvmconvert will explain the type of failure and any actions that can be taken before retrying the analysis.
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 via the vxvmconvert program. With certain limitations, you can reinstate the LVM volumes after they have been converted to VxVM using this data (see “Example: displaying the vxvmconvert menu” on page 31).
24 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups This change in names can present problems. Any application that refers to specific device node names will be at risk when these names change. Similarly, any files that record specific device node names for use by applications can be problematic. The most obvious area where this problem arises is in /etc/fstab.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Over time, the ultimate goal should be that the underlying VxVM naming is used by all applications, and that there are no indirect references to those volumes. 6. Stopping application access to volumes in the volume group to be converted No applications can be active on the LVM volume group undergoing conversion. Before attempting to convert any volume group, you must ensure that applications using that group are down.
26 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Note: The LVM logical volumes to be converted must all be available to the vxvmconvert process. You should not deactivate the volume group or any logical volumes before running vxvmconvert. To activate a volume group If you are not certain if the LVM volumes or the corresponding volume groups are active, you can activate them with the following command: # vgchange -a y vol_grp_name 7.
Converting LVM to VxVM Restoring the LVM volume group configuration 10. Restarting applications on the new VxVM volumes Once the conversion to VxVM is complete, file systems can be mounted on the new devices and applications can be restarted. If you unmounted file systems before running vxvmconvert, you need to remount them by the new volume names. vxvmconvert will have updated /etc/fstab with the new names.
28 Converting LVM to VxVM Restoring the LVM volume group configuration 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 The name changes that vxvmconvert makes as part of the conversion are managed by rollback, and do not count as VxVM configuration changes for the purposes of choosing a restoration method. The vgrestore command should not be confused with the LVM command, vgcfgrestore. vgcfgrestore is used to restore the LVM configuration information saved by vgcfgbackup, but it will not restore your device files and/etc/fstab entries.
30 Converting LVM to VxVM Restoring the LVM volume group configuration Caution: Do not use this option unless you are certain that you want to restore LVM volume groups. Once this is run, the VxVM disks that were created as a result of the original conversion from LVM to VxVM no longer exists. This option is not a full complement to vxvmconvert. It simply writes the saved LVM metadata back on top of the disks.
Converting LVM to VxVM Examples Examples Example: displaying the vxvmconvert menu To display the vxvmconvert menu, use the following command: # vxvmconvert The following menu is displayed: Volume Manager Support Operations Menu: Volume Manager/LVM_Conversion 1 2 3 list listvg ? ?? q Analyze LVM Volume Groups for Conversion Convert LVM Volume Groups to VxVM 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 f
32 Converting LVM to VxVM Examples Example: listing LVM volume group information To list LVM volume group information, use the listvg option of vxvmconvert. Select the listvg option from the vxvmconvert Main Menu: Menu: Volume Manager/LVM_Conversion/ListLVMVolumeGroups # listvg Use this menu option to display a list of LVM volume groups. You can also choose to list detailed information about the LVM volume groups at a specific disk device address. Select the Volume Group as follows: Enter Volume Group (i.
Converting LVM to VxVM Examples LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/vg08/lvol2 available/syncd 500 125 125 1 --- Physical volumes --PV Name PV Status Total PE Free PE /dev/dsk/c0t8d0 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.
34 Converting LVM to VxVM Examples listvg: list all LVM Volume Groups list: list all disk devices vg_name:a single LVM Volume Group, named vg_name :for example vg08 vg09 vg05 Select volume groups to analyze: [,all,list,listvg,q,?] vg08 Name a new disk group [,list,q,?] (default: dg08) Each volume group will be analyzed one at a time.
Converting LVM to VxVM Examples Use this operation to analyze one or more LVM volume groups for possible conversion using the VxVM Volume Manager. This operation checks for problems that would prevent the conversion from completing successfully. It calculates the space required to add the volume groups disks to a Volume Manager disk group, and to replace any existing partitions and volumes with Volume Manager volumes, plexes, and sub-disks.
36 Converting LVM to VxVM Examples the (vg08) Volume Group, and allowing that for every volume removed, the number of Database records required would be reduced by three. This is only a rough approximation, however. Hit RETURN to continue.
Converting LVM to VxVM Examples Select Volume Groups to convert : [,all,list,listvg,q,?] vg08 vg08 Convert this Volume Group? [y,n,q,?] (default: y) Name a new disk group [,list,q,?] (default: dg08) The following disk has been found in the vg08 volume group and will be configured for conversion to a VxVM disk group. c4t8d0 A new disk group dg08 will be created and the disk device c4t8d0 will be converted and added to the disk group with the disk name dg0801.
38 Converting LVM to VxVM Examples /dev/vg08/rlv2 will convert to /dev/vx/rdsk/vg08dg/dg08lv2 LVM Volume Group vg08 Records Saved Unmounting vg08 file systems Volume group "/dev/vg08" has been successfully changed. The Volume Manager is now reconfiguring (partition phase)... Volume Manager: Initializing c4t8d0 as a converted LVM disk. The system reconfiguration will now be done without rebooting. The Volume Manager is now reconfiguring (initialization phase)...
Converting LVM to VxVM Examples :for example vg08 vg09 vg05 Select Volume Groups to convert : [,all,list,listvg,q,?] listvg LVM VOLUME GROUP INFORMATION NAME TYPE PHYSICAL VOLUME vg00 ROOT c4t6d0 vg05 Non-Root c4t5d0 vg03 Non-Root c4t3d0 c4t2d0 vg08 Non-Root c4t8d0 Select Volume Groups to convert : [,all,list,listvg,q,?] vg08 vg08 Convert this Volume Group? [y,n,q,?] (default: y) Name a new disk group [,list,q,?] (default: dg08) The following disk has been found
40 Converting LVM to VxVM Examples 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. This would roughly translate to needing an additional 896 bytes available in the private space.
Converting LVM to VxVM Examples Example vxprint output before conversion TY NAME dg rootdg dm disk01 ASSOC rootdg c0t10d0 KSTATE - LENGTH PLOFFS 2079468 - STATE - TUTIL0 - PUTIL0 - The list and listvg output is from within the vxvmconvert command. vxprint is a command line command.
42 Converting LVM to VxVM Examples started, and the plex is enabled. Operations to the volume such as recovery and data access will be governed by the usage type fsgen. ■ The plex dg08lv1-01 is associated with volume dg08lv1, and maps the entire address range of the volume. Associated with the plex is one subdisk, dg0801-01 which maps the plex address range from 0 to the entire length of the plex, i.e. 102400 blocks.
Converting LVM to VxVM General information regarding conversion speed Selected Volume Groups have been restored. Hit RETURN to continue. Rollback other LVM Volume Groups? [y,n,q,?] (default: n) General information regarding conversion speed The speed of the process of converting an existing LVM volume group to a similar VxVM disk group is largely dependent upon the size of the volume group being converted, as well as on the complexity of the volumes within that volume group.
44 Converting LVM to VxVM General information regarding conversion speed Note: If you convert mirrored volumes, you must synchronize them in a separate step.
Chapter 3 Command differences This chapter describes the differences between LVM and VxVM commands, and tasks. It includes a task comparison chart which lists some of the tasks performed using LVM with a near equivalent task performed using VxVM. It also provides a list of VxVM tasks which are not available with LVM, and the LVM features currently not supported in VxVM.
Command differences LVM and VxVM command equivalents LVM and VxVM command equivalents The table below lists the LVM commands and a near equivalent command to use in VxVM. For more information, refer to the Task Comparison chart. For information on VxVM commands, refer to the Veritas Volume Manager documentation package. Table 3-1 Command comparison LVM Description/action VxVM Description/action lvchange Changes the characteristics of logical volumes.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action lvreduce Decreases disk space allocated to a logical volume. vxassist Decreases a volume in size with the shrinkto or shrinkby parameters. Example: vxassist shrinkto vol_name 200M Make sure you shrink the file system before shrinking the volume. lvremove Removes one or more logical volumes from a volume group. vxedit Removes volumes with the -rf rm parameters.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action lvsync Synchronizes mirrors that are stale in one or more logical volumes. vxrecover The vxrecover command performs resynchronize operations for the volumes, or for volumes residing on the named disks (medianame or the VxVM name for the disk). vxvol start Example: vxrecover vol_name media_name pvcreate Makes a disk an LVM disk.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action pvremove Removes the LVM header information and releases the disk from LVM control. vxdiskunsetu p Removes the VxVM header information and releases the disk from VxVM control. vgcreate Creates a volume group. vxdiskadd Creates a new disk group and/or adds disks to a disk group. vxdg init vgdisplay Displays information on all volume groups.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action vgsync Synchronizes mirrors that are stale in one or more logical volumes. vxrecover Starts resynchronization and recovery of volumes. vgremove Removes the definition vxdg deport of a volume group from the system. vxdiskadm vgexport vgimport lvchange, lvextend, lvcreate, lvreduce Removes a volume group from the system. Deports a disk group from the system.
Command differences Comparison of LVM and VxVM tasks Comparison of LVM and VxVM tasks This section contains a list of tasks which you can perform using LVM, and near equivalent tasks which you can perform using Veritas Volume Manager. You can perform the LVM tasks by using SAM or the command line interface. Similarly, you can choose to perform VxVM tasks by using the Veritas Enterprise Administrator (VEA) or the command line interface. This document focuses on the command line interface.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example VxVM Create a disk group. vxdg init disk_group disk_name Option 1 in the vxdiskadm menu performs this task. LVM Add a new disk to the existing volume group. vgextend /dev/vol_grp /dev/rdsk/ disk_name VxVM Add a disk to an existing disk group.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Extend a logical volume or increase space allocated to a logical volume. lvextend -l 50 /dev/vol_grp/ lvol_name l—indicates the number of logical extents in the logical volume VxVM Increase the volume by or to a given length.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Export and deactivate an LVM volume group, and its associated logical volumes. vgchange -a n vol_group vgexport /dev/vol_group VxVM Deport a disk group to disable access to vxdg deport disk_group the specified disk group. A disk group cannot be deported if any volumes in Option 9 in the vxdiskadm menu performs the disk group are currently open. this task.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Extend a volume group by adding LVM vgextend /dev/vol_grp/\ /dev/dsk/ disks to the volume group. 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.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Create a logical volume in LVM volume group. lvcreate -L vol_size /dev/vol_grp VxVM Create a volume of one of these layout types: A concatenated volume vxassist make vol_name length A striped mirror volume vxassist make vol_name length layout=mirror, stripe A RAID-5 volume vxassist make vol_name length layout=raid5 LVM Display information about logical volumes.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Display information about volume groups. vgdisplay -v /dev/vol_grp VxVM Display disk group information. vxdisk list Display information about a specific disk group. vxprint -g disk_group vxdg list vxdisk list disk_group LVM Display information about physical volumes. pvdisplay /dev/dsk/disk_name VxVM Display information about Volume Manager volumes.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description LVM Set up alternate links to a physical volume. If a disk has two controllers, you can make one primary and the other an alternate link.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Increase the number of mirror copies. lvextend -m 2 /dev/vol_grp/ lvol_name VxVM Add mirrors to a volume or increase the vxassist mirror vol_name number of plexes. LVM Convert a mirrored logical volume into two logical volumes. Split a logical volume. lvsplit -s backup /dev/vol_grp/ lvol_name VxVM Snapshot a volume and create a new volume.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example VxVM Resynchronize operations for the named volumes, or for volumes residing on the named disks. vxrecover -s vol_name 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.
Command differences Tasks with no direct LVM equivalents Tasks with no direct LVM equivalents The following table lists tasks which have no direct LVM equivalent. Most of these tasks can be performed either with the Veritas Enterprise Administrator (VEA) GUI, or the command line interface. For more information, refer to the Veritas Enterprise Administrator User’s Guide and the Veritas Volume Manager Administrator’s Guide.
Command differences Tasks with no direct LVM equivalents Table 3-3 Additional VxVM tasks with no LVM equivalents Task description Example Recover a volume. vxrecover -g disk_group volume medianame vxmend fix clean plex_name Repair a mirror vxplex att plex_name Disable a mirror vxplex det plex_name Remove a log from a volume. vxassist remove log vol_name Move a subdisk.
Command differences Existing Features in LVM not supported in VxVM Existing Features in LVM not supported in VxVM Some of the existing features in LVM are not supported in the current release of VxVM. Given below is a table with the unsupported LVM features, and possible workarounds in VxVM. Table 3-4 LVM features and VxVM equivalents LVM Feature VxVM Equivalent Physical volume groups VxVM has no equivalent feature.
Command differences Existing Features in LVM not supported in VxVM
Chapter 4 SAM and the VEA This chapter describes the Veritas Enterprise Administrator (VEA) graphical user interface (GUI), and its relationship with the LVM GUI, and the System Administration Manager (SAM). The following topics are discussed in this chapter: ■ Listing disk devices in SAM ■ Listing volume groups and disk groups in SAM ■ Listing logical volumes in SAM SAM and the VEA coexist as independent entities. The VEA recognizes and labels LVM volumes and disks, but does not manage them.
SAM and the VEA Listing disk devices in SAM Listing disk devices in SAM To list disk devices in SAM, from the Disks and File Systems SAM area, select Disk Devices. The Disk Devices screen lists the system’s disk devices. When VxVM is installed on the system, SAM includes a “Use” column to indicate whether a disk is under LVM or VxVM control, or whether it is unused. If a VxVM disk is online and part of a disk group, the disk group name is listed under the “Volume Group” column.
SAM and the VEA Listing volume groups and disk groups in SAM Listing volume groups and disk groups in SAM To list volume groups and disk groups in SAM, from the Disks and File Systems SAM area, select Volume Groups. The Volume Groups screen lists the LVM volume groups and the VxVM disk groups on the system. Figure 4-2 shows an example Volume Groups screen. vg00 is an LVM volume group with eight logical volumes; rootdg and maroon are VxVM disk groups, with one volume each.
SAM and the VEA Listing logical volumes in SAM Listing logical volumes in SAM To list logical volumes in SAM, from the Disks and File Systems SAM area, select Logical Volumes. The Logical Volumes screen lists the LVM logical volumes and the 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. Figure 4-3 shows an example Logical Volumes screen.
Appendix A 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.
Conversion error messages Table A-1 Conversion error messages 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 Table A-1 Conversion error messages 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. Too many LVM Volumes to convert in this LVM Volume Group If there is insufficient private space, the conversion is not allowed to continue.
Conversion error messages
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.
Glossary A disk that has been initialized by LVM becomes known as a physical volume. public region A region of a physical disk managed by VxVM that contains available space and is used for allocating subdisks. 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.
Index A alternate links 61 B back up volume group 57 Backup vgcfgbackup 22 C coexistence VxVM and LVM disks 13 commands vxedit 48 configuration LVM 15 configuration VxVM 15 conversion errors 71 speed 44 vxvmconvert 17 D deactivate disk group 57 volume group 57 deport disk group 57 destroy disk group 57 disable mirror 65 disk evacuate 64 offline 64 online 64 recover 64 rename 64 replace 64 disk group 55 rename 64 disk groups 7 disk headers 17 disks 7 coexistence 13 mirroring 58 display disk group 59 DMP
Index analyze LVM groups 32 conversion 32 failed coversion 32 list 32 list disk information 32 list LVM volume group information 32 listvg 32 VLM to VxVM 32 vxprint output 32 example Failed Analysis 32 export volume group 57 extend volume group 58 F File System 23 file system 56 convert 62 split 62 synchronize 62 Logical Volume Manager 7 lvchange 48 lvcreate 48 lvextend 48 lvlnboot 48 LVM 7 metadata 18 LVM metadata 12 LVM names symbolic names 25 LVM VGRA 17 lvmerge 49 lvreduce 49 lvremove 49 lvsplit 4
Index P physical volumes 10, 11, 12 Private Region 12 pvchange 50 pvcreate 50 pvdisplay 50 pvmove 51 R RAID-5 54 reduce 56 volume group 58 remove disk 60 volume 60 volume group 57, 60 rename disk group 64 repair mirror 65 restore volume group 57 resynchronize volumes 62 root disk configuring for VxVM 18 reconfiguring for LVM 18 root disks mirroring 58 rootability configuring a VxVM root disk 18 restoring a LVM root disk 18 root disk 18 root volume 18 S SAM 54 vgdisplay 21 split subdisk 65 subdisk join 65
Index symbolic link 25 VxVM volumes resynchronize 62 vxvol 50, 53
