{"id":114,"date":"2004-08-09T08:30:34","date_gmt":"2004-08-09T06:30:34","guid":{"rendered":""},"modified":"2007-07-03T10:08:32","modified_gmt":"2007-07-03T08:08:32","slug":"veritas-vxvm-volume-manager","status":"publish","type":"post","link":"http:\/\/www.lookit.org\/blog\/?p=114","title":{"rendered":"Veritas VxVM Volume Manager"},"content":{"rendered":"<p>Petit tutorial sur Veritas VxVM, gestion du raid de VERITAS.<br \/><!--more--><\/p>\n<h2 align=\"left\"><font face=\"Times New Roman\">Veritas Volume Manager<\/font><br \/><\/h2>\n<p><\/p>\n<dl><\/p>\n<dt><strong>     1.  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#1.%20%20Volume%20Manager%20Objects\">Volume Manager<br \/>Objects<\/a><\/strong><a href=\"http:\/\/www.adminschoice.com\/docs\/vxvm.htm\"> <\/a><strong>                      <\/strong><\/dt>\n<p><\/p>\n<dd>1.1  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Disks\">Disks <\/a><\/dd>\n<p><\/p>\n<dd>1.2  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Disk%20groups%20:\">Disk groups<\/a><\/dd>\n<p><\/p>\n<dd>1.3  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Volume%20Manager%20disks\">Volume Manager disks<\/a><\/dd>\n<p><\/p>\n<dd>1.4  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Subdisks\">Subdisks<\/a><\/dd>\n<p><\/p>\n<dd>1.5  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Plexes\">Plexes<\/a><\/dd>\n<p><\/p>\n<dd>1.6  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Volumes\">Volumes<\/a><\/dd>\n<p><\/p>\n<dd>1.7  <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Volume%20Manager%20Objects%20and%20Their%20Relationship\">Volume<br \/>        Manger Objects &amp; their Relationship<\/a><\/dd>\n<p><\/p>\n<dt><strong>     2.    <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Volume%20Manager%20Configuration\">Volume<br \/>      Manager Configuration ( options menu)<\/a><\/strong><\/dt>\n<p><\/p>\n<dd>2.1   <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Add%20or%20initialize%20one%20or%20more%20disks\">Add or initialize one or<br \/>      more disks <\/a><\/dd>\n<p><\/p>\n<dd>2.2  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Encapsulate%20one%20or%20more%20disks\">Encapsulate one or more disks <\/a><\/dd>\n<p><\/p>\n<dd>2.3  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Remove%20a%20disk\">Remove a disk <\/a><\/dd>\n<p><\/p>\n<dd>2.4  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Remove%20a%20disk%20for%20replacement\">Remove a disk for replacement<\/a><\/dd>\n<p><\/p>\n<dd>2.5  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Replace%20a%20failed%20or%20removed%20disk\">Replace a failed or removed<br \/>      disk <\/a><\/dd>\n<p><\/p>\n<dd>2.6  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Mirror%20volumes%20on%20a%20dis\">Mirror volumes on a disk<\/a><\/dd>\n<p><\/p>\n<dd>2.7  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Move%20volumes%20from%20a%20disk\">Move volumes from a disk <\/a><\/dd>\n<p><\/p>\n<dd>2.8  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Enable%20access%20to%20%28import%29%20a%20disk%20group\">Enable access to<br \/>      (import) a disk group<\/a><\/dd>\n<p><\/p>\n<dd>2.9  <br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Disable%20access%20to%20%28deport%29%20a%20disk%20group\">Remove access to<br \/>      (deport) a disk group <\/a><\/dd>\n<p><\/p>\n<dd>2.10<br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Enable%20%28online%29%20a%20disk%20device\">Enable (online) a disk device <\/a><\/dd>\n<p><\/p>\n<dd>2.11<br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Disable%20%28offline%29%20a%20disk%20device\">Disable (offline) a disk device <\/a><\/dd>\n<p><\/p>\n<dd>2.12<br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Mark%20a%20disk%20as%20a%20spare%20for%20a%20disk%20group\">Mark a disk as a spare<br \/>      for a disk group<\/a><\/dd>\n<p><\/p>\n<dd>2.13<br \/>      <a href=\"http:\/\/lookit.org\/guppy\/articles.php?lng=fr&amp;pg=89#Turn%20off%20the%20spare%20flag%20on%20a%20disk\">Turn off the spare flag on a<br \/>      disk <\/a><\/dd>\n<p><\/p>\n<p align=\"left\"><strong><font size=\"3\">About Veritas volume manager :<\/font><\/strong><\/p>\n<p>Veritas Volume Manager is a software product from veritas Inc. and it is<br \/>    used to manage disk storage .<\/p>\n<p><\/p>\n<p>The main features of volume manager are following :<\/p>\n<p><\/p>\n<p><strong>1.<\/strong> Allows creation of logical volumes spanning over multiple disks.<br \/>        This overcomes the physical limit of the disk .<\/p>\n<p><\/p>\n<p><strong>2.  <\/strong>Provides high availability storage solutions through RAID<br \/>        ,Mirroring of disks .<\/p>\n<p><\/p>\n<p><strong>3. <\/strong>Provides fail over features by providing transferable disk group<br \/>        ownership between systems.<\/p>\n<p><\/p>\n<p><strong>4.<\/strong>  Dynamic reconfiguration of disk storage in an online system state.<br \/>        what is veritas volume manager .<\/p>\n<p><\/p>\n<p align=\"left\">The following  article describes the volume manager<br \/>    objects and configuration of these  objects using a text menu based<br \/>    utility called vxdiskadm .<\/p>\n<h4 align=\"left\"><strong><a name=\"1.  Volume Manager Objects\" title=\"1.  Volume Manager Objects\"><\/a>1.0  Volume Manager<br \/>Objects         <\/strong><\/h4>\n<p align=\"left\"><strong><u><a name=\"Disks\" title=\"Disks\"><\/a><font size=\"3\">Disks<\/font><\/u><\/strong><\/p>\n<p align=\"left\">Disks are referred in volume<br \/>manager by two terms &#8211;  device  name  and disk name . The device name<br \/>specifies controller , target id and slice of  the disk . Disk name is the common<br \/>name given to the device name as an easy to remember  name .<\/p>\n<p align=\"left\">For example device name<br \/>c2t3dos2  represents  controller  number 2 , target id 3 , disk group 0<br \/>and slice 2 and disk01 may be its disk name . While device name is system dependent<br \/>based on controller and disk id  the  disk<br \/>name is user defined . <\/p>\n<p align=\"left\"><strong><u><a name=\"Disk groups :\" title=\"Disk groups :\"><\/a>Disk groups :<\/u><\/strong><\/p>\n<p><\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">A <em>disk group<\/em> is a collection of volume manager disks grouped together to hold<br \/>the data . All the configuration changes  made to a disk group are applied<br \/>    to the disks in that disk group only.   <\/p>\n<\/li>\n<li> \n<p align=\"left\">Volume Manager objects cannot span disk groups i.e. all the operations<br \/>    on a<br \/>particular disk group remains confined to that particular group .  <\/p>\n<\/li>\n<li> \n<p align=\"left\">Disk groups enable high availability as these can be<br \/>shared by two or more hosts  but can be accessed by only one host at <span style=\"background-color: #ffffff\"> a time.<br \/>    In two hosts and a shared storage situation one  host can take over the ownership of  the<br \/>    disk groups and<br \/>    drives  in case other  host fails.<\/span><\/p>\n<\/li>\n<\/ul>\n<p><\/p>\n<p align=\"left\"><strong><u><a name=\"Volume Manager disks\" title=\"Volume Manager disks\"><\/a>Volume Manager disks<\/u><\/strong><\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">Adding physical  disks  to the volume manager results in<br \/>    creation of  public and private region in the disk by the volume<br \/>    manager .The public region is the disk space available for volume space and<br \/>    the private region stores the configuration information.   <\/p>\n<\/li>\n<li> \n<p align=\"left\">A Volume Manager  disks are created from the public region of a<br \/>    physical disk that is under Volume Manager control. Each volume manager disk<br \/>    corresponds to one physical disk.  <\/p>\n<\/li>\n<li> \n<p align=\"left\"> A volume manager disk is given a disk media name when it is added to a disk<br \/>    group which can be default or unique user defined..  <\/p>\n<\/li>\n<li> \n<p align=\"left\">Once a volume manager disk is assigned a disk media name, the disk is no longer<br \/>    referred to by its physical address of <font face=\"Courier New, Courier, mono\">c#t#d#<\/font>.<br \/>    The physical address of <font face=\"Courier New, Courier, mono\">c#t#d#<\/font><br \/>    becomes known as the disk access record.<\/p>\n<\/li>\n<\/ul>\n<p><\/p>\n<p align=\"left\"><u><a name=\"Subdisks\" title=\"Subdisks\"><\/a><strong>Subdisks<\/strong><\/u><\/p>\n<p><\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">A subdisk is a subsection of a disk&#39;s public region  and is  the<br \/>    smallest unit of storage in Volume Manager.    <\/p>\n<\/li>\n<li> \n<p align=\"left\">A subdisk is defined by an offset and a length in sectors on a<br \/>    volume manager disk.  <\/p>\n<\/li>\n<li> \n<p align=\"left\">A volume manager disk can contain multiple subdisks  but subdisks cannot<br \/>    overlap or share the same portions of a volume manager disk.  <\/p>\n<\/li>\n<li> \n<p align=\"left\">volume manager disk space that is not reserved or that is not part of a subdisk is<br \/>    free space. You can use free space to create new subdisks.<\/p>\n<\/li>\n<\/ul>\n<p><\/p>\n<p align=\"left\">A subdisk is similar to a partition but with following differences :<\/p>\n<p><\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">The maximum number of partitions to a disk is eight.  <\/p>\n<\/li>\n<li> \n<p align=\"left\">There is no theoretical limit to number of subdisks that can be attached<br \/>    to a single plex, but<br \/>    it has been limited to a default value of 4096. If required, this default<br \/>    can be changed, using the <font face=\"Courier New, Courier, mono\">vol_subdisk_num<\/font><br \/>    tunable parameter.<\/p>\n<\/li>\n<\/ul>\n<p><\/p>\n<div>  <\/p>\n<p align=\"left\"><u><a name=\"Plexes\" title=\"Plexes\"><\/a><strong>Plexes<\/strong><\/u><\/p>\n<p>  <\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">A <strong style=\"color: black\">plex<\/strong> is a<br \/>      structured or ordered collection of subdisks that represents one copy of<br \/>      the data in a volume. A <strong style=\"color: black\">plex<\/strong><br \/>      consists of one or more subdisks located on one or more physical disks.    <\/p>\n<\/li>\n<li> \n<p align=\"left\">A plex<br \/>      is also<br \/>      called a mirror. The terms<br \/>      plex and mirror<br \/>      can be used interchangeably, even though a plex<br \/>      is only one copy of the data. The terms<br \/>      &quot;mirrored&quot; or &quot;mirroring&quot; imply two or more copies of<br \/>      data.    <\/p>\n<\/li>\n<li> \n<p align=\"left\">The length of a plex<br \/>      is determined by the last block that can be read or written on the last<br \/>      subdisk in the plex.    <\/p>\n<\/li>\n<li> \n<p align=\"left\">The default naming convention for plexes in a volume is <em><font face=\"Courier New, Courier, mono\">volumename<\/font><\/em><font face=\"Courier New, Courier, mono\">-##<\/font>.<br \/>      The default plex<br \/>      name consists of the volume name, a hyphen, and a two-digit number  <\/p>\n<\/li>\n<\/ul>\n<p><\/div>\n<p><\/p>\n<div>  <\/p>\n<p align=\"left\"><strong><u><a name=\"Volumes\" title=\"Volumes\"><\/a>Volumes<\/u><\/strong><\/p>\n<p>  <\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">A volume is composed of one or more plexes  not restricted by the<br \/>      physical size of the disk.     <\/p>\n<\/li>\n<li> \n<p align=\"left\">A volume can span across multiple disks.     <\/p>\n<\/li>\n<li> \n<p align=\"left\">Volume Manager uses the default naming convention <font face=\"Courier New, Courier, mono\">vol##<\/font><br \/>      for volumes, where ## represents a two-digit number but can be user defined <br \/>      as per requirement.  <\/p>\n<\/li>\n<\/ul>\n<p>      <\/p>\n<p align=\"left\"><strong><a name=\"Volume Manager Objects and Their Relationship\" title=\"Volume Manager Objects and Their Relationship\"><\/a>Volume<br \/>      Manager Objects and Their Relationship<\/strong><\/p>\n<p>  <\/p>\n<table border=\"1\" cellspacing=\"0\" cellpadding=\"0\" width=\"74%\" height=\"336\">\n<tbody>\n<tr>\n<td width=\"45%\" height=\"167\" align=\"center\" valign=\"middle\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/lookit.org\/guppy\/vxvm_P_fichiers\/vxvm1.jpg\" border=\"0\" alt=\"\" width=\"87\" height=\"151\" \/><\/td>\n<td width=\"24%\" height=\"167\" align=\"center\" valign=\"middle\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/lookit.org\/guppy\/vxvm_P_fichiers\/vxvm2.jpg\" border=\"0\" alt=\"\" width=\"178\" height=\"151\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\" width=\"100%\" height=\"167\" align=\"center\" valign=\"middle\">          <img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/lookit.org\/guppy\/vxvm_P_fichiers\/volume.jpg\" border=\"0\" alt=\"\" width=\"262\" height=\"179\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h4 align=\"left\"><strong>2.0  <a name=\"Volume Manager Configuration\" title=\"Volume Manager Configuration\"><\/a>Volume Manager Configuration<\/strong><\/h4>\n<p align=\"left\">Volume configuration consists of adding two or<br \/>more disks to form   disk group and create volume\/s from this disk group. File system<br \/>can be created on these volumes or these can be accessed as raw devices for some database<br \/>applications. First step in volume manager configuration consists of adding and initializing<br \/>disks  under volume manager  which  creates a public<br \/>region which is bulk of disk space available for volume space .Private  region which<br \/>is generally of a few megabytes stores the disk configuration information .<\/p>\n<p align=\"left\">Most of the volume manager operation related to disks<br \/>&amp;  volume can be performed by a character based menu utility call vxdiskadm  <\/p>\n<p align=\"left\">Following paragraphs describes   the use of vxddiskadm to configure and manage<br \/>  volume manager.<\/p>\n<p align=\"left\"><strong>#vxdiskadm<\/strong><\/p>\n<p align=\"left\">Typing vxdiskadm brings up a menu based utility (text)  . The options ,<br \/>their explanation and screen shots are given below .Most of the options need a<br \/>disk name , device name or disk group name and you can have this information by<br \/>typing list in the vxdiskadm menu .The list menu option is used  to display a<br \/>list of disks attached to your system. This also lists removed or failed disks. Most<br \/>useful to get a quick view of all disks or list details of  a single disk &#8211; its name<br \/>, volume association and status.<\/p>\n<p align=\"left\">A disk needs to be formatted in<br \/>order to be included in volume manager  . volume manager will report unformatted disk as invalid and a<br \/>will only recognize after formatting <\/p>\n<p align=\"left\">By default all the available disks in the system are considered for inclusion<br \/>as volume manager disk however to exclude certain disks, list the<br \/>names of the disks to be excluded in the file \/etc\/vx\/disks.exclude before the<br \/>initialization or encapsulation. Similarly, you can exclude all disks on specific<br \/>controllers from initialization or encapsulation by listing those controllers in the file<br \/>\/etc\/vx\/cntrls.exclude.<\/p>\n<p align=\"left\">? &amp; ??  options provide help about the menu item and menu system.<\/p>\n<p align=\"left\"><strong>#vxdiskadm<\/strong><\/p>\n<p><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" width=\"91%\">\n<tbody>\n<tr>\n<td width=\"100%\" bgcolor=\"#dbdbdb\">      <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">  Volume<br \/>    Manager Support Operations  <\/p>\n<p>      Menu: VolumeManager\/Disk  <\/p>\n<p>      1    Add or initialize one or more disks  <\/p>\n<p>      2    Encapsulate one or more disks  <\/p>\n<p>      3    Remove a disk  <\/p>\n<p>      4    Remove a disk for replacement  <\/p>\n<p>      5    Replace a failed or removed disk  <\/p>\n<p>      6    Mirror volumes on a disk  <\/p>\n<p>      7    Move volumes from a disk  <\/p>\n<p>      8    Enable access to (import) a disk group  <\/p>\n<p>      9    Remove access to (deport) a disk group  <\/p>\n<p>      10   Enable (online) a disk device  <\/p>\n<p>      11   Disable (offline) a disk device  <\/p>\n<p>      12   Mark a disk as a spare for a disk group  <\/p>\n<p>      13   Turn off the spare flag on a disk  <\/p>\n<p>      list List disk information  <\/p>\n<p>      ?    Display help about<br \/>    menu  <\/p>\n<p>      ??   Display help about the menuing system  <\/p>\n<p>      q    Exit from menus  <\/p>\n<p>      Select an operation to perform <\/font><\/p>\n<p>    <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>    <\/p>\n<h3 align=\"left\"><strong>2.1  <u><a name=\"Add or initialize one or more disks\" title=\"Add or initialize one or more disks\"><\/a>Add or initialize one or more disks<\/u><\/strong><\/p>\n<\/h3>\n<p align=\"left\">The formatted disks can be added or initialized with volume manager<br \/>    .<br \/>    Disk groups needs to be given for making a new group or adding disks in<br \/>    existing group. Default  disk group is rootdg and if none is specified<br \/>    the disks are added to volume manager and are kept as hot spares which can be used in<br \/>    place of a failed disk.  <\/p>\n<div align=\"left\">    <\/p>\n<dt><\/dt>\n<p>  <\/div>\n<p align=\"left\"><strong>Select<\/strong><font face=\"Courier New\" size=\"2\"> 1 (Add or initialize one or more disks)<br \/>    <strong> from the<\/strong> vxdiskadm <strong> main menu<\/strong>.<\/font><\/p>\n<p>    <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" width=\"100%\" bgcolor=\"#d7d7d7\" bordercolor=\"#000000\">\n<tbody>\n<tr>\n<td width=\"100%\" bgcolor=\"#dbdbdb\">      <\/p>\n<p style=\"margin-left: 40px\" align=\"left\"><font face=\"Courier New\" size=\"2\">  Add or initialize disks   <\/p>\n<p>          Menu: VolumeManager\/Disk\/AddDisks <\/p>\n<p>  Use this operation to add one or more disks to a disk group. You<br \/>can add the selected disks to an existing disk group or to a new<br \/>disk group that will be  created as a part of the operation. The<br \/>selected disks may also be added to a disk group as spares. The<br \/>selected disks may also be initialized without adding them to a disk<br \/>group leaving the disks available for use as replacement disks.   <\/p>\n<p>          More than one disk or pattern may be entered at the prompt. Here are some disk<br \/>      selection examples:  <\/p>\n<p>           all:          <br \/>        all<br \/>        disks  <\/p>\n<p>           c3 c4t2:       all disks on both controller 3<br \/>        and controller       4,target 2  <\/p>\n<p>           c3t4d0:        a single disk  <\/p>\n<p>          Select disk devices to add: <\/p>\n<p>          [,all,list,q,?]<strong>list<\/strong> <\/font>   <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p align=\"left\"> can be a single or more disks and\/or controllers. If <br \/>    consists of multiple items, those items must be separated by white space.<\/p>\n<p align=\"left\"> list at the prompt displays a list of the disks available to the system, followed by a prompt at which you<br \/>    should type the device name of the disk to be added:<\/p>\n<p>    <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\">  <font face=\"Courier New\" size=\"2\"><\/p>\n<p>    DEVICE      <br \/>  DISK        <br \/>  GROUP        STATUS  <\/p>\n<p>    c0t0d0      <br \/>  disk01       rootdg      <br \/>  online  <\/p>\n<p>    c0t1d0      <br \/>  disk02       rootdg      <br \/>  online  <\/p>\n<p>    c0t2d0      <br \/>  disk03       rootdg      <br \/>  online  <\/p>\n<p>    c0t3d0      <br \/>  &#8211;           <br \/>  &#8211;           <br \/>  online  <\/p>\n<p>    c1t0d0      <br \/>  disk10       rootdg      <br \/>  online  <\/p>\n<p>    c1t0d1      <br \/>  &#8211;           <br \/>  &#8211;           <br \/>  error  <\/p>\n<p>    .  <\/p>\n<p>    .  <\/p>\n<p>    .  <\/p>\n<p>    c3t0d0      <br \/>  &#8211;           <br \/>  &#8211;           <br \/>  error  <\/p>\n<p>    c3t1d0      <br \/>  disk33       rootdg      <br \/>  online  <\/p>\n<p>    c3t2d0      <br \/>  disk34       rootdg      <br \/>  online  <\/p>\n<p>    c3t3d0      <br \/>  disk35       rootdg      <br \/>  online  <\/p>\n<p>    Select disk devices to add:  <\/p>\n<p>    [,all,list,q,?] c1t0d1  <\/p>\n<p>  <\/font><\/p>\n<p>        <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>  <\/p>\n<p align=\"left\">All disks attached to the system are recognized by<br \/>    the Volume Manager<br \/>    and displayed here.. Error status indicates disks  not recognized by volume manager<br \/>  as part of volume manager and can be used to add in the volume manager .. Disks with a name , group and online status are<br \/>    present in volume manager in a  valid volume manager disk group .One or more disks separated<br \/>    by space  can be<br \/>    selected for adding into volume manager.<\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" width=\"575\" bgcolor=\"#e2e2e2\">\n<tbody>\n<tr>\n<td width=\"573\" align=\"left\" bgcolor=\"#dbdbdb\">\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">   <br \/>          Here is the disk selected.  Output format: [Device_Name]  <\/p>\n<p>              c1t2d0  <\/p>\n<p>            Continue operation? [y,n,q,?] (default: y) <strong>y<\/strong>      <\/font><\/p>\n<p>          <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">     <br \/>          You can<br \/>          choose to add this disk to an existing disk group, a  <\/p>\n<p>              new disk group, or leave the disk available for use<br \/>          by future  <\/p>\n<p>              add or replacement operations.  To create a<br \/>          new disk group, select  a disk group name that does not yet exist.  To<br \/>          leave the disk  <\/p>\n<p>              available for future use, specify a disk group name<br \/>          of &quot;none&quot;.  <\/p>\n<p>            Which disk group [,none,list,q,?] (<strong>default<\/strong>:<br \/>          rootdg)    <\/font><\/p>\n<p>          <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Use a default disk name for the disk? [y,n,q,?] (<strong>default<\/strong>: y)<\/font><\/p>\n<p>              <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"> Add disk as a spare disk for<br \/>              rootdg? [y,n,q,?] (default: n)<br \/>              <strong><br \/>              n<\/strong> <\/font>          <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    The<br \/>          selected disks will be added to the disk group rootdg with  <\/p>\n<p>            default disk names.  <\/p>\n<p>              c1t2d0  <\/p>\n<p>            Continue with operation? [y,n,q,?] (default: y) <strong>y<\/strong>  <\/p>\n<p>              The following disk device has a valid VTOC, but<br \/>          does not appear to have  <\/p>\n<p>              been initialized for the Volume Manager.  If<br \/>          there is data on the disk  <\/p>\n<p>              that should NOT be destroyed you should encapsulate<br \/>          the existing disk  <\/p>\n<p>              partitions as volumes instead of adding the disk as<br \/>          a new disk.  <\/p>\n<p>              Output format: [Device_Name]  <\/p>\n<p>              c1t2d0  <\/p>\n<p>            Encapsulate this device? [y,n,q,?] (default: y) <strong>n <\/strong> <\/p>\n<p>              c1t2d0  <\/p>\n<p>            Instead of encapsulating, initialize? [y,n,q,?] (default: n)<strong> <br \/>          y    <\/strong><\/p>\n<p>                Initializing device c1t2d0.  <\/p>\n<p>                Adding disk device c1t2d0 to disk group rootdg<br \/>              with disk  <\/p>\n<p>                name disk39. <\/p>\n<p>           Add or initialize other disks? [y,n,q,?] (<strong>default<\/strong>:<br \/>          n)  <br \/>          <\/font><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 align=\"left\"><strong>2.2 <a name=\"Encapsulate one or more disks\" title=\"Encapsulate one or more disks\"><\/a>Encapsulate one or more disks<\/strong><\/h3>\n<p align=\"left\">This is used to bring the disk under volume manager , which are<br \/>already present in the system with data but without volume manager  . Data on these disks are<br \/>not disturbed and if these disks meets certain volume manager requirements these are added<br \/>    under volume manager.<\/p>\n<p align=\"left\">System<br \/>needs rebooting if  encapsulation is used for disk with mounted<br \/>filesystem or running applications . Also the old  device names<br \/>needs to<br \/>be changed in applications\/scripts to reflect the new volume name. <\/p>\n<p align=\"left\">vfstab information is updated automatically but<br \/>it is worthwhile  to check vfstab if changes are proper as any discrepancy in vfstab<br \/>may cause system boot failure  on next reboot.<\/p>\n<p align=\"left\">Encapsulation preserves any existing data on the disk when<br \/>    the disk is placed under volume manager control. To reduce the<\/p>\n<p>    <\/p>\n<p align=\"left\">chance of encapsulation failure, make sure that the disk<br \/>    meets  the following requirements:-<\/p>\n<ul><\/p>\n<li> \n<p align=\"left\">It has a small amount of free space (at the beginning or end<br \/>    of the disk) that does not belong to any partition  <\/p>\n<\/li>\n<li> \n<p align=\"left\">It has two free partitions  <\/p>\n<\/li>\n<li> \n<p align=\"left\">It has an s2 slice that represents the whole disk<\/p>\n<\/li>\n<\/ul>\n<p align=\"left\">One of the most common application  is encapsulation of<br \/>    root disk to bring it under volume manager and then  mirror it to have an<br \/>    alternate boot disk . <\/p>\n<p align=\"left\">The EEPROM variable use-nvramrc? must be set to true and an<br \/>    alternate boot disk alias name needs to be defined to access the second boot<br \/>    disk by an alternate  alias name in case primary disk fails.<\/p>\n<p>    <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\">\n<p>    ok&gt;eeprom use-nvramrc?=true  <\/p>\n<p>        <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p align=\"left\">Procedure for encapsulating  a disk for volume manager use is <br \/>    as follows:<\/p>\n<p align=\"left\"><strong>Select menu item <\/strong> 2 (Encapsulate<br \/>        one or more disks) <strong> from the <\/strong> vxdiskadm <strong> main menu and follow the prompts<br \/>    :-<\/strong><\/p>\n<p>    <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>          <\/p>\n<dl><\/p>\n<div align=\"left\">              <\/p>\n<dt><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Encapsulate one or more disks  <\/p>\n<p>    Menu: VolumeManager\/Disk\/Encapsulate  <\/p>\n<p>      Use this operation to convert one or more disks to use the<br \/>  Volume Manager.  <\/p>\n<p>      This adds the disks to a disk group and replaces existing<\/font><\/dt>\n<p>            <\/div>\n<p><\/p>\n<div align=\"left\">              <\/p>\n<dt><font face=\"Courier New\" size=\"2\">    partitions  <\/p>\n<p>      with volumes.  Disk encapsulation requires a reboot<br \/>  for the <\/font><\/dt>\n<p>            <\/div>\n<p><\/p>\n<div align=\"left\">              <\/p>\n<dt><font face=\"Courier New\" size=\"2\">    changes to take effect.  <\/p>\n<p>      More than one disk or pattern may be entered at the<br \/>  prompt.  Here<\/font><\/dt>\n<p>            <\/div>\n<p><\/p>\n<div align=\"left\">              <\/p>\n<dt><font face=\"Courier New\" size=\"2\">    are some disk selection examples:  <\/p>\n<p>  all:           all<br \/>  disks  <\/p>\n<p>      c3 c4t2:       all disks on<br \/>  both controller 3 and controller 4, target 2  <\/p>\n<p>      c3t4d0:        a single<br \/>  disk  <\/p>\n<p>    Select disk devices to encapsulate:  <\/p>\n<p>    [,all,list,q,?] <strong>c2t5d0 <\/strong> <\/p>\n<p>                <\/font><\/dt>\n<p>            <\/div>\n<p><\/dl>\n<p>        <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p align=\"left\"> can be a single<br \/>    disk, or a series of disks and\/or controllers (with optional targets). If <br \/>    consists of multiple items, those items must be separated by white space.<\/p>\n<p align=\"left\">&nbsp;<\/p>\n<p align=\"left\">&nbsp;<\/p>\n<p align=\"left\">\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">     <br \/>          Here is the disk selected.  Output format: [Device_Name]  <\/p>\n<p>              c2t5d0  <\/p>\n<p>            Continue operation? [y,n,q,?] (default: y) <strong>y<\/strong>  <\/p>\n<p>            <\/font><\/p>\n<p>          <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">       <br \/>          You can choose to add this disk to an existing disk group or<br \/>          to  <\/p>\n<p>              a new disk group.  To create a new disk group,<br \/>          select a disk group name that does not yet exist.  <\/p>\n<p>            Which disk group [,list,q,?] (<strong>default<\/strong>:<br \/>          rootdg)  <\/p>\n<p>            Use a default disk name for the disk? [y,n,q,?]<br \/>          (<strong>default<\/strong>: y) <\/p>\n<p>                  The selected disks will be encapsulated and<br \/>              added to the rootdg  <\/p>\n<p>                  disk group with default disk names.  <\/p>\n<p>                  c2t5d0  <\/p>\n<p>                Continue with operation? [y,n,q,?] (default: y)<strong> y <\/strong><\/p>\n<p>            The following disk has been selected for encapsulation.  Output format:  <\/p>\n<p>            [Device_Name]  <\/p>\n<p>              c2t5d0  <\/p>\n<p>            Continue with encapsulation? [y,n,q,?] (default: y) <strong><br \/>          y<\/strong>  <br \/><\/font><\/p>\n<p>              <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">   <br \/>              The disk device c2t5d0 will be encapsulated and added<br \/>              to the disk  <\/p>\n<p>                  group  rootdg with the disk name<br \/>              disk01.  <\/p>\n<p>                  The c2t5d0 disk has been configured for<br \/>              encapsulation.  <\/p>\n<p>                  The first stage of encapsulation has completed<br \/>              successfully.  You  <\/p>\n<p>                  should now reboot your system at the earliest<br \/>              possible opportunity.  <\/p>\n<p>                  The encapsulation will require two or three<br \/>              reboots which will happen automatically after the next reboot.  To<br \/>              reboot execute the command:  <\/p>\n<p>                  shutdown -g0 -y -i6  <\/p>\n<p>                  This will update the \/etc\/vfstab file so that<br \/>              volume devices are  <\/p>\n<p>                  used to mount the file systems on this disk<br \/>              device.  You will need  to update any other references such as backup<br \/>              scripts, databases,<\/p>\n<p>                  or manually created swap devices.  <br \/>              <\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">  Encapsulate other disks?<br \/>              [y,n,q,?] (default: n)<br \/>              <strong> n<\/strong>  <br \/>              <\/font>          <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    The disk device c2t5d0 will be encapsulated and added to the<br \/>          disk group rootdg with the disk name disk01.  <\/p>\n<p>              The encapsulation operation failed with the<br \/>          following error:  <\/p>\n<p>              It is not possible to encapsulate c2t5d0, for the<br \/>          following reason:  <\/p>\n<p>          Unsupported disk layout.&gt;  <\/p>\n<p>            Hit RETURN to continue. <\/font><\/p>\n<p>    <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>  <\/p>\n<p align=\"left\"> Encapsulation may  fail  if  there is not enough free space available on<br \/>    the disk to accommodate volume manager. If this happens, the procedure above will end<br \/>    abruptly with an error message as above .<\/p>\n<h3 align=\"left\">2.3 <a name=\"Remove a disk\"><\/a>Remove a disk<\/h3>\n<p align=\"left\">This option  is used to remove a disk from a<br \/>disk group    provided there is no active volume using this disk .. If there are<br \/>some volumes using the disk the  those have to be either moved to some other disk or<br \/>removed  if they are no longer needed.<\/p>\n<p align=\"left\">However since a diskgroup must have at least one<br \/>disk you can not remove all the disks from a disk group . To remove all disks from a<br \/>diskgroup you have to disable the volume group with the exception of  rootdg disk<br \/>group which can not be disabled .<\/p>\n<p>      <\/p>\n<p align=\"left\"><strong>Select menu item <\/strong> 3<strong> (<\/strong>Remove a disk<strong>) from the<br \/>      <\/strong><br \/> vxdiskadm<strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td bgcolor=\"#dbdbdb\">\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Remove a disk  <\/p>\n<p>    Menu: VolumeManager\/Disk\/RemoveDisk  <\/p>\n<p>    Use this operation to remove a disk from a disk group. This  <\/p>\n<p>    operation takes, as input, a disk name. This is the same<br \/>  name  <\/p>\n<p>    that you gave to the disk when you added the disk to the<br \/>  disk  <\/p>\n<p>    group.  <\/p>\n<p>    Enter disk name [,list,q,?] <strong>disk01  <\/strong><\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Requested operation is to<br \/>            remove disk disk01 from group rootdg.  <\/p>\n<p>              Continue with operation? [y,n,q,?] (<strong>default<\/strong>:<br \/>            y)    <\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Removal of disk disk01 is<br \/>            complete.  <\/p>\n<p>              Remove another disk? [y,n,q,?] (<strong>default<\/strong>: n)<\/font><\/p>\n<p>          <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p align=\"left\">\n<h3 align=\"left\"><strong>2.4 <a name=\"Remove a disk for replacement\"><\/a>Remove a disk for replacement<\/strong><\/h3>\n<p align=\"left\">This option is used for removing the disk <br \/>but retaining the name of the disk so that it can be used by the newly  replaced disk . The<br \/>replacement disk can be a newly added disk or already available disk in the other disk<br \/>groups <\/p>\n<p>      <\/p>\n<p align=\"left\"><strong>Select menu item <\/strong> 4 (Remove a<br \/>          disk for replacement<strong>) from the <\/strong><br \/> vxdiskadm<strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Remove a disk for replacement  <\/p>\n<p>    Menu: VolumeManager\/Disk\/RemoveForReplace  <\/p>\n<p>    Use this menu operation to remove a physical disk from a<br \/>  disk  <\/p>\n<p>    group, while retaining the disk name. This changes the<br \/>  state  <\/p>\n<p>    for the disk name to a removed disk. If there are any  <\/p>\n<p>    initialized disks that are not part of a disk group, you will<br \/>  be  <\/p>\n<p>    given the option of using one of these disks as a<br \/>  replacement.  <\/p>\n<p>    Enter disk name [,list,q,?] disk02  <\/p>\n<p><\/font><\/p>\n<p>          <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>      <\/p>\n<p align=\"left\">Additional screens display if there are volumes<br \/>      associated with the disk you want to remove. You have to decide if data is<br \/>      needed or not needed and answer the prompts as asked .<\/p>\n<p>          <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    The following devices are available as replacements:  <\/p>\n<p>         c1t1d0  <\/p>\n<p>    You can choose one of these disks now, to replace disk02.  <\/p>\n<p>    Select &quot;none&quot; if you do not wish to select a replacement<br \/>  disk.  <\/p>\n<p>    Choose a device, or select &quot;none&quot;  <\/p>\n<p>    [,none,q,?] (default: c1t1d0)    <\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Requested operation is to<br \/>            remove disk disk02 from group rootdg.  <\/p>\n<p>              The removed disk will be replaced with disk device<br \/>            c1t1d0.  <\/p>\n<p>              Continue with operation? [y,n,q,?] (default: y)<\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Removal of disk disk02<br \/>            completed successfully.  <\/p>\n<p>              Proceeding to replace disk02 with device c1t1d0.<br \/><\/font><\/p>\n<p>                <\/p>\n<p align=\"left\"><font size=\"2\">  <font face=\"Courier New\"> <br \/>                Disk replacement completed successfully.<\/font><\/font>            <\/p>\n<p align=\"left\"><font size=\"2\">     <font face=\"Courier New\"><br \/>            Remove another disk? [y,n,q,?]<br \/>            (<strong>default<\/strong>: n)<\/font><\/font>            <\/p>\n<p align=\"left\">&nbsp;<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>    <\/p>\n<h3 align=\"left\">2.5 <a name=\"Replace a failed or removed disk\"><\/a>Replace a failed or removed disk<\/h3>\n<p align=\"left\">This option is used to replace a failed or<br \/>removed disk  . The new disk can be initialized or non initialized  as this option<br \/>does initialization  .<\/p>\n<p>      <\/p>\n<p align=\"left\"><strong>Select menu item <\/strong> 5<strong> (<\/strong>Replace a<br \/>          failed or removed disk<strong>) from the <\/strong><br \/> vxdiskadm<strong> main menu.<\/strong><\/p>\n<p>          <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Replace a failed or removed disk  <\/p>\n<p>    Menu: VolumeManager\/Disk\/ReplaceDisk  <\/p>\n<p>    Use this menu operation to specify a replacement disk for a<br \/>  disk  <\/p>\n<p>    that you removed with the &quot;Remove a disk for replacement&quot;<br \/>  menu  <\/p>\n<p>    operation, or that failed during use. You will be prompted<br \/>  for  <\/p>\n<p>    a disk name to replace and a disk device to use as a<br \/>  replacement.  <\/p>\n<p>    You can choose an uninitialized disk, in which case the disk<br \/>  will  <\/p>\n<p>    be initialized, or you can choose a disk that you have<br \/>  already  <\/p>\n<p>    initialized using the Add or initialize a disk menu<br \/>  operation.  <\/p>\n<p>    Select a removed or failed disk [,list,q,?] disk02      <\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    The following devices are<br \/>            available as replacements:  <\/p>\n<p>                   c1t0d0s2 c1t1d0s2  <\/p>\n<p>              You can choose one of these disks to replace<br \/>            disk02.  <\/p>\n<p>              Choose &quot;none&quot; to initialize another disk to replace<br \/>            disk02.  <\/p>\n<p>              Choose a device, or select &quot;none&quot;  <\/p>\n<p>              [,none,q,?] (default:<br \/>            c1t0d0s2)    <\/font><\/p>\n<p>                <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">  The requested operation is to use the initialized device<br \/>                c1t0d0s2  <\/p>\n<p>                  to replace the removed or failed disk disk02 in disk<br \/>                group rootdg.  <\/p>\n<p>                  Continue with operation? [y,n,q,?] (<strong>default<\/strong>: y) <\/font>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">   <br \/>            Replacement of disk disk02 in group rootdg with disk<br \/>            device  <\/p>\n<p>              c1t0d0s2 completed successfully. <\/p>\n<p><\/font><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>      <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody><\/tbody>\n<\/table>\n<h3 align=\"left\">2.6 <a name=\"Mirror volumes on a dis\"><\/a>Mirror volumes on a disk<\/h3>\n<p align=\"left\">volumes can be mirrored to another disk with<br \/>available space however it can not be used to mirror existing mirrors or mirrors spanning<br \/>more than one sub disk .   <\/p>\n<p align=\"left\"> To mirror volumes on a disk, make sure that the<br \/>      target disk has an equal or greater amount of space as the originating disk and then do<br \/>      the following<\/p>\n<p align=\"left\"><strong>Select menu item<\/strong> 6 (Mirror<br \/>          volumes on a disk) <strong> from the <\/strong> vxdiskadm<strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td bgcolor=\"#dbdbdb\">\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Mirror volumes on a disk  <\/p>\n<p>    Menu: VolumeManager\/Disk\/Mirror  <\/p>\n<p>    This operation can be used to mirror volumes on a disk.<br \/>  These  <\/p>\n<p>    volumes can be mirrored onto another disk or onto any  <\/p>\n<p>    available disk space. Volumes will not be mirrored if they<br \/>  are  <\/p>\n<p>    already mirrored. Also, volumes that are comprised of more<br \/>  than  <\/p>\n<p>    one subdisk will not be mirrored.  <\/p>\n<p>    Mirroring volumes from the boot disk will produce a disk that<br \/>  can  <\/p>\n<p>    be used as an alternate boot disk.  <\/p>\n<p>    Enter disk name [,list,q,?] <strong>disk02  <\/strong><\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">  You can choose to mirror<br \/>            volumes from disk disk02 onto any  <\/p>\n<p>              available disk space, or you can choose to mirror onto a<br \/>            specific  <\/p>\n<p>              disk. To mirror to a specific disk, select the name of that<br \/>            disk.  <\/p>\n<p>              To mirror to any available disk space, select<br \/>            &quot;any&quot;.  <\/p>\n<p>              Enter destination disk [,list,q,?] (default: any) <strong>disk01<\/strong>      <\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p><\/font><\/p>\n<p>          <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>        <\/p>\n<p align=\"left\">Note &#8211; Be sure to always specify the<br \/>      destination disk when you are creating an alternate root disk. Otherwise, the<br \/>        volume manager will select space available in the disk group which might<br \/>        span disk and will result in boot failure from this disk.<\/p>\n<h3 align=\"left\">2.7 <strong><a name=\"Move volumes from a disk\"><\/a>Move volumes from a disk<\/strong><\/h3>\n<p align=\"left\">This option is used in case the disk is to be replaced or<br \/>removed and has active volumes on the disk. . Also volumes can be moved to different disk<br \/>groups for better space , performance etc.<\/p>\n<p align=\"left\"><strong>Select menu item <\/strong>7 <strong>(<\/strong>Move volumes from a disk<strong>)<\/strong><strong> from the <\/strong>  <strong> from the from the from the <\/strong> vxdiskadm<strong><br \/>          main menu.<\/strong> <\/p>\n<p>          <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" width=\"552\" bgcolor=\"#e2e2e2\">\n<tbody>\n<tr>\n<td width=\"550\">\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Move volumes from a disk  <\/p>\n<p>    Menu: VolumeManager\/Disk\/Evacuate  <\/p>\n<p>    Use this menu operation to move any volumes that are using<br \/>  a  <\/p>\n<p>    disk onto other disks. Use this menu immediately prior to  <\/p>\n<p>    removing a disk, either permanently or for replacement. You<br \/>  can  <\/p>\n<p>    specify a list of disks to move volumes onto, or you can move<br \/>  the  <\/p>\n<p>    volumes to any available disk space in the same disk group.  <\/p>\n<p>    NOTE: Simply moving volumes off of a disk, without also<br \/>  removing  <\/p>\n<p>          the disk, does not prevent volumes<br \/>  from being moved onto  <\/p>\n<p>          the disk by future operations. For<br \/>  example, using two  <\/p>\n<p>          consecutive move operations may<br \/>  move volumes from the  <\/p>\n<p>          second disk to the<br \/>  first.  <\/p>\n<p>    Enter disk name [,list,q,?] <strong>disk01<\/strong>  <br \/>    <\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>              You can now specify a list of disks to move onto. <br \/>            Specify a list  <\/p>\n<p>              of disk media names (e.g., disk01) all on one line separated<br \/>            by  <\/p>\n<p>              blanks.  If you do not enter any disk media names, then<br \/>            the  <\/p>\n<p>              volumes will be moved to any available space in the disk<br \/>            group.<\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"> Requested operation is to<br \/>            move all volumes from disk disk01 in  <\/p>\n<p>              group rootdg.  <\/p>\n<p>              NOTE: This operation can take a long time to<br \/>            complete.  <\/p>\n<p>              Continue with operation? [y,n,q,?] (<strong>default<\/strong>: y)  <\/p>\n<p>              Move volume   vol3<br \/>            &#8230;  <\/p>\n<p>              Move volume vol3-bk00 &#8230;  <\/p>\n<p>              Evacuation of disk disk01 is complete. <\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"> Move volumes from<br \/>                another disk? [y,n,q,?] (<strong>default<\/strong>: n)  <\/font><\/p>\n<p align=\"left\">&nbsp;<\/p>\n<p>      <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 align=\"left\">2.8 <a name=\"Enable access to (import) a disk group\"><\/a>Enable access to (import) a disk group<\/h3>\n<p align=\"left\">Used in enabling ownership of the other system to<br \/>a disk group which has been deported  by the other  system. Used in failover<br \/>configurations where the ownership  of a shared disk\/disk group is transferred to the other<br \/>system in case of failure of current system. <\/p>\n<p align=\"left\"> <strong>Select menu item<\/strong> 8(Enable access to (import) a disk group)<br \/><strong><br \/>          from the <\/strong> vxdiskadm <strong> main menu.<\/strong><\/p>\n<p>      <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#e2e2e2\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Enable access to (import) a disk group  <\/p>\n<p>    Menu: VolumeManager\/Disk\/EnableDiskGroup  <\/p>\n<p>    Use this operation to enable access to a disk group. This can<br \/>  be  <\/p>\n<p>    used as the final part of moving a disk group from one system<br \/>  to  <\/p>\n<p>    another. The first part of moving a disk group is to use<br \/>  the  <\/p>\n<p>    &quot;Remove access to (deport) a disk group&quot; operation on<br \/>  the  <\/p>\n<p>    original host.  <\/p>\n<p>    A disk group can be imported from another host that failed<br \/>  without  <\/p>\n<p>    first deporting the disk group. Be sure that all disks in the<br \/>  disk  <\/p>\n<p>    group are moved between hosts.  <\/p>\n<p>    If two hosts share a SCSI bus, be very careful to ensure that<br \/>  the  <\/p>\n<p>    other host really has failed or has deported the disk group.<br \/>  If  <\/p>\n<p>    two active hosts import a disk group at the same time, the<br \/>  disk  <\/p>\n<p>    group will be corrupted and will become unusable.  <\/p>\n<p>    Select disk group to import [,list,q,?] (default:<br \/>  list)  <\/p>\n<p>  <strong>newdg<\/strong>  <\/p>\n<p>  The import of newdg was successful.<\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">Select another disk<br \/>            group? [y,n,q,?] (<strong>default<\/strong>: n)<\/font>          <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 align=\"left\"><strong>2.9 <a name=\"Disable access to (deport) a disk group\"><\/a>Disable access to (deport) a disk group<\/strong><\/h3>\n<p align=\"left\">Disk group is deported if  disks<br \/>groups  ownership needs to be transferred  to another system or all the disks in<br \/>a disk groups needs to be freed from group. Disks in a disk groups to be deported should<br \/>not  be active.<\/p>\n<p align=\"left\"><strong>Select menu item <\/strong>9 <strong>(<\/strong>Remove access to (deport) a disk group<strong>)<br \/>          from the <\/strong>vxdiskadm<strong> main menu.<\/strong> <\/p>\n<p>          <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#e2e2e2\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><br \/>    Remove access to (deport) a disk group  <\/p>\n<p>    Menu: VolumeManager\/Disk\/DeportDiskGroup  <\/p>\n<p>    Use this menu operation to remove access to a disk group that<br \/>  is  <\/p>\n<p>    currently enabled (imported) by this system. Deport a disk  <\/p>\n<p>    group if you intend to move the disks in a disk group to<br \/>  another  <\/p>\n<p>    system. Also, deport a disk group if you want to use all of<br \/>  the  <\/p>\n<p>    disks remaining in a disk group for some new purpose.  <\/p>\n<p>    You will be prompted for the name of a disk group. You will<br \/>  also  <\/p>\n<p>    be asked if the disks should be disabled (offlined). For  <\/p>\n<p>    removable disk devices on some systems, it is important to  <\/p>\n<p>    disable all access to the disk before removing the disk.  <\/p>\n<p>    Enter name of disk group [,list,q,?] (default: list) <strong>newdg<\/strong>    <\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">  The requested operation is to<br \/>            disable access to the removable  <\/p>\n<p>              disk group named newdg. This disk group is stored on<br \/>            the  <\/p>\n<p>              following disks:  <\/p>\n<p>                   newdg01 on device<br \/>            c1t1d0s2  <\/p>\n<p>              You can choose to disable access to (also known as<br \/>            &quot;offline&quot;)  <\/p>\n<p>              these disks. This may be necessary to prevent errors<br \/>            if  <\/p>\n<p>              you actually remove any of the disks from the<br \/>            system.  <\/p>\n<p>              Disable (offline) the indicated disks? [y,n,q,?] (<strong>default<\/strong>:<br \/>            n)  <\/p>\n<p>            Continue with operation? [y,n,q,?] (<strong>default<\/strong>: y)  <\/font><\/p>\n<p>                <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">Removal of disk group newdg was successful.<\/font>              <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"> Disable another disk group? [y,n,q,?] (<strong>default<\/strong>: n)<\/font><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>                <\/p>\n<p align=\"left\"><font size=\"-1\"><\/p>\n<p><\/font><\/p>\n<h3 align=\"left\"><strong>2.10  <a name=\"Enable (online) a disk device\"><\/a>Enable (online) a disk device<\/strong><\/h3>\n<p align=\"left\">Disks which are turned offline by volume manager<br \/>, or which are to be imported can be enabled by this option. This operation causes disks to be scanned and find out the<br \/>disk belonging  to a disk group.<\/p>\n<p align=\"left\"><strong>Select menu item <\/strong> 10 (<font face=\"Courier New\" size=\"2\">Enable<br \/>          (online) a disk device<\/font>)<strong> from the <\/strong><br \/> vxdiskadm<strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Enable (online) a disk device  <\/p>\n<p>    Menu: VolumeManager\/Disk\/OnlineDisk  <\/p>\n<p>    Use this operation to enable access to a disk that was<br \/>  disabled  <\/p>\n<p>    with the &quot;Disable (offline) a disk device&quot;<br \/>  operation.  <\/p>\n<p>    You can also use this operation to re-scan a disk that may<br \/>  have  <\/p>\n<p>    been changed outside of the Volume Manager. For example, if a<br \/>  disk  <\/p>\n<p>    is shared between two systems, the Volume Manager running on<br \/>  the  <\/p>\n<p>    other system may have changed the disk. If so, you can use<br \/>  this  <\/p>\n<p>    operation to re-scan the disk.  <\/p>\n<p>    NOTE: Many vxdiskadm operations re-scan disks without user  <\/p>\n<p>          intervention. This will eliminate<br \/>  most needs to online a  <\/p>\n<p>          disk directly, except when the disk<br \/>  is directly offlined.  <\/p>\n<p>    Select a disk device to enable [<\/font><\/p>\n<address><font face=\"Courier New\" size=\"2\">,list,q,?] <strong>c1t1d0<\/strong>      <\/font>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Enable another device? [y,n,q,?] (<strong>default<\/strong>: n)<\/font><\/p>\n<p>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p><\/font><\/p>\n<p>          <\/address>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 align=\"left\"><strong>2.11  <a name=\"Disable (offline) a disk device\"><\/a>Disable (offline) a disk device<\/strong><\/h3>\n<p align=\"left\">This<br \/>option disables  all access to a disk  which is not part of<br \/>any disk group . This is used to remove disk from volume group. Some<br \/>systems do not support disks that<br \/>can be removed from a system during normal operation. On such systems,<br \/>the offline<br \/>operation is not very useful.  <\/p>\n<p align=\"left\">  <strong>Select menu item 11 (<\/strong><font face=\"Courier New\" size=\"2\">Disable<br \/>          (offline) a disk device) <\/font> <br \/>  <strong> from the <\/strong><\/p>\n<p> vxdiskadm <br \/>  <strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#dbdbdb\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Disable (offline) a disk device  <\/p>\n<p>    Menu: VolumeManager\/Disk\/OfflineDisk  <\/p>\n<p>    Use this menu operation to disable all access to a disk<br \/>  device  <\/p>\n<p>    by the Volume Manager. This operation can be applied only<br \/>  to  <\/p>\n<p>    disks that are not currently in a disk group. Use this<br \/>  operation  <\/p>\n<p>    if you intend to remove a disk from a system without<br \/>  rebooting.  <\/p>\n<p>    NOTE: Many systems do not support disks that can be removed<br \/>  from  <\/p>\n<p>          a system during normal operation.<br \/>  On such systems, the  <\/p>\n<p>          offline operation is seldom<br \/>  useful.  <\/p>\n<p>    Select a disk device to disable [<\/font><\/p>\n<address><font face=\"Courier New\" size=\"2\">,list,q,?] <strong>c1t1d0<\/strong>      <\/font>            <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">    Disable another device? [y,n,q,?]<br \/>            (<strong>default<\/strong>: n)  <\/p>\n<p><\/font><\/p>\n<p>          <\/address>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 align=\"left\"><strong>2.12 <a name=\"Mark a disk as a spare for a disk group\"><\/a>Mark a disk as a<br \/>    spare for a disk group<\/strong><\/h3>\n<p align=\"left\"> This   is used to reserve the disk as an automatic<br \/>    replacement disk ( hot-relocation) in case of  another disk in the disk<br \/>    group  fails. Hot-relocation  relocates redundant subdisks to<br \/>    other disks and restores  the affected volume manager objects and data. If a disk<br \/>    has already been designated as a spare in the disk group, the subdisks from<br \/>    the failed disk are relocated to the spare disk. Otherwise, any suitable<br \/>    free space in the disk group is used. <\/p>\n<p>  <\/p>\n<p align=\"left\">  <strong>Select menu item <\/strong>12 <strong>(<\/strong>Mark a <br \/>    disk as a spare for a disk group<strong>)<\/strong><strong> from the <br \/>    <\/strong>vxdiskadm<strong> main menu.<\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#d7d7d7\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Mark a disk as a spare for a disk group  <\/p>\n<p>    Menu: VolumeManager\/Disk\/MarkSpareDisk  <\/p>\n<p>      Use this operation to mark a disk as a spare for a disk<br \/>  group.  <\/p>\n<p>      This operation takes, as input, a disk name. This is the<br \/>  same name  <\/p>\n<p>      that you gave to the disk when you added the disk to the<br \/>  disk group.  <\/p>\n<p>    Enter disk name [,list,q,?] <strong>disk01<\/strong>  <\/p>\n<p>    Marking of disk01 in rootdg as a spare disk is complete.  <\/p>\n<p>        <\/font><\/p>\n<p>        <\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">Mark another disk as a spare? [y,n,q,?] (<strong>default<\/strong>:<br \/>  n)  <\/p>\n<p>        <\/font><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>    <\/p>\n<p align=\"left\">Any VM disk in this disk group can now use this disk as a spare in the <br \/>  event of a failure. If a disk fails, hot-relocation should automatically occur<br \/>    .The failed disk needs to be replaced.<\/p>\n<h3 align=\"left\">2.13 <a name=\"Turn off the spare flag on a disk\"><\/a>Turn off the spare flag<br \/>    on a disk<\/h3>\n<p align=\"left\">This  is used to remove  a VM Disk From the Hot-Relocation<br \/>    Pool &amp;  free hot-relocation spare disks for use as regular volume manager<br \/>    disks While a disk is designated as a spare, the space on that disk is<br \/>    not used as free space for the creation of volume manager objects within its disk<br \/>    group and this option makes this space available.<\/p>\n<p align=\"left\">  <strong>Select menu item <\/strong>13 <strong>(<\/strong>Turn off <br \/>    the spare flag on a disk<strong>)<\/strong><strong> from the <br \/>    <\/strong>vxdiskadm <strong>main menu.<\/strong><\/p>\n<p>      <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" bgcolor=\"#d7d7d7\">\n<tbody>\n<tr>\n<td>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"><\/p>\n<p>    Turn off the spare flag on a disk  <\/p>\n<p>    Menu: VolumeManager\/Disk\/UnmarkSpareDisk  <\/p>\n<p>      Use this operation to turn off the spare flag on a<br \/>  disk.  <\/p>\n<p>      This operation takes, as input, a disk name. This is the<br \/>  same  <\/p>\n<p>      name that you gave to the disk when you added the disk to<br \/>  the  <\/p>\n<p>      disk group.  <\/p>\n<p>    Enter disk name [,list,q,?] <strong>disk01<\/strong>    <\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\"> <br \/>        Disk disk01 in rootdg no longer marked as a spare disk.<\/font><\/p>\n<p align=\"left\"><font face=\"Courier New\" size=\"2\">   <br \/>        Turn-off spare flag on another disk? [y,n,q,?] (<strong>default<\/strong>: n)<\/p>\n<p>        <\/font><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>  <\/p>\n<p>After using the vxdiskadm for configuring disks and diskgroups<br \/>  next step is to configure volumes and then use them for storage operations .<br \/>  The second part of this article discusses this aspect  of volume manager<\/p>\n<p align=\"left\">&nbsp;<\/p>\n<\/div>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"<p>Petit tutorial sur Veritas VxVM, gestion du raid de VERITAS.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8],"tags":[],"class_list":["post-114","post","type-post","status-publish","format-standard","hentry","category-informatique"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pWrTo-1Q","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=114"}],"version-history":[{"count":0,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/114\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=114"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}