<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Transitional//EN">
<HTML>
<HEAD>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

      For third-party license citations, please see the bottom of this file.
    *************************************************************************************
  -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="TEMPLATEBASE" content="vx_vxhelp_2005c">
<meta name="LASTUPDATED" content="06/13/05 10:25:30">
<meta name="PRODUCTNAME" content="VERITAS Software Documentation">
<meta name="FILENAME" content="02_convertLVM.fm">
     
<title>Conversion Steps Explained</title>

</HEAD>

<BODY bgcolor="#FFFFFF" link="#000066" vlink="#0000ff" marginheight="0" topmargin="0">
<basefont=1>

<a name="107570"></a>

<div align="left">
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
   <td height="2" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#000000">
   </td>
 </tr>
 <tr>
   <td height="15" width="50%" border="0" cellspacing="0" cellpadding="0" bgcolor="#cccccc">
    <img src="images/vxsymbol.gif" height="20" width="31" border="0" cellspacing="0" cellpadding="0" align="left">
     
     
   </td>
   <td align="right" width="50%" bgcolor="#cccccc">

<!-- Header Breadcrumbs -->
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="02_convertLVM_vxvm222_107549.html" title="Previous - Conversion Process Summary">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="02_convertLVM_vxvm224_107742.html" title="Next - Restoring the LVM Volume Group Configuration">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
   </td>
 </tr>

 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vxvm_splashpage_docCD_vxvm1_103036.vxhd" title="Volume Manager Guides title page ">Volume Manager Guides</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>
 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="mig_titlepage_docCD_vxvm207_73700.vxhd" title="Volume Manager 4.1 Migration Manager title page ">Volume Manager 4.1 Migration Manager</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>


</table>
</div>

<div align="left">
 <table border="0" width="100%" bgcolor="#FFFFFF">
  <tr>
   <td width="100%" valign="top" bgcolor="#FFFFFF">

<!-- Start Main Topic Content -->
        <a name="startcontent"></a>
	
<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="107570"></a> Conversion Steps Explained</font>
</h2>

        



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107573"></a>1. Identifying LVM disks and volume groups for conversion</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107574"></a>The obvious first step in the conversion process is to identify what you want to convert. The native LVM administrative utilities like <font face="Courier New, Courier, sansserif, sans serif" size="2">vgdisplay</font> and SAM can help you identify candidate LVM volume groups as well as the disks that comprise them.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107576"></a>You can also use the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">vxdisk</font> commands to examine groups and their member disks. The information presented through the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">vxdisk</font> utilities and their interpretation is shown in <a href="02_convertLVM_vxvm225_107799.html#107799">Examples</a>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107580"></a>You can also list the LVM disks with the following VxVM command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107581"></a>#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vxdisk&nbsp;list</b></font>
</font>



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107583"></a>2. Analyzing an LVM volume group to see if conversion is possible</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107584"></a>After you have selected a volume group for conversion, you need to analyze it to determine if conversion for VxVM use is possible.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107585"></a>Use the analyze option of <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> to check for problems that would prevent the conversion from completing successfully. This option checks for all the conditions listed in <a href="02_convertLVM_vxvm221_107514.html#107523">Volume Group Conversion Limitations</a>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107589"></a>The analysis calculates the space required to add the volume group disks to a VxVM disk group, and to replace any existing disks and volumes with VxVM volumes, plexes, and subdisks. If you don't have the required space to convert the disks, the conversion would fail. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107590"></a>Analysis can be run on a live system while users are accessing their data. To analyze LVM volume groups, choose option 1 of the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> utility.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107591"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">The analysis option is presented as a separate menu item in <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>, but there is an implicit analysis with any conversion. If you simply select the &quot;Convert LVM Volume Groups to VxVM&quot; menu option, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will go through analysis on any group you specify. When you are using the convert option directly, you are given a chance to abort the conversion after analysis, and before any changes are committed to disk. For more information, see <a href="02_convertLVM_vxvm221_107514.html#107514">Converting LVM Volume Groups to VxVM Disk Groups</a>. <br><br>The analysis option is useful when you have a large number of groups/disks for conversion and some amount of planning is needed before the actual conversion. Installations with many users or critical applications can use the analyze option on a running system. Then conversion downtime can be better planned and managed. Smaller configurations may be better served by using the convert option directly while in a downtime period.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107598"></a>Sample examples of the analyze option are shown in <a href="02_convertLVM_vxvm225_107799.html#107799">Examples</a>.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107599"></a>3. Taking actions to make conversion possible if analysis fails</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107602"></a>Analysis may fail for any of the reasons listed in the section <a href="02_convertLVM_vxvm221_107514.html#107523">&quot;Volume Group Conversion Limitations</a>&quot;.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107604"></a>Messages from <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will explain the type of failure and any actions that can be taken before retrying the analysis. Refer to <a href="0A_errmsgs_vxvm238_73059.html#73059">Conversion Error Messages</a> for complete details of specific error messages and actions.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107609"></a>4. Backing up your LVM configuration and user data</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107610"></a>After analysis you know which volume group or groups you want to convert to VxVM disk groups. Up to this point, you have not altered your LVM configuration. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107611"></a>By taking the next step (completing the conversion to VxVM), you are significantly changing access to your storage. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107612"></a>Although the conversion process does not move, or in any other way affect user data, you are strongly encouraged to back up all data on the affected disks. Similarly, you should back up the LVM configuration itself. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107613"></a>During a conversion, any spurious reboots, power outages, hardware errors or operating system bugs can have unpredictable and undesirable consequences. You are advised to be on guard against disaster with a set of verified backups.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107615"></a>Backing up an LVM configuration</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107616"></a>Use the <font face="Courier New, Courier, sansserif, sans serif" size="2">vgcfgbackup</font>(1M) utility before running <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> to save a copy of the LVM configuration.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107617"></a>You can back up the LVM volumes using the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107618"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">#&nbsp;</font><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vgcfgbackup&nbsp;-f&nbsp;</b></font><em>pathname</em><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>/</b></font><em>filename</em><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;</b></font><em>vol_grp_name</em>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107619"></a>Be sure to use the <font face="Courier New, Courier, sansserif, sans serif" size="2">-f</font> option to save the data into a file other than the default. <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> uses LVM utilities which themselves save the configuration using <font face="Courier New, Courier, sansserif, sans serif" size="2">vgcfgbackup</font>. If you do not use the <font face="Courier New, Courier, sansserif, sans serif" size="2">-f</font> option when you attempt to backup the configuration, the conversion process will overwrite your attempted backup.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107620"></a>A copy of this LVM configuration should be kept off-line on tape or some other medium for use in the event of a disaster during conversion. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107621"></a>For example, to put a copy on tape, use the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107622"></a>#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>tar&nbsp;cvf&nbsp;/dev/rmt/c3t0d0BEST&nbsp;/vgbackups/vg08</b></font>&nbsp;
</font>
<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107623"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">The <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> 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 <font face="Courier New, Courier, sansserif, sans serif" size="2">vgcfgbackup</font>. It can only be used via the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> program. With certain limitations, you can reinstate the LVM volumes after they have been converted to VxVM using this data (see <a href="02_convertLVM_vxvm225_107799.html#107808">Example: displaying the vxvmconvert menu</a>). Even though <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> provides this level of backup of the LVM configuration, you are advised to use <font face="Courier New, Courier, sansserif, sans serif" size="2">vgcfgbackup</font> before running <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>.
</font>
<hr noshade size="2" width="100%" color="#000000">
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107627"></a><b>Backing up user data</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107628"></a>To back up user data, use your regular backup processes. </font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/caution.gif" alt="Caution " height="16" width="16">&nbsp;<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107631"></a><b>Caution  &nbsp;&nbsp;</b></font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000"> Before you do the backup, you should carefully review &quot;step <a href="02_convertLVM_vxvm223_107570.html#107710">9. Implementing changes for new VxVM logical volume names</a>.&quot; Backup processes and systems themselves may have dependencies on the volume names currently in use on your system. The conversion to VxVM changes those names. You are advised to understand the implications name changes have for restoring from the backups you are about to make. </font>
<hr noshade size="2" width="100%" color="#000000">
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107634"></a><b>File system back up of user data</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107635"></a>You can use the backup utility that you normally use to back up data on your logical volumes. For example, to back up logical volumes that contain file systems, the <font face="Courier New, Courier, sansserif, sans serif" size="2">fbackup</font>(1M) command can be used to back up the data to tape.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107636"></a>For example, to backup the data on <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vg01/lvol3 </font>mounted on<font face="Courier New, Courier, sansserif, sans serif" size="2"> /foodir</font>, use the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107637"></a>#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>fbackup&nbsp;-0i&nbsp;/foodir&nbsp;-f&nbsp;/dev/rmt/c0t0d0BEST</b></font>
</font>
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107638"></a><b>Non-file system back up</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107639"></a>If a logical volume you are converting does not contain a file system, and is being used directly by an application (such as a database application), use the backup facilities provided by the application. If no such facility exists, consider using the <font face="Courier New, Courier, sansserif, sans serif" size="2">dd</font> command.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107641"></a>5. Planning for new VxVM logical volume names </font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107642"></a>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 <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev</font> under directories named for the volume group. VxVM creates its device nodes in <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vx/dsk</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vx/rdsk</font>. When conversion is complete, the old LVM device nodes are gone from the system, and the system will access data on the device nodes in <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vx</font>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107643"></a>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.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107644"></a>The most obvious area where this problem arises is in <font face="Courier New, Courier, sansserif, sans serif" size="2">/etc/fstab</font>. To handle this problem, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will rewrite the <font face="Courier New, Courier, sansserif, sans serif" size="2">fstab</font> with the new VxVM names when conversion is done so that <font face="Courier New, Courier, sansserif, sans serif" size="2">fsck</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font>, and related utilities will behave as they did prior to the conversion.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107645"></a>There are potentially many other applications, though, that may be put at risk by the name changes in conversion. <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> cannot help with these. The system administrator must examine the mechanisms used in each of the following areas to see if they reference LVM device names:</font>
</p>

<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107646"></a>Databases run on raw logical devices may record the name of that device node.</font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107647"></a>Backup systems may do device level backups based on device node names recorded in private files. Also labeling of the backups may record device names.</font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107648"></a>Scripts run by cron(1M).</font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107649"></a>Other administrative scripts.</font>
</li>
</ul>
</p>
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107650"></a><b>A Workaround</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107652"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> records a mapping between the names of the LVM device nodes and VxVM device nodes. This data can be used to create symbolic links from the old LVM volume to the new VxVM device names. The mapping is recorded in the file:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107653"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">/etc/vx/reconfig.d/vgrecords</font>/<em>vol_grp_name</em>/<em>vol_grp_name</em>.<font face="Courier New, Courier, sansserif, sans serif" size="2">trans</font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107654"></a>This file provides information on how to proceed further to link the old LVM volume names to the new VxVM device names. </font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/caution.gif" alt="Caution " height="16" width="16">&nbsp;<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107655"></a><b>Caution  &nbsp;&nbsp;</b></font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000"> This method of resolving the naming problem has risks. The symbolic links can become <em>stale</em>. For example, if a database refers to <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vx/rdsk/vol1</font> through a symbolic link <font face="Courier New, Courier, sansserif, sans serif" size="2">/dev/vg00/rvol1(</font>&quot;the old LVM name)&quot;, and if the underlying VxVM volume configuration is changed in any way, the database could refer to a missing or different volume.</font>
<hr noshade size="2" width="100%" color="#000000">
<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107657"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">You may want to use this symbolic link approach to ease the transition to VxVM. You can set up the symbolic links after the successful conversion to VxVM. Then, you can do the investigation on a case by case basis for each volume. Once you are satisfied that there are no problems introduced by the name change, the symbolic link to that volume can be removed. You must be careful to maintain a static VxVM volume configuration during this transition period.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107658"></a>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.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107659"></a>6. Stopping application access to volumes in the volume group to be converted</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107660"></a>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. This involves stopping databases, unmounting file systems, etc. </font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107661"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">If you are converting a volume with swap space on it, the conversion requires a reboot. The swap space cannot be taken out of control of the operating system with a shutdown to single user mode.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107665"></a>As described in <a href="02_convertLVM_vxvm223_107570.html#107670">Conversion and Reboot</a>, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> tries to unmount mounted file systems during the conversion. Bear in mind though, that <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> makes no attempt to close down running applications on those file systems, nor does it attempt to deal with applications (e.g., databases) running on raw LVM volumes.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107666"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">It is strongly recommended that you do not rely on <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>'s mechanisms for unmounting file systems. Conversion will be simpler if you close applications, and unmount file systems before running <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107667"></a>To unmount a file system, use the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107668"></a>#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>umount&nbsp;</b></font><em>file-system</em>
</font>
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107670"></a><b>Conversion and Reboot</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107671"></a>During conversion, after the analysis phase is complete, the disks to be converted are deemed to be <em>conversion ready</em>. The <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> program asks if you are ready to commit to the conversion changes. If you choose to complete the conversion, the system will try to unmount all of the associated mounted file systems, stop and export the volume group, and then install the VxVM configuration.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107672"></a>If <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> is unable to stop and export volume groups or unmount file systems, the conversion cannot be completed without rebooting the system. You will have the option of aborting the conversion or completing the conversion by rebooting the system. If you choose to reboot, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will trigger the completion of the conversion automatically, during reboot, when it can be guaranteed that no processes have access to the volumes that are being converted.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107673"></a>If you choose to abort rather than reboot to complete the conversion, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will return to the main menu.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107674"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">The LVM logical volumes to be converted must all be available to the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> process. You should not deactivate the volume group or any logical volumes before running <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>.
</font>
<hr noshade size="2" width="100%" color="#000000">
<br>
<p>
<font face="Font_SingleByte;" size="2"><a name="107675"></a><b>To Activate a Volume Group</b></font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107676"></a>If you are not certain if the LVM volumes or the corresponding volume groups are active, you can activate them with the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="107677"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">#&nbsp;</font><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vgchange&nbsp;-a&nbsp;y&nbsp;</b></font><em>vol_grp_name</em>
</font>



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107679"></a>7. Converting a volume group</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107680"></a>To do the actual conversion of LVM volume groups to VxVM disk groups, choose option 2 of the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> utility. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107681"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will prompt for a name for the VxVM disk group that will be created to replace the LVM volume group you are converting. This is the only object naming that is done through <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>. For details on modifying VxVM volume names, see &quot;step <a href="02_convertLVM_vxvm223_107570.html#107722">11. Tailoring your VxVM configuration</a>,&quot; on <a href="02_convertLVM_vxvm223_107570.html#107722"> </a>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107690"></a>As described earlier in &quot;step <a href="02_convertLVM_vxvm223_107570.html#107583">2. Analyzing an LVM volume group to see if conversion is possible</a>,&quot; on <a href="02_convertLVM_vxvm223_107570.html#107583"> </a>, the volume groups selected for conversion are analyzed to ensure that conversion is possible. After a successful analysis phase, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert </font>will ask you to commit to the change or abort the conversion. When you select to commit to conversion, the new VxVM metadata is written.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107695"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">It is good practice to convert one volume group at a time to avoid errors during conversion.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107699"></a>The details of the conversion process are shown in <a href="02_convertLVM_vxvm225_107799.html#107799">Examples</a>.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107700"></a>8. Taking actions if conversion fails</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107703"></a>Conversion can fail for any of the reasons detailed in the <a href="02_convertLVM_vxvm221_107514.html#107523">&quot;Volume Group Conversion Limitations</a>&quot; section. Messages from <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will explain the type of failure, and any actions you can take before retrying the conversion.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107708"></a>See <a href="0A_errmsgs_vxvm238_73059.html#73059">Conversion Error Messages</a> for complete details of specific error messages.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107710"></a>9. Implementing changes for new VxVM logical volume names</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107711"></a>You must be sure that all applications and configuration files refer properly to the new VxVM logical volumes. See &quot;step <a href="02_convertLVM_vxvm223_107570.html#107641">5. Planning for new VxVM logical volume names</a> on <a href="02_convertLVM_vxvm223_107570.html#107641"> </a>&quot; for details.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107718"></a>10. Restarting applications on the new VxVM volumes</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107719"></a>Once the conversion to VxVM is complete, file systems can be mounted on the new devices and applications can be restarted.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107720"></a>If you unmounted file systems before running <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font>, you need to remount them by the new volume names. <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> will have updated <font face="Courier New, Courier, sansserif, sans serif" size="2">/etc/fstab</font> with the new names. When you started <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert,</font> you may have left file systems mounted that are associated with the volumes you converted. <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> remounts these with the new VxVM volume names.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="107722"></a>11. Tailoring your VxVM configuration</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107723"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> 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. By default, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> renames the LVM volume group by replacing the prefix <font face="Courier New, Courier, sansserif, sans serif" size="2">vg</font> in the volume group name with the prefix <font face="Courier New, Courier, sansserif, sans serif" size="2">dg</font>. For example, <font face="Courier New, Courier, sansserif, sans serif" size="2">vg08</font> would become <font face="Courier New, Courier, sansserif, sans serif" size="2">dg08</font>. If there is no <font face="Courier New, Courier, sansserif, sans serif" size="2">vg</font> in the LVM volume group name, <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> simply uses the same volume group name for its disk group.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107724"></a>The disks in the new VxVM disk group are given VxVM disk media names (see <font face="Courier New, Courier, sansserif, sans serif" size="2">vxintro</font>(1M)) based on this disk group name. If your new VxVM disk group is <font face="Courier New, Courier, sansserif, sans serif" size="2">dg08</font>, it will have VxVM disks with names like <font face="Courier New, Courier, sansserif, sans serif" size="2">dg0801, dg0802</font>, etc. The VxVM plexes within the logical volumes will be <font face="Courier New, Courier, sansserif, sans serif" size="2">dg0801-01, dg0801-02</font>, etc.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="107725"></a>If you do not like the default object names generated by the conversion, use the standard VxVM utilities to rename these objects. See the rename option in the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxedit</font>(1M) man page for more details on renaming the disk groups.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="107726"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">You must only rename objects in the VxVM configuration after you are fully satisfied with that configuration. In particular, you should never use menu option 3 of <font face="Courier New, Courier, sansserif, sans serif" size="2">vxvmconvert</font> (Roll back) after name changes. If you have chosen to set up symbolic links to the VxVM volumes as described in &quot;step <a href="02_convertLVM_vxvm223_107570.html#107641">5. Planning for new VxVM logical volume names</a>,&quot; avoid renaming VxVM objects. These symbolic links are made invalid if the underlying VxVM device node name changes.
</font>
<hr noshade size="2" width="100%" color="#000000">

<!-- End Main Topic Content -->

   </td>
  </tr>
 </table>
</div>

<div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
  <td height="18" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
  </td>
 </tr>
  <td align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&nbsp;&#94;&nbsp;<a href="02_convertLVM_vxvm223_107570.html" title="Conversion Steps Explained">Return to Top</a></font>

  </td>
  <td align="right"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="02_convertLVM_vxvm222_107549.html" title="Previous - Conversion Process Summary">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="02_convertLVM_vxvm224_107742.html" title="Next - Restoring the LVM Volume Group Configuration">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
  </td>
 <tr>
   <td height="9" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
   </td>
 </tr>

<!-- Footer Breadcrumbs -->
<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vxvm_splashpage_docCD_vxvm1_103036.vxhd" title="Volume Manager Guides title page ">Volume Manager Guides</a>&nbsp;&nbsp;</font></td>
</tr>

<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="mig_titlepage_docCD_vxvm207_73700.vxhd" title="Volume Manager 4.1 Migration Manager title page ">Volume Manager 4.1 Migration Manager</a>&nbsp;&nbsp;</font></td>
</tr>


 <tr>
  <td colspan="2" align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" color="#000000" align="right" size="-2">
<em>VERITAS Software Corporation
</em></font><br>

<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">www.veritas.com</font><br>
  </td>
 </tr>
</table>
</div>

</BODY>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

    VERITAS, VERITAS SOFTWARE, the VERITAS Logo, and VERITAS Software Documentation 
    are trademarks or registered trademarks of VERITAS Software Corporation 
    or its affiliates in the U.S. and other countries. Other names may be 
    trademarks of their respective owners. 

    Apache Jakarta Lucene:
    Apache Software License
    Version 1.1

    Copyright (c) 2000 The Apache Software Foundation. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, 
    are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, this 
    list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright notice, this 
    list of conditions and the following disclaimer in the documentation and/or other 
    materials provided with the distribution.

    3. The end-user documentation included with the redistribution, if any, must include 
    the following acknowledgment: "This product includes software developed by the Apache 
    Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may 
    appear in the software itself, if and wherever such third-party acknowledgments 
    normally appear.

    4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or 
    promote products derived from this software without prior written permission. For 
    written permission, please contact apache@apache.org.

    5. Products derived from this software may not be called "Apache", nor may "Apache" 
    appear in their name, without prior written permission of the Apache Software Foundation.

    THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, 
    BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 
    PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 
    OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, 
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 
    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 
    ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
    NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 
    ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    This software consists of voluntary contributions made by many individuals on behalf 
    of the Apache Software Foundation. For more information on the Apache Software Foundation, 
    please see <http://www.apache.org/>. Portions of this software are based upon public domain 
    software originally written at the National Center for Supercomputing Applications, University 
    of Illinois, Urbana-Champaign.
    
    This product includes WebWindow Software developed by Horst Heistermann.
    *************************************************************************************
  -->
</HTML>
