TDC-004 Veritas Volume Manager For Support Personel

Draft v 1

Removing disks from the DISKS category .................................................................................... 62 Placing disks under VxVM control ..................................................................................................... 6 Changing the disk-naming scheme ................................................................................................. 64 Discovering the association between enclosure-based disk names and 0s-based disk names......64 Installing and formatting disks....................................................................................................... 65 Displaying and changing default disk layout attributes ................................................................. 6 Adding a disk to VxVM...................................................................................................................... 65 To initialize disks for VxVM use................................................................................................... 66 Reinitializing a disk ........................................................................................................................7 Using vxdiskadd to place a disk under controt of VxVM .............................................................. 72 Encapsulating a disk....................................................................................................................... 73 To prevent the encapsulation failing, make sure that: .................................................................... 73 To encapsulate a disk for use in VxVM ......................................................................................... 7 Rootability ........................................................................................................................................... 77 Booting root volumes ..................................................................................................................... 78 Boot-time volume restrictions ........................................................................................................ 7 Mirroring an encapsulated root disk .................................................................................................... 79 To mirror your root disk onto another disk ................................................................................... 79 Defining alternate boot disks.......................................................................................................... 80 Removing disks................................................................................................................................... 8 To prepare your system for the removal of the disk ....................................................................... 81 To remove the disk from its dish group.......................................................................................... 81 Removing a disk with subdislts ...........................................................................................................82 Renaming a disk .................................................................................................................................. 83 Reserving disks .................................................................................................................................... 84 Displaying disk information ................................................................................................................ 84

.'

,
4 '

..

Module 5: .............................................................................................................................................. Administering dynamic multipathing (DMP).......................................................................................... How DMP works................................................................................................................................. How DMP monitors 110 on paths ................................................................................................... Path failover mechanism ................................................................................................................. 110 throttling ................................................................................................................................... Load balancing ................................................................................................................................ Dynamic Reconfiguration ...............................................................................................................

86 86 86 88 89 89 89 90 Using MPxIO with DMP................................................................................................................ 90

Booting from DMP devices ............................................................................................................ 90 Disabling and enabling multipathing for specific devices.............................................................. 90 Disabling multipathing and malting devices invisible to VxVM ................................................... 90 Enabling multipathing and making devices visible to VxVM ........................................................ 92 Displaying the paths to a disk ......................................................................................................... 93 Administering DMP using vxdmpadm ................................................................................................ 95 Retrieving information about a DMP node .................................................................................... 95 Specifying the 110 policy ................................................................................................................ 96

Module 6............................................................................................................................................... Creating and administering disk groups...................................................................................................

99 99

Specifying a disk group to commands .......................................................................................... 100 System-wide reserved disk groups............................................................................................... 100 Rules for determining the default disk group............................................................................... 101

Displaying the system-wide boot disk group................................................................................ 101 Displaying and specifying the system-wide default disk group................................................... 101 Displaying disk group information ............................................................................................... 102 103 Displaying free space in a disk group ........................................................................................... Creating a disk group.................................................................................................................... I04 Adding a disk to a disk group....................................................................................................... 105 Removing a disk from a disk group.............................................................................................. 105 Deporting a disk group................................................................................................................. 107 Importing a disk group................................................................................................................. 109 109 To import a disk group................................................................................................................. Renaming a disk group................................................................................................................. 110 Destroying a disk group................................................................................................................ 111

Module 7:............................................................................................................................................ 12 1 Creating and administering subdisks..................................................................................................... 112 I 12 Creating subdisks .......................................................................................................................... Displaying subdisk information .................................................................................................... 113
Moving subdisks........................................................................................................................... 1 4 Splitting subdisks.......................................................................................................................... 114 Joining subdisks............................................................................................................................ 1 15 Associating subdisks with plexes ................................................................................................. 115 . . Assoclat~ng subdisks............................................................................................................... 117 log Dissociating subdisks from plexes ................................................................................................ 117 Removing subdisks....................................................................................................................... 118

Module 8:............................................................................................................................................ I 19 Creating and administering plexes ......................................................................................................... 1 9 Creating plexes ............................................................................................................................. 1 19 Creating a striped plex.................................................................................................................. 119 Displaying plex information ..................................................................................................... 120 Plex states..................................................................................................................................... 120 Plexes that are associated with a volume have one of the following states: ..................................... 121 ACTIVE plex state....................................................................................................................... 121 CLEAN plex state......................................................................................................................... 121 121 DCOSNP plex state...................................................................................................................... EMPTY plex state......................................................................................................................... 121 IOFAIL plex state........................................................................................................................ 121 122 LOG plex state............................................................................................................................... OF= INE plex state...................................................................................................................... 122 SNAPATT plex state.................................................................................................................... 122 SNAPDIS plex state..................................................................................................................... 122 SNAPDONE plex state ................................................................................................................. 122 SNAPTMP plex state.................................................................................................................... 122 STALE plex state.......................................................................................................................... 122 TEMP plex state........................................................................................................................... 122 TEMPRM plex state..................................................................................................................... 123 TEMPRMSD plex state................................................................................................................123 Plex condition flags........................................................................................................................... 124 IOFAIL plex condition ................................................................................................................. 124 NODAREC plex condition ........................................................................................................... 124

NODEVICE plex condition .......................................................................................................... 124 RECOVER plex condition ............................................................................................................ 124 REMOVED plex condition ........................................................................................................... 124 125 Plex kernel states............................................................................................................................... DETACHED plex kernel state...................................................................................................... I25 DISABLED plex kernel state....................................................................................................... 125 ENABLED plex kernel state........................................................................................................ 125 Attaching and associating pleses...................................................................................................... 126 Taking plexes offline .................................................................................................................... 126 127 Detaching plexes ........................................................................................................................... Reattaching plexes ........................................................................................................................ 127 I28 Moving plexes.............................................................................................................................. Copying plexes ............................................................................................................................. 128 Dissociating and removing plexes................................................................................................ 129

. .. . .

. . ... ..

Module 9:............................................................................................................................................ 130 Creating volumes................................................................................................................................... 130 Types of volume layouts ............................................................................................................... 130 Supported volume logs and maps ................................................................................................. 131 Creating a volume ............................................................................................................................. 132 Advanced approach...................................................................................................................... 132 To create a volume using the advanced approach ....................................................................... 132 Assisted approach ......................................................................................................................... I32 Using vxassist .......................................................................................................................... 133 Setting default values for vxassist ................................................................................................ 134 Discovering the maximum size of a volume ................................................................................ 135 Disk group alignment constraints on volumes .............................................................................. 135 Creating a volume on any disk ..................................................................................................... 3 136 Creating a volume on specific disks...................................................................................... Specifying ordered allocation of storage to volumes................................................................... 138 Creating a mirrored volume.......................................................................................................... 141 Creating a mirrored-concatenated volume .................................................................................... 141 Creating a concatenated-mirror volume ....................................................................................... 142 To create a volume with an attached DCO object and volume ................................................... I42 Creating a striped volume ............................................................................................................. 143 Creating a mirrored-stripe volume ................................................................................................ 144 Creating a striped-mirror volume ................................................................................................. 144 Mirroring across targets, controllers or enclosures....................................................................... 144 Creating a RAID-5 volume ........................................................................................................... 4 Creating tagged volumes.............................................................................................................. 146 Creating a volume using vxmake ................................................................................................. 147 Creating a volume using a vxmake description file...................................................................... 148 Initializing and starting a volume ...................................................................................................... 149 Initializing and starting a volume created using vsmake ............................................................. 150 Accessing a volume ...................................................................................................................... 150 Module 10:......................................................................................................................................... 151 Administering volumes.......................................................................................................................... 151 Displaying volume information .................................................................................................... 151 153 Volume states....................................................................................................................................

. .

.
. .-

ACTIVE volume state.................................................................................................................. 153 CLEAN volume state.................................................................................................................... 153 EMPTY volume state................................................................................................................... 153 INVALID volume state................................................................................................................ 153 NEEDSYNC volume state............................................................................................................ 154 REPLAY volume state ................................................................................................................. 154 SYNC volume state...................................................................................................................... 154 Volume kernel states......................................................................................................................... 154 DETACHED volume kernel state ................................................................................................ 154 DISABLED volumekernel state............................................................................................ 154 ENABLED volume kernel state................................................................................................... 155 Managing tasks with vxtask .............................................................................................................. 155 155 vxtask operations.......................................................................................................................... Using the vxtask command........................................................................................................... 156 Stopping a volume............................................................................................................................. 156 Putting a volume in maintenance mode ............................................................................................ 157 157 Starting a volume ............................................................................................................................... Adding a mirror to a volume ............................................................................................................. 158 Mirroring all volumes ........................................................................................................................ 158 Mirroring volumes on a VM disk...................................................................................................... 159 Additional mirroring considerations ................................................................................................. 160 To create a mirror under any of these scenarios........................................................................... 160 Removing a mirror ............................................................................................................................ 161 Resizing a volume ............................................................................................................................. 162 Resizing volumes using vxresize .................................................................................................. 163 Resizing volumes using vxassist .................................................................................................. 164 164 Extending to a given length .......................................................................................................... Extending by a given length ......................................................................................................... 164 Shrinking to a given length ........................................................................................................... 165 Shrinking by a given length .......................................................................................................... 165 Resizing volumes using vxvol ...................................................................................................... 165 Setting tags on volumes ................................................................................................................ 166 Changing the read policy for mirrored volunes ............................................................................... 167 168 Removing a volume ...........................................................................................................................

Module 11:......................................................................................................................................... Administering hot-relocation ................................................................................................................. How hot-relocation works............................................................................................................ Partial disk failure mail messages................................................................................................. Complete disk failure mail messages ........................................................................................... How space is chosen for relocation ..............................................................................................

169 169 170 173 174 174 Configuring a system for hot-relocation ....................................................................................... 175 Displayingspare disk information ................................................................................................ 175 Marlting a disk as a hot-relocation spare...................................................................................... 176 Removing a disk from use as a hot-relocation spare.............................................................. 177 Excluding a disk from hot-relocation use..................................................................................... 178 179 Making a disk available for hot-relocation use............................................................................. Configuring hot-relocation touse only spare disks.......................................................................180 Moving and unrelocating subdisks ............................................................................................... 180 Moving and unrelocating subdisks using vxdiskadm ................................................................... 181

Moving and unrelocating subdisks using vxassist .................................................................... 182 Moving andunrelocating subdisks usingvxunrcl~ .. ............................................ 182 Moving hot-relocated subdisks back to their o r i g ~ i~ l ~ , ........................................... 183 Moving hot-relocated subdisks back to a different disk .............................................................. 183 Forcing hot-relocated subdisks to accept different offsets.......................................................... 183 Examining which subdisks were hot-relocated from a disk......................................................... 184 Restarting vxunreloc after errors ................................................................................................. 185 vxunreloc moves subdisks in three phases: .................................................................................. 185 Modifying the behavior of hot-relocation ..................................................................................... 185

... ...... .

Module 12:......................................................................................................................................... 186 Recovery From hardware failure............................................................................................................ 186 Listing unstartable volumes.......................................................................................................... 187 Displaying volume and plex states ............................................................................................... 187 188 Understanding the plex state cycle............................................................................................... Recovering an unstartable mirrored volume .................................................................................190 Recovering an unstartable volume with a disabled plex in the RECOVER state........................ 190 Forcibly restarting a disabled volume ........................................................................................... 191 Clearing the failing flag for a disk................................................................................................ 191 Reattaching failed disks................................................................................................................ 192 Failures on RAID-5 volumes ........................................................................................................ I93 System failures.............................................................................................................................. I94 Disk failures.................................................................................................................................. 194 Default startup recovery process for RAID-5........................................................................ 196 Recovering a RAID-5 volume ...................................................................................................... 196 Parity resynchronization ............................................................................................................... 197 Log plex recovery ......................................................................................................................... 198 Stale subdisk recovery .................................................................................................................. 198 Recovery after moving RAID-5 subdisks..................................................................................... 198 Starting RAID-5 volumes............................................................................................................. 199 Unstartable RAID-5 volumes....................................................................................................... 199 200 Forcibly starting RAID-5 volumes............................................................................................... Recovering from incomplete disk group moves........................................................................... 201 Module 13:......................................................................................................................................... 203 203 Recovery from boot disk failure............................................................................................................ Possible root, swap, and usr configurations .................................................................................. 203 Booting from alternate boot disks................................................................................................. 204 The boot process on SPARC systems........................................................................................... 205 Hot-relocation and boot disk failure............................................................................................. 205 Unrelocating subdisks to a replacement boot disk .......................................................................206 Recovery from boot failure........................................................................................................... 206 Boot device cannot be opened ...................................................................................................... 207 Cannot boot from unusable or stale pleses ................................................................................... 207 Invalid UNIX partition ................................................................................................................. 208 Incorrect entries in /etc/vfstab ...................................................................................................... 209 Damaged root (I) entry in Ietclvfstab ............................................................................................ 209 Damaged Iusr entry in Ietclvfstab ................................................................................................. 209 Missing or damaged configuration files....................................................................................... 210 Restoring a copy of Ietclsyste~non the root disk .......................................................................... 210

... ..... . .

Copy of letclsystem is not available on the root disk ................................................................... 211 Repairing root or Iusr file systems on mirrored volumes ............................................................. 212 212 Recovering a root disk and root mirror from backup tape ............................................................ 215 Re-adding and replacing boot disks.............................................................................................. Re-adding a failed boot disk......................................................................................................... 215 Replacing a failed boot disk ......................................................................................................... 216 217 Recovery by reinstallation ............................................................................................................ General reinstallation information ................................................................................................218 Reinstalling the system and recovering VxVM ............................................................................218 Prepare the system for reinstallation ............................................................................................. 219 219 Reinstall the operating system ...................................................................................................... Reinstall VxVM ............................................................................................................................ 219 219 Recover the Veritas Volume Manager configuration ................................................................... 221 Clean up the system configuration ............................................................................................... 221 Clean up Rootability ..................................................................................................................... Clean up Volumes......................................................................................................................... 221 Clean up Disk Configuration ........................................................................................................ 224 Reconfigure Rootability ................................................................................................................ 225 Final Volume Reconfiguration ..................................................................................................... 225 Start up hot-relocation .................................................................................................................. 226

Module 14:......................................................................................................................................... 227

Backing up and restoring disk group configurations ............................................................................. Backing up a disk group configuration ......................................................................................... Restoring a disk group configuration ........................................................................................... Resol~riny conflicting backups for a disk group ........................................................................... 227 228 229

230

Module 1: Understanding Veritas Volume Manager

VeritasTM Volu~ne Mauager (VxVM) by Syluautec is a storage mauagement subsystem that allows you to luauage physical disks as logical devices called vol~umes. VxVM volume appears to A applications w d the operatiug system as a pliysical disk partition device 011 which file systems, databases aud other lnaliaged data objects cau be collfigured. VxVM provides easy-to-use o111i11edisk storage luauagemeut for computing envirouments and Storage Area Network (SAN) environme~its.By s~lpportiug Reduudaut A m y of I~ldepe~idel~t (RAID) the Didis model, VxVM can be co~~figllredprotect agaiust disk aud hardware failllre, and to iucrease 110 to thoughput. Additionally, VxVM provides features that erhauce fault tolerance aud fast recovery fron~ disk failure. VxVM overcomes physical restrictious iiliposed by hard\vare disk devices by providiug a loyical voliune mauagelueut layer. This allows vol~ulues span multiple disks. to VxVM provides the tools to i~nprove performance aiid ensure data availability aiid integrity. You call also use VxVM to dyua~llicallyconfigure disk storage while the systel~i active is

VxVM and the operating system

VxVM operates as a subsystem betwee11your operating system w d your data mauagelueut systems, such as fde systelus and database ~nmagement systems. VxVM is tightly coupled wit11 the operatiuy system. Before a disk call be brought ituder VxVM co~~trol, disk 1u11stbe accessible thou& the the operatiug system device interface. VxVM is layered ou top of the operating system interface services, and is depeudent up011 how the operatiug systeul accesses physical disks. VxVM is depeudeut upou the operating system for the followiug fimctiouality: operatiug system (disk) devices
w device handles w VxVM dynamic multipathing

(DMP) metade\rice

This guide iutroduces yon to the VxVM colmauds wllic11 are used to cany out the tasks associated with VxVM objects. These c o m ~ u a ~ are s ~ d described on the relevallt ~nauual pages and in the cl~apters of this guide where VxVM tasks are described.

VxVM relies or1 the follo\vh~g coustautly-r~ruuiug daemons and ke111el threads for its operatiou: vxcodgd-The VxVM coifigi~ratioudaemou maiutaius disk and group conf g~~ratious 'aud comtllicates c o u i i g ~ ~ a t i changes to the kernel, and ulodifies coufigirration iufoilnation stored on on disks. vxiod-VxVM 110 kermel threads provide extended I10 operatious tvitltoot blockulg calliug processes. By default, 16 110 threads are started at boot t h e . and at least oue I/O thread most coutiuue to nru at all times.
m vxrelocd-The hot-relocation dae~nou inouutors VxVM for eveuts that affect reduudaucy. aud perfo~vls hot-relocation to restore reduudaucy.

I...

I;hangvr i n path fro^:: !.)MIi s!o(le r,> slor a)?:?art. au:cr~>~aticollv ci~~lcrit~!?~cd :~i~i~~laisrc~:l :i11t; ~

How data is stored

There are several ~netl~ods to store data ou physical disks. These methods organize data on the used is disk so the data can be stored and retrieved efficieutly. The basic method of disk orgal~izatiou called foiluatth~g. Fo~mattiog prepares the hard disk so that files can be wittell to aud ret~ieved from the disk storage pattern. by using a prea~~anged Hard disks are folmatted, m d ulfoi.lllation stored, usiug two metllods: physical-storage layout aud logical-storag layout. VxVM uses the logical-storage layout method. The types of storage layout supported by VxVM are introduced in this chapter.

How VxVM handles storage management

VxVM uses two types of objects to handle storage management: physical objects and virhlal objects. Physical objects-physical disks or other hardware with block aud raw operatiug system device iuterfaces that are used to store data. Vi~tualobjects-When one or 1110rephysical disks are brought under the coutrol of VsVM, it creates virtual objects called volumes on those physical disks. Each volume records aild retrieves data from one or more physical disks. Voliumes are accessed by file systems. databases, or other applications iu the same way that physical dislts are accessed. Volu~nes also con~posed other virtual objects are of (plexes aud subdisks) that are used UI cl~aanging voliune configuration. Vol~imes d their virtual the m compoueuts are called virtual objects or VxVM objects.

Physical objects-physical disks

A physical disk is the basic storage device (media) where the data is ultimately stored. You can access the data ou a physical disk by using a device ualue to locate the disk. The physical disk device name varies with the computer system you use. Not all parameters are used ou all systems.

Typical device names are of the foim c#t#d#s#, wbere: c# specifies the controller t# specifies the t a r g t LD d# specifies the disk s# specifies the partition or slice The following figure shows how a physical disk and device name (devname) are illustrated i this n docuineut. For example, device ilallle cOtOdOs2 is the elltire hard disk couuected to controller ui1~7ber 0 in the system, with a target JD of 0, and physical disk number 0. F'k.ysir?i disk exampie

Device discovery
Device discovely is the tenu used to describe the process of discovering the dislts that are attaclied to a host. This feature is importaut for DMP because it needs to suppo~t growing number of disk arrays a from a 1111mberof vendors. III conju~i~ctiou the ability to discover the devices attached to a host, t l ~ e wit11 Device Discovery service euables you to add support dy~~au~icallynew disk arrays. This operation, for which uses a facility called the Device Discovery Layer (DDL). is achieved without tlie ileed for a reboot. This meaus that you can dyllalllically add a new disk array to a host, and rm1 a command which scans the operating systenl's device tree for all the attached disk devices, aild recollfigu~res DMP wit11the new device database.

Enclosure-based naming
Enclosure-based ilalllii~g provides an alternative to the disk device 11a111iilg described in previous pages. This allows disk devices to be uaiued for enclosu~res ralher than for the co~~trollers througl~\vllich they are accessed. Iu a Storage Area Network (SAN) that uses Fibre Channel hubs or fabric switches, infonnatio~~ about disk locatioi~ prolided by the operating systen] 111ay not c o ~ ~ e c tu~dicate ly the physical location of the disks.

u For example, c#t#d#s# 11ami11gassigns controller-based device names to disks i separate enclosures allows VxVM to access that are co1111ectedto the same host controller. Enclosure-based nan~iilg enclosiues as separate pllysical entities. By configu~iing redimdant copies of yoiir data on separate er~closores, yoti c a l safegi~ard against failure of one or more enclosures.

Iu a typical SAN er~vironiuent, host conh.01le1.sare coiliiected to multiple enclosures in a daisy c l ~ a i or i~

though a Fibre C h a u ~ ehub or fabric switch as illustrated iu the following figure. l

..,. ........ ...., ... . .. ...., . . . , .

F ~ b rChannel hub r
br switch

MMMM

In such a coufiguration, enclosore-based namiug cau be used to refer to each disk witllin an enclosore. For example, the device llallles for the disks in euclosure encO are nalned enc0-0. encO-I. and so on. The maiu beuefit of this scheme is that it allows you to qidckly dete~lili~le where a disk is physically located in a large SAN configirration. Note: I11 illally advauced disk arrays, you call use hardware-based storage i l ~ a ~ ~ a g e ~tol represent l ei~t several physical disks as one logical disk device to the operatulg system. Iu such cases, VxVM also sees a single logical disk device rather thau its co~llpoueut disks. For this reason, when reference is made to a disk w i t h an enclosirre, this disk may be either a physical or a logical device. Another impoitaiit benefit of et~closure-based naming is that it enables VxVM to avoid placiug reduudant copies of data hl the same enclosure. This is a good t11ing to avoid as each e~~closure be call considered to be a separate fault domain. For example, if a mirrored volume were configured only on the disks in enclosirre encl, the failure of the cable betweell the hub and tlre enclosirre would lllake the entire volml~e unavailable. If required, you car) replace the default llallle that VxVM a s s i p s to an ei~closure with one that is more ~ u e a ~ ~ i ~to g f i i l coufigoratiou. ~ your In High Availability (HA) coufigurations. reduudant-loop access to storage can be implemented by collllectiug iudependent co~~trollers the host to separate hubs with iudepelldeut paths to the on enclosures as show11 iu the followiug figure.

Fibre Cl>ann!:l hubs or :v;itches

Disk en:lur.r~res

Such a colfig~~ration protects agaiilst the failure of oue of the host con&ollers (cl aud c2), or of the cable between the host md one of the hubs. lu this example, each disk is l i u o w by the same name to VxVM for all of the paths over which it call be accessed. For example, the disk device euc0-0 represents a siugle disk for ~ c two diffel,entpaths are liuowu to the operating system, st~ch h as clt99d0 and c2t99d0. To take accouut of fault domains when collfiguriug data redimdancy, you call coutl.ol how ~ n i r ~ o r e d volumes are laid out across enclosures.

Virtual objects
Vh-hlal objects in VxVM include the following: Disk groups VM disks Subdisks Plexes Volumes The couuectiou betweeu physical objects and VxVM objects is made when yon place a physical disk umder VxVM control. After iustalliug VsVM on a host system, you must briug the contents of physical disks tluder VxVM control by collecting the VM disks iuto disk groups and allocating the disk group space to create logical volumes. B ~ h g i u g contents of physical disks under VxVM control is accomplished ouly if VxVM takes the control of the physical disks and the disk is not tmder control of mother storage manager such as Sun Microsyste~ns Solaris Volt~me Manager sofhvare. VxVM creates vimral objects and makes logical col~uectiolls between the objects. The virtoal objects

are theu used by VxVM to do storage managemeut tasks. Note: The vxpiiut comlllaud displays detailed iufollilation on existu~lg VxVM objects.

Combining virtual objects in VxVM

VxVM vuhml objects are cooliibined to build volumes. The viihlal objects contaiued iu vol~unes VM are disks, disk groups, subdisks, aud plexes. Veritas Volu~ne Manager objects are organized as follows: VM disks are grouped iuto disk groups .Subdisks (each represeduig a specific region of a disk) are combiued to foivl plexes Voluines are composed of one or more plexes Manager virtual objects aud how The following figure shows the couuectious between Veiitas Volu~me they relate to physical disks. The disk group coutaiiis t h e e VM disks which are used to create two volulnes. Volr~me volOl is siniple aiid has a single plex. Vo111me vo102 is a luirrored volume with two plexes.
F7
I'. ,. .
L .

Yo101
I I

lV101-01

uolOl -GI

I disk01-01 I

i
i

disk0l-01

diskOl

i Disk grcltlp
~"..""w~.".\.". ,~A"~.,~"*"..." .~".~"~"~"~~A".

devna!:~;

Pl~ysical 1:lisks

The various types of vilhlal objects (disk groups, VM disks, subdisks, plexes and volu~nes) are desc~ibed the followiug sections. Other types of oljects exist in Veritas Volume Manager, such as ~I I data cl~ange objects (DCOs). aud cache objects, to provide extended fumctionality. These objects are discussed later ui this chapter.

Disk groups
A disli g o u p is a collection of disks that share a colnluou configuration. and which are managed by co~~figu~ration set of records with detailed info~~uation is a about related VxVM VxVM. A disk grou~p objects, their attributes, and their connections. A disk group name can be up to 31 characters long. 111releases prior to VxVM 4.0, the default disk group was rootdg (the root disk group). For VxVM to fimction. the rootdg disk grou~p to exist and it had had to contaiu at least one disk. This requiremeut uo longer exists. aud VxVM can work without ally disk groups co~~figu~red (althougl~ must set up at least one disk group before you call create any you vol~uues otherVxVM objects). of

Yon c m ~ create additional disk groups when yon need them. Disk groups allow yo11 to g o ~ disks into p logical collections. A disk group and its conipo~lents be moved as a unit fio111one host machine to can another. The ability to lllove whole voliunes and disks between disk groups. to split \vlvhole voluuues and disks between disk groups, and to joiu disk groups is provided by VXVM 5.0 Volunles are created withiu a disk group. A given volume and its plexes aud subdisks must be configured fiom disks in the same disk group.

VM disks
When you place a physical disk under VxVM control. a VM disk is assigned to the 1,hysical disk. A VM disk is under VxVM conh.01 and is usually in a disk group. Each VM disk conesponds to at least disk or disk partition. VxVM allocates storage fiom a contiguous area of VxVM disk one space.
A VM disk typically iucludes a public region (allocated storage) aud a small private region where VxVM internal colfigi~rationh f o ~ ~ n a t i o n stored. is

Each VM disli has a u~uque disk media name (a virtual disk name). You call either defme a disk name of up to 3 1 characters, or allow VxVM to assign a default name that takes the f011u diskg~.oup##, where diskgroup is the uame of the disk group to which the disk belongs. The following figure shows a VM disk with a media name of disk01 that is assigned to the pl~ysical disk devuame.

;Physir:al disk

Man ajea.1301 a x d s aa.g asn tre3 noh .a3eds aa.g s! ys!pqns

" 0

0" 1

dOII

s! let[) awds qs!p

'SySIpqnS rnd t v

(.ys!p IW!S<II~ arro 01 patG!sse s! ys!p NA a q l ) .sys!pql~saa.rql q l qs!p MV\ m o r [ s a11129Sqwonoj aql'qsIp ~ U J O SIIO!LIO~ aules ag) aregs .lo d e l ~ a ~ o )omre:, sys!pqns lnq 's>[s!pqus a[d!l111rn maloo3 me3 qsrp rn v

y Qrpqnsauo I ~ ~ I I ' Y~ % I ~ y h . ~

'[OqS!p pamen p!p

rn aq1 no p!pqus

1s.ry aqljo amen aq) s! ~o-loys!p'a.1114yS q w o n o ~ q ) q a

.sSuolaq ys!p at11 r p ! r p 01 dn0.15 qs!p aqljo amerr arlls! dno.Gqs!p a.rar[M '##-##d~~o.rZp!p ys!pqns e ,103amen IIuejap at11 pue ##dl~o.rSqs!p qsrp MA e JOJ amen quejap aqL s! s! .ys!p [e3!s.<rId e JO no!Sa.~q 3 a d s e 01 paddetrr s! I I ~ ! ~ M MA e JO IIO!UO~ 3gpads e slnasa.rda.1 .ys!p ys!pqns r13e3 'sys!pqns a,rorn .lo ano olm pap!,\!p aq rre3 ys!p MA v ,sys!pqns Zmsn a3eds qs!p sale3olI"AxA 'ys!p arl) no a ~ d s j jnrn e s! ?1301qv . s ~ o [ q S I I O I I ~ ! ~ ~ O ~)as e S! qs!pqu~sv o ys!p JO

Plexes
VxVM uses subdisks to build virtual objects called plexes. A plex collsists of one or more subdisks located on one or Inore physical disks. For example, see the plex volOl-01 shown in the following figure.

Plex with

t~vic::r ssubd~sks

You cau organize data on subdisks to foul11 a plea by using the follow in^ methods: co~~catenation striping (RAID-0) mi~~oring (RAID- I ) striping wit11 parity (RAID-5)

Volumes
A volume is a vi~?ualdisk device that appears to applications. databases, and file systems like a physical disk device. but does not have the pllysical limitations of a physical disk device. A volume co~~sists one or lllore plexes, each holding a copy of the selected data in the vol~une. of Due to its virtual nah~re, voluu~e uot restricted to a pallicular disk or a specific area of a disk. a is

The configuration of a volume can be changed by using VxVhl user interfaces. Co~lfigurationchanges can be accomplished witho~~t causing disruption to applications or file systeu~s are using the that volume. FOI.example, a vol~une be mirrored on separate disks or moved to use different disk cau storag. Note: VxVM uses the default naming conventio~ls vol## for volumes and vol##-## for plexes in a of volu~ne. ease of administration, yon cau choose to select more meani~lgful For nan~es the volumes for that yo11 create.

A \u~tuur: ,mn\

. .'rd under the followill%cotlstr>,~l..s:

Its name can , ~ L . . L I I ~ up to 3 1 characters. .It can consist of up to 32 plexes, eacln of which contains oue or more subdisks. .It mnst have at least o~ne associated plex that has a complete copy of the data in the volume with at least one associated subdisk. All subdisks w i t h a volume must belo~lg the same disk group. to

Note: You c w use the Veritas Intelligent Storage Provisioning (ISP) feature to create and a d ~ ~ ~ i n i s t e r applicatiou volumes. These volumes are very siuular to the traditional VxVM volumes that are described in tllis chapter. However, there are siqifica~lt diffel.ences between the fiunctionality of the t. . I (\,pes of volume that pre\.ent them fiom being used i~nterchangeably.Refer to the Veritas Storage : I.ui~itd:~iiou Iutelligent Storage Provisioning Ad~~ilistrator's Guide for more ulfonnation about creating and adllliuistering ISP application volumes.

IIIthe following figure, volume volOl has the following characteristics:

It contains one plex named vo101-0 1. The plex contaius one subdisk nn~ned disk01-01. w The subdisk disli01-01 is allocated fiom VM disk disk0l.

vo10 1-01

'!., : ~ I u ~ G viith \<

~IQX

:s~!js!.~aps.rer~:, o l l o j aq1 seq 9010~ m n [ o ~ Sw a

Module 2: Volume layouts in VxVM

A VxVM virtual device is defined by a volume. A volume has a layout defuied by the associati011of a volume to one or Inore plexes. each of which map to subdisks. The voltume presents a virtual device iuterface that is exposed to other applicatious for data access. These logical building blocks re-map the volume address space tl~l.ougIi u c h 110 is re-directed at run-time. d

Differeut v o l ~ u ~layouts each provide different levels of storage service. A volume layout cau be le configlu.ed and recolfigmed to ~ilatcli yal-ticdar levels of desired storage sen ice.

Iln plementation of non-layered volumes

Iu a uou-layered volume, a subdisk is restricted to ~nappiug directly to a VM disk. Tlus allows the subdisk to defme a contiguous extent of storage space backed by the public region of a VM disk. When
active, the VM disk is diiectly associated with at1 lmderlying physical disk. The combination of a voltime layout and the physical disks therefore dete1.1iunesthe storage service available from a given vi~-tual device.

Implementation of layered volumes

A layered volunle is colistri~cted ~iiapping sttbdisks to u~iderlying by its \;olumes. The subdisks in the

underlying volumes must nlap to VM disks, and hence to attached physical storage. Layered volt~nles allow for more coiiibi~latio~ls logical compositions, solne of which inay be of desirable fox cofigl~riug vu-tual device. Became pei.luitting fiee use of layered volt~mes a th~,ougliot~t the couunand level would have resulted in lmwieldy adillinish.ation. solne ready-made layered volume cotlfigurations are designed illto VxVM. These ready-made configurations operate with built-ul rules to automatically match desired levels of is service within specified coustrahts. The automatic cod~gul.ation done on a "best-eff01-t" basis for the cuweut command hvocatio~i working against the culrent coutig~uration. To achieve the desired storage service fiom a set of v u h ~ adevices, it iilay be necessary to include an l appropriate set of VM disks into a disk group, aid to execute nl~iltiple coufiguration commands. To the extent that it can. VxVM handles i~iitial configi~ratioii on-line re-co~lftgul.ationbit11 its set of and layouts and admiuistration interface to ~uake job easier and Inore detennhustic. this

Layout methods
Data iu virtual objects is organized to create volr~mes using the following layout methods: by Collcate~latio~~ spanniug and Striping (RAID-0) Mhroriug (RAID-I) Striping plus mirroring (mi~rored-stripeor RALD-O+l) Mirroring plus striping (striped-minor. RAID-1+0 or RAID-10) RAID-5 (striping with parity) The following sections describe each layout method.

Concatenation and spanning

Collcatenatio~l lllaps data hl a linear lllanllei onto one or more sr~bdislis a plex. To access all of the hl data i a co~lcatellated u plex seqoentially, data is first accessed in the first sltbdisli from begimiug to end. Data is then accessed in the remaining subdislis sequentially fro~om begiuuing to end. until the end of the last subdisli. The subdisks UI a collcatellated plex do not have to be physically contiguous and can belong to more than oue VM disk. Concatenation using subdislis that reside on more thau one VM disk is called spanuing.

The followiug figwe sl~ows coucate~~atio~i subdisks from the saule VM disk. The blocks n, the of two u+l, n+2 and n+3 (numbered relative to the start of the plex) are contiguous on the plex, but actually colue from two distinct subdislis on the same physical disk.

diskol-Ul

Data in

Data in cEisk01-03 Data blocks

Phys~cal disk

Tl~e remaiuiug free space iu the subdisk, disk01-02. 011 VM disk, diskO1, can be put to other uses. subdisks when there is ins~~fficient contiguous space for the You c w use concatenation with ~ll~rltiple plex on any one disk. This folu~ concatenation can be used for load balmciug between disks, and for of head movelllellt optiulizatiou on a particular disk.

.saw .ralllo ot tud aq tw3 ~ o y s ! p qs!p KA no Z O - Z O ~T S !P ~ I I S at[) ~nmuds aay 8rr!rr!etra.r aqL S!~

Striping (RAID-0)
Stripiug (RAID-0) is useful if you need large amounts of data witten to or read from physical disks, and perfo~uiance iuiportalt. Stripung is also helpfill in balaucing tlie VO load from molti-user is applicatious across multiple disks. By using parallel data transfer to aild from multiple disks, stripiug siguificwtly improves data-access perfol~nauce. Shipiuz maps data so that the data is interleaved among two or more physical disks. A striped plex contaius two or more subdisks, spread out over two or more physical disks. Data is allocated alte~uately and evenly to the subdisks of a striped plex. The subdisks are grouped into "colu~ilus."with each physical disk limited to olie colomn. Each collunn coutahns one or more subdislis and call be derived from one or Inore physical disks. The number and sizes of subdisks per columu call vary. Additional sobdisks can be added to colmm~s, necessaly. as Cantion: Stripiug a volmne, or splitti~ig volume across lll~~ltiple a disks, iucreases tlie chance that a disk failure will result in failure of that volume.
If five voluines are striped across the sainie five disks. then failure of any one of the five disks will require that all five vol~uines restored froui a backup. If each vollime is on a separate disk, only one be volume has to be restored. (As a alternative to stiiphig, use m i ~ ~ o r i n g RAID-5 to substantially n or reduce the cliauce h a t a single disk failure results in faillwe of a large nlumber of volu~mes.)

Data is allocated h equal-sized tunits (swipe units) that are i~lterleavedbetween the colmmls. Each n stripe uuit is a set of coutig~~ous bloclis on a disk. The default stripe w i t size (or width) is G4 liilobytes.

For example. if there are three colu~~nus a striped ples aud six stripe wits, data is striped over tile iu t h e e colums, as illustrated iu followiug figwe.

Stripe I Stripe 2

SU = stripe unit

A sh-ipe co~~sists the set of shipe 111lits the sallle positious across all coiumns. h the figure. stripe of at L I I U ~ S 2, and 3 co~lstittite single shipe. 1, a

n Viewed i sequence, the fust stripe cousists of:

stripe uuit 1 iu coluuuu 0 stripe unit 2 i col~llnu1 n stripe mut 3 iu c o l u m ~ ~ 2

The secoud stripe co~lsists of:

stripe ~mit iu colu~lll~ 4 0 shipe uuit 5 ill coiul~nn1 stripe uuut 6 iu c o l u m ~ ~ 2

Stl.ipiilg coiitiill~es the length of the colunuis (if all c o l u m ~ are the s a u e length), or until the elid of for s k the shortest columu is reached. Ally space remaining at the end of s ~ ~ b d i s inslonger coltuuns becomes urnused space. The followiug figwe shows a striped plex with t h e e equal sized, single-subdisk columus. There is one col~unu physical disk. This example shows t h e e subdisks that occupy all of the space on the VM per disks. It is also possible for each su~bdishn a striped plex to occupy oiily a poi-tioii of the VM disk, i which leaves free space for other disk ma~iagement tasks.

. ..

Stlipe units
, ," ,X .I
," ,
, ,

,.*... ~. . .\

,...

, ,

, .

~.\<, . ,.

-..

Column 2 Striped l:~lex

S~.rlsdkks

VM disks

dis kD3

Physitxf disks

'sys'p WA !na.Iag!p mog syslpqns melno:, osla nag strum103 .(pasaa.~:,ys! x a ~ d arpjo az!s arpj! 'aldmsxa ~ o j ys!p .Iarpous m o g .lo ys!p amss attljo sno!8a.1 pa.~ajj!p mog a x d s a!s:,o~ls o! alq!ssod osla ) s! 11 . S S O pad!.r!s Brl!aq sys!p UA aqljo tpsa mo.g ys!pqns al8ms s 'on!su Lq pa~aa.~:, m:, saxald .~ aq padl.11~ 'ys!p ~s:,!sLqd ad rrrunlo:, ano s! a.laq1 .sys!pqnsjo .Iaqnrlin lua.rag!p s su!s!noo nmnlo:, q3sg 'sazls !na.lagpjo syslpqns Sn!rr!sjr103 sum11lo3aa.ni) 1 l 1 xald pad!qs s saqs.qsnlp a.mSg SU!MO~~OJ1 ~ ag

.atrrnlo~\ paletrajsotroo-pa.ro.~tm parma) s s! arrmloi\ at[) 'palsoaleonoo [la a.ts d a r l l j ~ 'attnilo,\ ad!.r)s-pa.rorr!nr s pam.lal ~l!)ss! anlnloA arlj 'pad!.qs s! ano Lpoj! ua;\a .pad!.r~s.lo palenajsonoo aq us3 .IO.LIFs II! sasald slep aqljo ad& jnoLel a t n

.anmioh ad!.~ls-pa.~o.rrp alea.ro 01 amnloA ames aql 01 s . ~ o . ~sep e r paqosue als 'sys!p aa.rql sso.r3e padrrls [pea 'saxald OMJ a l a r p aldrosxa m s ~ o r l a.111SgZtyqloj arlL s q s ! p a)e.tsdas m0.q pa)soo[paq jsntn S.IO.LI!~pus xald padt.4~ 'ayjoajja aq 01 Srt!d!.r)s a,\oqs B m . ~ o . ~JOJ s]! arli ty

.anrnloi\ parmeds .lo pad!.rls s j o (&!g!qel!e~e p m ) ,Q!~qega.~y ano.~dnr! Smro.u!ra .lap!snoo plnoqs uob a 04 &qS!tl.A1qsuosuaars! Brr!l!y sys!p Is.rahas j o luo anojo pooq!laT!l aqj asneoaa .alqssllml xald a.l!lua arl) aynn uao sqs!p asotl)jo atlo Ane j o a.m[!g 's-\~s!p ,raqmnrl aBra1 u s s 0 . r ~ jo Srr!trwds .LO Brt!d!.~js n a r m

.s.ro.rrpt papagem1 aqj Sn!sn ajslado 01 sa11m)noo nwrsZs arll jnq 'a1qq!b\srn1 samooaq qs!p p a l y aq) no xald aq) 'aml!ej qs!p p!sLqd e ~ Inaha o ag) "1 a[,:1110.\ q pat~!s)ao:, rlo!)erruojn! aqj aleo!ldlip o) (saxaid) s . ~ o . ~a[d!llnrrl sasn E~II~IO.LI!N ry

.mt~oloo rpea jo paalsu! Klpr~p!,\!pn! pa.lo.Lrp1 aq [re:, ys!pqr~s rpea .m~rnloo sxs!pq~ls .[ad ald!llnm ale a.IatgjI .ad!.~)sarlljo rrrrm~oo rlosa s.ro.rpm So!d!.rls Molaq BII!.IO.L~~ Brl!~li~ 'l110be[ .ro.Lv - p a d ~ e palla3 s! 1noXel pamqrno3 s!ru .SII?IO.LI!~~I Srqdys j o no!letnqmo3 aq) s ~ o d d ~ ~ sx ~s aAoqe ~

( O I - ~ I W o + r - a m '-lo-lr!w-pady~s) -lo %U!~!JJS snld %u!.Io.J.J!~

'no!leoola.r -joq Lq JO Llle~lnenr .~ar[l!a'paoe1da.r naaq seg ystp p a p j js.11~ a.rojaq p q ys!p pnooas e p111oqs at11 . r a ~ ~ l Q o ~ l ~ Ino sli1c1 Sn!aq 04 alquaarrllu a.loru s! arrrnlo~y ?a ~~~o adgs-pa~orr!m s 'Llleno!l!ppv .pa.rahooa.t nn nl ~ n a arnnloh aqljo rro!&rod e All10 'paoelc1a.1S! ys!p aqj rlarm .K3nep1mpa.r sasol amnloh x ~ . ,%: 'parpelap acl jst ~ ! ~ I S11!le3 aq) L ~ U'O IS! 111oKe[ .~o~l!ur-pad!qs s p q e at11 , -ar...-,.. . . . , : I : J ~ ~ I I S e aye) rle:, xald aqlna aql S m . r a ~ o ~ .alep oj dn p1Suo.rq aq 1s11m aa ys!:: ... . , ; xal': a.IyL!:; 'r*aql'La.l s! qs!p aql [ l a m 'anllqoh a.r!~rra avl rro Lonepnnpa.1Sursol Lqa~ar~j slap 'xa~d a.qna ne saq~elap lnoLel adys-pa no.^^ e n ys!p e j o a.ll~,!cj 'a.111Zg B~++io~~oj m m o q s s v ! aqj aql
3T :: 7.

RAID-5 (striping with parity)

Note: VxVM supports RAID-5 for private disk groups. but not for shareable disk groups in a cluster of environment. I11 additiou. VxVM does not support the m i ~ ~ o r i u g RAID-5 volumes that are configl~redusing Veritas Volume Mauager software. Disk devices that support RAID-5 in hardware may be l u i ~ ~ o r e d .
Although both mirroriug (RAID-1) a ~ l d RAID-5 provide red~mdaocy data, they use different of methods. Mirrolvlg provides data redundancy by maintaiuiug luultiple colllplete copies of the data UI a volume. Data being written to a minored volt~me reflected in all copies. If a pol-tiou of a luil-rored is v o l i ~ ~fails. the system continues to use the other copies of the data. ~le RAID-5 provides data redundatlcy by using parity. Parity is a calculated value used to reconstruct data after a failure. Wlde data is being witten to a RALD-5 volume, parity is calculated by doing au excll~sive (XOR) procedure on the data. The reslllting parity is then written to the voli~ue. OR The data and calculated parity are contained in a plex that is "striped across llli~ltipledisks. If a portion of a RAID-5 volume fails. the data that was 011 that portion of the failed volume call be recreated from the remailling data and parity infolmation. It is also possible to mix concatenation and striping in the layout. figure shows parity locations ul a RAID-5 amay collfiguration. Every stripe has a The followi~~g col~um~ contaiuing a parity stripe nuit aud c o l i ~ ~ m ~ s contail~illg data. The parity is spread over all of the disks in the array, reduciug the write time for large independe~lt wites because the writes do not have to wait until a single parity disk call accept the data.

use RAID-5 volumes can additioually perfolul logging to uliuilnize recovery time. RAID-5 volu~ues RAID-5 logs to keep a copy of the data aud pxity curreutly beiug written. RALD-5 logging is optio~~al aud call be created alor~g wit11 RAID-5 v o l ~ m ~ or added later. es

.az!s ~ e n b a j o o) smo.1 p w 'smnnlo3 syslp aq 11" sar!nba.r Ks.rre~o adb) s!rl~.no os pus 'sys!p 0 M O arl) sso.13ead!.~pp.r!q) ail) naq) '[ hiox m syslp ~ arI) sso.13e ad!.~lspoo2as ail) crag) '0 MOX m sys!p ail) ss0.13e ad!.qs )s.~g Zi~!KlddeKq paqs!ldmo33e ail) s! Zu!d!.qs .awlllo3 .lad SMOJ a,rotn B q p e K ~ L M O spoddns a.mpn.qs de.ue leoo!)!pe.q s u q IB

.. . .
~

.Kerre g - m 1wo!)!pe.u a j o )rramaSue.rra trmnlo3 pne MO.I s ~ o q am89 S n ~ o l l oarK .ad!.qs ,Q!.~ede j o t p p p 1111~ troddrls 03 aq) s j aq) K.ressa3an syslp j o .raqmnn leirmrp aql s! ,NO.[v 'Ke.na atp m oo!l!sod leo!p.ro amas arp n pa)s3o[ syslp ! j o laqtunu a s! tmm[o3 y .snmnIoo pne sMor II! paz!neZ.ro sys!p [s.ra.\as s! Ke.~raS-rn 1mo!)!pe4 v

.safiqo1!~91 s! az!s Inn1 ad!.qs lIItqap arll ' E - ~ .IOJ .rrrr~~tloo ,103pasti ale sl!rrn ad!.rls pazls-lertbg .snrntiloo aq) W qoea JO 11final arll ,103 no os prle 'lerll Molaq ad!qs .1arllorw Bn!hldde rrarll 'rnrrtiloo rpea 30 do1 aql le ys!pqtts q3w sso,roe a d y s ls.rg arp fmL1dde bq palrrarr~aldrn! fmd!.rl~'L~essaoan s m r ~ ~ i ~ o o pappe s! se arllol aq neo sys!pqtis leno!l!ppv 'syslp [eo!sdr~dlua.rag!p rr1o.g pai\rrap aq rwo nunqoo nai\!B e LI! sys!pqtis aqL ~sys!pqtisjo.raqmnu lna.Iag!p e j o ls!snoo 01 x a ~ d - m q o rmuiloo qoea sMo[[e I / ~ A X A s

2 edr11~ F ailyi~

ys!p 1230 ea.w og!oads e slnasa.1da.r ys!pq~tsrloq .a.rtiZg BII:NO[~OJ IF m o q s se sys!pqtis r@rra[ alqe!.Iei\jo fn!~s!snoo aql smmiloo sasti m x , j 'puaalsq .si\zo.t asti Ion saop ~ x , 'spafqo .Iaqjo pne sys!p ss,!jo altijerI1"'4"!~aql j 01 a n a .a.rtqotulrls leno!l!peq aqj ~xrog srajyp . l a B e ~ m ~ aurnIoA sel!.raA n artwnrjs Lena S-W ! aqL

Left-symmetric layout
There are several layouts for data and parity that L , I ~ Ibe used in the sehlp of a RMD-5 array. The illlple~ne~ltatiou RAID-5 UI VsVM uses a left-symmetric layout. This provides optillla1 performance of for both raudom 110 operatious aud large sequential I/0 operatious. However, the layout selectio~l is as are ~s not as critical for perfo~lna~~ce the nmnber of c o l u m ~ aud the stripe unit size. Left-syuuuetric layout stripes both data aud parity across coluuu~s, placing the parity iu a different col~uuu every stripe of data. The fust parity stripe twit is located iu the ~ight~nost l u u of the fnst for co stripe. Each successive parity stripe twit is located in the next stripe. shifted left one co1tu1111 from the previous parity stripe ~nlit locatiou. If there are more stripes thau CO~LUIIIS, parity stripe uuit the placement begins ~ I the rigl~truost I colul~lu agaiu. The following figure shows a left-symmetric parity layout with five disks (one per column).

Parity stripe unit

1 For each stripe. data is organized startiug to the right of the parity stripe unit. I 1 the figure, data orgauizatio~~ the first stripe begins at P and contiuues to stripe ~mits for O 0-3. Data orgauizatiou for the seco~ld stripe begins at PI. then conti~lues stripe ~ u u4. and on to stripe muts 5-7. Data organization to t proceeds iu this manuer for the renlahliug stripes. OR on Each parity stripe unit contains the result of an exclosi\~e (XOR) operation perfo~lned the data in the data stripe uuits \iithin the same stripe. IFone coltumn's data is h~accessible to hardware or due software failure, the data for each stripe call be restored by XORing the conteuts of the re~uaiuing col~unus data stripe units agaiust their respective parity stripe twits.

For example, if a disk co~respondulg the whole or part of the far lef column fails. the volurne is to placed iu a degraded mode. While i degraded mode. the data fiom the failed col\~ruu be recreated u cau by XORiug stripe uuits 1-3 agaiust parity stripe uuit PO to recreate stripe ~ulit theu XORiug stripe 0, mlits 4, 6 , aud 7 agaiust parity stripe unit P1 to recreate stripe uuit 5, and so ou.

RMD-5 logging
Loggiug is used to preverlt corru~ption data during recovery by immediately recording changes to of data and parity to a log area on a persisteut device such as a volume on disli or UOII-volatile RAM. The uew data and parity are the11 witten to the disks. Without loggiug, it is possible for data not iuvolved ul any active writes to be lost or silently col~i~pted if both a disk iu a RAID-5 volume aud the system fail. If tlus double-failure occi~rs. there is no way of knowiug if the data being mitten to the data portious of the disks or the parity beiug written to the have actually been witten. Therefore, the recovery of the cor~upted may be disli parity po~-Iions corrupted itself. The following figtire illr~strates RAID-5 volulne co~lfigi~red a across three disks (A, B aud C). Iu this volume. recovely of disli B's co~lllpted data depends on disk A's data aud disk C's parity both being complete. However, only the data write to disk A is complete. The parity write to disk C is incomplete. which would cause the data OII disk B to be reconstructed inco~rectly.
tfatn write

Completed
/,. - .

parity 'b,5-i . ~:rrite E'-......\.

" -Ji

Inr:omplete

--.

... . .
---.
.........................

__

-..

._I,-__-- __-

This failure can be avoided by logging all data and parity writes before comulitti~lgh e ~ n the allay. t to 1 1 tllis way, the lo? call be replayed. causing the data aud parity updates to be completed before the 1 recoustructior~ the failed drive takes place. of Logs are associated with a RAID-5 volume by beiug attached as log plexes. More thau one log plex can exist for each RAID-5 volume, iu which case the log areas are ~nirrored.

Layered volumes
A layered v o l m ~ ~ ea virtual Veritas Volu1111eManager object that is built on top of other voluu~es. l ~ e is T layered volume strl~chlre tolerates failure better aud has greater redu~i~dancy the stwdard volml~e thau struch~re. example, iu a striped-mhror layered volume, each miiror (plex) covers a smaller area of For storage space, so recovely- is quicker than with a standard mirrored vol~une.
The following figure illustrates the struct1u.e of a typical layered voliuue. It shows subdisks with two colullms, built on ulnderlyilg volumes with each vol~uue iuteiaally miirored. The voltume and striped plex iu the "Managed by User" area allow you to perfollu nolual tasks iu VxVM. User tasks cau be pelfolmed only on the top-level volume of a layered vollune.

-. -

Striped pled

Subdlsks on
VM disks

Ui~derlyiug volumes in the "Managed by V x V M area are used excll~sively VxVM and are not by desigued for user manipulation. You c m o t detach a layered volume or perfoiu any other operation on the utlderlying voluiues by manipnlatitlg the iutemal stru1cttu.e. You call perfom all necessary operatious h the "Mauaged by User" area that iucludes the top-level volume and striped plex (for example, resiziug the vol~ull~e, changing the col~u~un width. or addiug a coluuu~).

System a d n ~ i s t r a t o r call mauipulate the layered vol~ume s structure for troubleshootiug or other operations (for example. to place data ou specific disks).

Volume resynchronization
When storing data ~.edunda~ltly usu~g and i~li~vored M I D - 5 volumes, VxVM ensures that all copies or of the data match exactly. However, uuder cel-taiu conditioas (usually due to coil~plete system failures), c or some redundant data ou a vol~ume w become lllco~lsisteut unsyucl~ronized.The minored data is not exactly the same as the original data. Except for uoimal coufigu~rationchauges (such as detachiug aud reattacling a plex), this c w ouly occur when a system crashes while data is being witteu to a volun~e. Data is witten to the mirrors of a volou~e parallel, as is the data and parity iu a RAID-5 volume. If a iu system crash occurs before all the iudividual writes coulplete, it is possible for some w-ites to complete while others do not. This can result iu the data beco~ning ~~i~syuchroiized. ~ ~ l i ~ v ovolumes, it call For red cause two reads fiom the same region of the voluine to retuiln differeut results, if differeut minors are used to satisfy the read request. hl tlie case of RAID-5 volumes. it cau lead to parity co~luptiou aud i~~correct recoi~struction. data VxVM needs to ensure that all minors contaiu exactly the same data and that the data aud parity iu RAID-5 volumes agree. Illis process is called voluille resy~~chrouization. volumes that are part of For the disk g o u p that is automatically imported at boot time (osually aliased as the reserved system-wide disk group, bootdg). the resyi~chrouization process takes place when the syste~n reboots. require resynchronization after a systeiil failure. Volumes that were never witten or Not all volull~es that were quiescent (that is. had no active 110) when the systeul failure occnned could not have had outstaudiug writes and do not require resynchouizatio11.

Dirty flags
VxVM records wheu a volulne is f i s t witteu to and ~narlis as dirty. When a volu~ne closed by all it is processes or stopped clea~lly the adu&istrator, aud all wites have been completed, VxVM removes by the dirty flag for the volume. Ouly volumes that are marked dirty whel~ system reboots require the resyucln.o~~izatiou.

Resynchronization process
The process of r e s y n c l r o a t i o n depends on the type of voliume. M I D - 5 volumes that contaiu RAID5 logs can "replay" those logs. If IIO logs are available, the \~olume placed in reco~~struct-recovery is mode and all parity is regenerated. For milrored volumes, resynchrouizatio~is done by placiug the volu~ne recovery Inode (also called read-witeback recovery mode). UI Resynchrouization of data in the voluu~e done iu the backgound. Tlis allows the \lolume to be is available for use while recovery is takiug place. The process of resyncluouizatiou can impact system perfoilnance. The recovery process reduces some of this unpact by spreading the recoveries to avoid stressing a specific disk or controller.

For large volmnes or for a large n~mlber volumes. the resynchrouizatio~iprocess cau take t h e . of These effects can be addressed by ~isiug dirty region logging (DRL) and FastResync (fast minor respcluo~~izatiou) ~uirroredvolmues, or by ens111-ing RAID-5 volu~nes for that have valid RALD-5 logs.

Dirty region logging

Dirty regiou loggiug (DRL), if euabled, speeds recovery of ~ n i ~ r o r e d vol~umes after a system crash. DRL keeps track of the regious that have chauged due to I/ 0 writes to a minored \volume. DRL uses this iilfo~rnatiouto recover only those portions of the volume that need to be recovered. If DRL is not used and a system failure occurs, all mirrors of the volumes must be restored to a consisteut state. Restoratiou is doue by copying the full contents of the volmne between its minors. This process can be lengthy and 110 uitensive. It may also be uecessaly to recover the areas of volu~nes that are already consistent.

Dirty region logs

DRL logically divides a volu~ue a set of cousecutive regions, and maultaius a log ou disk where into each regiou is represented by a status bit. This log records regious of a volulne for which writes are pe~~dulg. Before data is witteu to a region, DRL sy~ichrono~lsly marks the co~respondu~g bit iu status the log as dirty. To euhance perfonuance, tlie log bit remains set to dirty uutil the region becomes the to least recently accessed for wites. This allows wites to the same region to be witten i~umediately disk if the region's 10s bit is set to dirty.
Ou restarting a systen~ after a crash, VxVM recovers oulg those regions of the volume that are marked as duw i the dirty region log. u

Log subdisks and plexes

DRL log s~~bdisks the dirty region log of a m i ~ ~ o r e d store volume that has DRL enabled. A volume with DRL has at least oue log s~tbdisk:multiple log subdisks can be used to ~ n i ~ theodirty region log. ~ r Each log subdisk is associated with one plex of tlie volume. Only one log subdisk can exist perplex. If tlie plex coiltauis ouly a log subdisk w d uo data snbdislis, that plex is refelred to as a log plex. The log subdisk can also be associated with a regular plex that coutaius data subdisks. III that case, the log subdisk risks becoming uuavailable if the plex must be detached due to the failure of oue of its data subdislis. If the vxassist colluuand is used to create a dirty region log, it creates a log plex contauliug a single log subdisk by default. A dirty region log can also be set up manually by creating a log subdisk and associatbg it with a plex. The plex then contains both a log and data subdisl\s.

Sequential DRL
Soule voliumes, soch as those that are used for database replay logs, are witten sequentially and do uot benefit fiom delayed cleaning of the DRL bits. For these volun~es. seq~re~~tial can be used to limit DRL the nuunber of di~ty regions. This allows for faster recovery should a crash o c c ~ ~ r . However. if applied to volumes that are witten to randomly. sequ~e~ltial can be a perfo~~l~ance DRL bottleneck as it lunits the uumber of parallel writes that can be canied out.

Data volume configuration

The recovery takes place when the database software is started, not at system stalhlp. This reduces the overall impact of recovery wheu the system reboots. Because the recovely is coutrolled by the database, the recovery t h e for the voluuue is the resilveru~g time for the database (that is, the t h e required to replay the redo logs). Because the database keeps its o w l logs. it is uot necessary for VxVM to do loggulg. Data voluuues should be coufigiured as mil-rored volumes without dirty region logs. h addition to iu~proviug recovely time, this avoids any rmrtune 10 overhead due to DRL. and i~l~proves 1 nonnal database write access.

Redo log volume configuration

A redo log is a log of chauges to the database data. Because the database does uot main tau^ cchmges to the redo logs, it c m o t provide iufo~nlatiouabout mluch sections require resilvering. Redo logs are also w.itte11sequentially, w d siuce traditioual duty region lops are most useful with r,udo~nly-written data. they are of ~niui~nal for reducing recovery time for redo logs. However. VxVM call reduce the use number of duty regious by u~odifyiug behavior of its dirty region logging feature to take advantage the of seq~~ential access pattems. Seqi~eutialDRL decreases the amouut of data ueediug recovely w d reduces recovery t h e unpact ou the system.

The e1111ancediuterfaces for redo logs allow the database software to infoml VxVM when a volume is to be used as a redo log. This allows VxVM to modifj the DRL bel~avior the volume to take of advaiitag of the access pattems. S u ~ c e unproved recovery t h e depends on d i ~ t y the regiou logs, redo DRL. log voliunes shodd be configured as muyored volumes with seqi~eutial

FastResy nc
Note: You ueed a Veritas F l a s l ~ S ~ ~ a FastResyuc license to use this feature. or p

The FastResync feature (previously called Fast Mirror R e s y ~ ~ c h o ~ u ~ a t iFMR) perfo~ms or o n quick and efficient resyuchronizatio~of stale llli~rors mil-ror that is not synchronized). This illcreases the (a efficiency of the VxVM s ~ ~ a p s lmechanis~n. i~llproves perfo~mance operations such as ~ot aud the of backup and decision ssuppo~t applications. Typically, these operations requke that the volume is qi~iescent, that they are not in~peded updates to the volome by other activities ou the system. and by

To achieve these goals. the si~apshot mechanis~u VxVM creates all exact copy of a primary volume in at an instant in time. After a snapshot is taken, it call be accessed independently of the volu~mefrom wluch it was taken. h~ a clustered VxVM envirom~~ent shared access to storage, it is possible to with elimiuate the resolute contention and perfoivlance overhead of using a snapshot snnply by accessing it fiom a different node.

.... . ... .

FastResync enhancements
FastResyllc pro\lides two fulldamental euhaucemeuts to VxVM: FastResync optunizes ilrkror resynchrouizatioi~by keeping track of updates to stored data that have . been llussed by a m u ~ o r(A mirror may be uuavailahle because it has been detached from its volmne, either automatically by VxVM as the result of a11 error, or directly by an adlniuistrator using a utility such as vxplex or \rxassist. A returning m i ~ ~ is r inil~or was previously detached and is in the oa that process of beiug re-attached to its oligi~~al volume as the resnlt of the vxrecover or vxplexatt operation.) When a mirror returns to service, only the updates that it has missed need to be re-applied to resynclno~lize This requires much less effort than the traditioi~al it. method of copying all the stored data to the retuiuiug mi~+or. Once FastResync has been enabled on a volume, it does not alter how you administer murors. The ouly visible effect is that repair operatiol~s conclude more quickly. FastResync allows you to refresh and re-use snapsl~ots rather than discard them. You can q ~ ~ i c krely plexes with tl~eir original voluuues. This reduces the system overhead associate (snapback) s~lapshot required to perfo~m cyclical operatiom such as backups that rely on the sllapshot functionality of VxVM.

Non-persistent FastResync
Non-persistent FastResync allocates its c h a u g maps iu memory. If uon-persistent FastResyilc is euabled, a separate FastResyuc lnap is kept for the origu~al volume and for each snapshot volume. Unlike a dirty region log (DRL), they do not reside on disk nor UI persistent store. This has the advantage that updates to the FastResync map have little impact OII 110 perfo~luance,as no disk updates needed to be perfollued. However, if a systeul is rebooted, the ii~fo~il~ation map is lost, ~ I the I so a full resynchronization is required on snapback. This limitation can be overcome for volumes in cluster-shareable disk groups. provided that at least one of the nodes iu the cluster remained r u u ~ i n g to preserve the FastResyuc map in its memory. However, a node crash iu a High Availability (HA) enviroment requires the full resynchronization of a ufiror when it is reattached to its parent volmne.

FastResync limitations
The followiug limitations apply to FastResync: .Persistent FastResync is supported for RAID-5 volumes. b i t this prevents the use of the relayout or resize operations on the volume while a DCO is associated with it. .Neither nou-persistent nor persiste~~t FastResync call be used to resyucllronize mu-rors after a system crash. Dirty region logging (DRL). which can coexist with FastResync. sl~ould used for this purpose. be hl VxVM 4.0 and later releases, DRL logs may be stored in a version 20 DCO volume. .When a subdisk is relocated, the entire plex is marked "dilty" and a fill1 resynchonization beco~nes necessary. .If a snapshot v o l i ~ n ~ esplit off iuto another disk groitp, non-persistent FastResync caunot be used to is resynchro~lize snapshot plexes with the original voluule when the disk group is rejoiued with the the original volmne's disk group. Persistent FastResy~lc must be used for this pmpose. .If yo11 move or split an origiual volulne (011 which persistent FastResync is enabled) into another disk group, aud then move or joiu it to a snapshot volu~ne'sdisk group. yoit calu~ot vxassists~~apback use to resynchonize traditioual snapshot plexes wit11 the original volume. This restriction arises because a snapshot volume references the original volu~ne its record ID at the time that the snapshot volume by was created. Moving the original volume to a different disli group cl~anges volmne's record ID. and the i~d so breaks the association. However, iu such a case, you call use the vxplexsuapback c o i m ~ ~ awith the -f (force) optiou to perf01111the snapback. Note: This restriction ouly applies to traditional snapsl~ots. does not al~ply illstant snapshots. It to .Any operation that c h a ~ ~ gthe layout of a replica volume can mark the FastResync cha~lge es map for that snapshot "dim" and require a fit11 resynchonizatio~~ ditriug snapback. Operatiolls that cause this include subdisk split. sobdisk move, aud odiue relayout of the replica. It is safe to perfoin~ these operations after tlle snapshot is completed. For more information, see the vxvol(1M). \xassist(lM), and vxplex (IM) manoal pages.

.a~rlerr~roj .raUaq t l l p sarrrlllo.\ IIO sjep .rasn pns 'L3asprnipa.r .raQ!q q j p samnloA lad rro palojs aq ~11103 elepalam taa1sLs a19 'aldtnwa .log 'sarrmloi\ SmLl.rapml ar[)jo s3!)s!.raj3s.1sq3 Qq!qq!we ptle a311~u~roj.1ad lrla.~ajj!parpjo asn jsaq ayerrl 01 stnalsLs alg snzo~ls anqeaj s ! q ~' ( s ~ x A ) rrra)sLs a[!$ sel!raA o) )nama~uarpa amu~o,\-!l~lim s$rodd~isanqeaj las anlnloA aqL ')as amloA at[) aqjjo sa~g.ra)n! arl) B!A papanp s! sarrmlo~ 011 Bn!Lpaprni aql 01 prre rnog 1 1 .jga!qo ls3!Bol ~ alBn!s I? Lq pa)nasa.tda.~ 01 samuIoA le.la,\as ~ o l l ~ l e q ~ 01 ~ r r a m a ~ w qne a slas amiloA aq t ~ ale

.alq!ssame nlema.1 ys!p arlljo sno!$~odpal3ajjsr11iat11 r10 SarnliloA Btm)s!xg 'pale3ola.1s! ys!p arlljo no!$rod p a p g atp no e)ep lueprnipa.1 '(qs!p e no sysrpqlis amos Lpo Smt3ajje aml!q s 's! lsrl]) s.111330a.lul!q ys!p ls!$red e u a m

.n!e8e alq!ssame marl4 say" pns a.nq!q aq) a.rojaq pals!xa lsql spa[qo ag) sl3u.1lsno3a.1 naql I/VAXA 'd11o.18qs!p aql 11!q)p awds aay .ro/pue s p p a x d s se pajetB!sap sqsrp 01 pa)e3ola.1ale sqs!pqm arll .sqs!pqns pal3ajje arp sale3ola.1pne s~3aFqo s a m p q O/I spalap m no x .s]3afqo asorp 01 ssa33e prle L311epmipa.1 aJ0)sa.l pne I / V A X / (samnlo,\ S-rn . 1 0 . ~ sl3aFqo 1n Z .IOp a ~) Ir1eprmpa.r no sanq!q O/I 04 L ~ ~ W ! ] W I O ) I ~ uralshs e I 01 ~ ~ E ~ . smone )eql a.114~aj s! no!le301a,r-)o~ e

Module 3: Veritas Volume Manager Installation

Preinstallation Instructions
Symantec product licensing
This product includes a License Key certificate. The certificate specifies the product keys aud the number of product lice~~ses purchased. A siugle key lets yon iustall the p r o d ~ ~ou the number and type ct of systems for whicll you purchased the license. A key may euable the operation of more products thau are specified 011 the certificate; however, yon are legally limited to the uumber of product liceuses purchased. The product installatiou procedtue describes how to activate the key. If you eucouuter problelns while lice~lsulg product, visit the Synlautec licensing support website at: this

The VRTSvlic package enables product licensing. After the VRTS\:lic is installed, the followhlg c o m r u ~ d and their rnal~oal s pages are available on the system: vxliciust Iustalls a license key for a Symantec product vxlicrep Displays c u ~ ~ e n tiustalled licenses ly vxlictest Retrieves features aud their descriptions encoded in a liceuse key E\ren tl~ough other products are iuclnded on the et~closed software discs. you call only install the Sy~nantec o h a r e products for which you have purchased a license. s

Supported Solaris operating systems

Veritas Storage Fouudation cau ouly be iustalled ou a system nuu~ing Solaris 8 (32-or G4-bit). 9 (32-or 64-bit), or 10 (64-bit). I~lstalli~lg product on any other Solaris release will fail. If necessary, this upgrade So1al.i~ before you iustall the Veritas products.

/opt directory
The directo~y /opt 111ust exist, be witable and ~uust be a sylnbolic l i d . W ~ e n not 1.1~:r:'adi~;. v7i: . ' not te~nporarily converted by the upgrade- .st.. : script 4 1 be unavailable d u ~ i i ~ g , th: you have a symbolic l i d from /opt to one of the uuconverted volumes, the syulbolic liuli will 1101 fiuctior~ during the upyrade and itelus i /opt will not be installed. n

Environment variables
Most of the couuuauds used in the installation are ill the Isbill or /usr/sbi~~ directory. However, there are atidilional variables ueeded to use the Veritas Storage Fou~~dation product after installation. Add the followiuy directories to your PATH environment variable:
w If you are using Bou~ne K O Ishell (sh or ksh), use the commands: or ~

$ PATH=$PATH:/usr/sbin:/opt/VRTS/biu:/opt/VRTSvxfs/sbi~~:\

loptNRTSob/bu~:/optNRTScvs/bi~~:/etc/~i~~
$ MANPATH=/usr/share/man:/opt/VRTS/man:$MMATH $ export PATH MANPATH

If you are usullg a C shell (csh or tcsh). use the co~nmands: % set path = ( $path /usr/sbin loptNRTSvxfslsbiu \ loptNRTScvs/bu~ loptNRTSob/biu 1optNRTSlbi11/etc/vs/bi~~ ) % setenv MANPATH lusrlsI~arel~uan:/optNRTS/n~an:$MMPATH Note: If you are not installin&an HA prod~~ct. can onlit loptNRTSvcsl bin. you

Veritas Volume Manager requirements

Malie sure you meet all Vol~une Mwager-related requireineuts before installiug or upgradiug a Veritas Storage For~rllldatiou product or Veritas Vololne Manager.

Taking a disk inventory How to select disks

Decide wllicl~ disks you waut to place nuder VxVM coutrol. The other disks in your collfigmation are not affected. Disks may be brought under VxVM control iu two ways: Eucapsulated disks-Data iu all existiug file systeins and pa~titious the disk are preserved. on Iuitialized disks-Data on the disks is removed.

Verifying disk contents

Verify the disk couteuts. Auswer the followiug questions and list the data for your coi~venieuce. 1 Make sure yorl are aware of the coilteuts of each disk. Deteil~liile whicl~ dislis call be encapsulated (data is preserved) or iuitialized (data is removed).

2 Do you waut to place the system root disk rulder VxVM colltrol?
3 Do you want to either encapsulate or iuitialize all disks on a coutroller together? Ideutify the coutrollers (for example cOtOd0). 4 Ideutify the disks to be encapsulated, iuitialized. 01.excluded.

5 Verify that the disks that are to be ei~capsnlated VxVM have two free paititioi~s a by and recollunellded ainount of 32MB of free space. The free space must be at the begiiming or end of the This space is used for storiilg disk group coufigr~rations a aud disli aud most not belollg to a pa~titiou. disk label that ensores VxVM call ideutify the disk. eveu if it is moved to a different address or and recovely. The boot coutroller. It is also used to keep track of disk coilfig~~ratiou to ensure co~rect disk is a special case. If uo other space is available, VxVM attempts to allocate space usually resewed for swap by sluiuliiug the swap pa~titiou. This process is knonu as swap relocation and, ifuecessaiy, happeus automatically durillg root disli encapsulation.
Note: Although it is possible to put disks with uo fiee space rmder VxVM coutrol. tllis is oilly used as a illigratioil strategy. Many VxVM capabilities based on disk identity are available oilly for disks with the required free space. See the vxdisk(lM) luaur~al page for iufo~lnation11 the 1lop1-i~ type. 0 disli

6 If you are encapsulating the boot (root) disk:

.-.. .,. a: Before encapsulating your boot disk, set the EEPROM variable osenvramc? to true. This will enable VxVM to take advantage of boot disk aliases to identify the minor of the boot which disks are disk if a replacen~eutis needed. If this variable is set to false. yon must dete~mine bootable yourself. Set this variable to true as follows:
# eeprom "use-n\,ra~l~c?-tr~~e''

If your root disk is conuected over fabric, you should chech the Hardware Compatibility List at htp://support.v~i~itas.coiu see if your device type is supported for boot encapsdatiou to
b: Use the p~hrtoc(lM) o m a u d to record the layout of the paltitions on the ~meucapsdated c boot disk (/de\l/rdsWcOtOdOs2 in this example):
# prtvtoc /dev/rdsli/cOtOdOs2 Record the output froin this c o m a u d for fi1tl11.e reference.

c: To encapsulate the boot disk, tag the swap paitition as swap so that it is possible to duliilp to that partition later. See foivlat(lM) for infonnatioi~ taggiug the s ~ v a p on paltitio~~.
Note: If the path to an aliased boot device is different from the path i the / devices directory, aliases u may not f~u~ction coirectly. This inigl~t happen if the pathame is iuco~~ectly entered at the command line, or if the device's patllualue changes at a later date.

DMP and Alternate Pathing

Note: The iufolvlatiou
UI

this section only applies if yolk are runuiug Solaiis 8.

VxVM 5.0 does uot allow Dyuamic Moltipathing (DMP) to co-exist wit11 Sml's Alternate Pathiug (AP) s o h a r e . The AP driver must be disabled before iustallii~g upgrading VxVM. or

Array Support Libraries (ASL)

VxVM provides suppol? for new disk airnys iu the f o m of Anay Suppoi? Library (ASL) software packages. You cau obtain ASL packages from: The VxVM release package OII the software disc The disk alray provided by the vendor The Velitas Teclu~ical Su~ppol? l~~tp://s~rl,port.veritas.com site,

Veritas Enterprise Administrator

Veritas Storage Foimdatiou must l iustalled aud riun on a UNTX (Solaris) machiue. The Veritas x Enterprise Administrator (VEA) client can be iustalled aud run on any Solaris. Wiudows XP, Wiudows NT, Wiudows ME, Windows 2000, or Windows 98 machine that soppol+s the Java Rimtime Envuomeut. Veritas Enterprise Adluiustrator (VEA) is required to access the graphical user interface (GUI) for Veritas Storage F o ~ ~ u d a t iYou tau use the GUI to adllliuister disks, volumes, file systems, and o~~. database fimctio~~ality local or remote m a c h e s . on One of the followiug needs to be iustaUed aud rilluiug on the client:
m VERITAS Eute~prise Administrator (VRTSobgiii, VRTSat. VRTSpbx. and VRTSicsco) These are the client packages for Solaris and are located iu the prodoct-uame/pkgs directory.

VERlTAS Ellte~yrise Aduul~istrator Windows (\~~indo\vs\VRTSobglli.msi) is the client for This package for Windows. See the Veritas Storage Foundation Release Notes for patch infonuation before you iustall VEA.

Checking minimum requirements

The following are miuimu~n system recoumendatious for the GUI: Solaris SPARCstation 5 with 64M memory Windows XP, NT. Me, 2000, 01.98 300MHz Peutiiilu with 256M lneuloiy For the VEA client to fimctiou properly with the Java Rimtime Environment 1.5 (JRE 1.5). iustall the latest patches for JRE 1.5. To obtaiu patch infol~~lation, the Sun Microsystems Web site. see

VMSA and VEA co-existence

If you do not plan to use VMSA to admillister otl~el. (pre-VxVM 3.5) maclines, then you shodd i~lliustall VMSA before iustalliug VEA. You c w later do a client-ouly illstall if you want to rim the VMSA client ou your macl~iue. Note: 1 1 e release of VEA that ships wit11 VxVM 5.0 is not compatible with VMSA. the previous Veritas Volome Mwager GUI. Yo11 cannot run VMSA with VxVM version 5.0. If you do not remove VMSA, the following wartliug appears d~iriup reboot: a

About the operating system

If patcl~es the Solaris operating system are required, the patches shoi~ld applied ju.,, to be
,d

iustalliug the Ve~itas products. Patches may be required to resolve Solaris kernel, product perfo~mance, or other issues.

Mounting the software disc

Yoiu l1111sthave superuser (root) privileges to load the Veritas software.

1 Log hl as superuser.

2 Place the Ve~itas software disc containing your product into a DVD drive connected to yoiu system
3 If Solaris voluule mauagemeilt software is r u u n i ~ ~ g your system. the sofhvare disc ai~to~natically on inoiults as /cdrom/cdromO.
4 If Solaris voli~ine managemalt software is not available 10 Inotult the DVD, you must mount it

mauuall y. After inserting the software disc, euter:

# mouut -F hsfs -0 ro /de\ddsli/cOt6dOs2 /cdrom where cOt6dOs2 is the default address for the disc

drive.

Installing using the product installer

The prodt~ctinstaller suuplifies the process of installing Veritas software and Veritas stroogly recouuuends this method of u~stallation. iustaller euables you to configirre the product, verify The preiustallation requirements, and view the product's descriptiou. Select a prod~~ct install fro111 the product installer menu to iuvoke the product installatiou script. to

Note: If you obtained a Veritas product from an electro~lic download site, the single product dowuload files do not c o ~ ~ t athe product installer, so you must use the product iustallatiou script to install the in prodnct.
At most poiuts during an installation, you call type b ("back") to retom to a previoos sectioil of the installation procedme. The back feature of the installation scripts is context-sensitive, so it returns to the begumiug of a grouped sectioil of questions. If an iustallatiou procedure hangs. use Control-c to stop aud exit the program. There is a short delay before the script exits. Euteiyrise The following sample procedtue is based on the installatiou of a Veritas Storage Fotu~dation HA cluster with two nodes: "hostl" aud "host2." If yo11are u~stalling stand-alone systeins ouly, on some steps are mmecessaiy. and these are indicated. Default responses are enclosed by parentheses. Press Retiurn to accept defaults.

To install a Veritas Storage Foundation product

1 h~sert product software disc into a DVD drive attached to y o ~ u the system and mount it .

2 Move to the DVD directory: # cd icdromdcdrom0

3 From the this directo~y, invoke the i~~staller script:
# ./il~staller(to iustall using ssh)

or # ./iustaller -rsh (to install using rsh)

4 Enter I to iustall a product and press Rehun to begin.

5 Wlleu the list of available products is displayed, select the product you want to install and cuter the cor~espondiug number and press Retiinl. The product installati011 begins automatically.
6 You are prompted to enter the syste~ns names (iu the following example. "hostl" and "host?") which the software is to be iustalled. Euter the systen~ i~ame names and then press Rehuu. or filler the .rj:1:rtenl 11or17e.r se1~or.utetf spaces on il~liich Lg. to in.rtall l ~ r o d r ~ c t ~ ~ ~ a i i i e : host1 hosl2
7 Enter the product licel~se ilfioiu~atioi~.
01 1

Enter. a p r o h i c l nu~ne Iicerlse kej,,/i,iIiosll: /?/ .C~W-.C\:Y\':CYKY-..LYY~-.CY.Y.Y-.KCLYYYY ,YX,Y,Y-~LY-~YXY,Y-.i~i~~Y-.LCCY-.LKLY-.Y sl~ccav.,li~l!~. re,oi.s/ei~ec/ ho.r/l on
Do j.0~1 i~~criit ei11er.onolher. license kej;~'~.,/i)i. /J..II,(J,?] lo ho.r/l? (17)

Do j.021 11~c1nt enler ono/l~er. 1 0 license kej>,/br. O S I ZI?. , I I , ( ~(11) ~ / .?] Enter n if you have no further license keys to add for a system. You are then prompted to enter the keys for the next system. Note: Each system requil-esa p r o d ~ ~license before installatio~~. ct License keys for additioual product features should also be added at this time.

.. . .-.

: S ~ o l 1 0aqlol el-s lndlno aas plrioqs uoL j 'aldtr~exa .mn]ax ssa~d llelsrr! o] ] I I ~ M .IO.J pne iioX no!ldo q31q~ ]palas .rro!le[[e)sn!.loj pa.nc1ba.1 awds ys!p aql sXelds!p no!]do rpeg .sa%ey3ed ro saSey3ed pa.rrnba.~ lie bpo ~IQSII! .caq)!a 01 asooq:, m 3 IIOA 8

Installing the Veritas Enterprise Administrator client

If yoii plai~ l m ~ VEA clie~~t. must install the VRTSobgiii, VRTSat, VRTSpbx. and to the you VRTSicsco packages 011 the machine you are planuiug to use. By default. the VRTSobgui, VRTSat. VRTSpbx. aud VRTSicsco packages are iustalled when you illstall a Veritas Storage Foui~dation product. You ouly need to install the packages manilally if yoti are iustalliug on a machine other thau the server.

Installing on Solaris
To illstall the VEA clieut on a Solaris m a c b e usiug pkgadd

I Log hl as siperilser (root).

2 First, check to deteilniue whether the VEA client package is already installed.

This colnlnaud will rehuu VRTSobgiii if VRTSobgui is already iustalled. It will return uothiug if the package has not beeu installed.

3 To iustall the VEA client package for Solaris, iusert the appropriate 111edia disc iuto your system's DVD-ROM or CD-ROM drive.

4 Copy the VRTS0bgui.tar.g~pacliage, and the dependent packages (VRTSat. VRTSpbx, aud VRTSicsco) to the c ~ i i ~ eworkiug directory on your system. ut

5 Decompress the packages, a d then extract the coutents.

6 Use the pkgadd c o ~ m n w d iustall the packages. to

Answe~ questions, as the iustallatiol~ ally proceeds.

UI

the following order, to allow for depeudeilcies.

7 The VEA client packaze for Solalis, and dependent packages, are iustalled.

Installing on Windows
The VEA clieut rLms on Wiudows NT, Wn~dows Windows 2003, Windows 2000, Wu~dows XP, ME, Wii1dows 98, w d Wiudows 95 luacl~iues. you plan to rLm VEA froln a Wiudows machu~e, If ulstall the optional Wiudows package aftel you have iustalled the VEA serve1 on a Sola~is maclliue. Before yo11 iustall VEA ou a Wu~dows luachhe, you must tuuinstall ally existing Veritas Volume Manager Storage Adnillistratoflh' (VMSA) packages and remove the old sehip.exe fiom that machine. Ouly oue VEA package cau be installed ou a Wiudows machine at auy giveu time. be Note: If you plau to install the GUI clieut on Windows NT 1.0, Wiudows Installer 111~ist upgraded to version 2.0. For more infonnatiou about upgrading Windows Installer, visit II~~~:!'/\vLLZV.II~~CI~OSOC~.COI~~. If you are i~siug Wiudows NT 4.0, it is also reco~mne~lded you use Windows NT 4.0 Service Pacl~ that 6. I

Module 4: Administering disks

This chapter describes the operations for managing dislis used by the Veritas Voliu~ne Mauager (VxVM). This includes placing dislis ~mder VxVM control, iuitializiug disks, encapsnlatiug disks, minoring the root disk. and removiug aud replacing disks. Note: Most VxVM colmands require superuser or equivalent privileges.

Disk devices
When perfoivliug disk administratim. it is inlportant to imderstaud the difference between a disk name and a device naine. When a disk is placed uuder VxVM control, a VM disk is assigned to it. You call define a symbolic disk name (also l i ~ l o w a disk media name) to refer to a VM disk for the purposes of adllliuistration. as A disli name can be up to 3 1 characters long. If yo11 do not a s s i p a disk name. it defaults to diskgroup## where diskgroup is the i~allle the disli group to wllich the disk is beiug added, and ## is of number. a seqi~ence Your system nlay use device uaules that differ fiom those given in the esanlples. The device name (sometimes refelred to as devname or disli access uame) defines the ilame of a disli device as it is I ~ I I O W ~to the operating system. Such devices are nsi~ally. uot always. located in the ~ but Idevl[r]dsli directories. Devices that are specific to hardware fi0111certain vei~dors inay use their o w path tlaille con~et~tions. VxVM recreates disk devices. iucl~tdii~g from the Idevl[f]dsli directories. as inetadevices iu the those Idevlvxl[r]dmp directories. The dynamic multipatlling ( D m ) feature of VxVM uses these n~etadevices (or DMP nodes) to represent disks that cau be accessed by more than one physical path, i~sually via different coutrollers. The nilinber of access paths that are available depends on whether the disk is a single disli. or is part of a multiported disk away that is connected to a system. You call use the vxdisk utility to display the paths su~bsumed a inetadevice, and to display the stah~s by of each path (for example. whether it is enabled or disabled).

Disk device naming in VxVM

Prior to VxVM 3.2, all disks were named according to the c#t#d#s# naming folliiat used by the operatiug system. Fabric mode disks were not supported by VxVM. From VxVM 3.2 onward, there are two different methods of llalnillg disk devices: c#t#d#s# based naming Endosure based na~ning Note: Disk devices coutroIled by MPXIO are always iu fabric iuode (ilrespective of their hardware ~ o ~ g i ~ r a t i oau d .are therefore uamed in the enclosure name folmat. This is true for both naming i) schemes.

c#t#d#s# based naming

In this namiug scheme, all disk devices except fabric mode disks are named using the c#t#d#s# foiluat. The syntax of a device name is c#t#d#s#, where c# represents a controller 011 a host bus adapter. t# is the target controller ID, d# identifies a disk on the target controller, and s# represents a paltiti011 (or slice) on the disk. Note: For non-EFI disks, the slice s2 represents the entire disk. For both EFI and non-EFI disks, the entire disk is ilnplied if tlie slice is omitted from the device name. The boot disk (which contains the root file system and is used when bootiug tlie system) is often identified to VxVM by the device name cOtOd0. Fabi-ic mode disk devices are named as follows: Disk iu supported disk alrays are nanied using the enclosure name-# foi~uat. esa~iiple, For disks in the supported disk array name FirstFloor are named FirstFloor-0, FirstFloocl, FirstFlooc2 and so 011. (You cau use the vxdmpadm colu~uaud adlniuister enclosi~re to names.)
w Disks it1 the DISKS category (JBOD disks) are named nsiug the Disk-# forniat.

a Disks i the OTHER-DISKS category (disks that are not multipatlied by DMP) are named ilsu~g u tlie fabric-# fonnat.

Enclosure based naming

Enclosu~re-basednaming operates as follows: Devices with very long device names (for example, Fibre Cliailuel devices that ulclude worldwide name ( W N ) identifiers) are always represented by e~~closure-based naines. All fabric or non-fabric disks in suppoi-teddisk arrays are nanled usiug the enclosure-na~ne-# format. For exaiuple, disks in t11e suppol-teddisk ai-ray, enggdept are ~lanled enggdept-0. euggdept-l , enggdept-2 w d so ou. (Yo11 cau use the vxdmpadm c o ~ ~ u u w dadminister e~~closure to nalues. Dislis in the DISKS category (JBOD disks) are nained using the Disk-# format. Disks in the OTHER-DISKS categoiy (disks that are not multipathed by DMP) are named as follows: Non-fabric dislis are ila111ed t i s i ~ ~ g c#t#d#s# fom~at. the Fabric disks are uaiiied using the fabric-# fomlat. To display the native OS device names of a VM disk (such as mydgO1). use the followiug command:
# wdisk path I egrep diskname

Private and public disk regions

Most VM disks have two regions:
private region

A small area where co~lfigurationinfoin~ation stored. A disk header label, is co~dguratio~~ records for VxVM objects (such as volui~ies, plexes and subdisks), log and au u~tent foi the collfigtlration database are stored here. The default piivate region size is 32 megabytes. which is large eilouph to record the details of VxVM objects iu a disk group. several thousai~d Under most circtuustwces. the default private region size should be sufficient. For adlniuistrative puiyoses, it is usually much simpler to create more disk groups that co11tai11fewer volmues, or to split large disk groups into several smaller ones. If required. the value for the private region size ]nay be overridden when you add or replace a disk using the vxdiskad~li coi11111a11d. Each disk that has a private region holds an entire copy of t11e configuration database for the disk group. The size of the configuration database for a disk group is limited by the size of the smallest copy of the colfigtu.atiou database on ally of its nie~iiber disks.

public region

AII area that covers the remainder of the disk, and which is used for the allocatioi~ storage space to st~bdisks. of

..

A disk's type identifies how VxVM accesses a disk, and how it manages the disk's private and piblic regions. The following disk access types are used by VxVM:

simple sliced nopriv

The pitblic and private regions are on the same disk area (wit11 the public area following the private a~ea). The pu~blic private regions are oil different disk pa~titions. and There is no private region (only a pu~blic region for allocating si~bdisks). Tllis is the sin~plest disk type consistii~g only of space for allocating subdisks. Soch dislcs are no st usefud for defining special devices (such as RAM disks, if supported) ou wllich private region data woold not persist behveen reboots. They can also be used to encapsolate disks where tliere is insofficient room for a private region. The disks cannot store configination and log copies, and they do not sitpport the use of the vxdiskaddregio~~ collunand to define reserved regions. VxVM callnot track the lnoveii~ei~t nopriv disks of on a SCSI chain or between controllers. When the vxconfigd daemon is started, VxVM obtains a list of h o w disk device addresses from the operating system and configores disk access records for thein automatically.

auto

Auto-collfiguured dislts (with disk access type auto) support the followiug disk foimats:

cdsdislc

The disk is fo~natted a Cross-platfoiln Data Sharing (CDS) disk that is suitable for as inoving between different operating systems. This is the default forn~at disks that are for as not used to boot the system.Typically, most disks on a system are co~ifigored this disk type. Hobvever. it is not a suitable foilnat for boot, root or swap disks, for i n i ~ ~ oorshotr relocation spares of su~ch disks, or for Extensible Fullware Interface (EFI) disks. The disk is fo~ruatted a simple disk that can be converted to a CDS disk. as The disk is fo~natted a sliced disk. This fo~ruat be applied to disks that are uused as can to boot the system. The disk can be converted to a CDS dislt if it was not initialized for use as a boot disk.

simple sliced

Caution: The CDS disk foinat is incompatible wit11 EFI disks. If a disk is iuitialized by VxVM as a CDS disk, the CDS header occul>iesthe poiti011 of the disk where the VTOC wodd osoally be located. If yo11 sitbsequ~ently a command soch as fdisk or foil~iat create a paitition table on a CDS disk, use to and this erases the CDS info~nation could cause data coi~itption.
By default, atdo-configured non-EFI disks are foinatted as cdsdisk disks bvlien they are initialized for ose with VxVM. Yo11 can change the default foi~nat osiug the vxdiskadm(1 M) command to update by the /etc/default/vxdisk defaolts fde. See the vxdisk(1M) manoal page for details of the itsage of this file, aud for more infoination abotd disk types and their co~lfiguratioi~. Aoto-collfigored EFI disks are fo~ruatted sliced disks by default. as

I-"
9

F?
! .', :

-.
~

VxVM initializes each new disk with the smallest possible number of partitions. For uon-EFI disks of type sliced, VxVM usually collfig~~res paltition s3 as the private region. s4 as the public region, aud s2 as t11e entire physical disk. AII exception is an eucapsulated root disk, on w l k h s3 is usually configured as the pnblic region and s4 as the private region.

r.7

Discovering and configuring newly added disk devices

The vxdiskcollfig utility scaus aud cordigures new- disk devices attached to the host, disk devices that become ouliue, or fibre chalmel devices that are zoued to host bus adapters coullected to this host. The co~~uuaud platfo~~n calls specific interfaces to configme new disk devices and blulgs them imder control of the operating system. It scaus for disks that were added since VsVM's co~lfiguratiou daemou was last started. These disks are theu dy~~amically coufigtu.ed aud recoguized by VxVM. vxdishconfig should be used wheuever disks are physically col~llected the host or w1le11fibre chamel to devices are zoned to the host.

. ..-.
-

F T
-

i :
&
7

vxdislicoufig calls vxdctlenable to rebuild \~olmne device node di~ecto~ies update the DMP u~tenlal aud database to reflect the new state of the system. You can also use the vxdisksca~ldisksco~nruaud scan devices iu the operating system device tree, to disks. aud to iuitiate dynamic reconfiguration of m~~ltipathed If you want VxVM to scan ouly for uew devices that have been added to the system. and for devices that have bee11 ellabled or disabled, specify the -f option to either of the commands. as s h o w here:

il.

However. a complete scan is initiated if tlre system co~lfiguration bee11 modified by chauges to: has lustalled allay suppolt libraries. The devices that are listed as being excluded from use by VxVM. DISKS (JBOD). SCSI3. or f o r e i g device definitions. See the vxdctl(1 M) and vxdisk(1M) mauoal pages for more illfo~~nation.

Partial device discovery

The Dyna~nic Multipathing (DMP) featwe of VxVM supports partial device discovery where you can include or exclude sets of disks or disks attached to controllers from the discovery process. The \I+. .]disks cornland rescans the devices in the OS device tree and triggers a DMP recollfigurat~on.You cau specify parameters to vxdisk scandisks to i~uplelne~lt partial device discovery.
I For examplc, this conllnand 111akesVxVM discover newly added devices tbat were L ~ C U O W to it earlier:

..-

..

The next example discovers fabric devices (that is, devices with the characteristic DDI-NT-FABRIC property set on thenl):
# 17x~fisk scur?tfi.~ksfubr~ic The following command scans for the devices c ItldO and c2t2d0:

Alternatively, you can specify a ! prefix character to iudicate that you want to scan for all devices except those that are listed:

You cau also scan for devices that are coullected (or not co~mected) a list of logical or pllysical to controllers. For example, this co~ummd discovers and co~lfigures devices except those that are all connected to the specified logical co~~trollers:

The next command discovers devices tbat are collllected to the specified physical controller:

Discovering disks and dynamically adding disk arrays

You can dyuanucally add support for a new type of disk away which has been developed by a tlurdp a 1 9 vendor. The support comes it1 the f o ~ ~ i ivendor-supplied libraries, and is added to a Solaris of system by using the pkgadd coullna~~d.

Disk categories
Disk arrays that l~ave been certified for use wit11 Veritas Voluu~e Manager are supported by an allay s i ~ l ~ plibrary (ASL), and are categorized by the v e ~ ~ d L r string that is retu111ed by the disks (for o~t oD example, "HITACHI"). Disks iu JBODs for wliicli DMP car1 be supported in ActiveIActive mode, aud which are capable of bei~ig mnltipathed, are placed in the DISKS categoly. Disks in uusupported allays cau be placed in this catego~y. Disks h~JBODs that do not fall into any supported category, aud which are not capable of being luultipathed by DMP are placed h~the OTHER-DISKS cateeory.

Adding support for a new disk array

The following exa~nple illustrates how to add support for a new disk anay I Solarissyste~n 11si11ga vendor-si~ppliedpackage on a moimted CD-ROM:
I ~ I I v~tsda I ~ ~ to

The new disk anay does uot need to be already conuected to the system when the package is iustalled. If any of the disks iu the new disli allay are subsequently connected, and if vxco~~figd nuluing, is vxcoufigd immediately u~vokes Device Discovery fimction and includes the new disks iu the the VxVM device list.

Enabling discovery of new devices

To have VxVM discover a new disli allay. use the follo\~iug command:

ti ~~xu%d enable
This comnland scans all of the disk devices aud their attributes. updates the VxVM device list, and reco~lfigi~res DMP ~ i t the new device database. Tl~ere 110 need to reboot the host. h is Note: This command eusiwes that dyua~nic u l t i p a t h g is set up correctly on the allay. Otherwise, m VxVM treats the i u d e p e ~ ~ dpathstto the disks as separate devices, ~vkich result iu data c o ~ ~ i ~ p t i o n . e~~ can

Administering the Device Discovery Layer

Dylia~nic additiou of disk allays is possible because of tlie existence of the Device Discovery Layer (DDL) which is a facility for discoverilig disks and t!)eir ait.;ibutes that are required for VxVM and DMP operations. The DDL is admiuistered ilsillg the vsddladm utility, which can be used to perfo~m the followiug tasks:
w List the types of arrays that are s~~ppol-ted.

Add support for an aimy to DDL. Remove si1ppo1.t for an away from DDL. List u~fo~matiou about exclitded disk anays. m 1 ic,t disks that are supported in tlie DISKS (JBOD) category. r .,:.id disks from differeut vendors to tlie DISKS category. Relnove disks from the DISKS category. Add disks as foreigu devices. The followiug sections explain these tasks iu more detail. For fi~rtlier i~~folmation, the see vxddlad~u(lM) mauilal page.

Listing details of supported disk arrays

To list all cui~eutly s11ppo1.teddisk allays, use the following command:

Note: Use this connnaud to obtaiu values for the vid a i ~ d attributes that are used with other follns of pid the vxddladm commaud.
To display more detailed iufoilnatiou about a particular allay library, use this folm of the c o i m a i d :

This comluai~d displays the vendor ID (VID), product IDS (PIDs) for the arrays. m a y types (for example, A/A or AIP), and allay uames. The followillg is sa~nple output.

ATTR-NAME ATTR-VALU E ................................................. LIBNAME Iibvxfuiitsu.so VI D vendor GR710, GR720, GR73o PID GR740, GR820, GR840 ARRAY-TYPE A/A, A/P FJ-GR710, FJ-GR720, FJ-GR730 ARRAY-NAME FJ-GR740, FJ-GR820, FJ-GR840

Excluding support for a disk array library

To exclude all at-rays that depend 011 a palticular atray library from participatiug in device discovely, use the followiug comnand:

This example excli~des support for disk anays that depends on the libray libvxeuc.so. You can also exclude suppoit for disk airays from a particular vendor, as s11o\w1 UI tlus example:
~~..rrl~llcrt/rrr e.~.vcl~ir/eor.r.q. 17irI-A('MEpic/=.Yl

For liiore ulfonnation about excludii~g disk anay support, see the vxddladm (1M) manual page.

Re-including support for an excluded disk array library

If you have excluded suppott for all atrays that depend on a paiticular disk array library, you can use the iuclndeanay keyword to remove tlie elltry from the exclude list. as s h o w in the followi~lg example:

This comliiaiid adds the airay library to the database so that the library can once agaiu be used in device discoveiy. If vxcoi~figd running. you call use the \i?tdiskscaudislis command to disco\;er the is arrays and add their details to the database.

Listing excluded disk arrays

To list all disk arrays that are currently excluded from use by VxVM, use the folIo\ving command:

Listing supported disks in the DISKS category

To list dislis that are s~~ppoltedtlie DISKS (JBOD) category, use the followiilg c o m a u d : in
+Y i-..rc/~l/udrr~ /i,~fjl)o~/

Adding unsupported disk arrays to the DISKS category

Caution: The procedure iu this section ensi~res Dynamic Milltipathiup (DMP) is set up con.ectly that on an allay that is uot supported by Veritas Voluu~e Manager. Otherwise, Velitas Voliuue Manager treats the independent paths to the disks as separate devices, which call result in data conuption.

To add an unsupported disk array

I Use the follo\Yiug c o m ~ a u d identify the vendor ID and produ~ctID of the disks iu the array: to

Wllere de\ice_i7u1ne is the device name of one of the disks hl the allay ( f o ~ example, /dev/rdsldclt20dOs2). Note the vali~es the vendor ID (VID) and product ID (PID) iu the output from of this col~mand. Fijitsr~ For disks, also uote the niunber of characters iu the serial number that is displayed. The followiug is sample output:

Vendor i d ( V I D ) : Product i d (PID): Revision : S e r i a l Number :

SEAGATE ST318404LSUN18G 8507 oo25ToLA3H

Iu this example, the vendor ID is SEAGATE and the product ID is ST3 18404LSUN 18G.
2 Enter the following command to add a new JBOD category:

Where ve~tdorid prodnctid are the VLD and PID values that you found fioun the previous step. For and example, vendorid might be FUJITSU, IBM, or SEAGATE. For Fiditsu devices, you must also specify the number of characters i the serial 1111mberas the argiument to the length argiuneut (for exanlple, 10). u Note: Iu VxVM 4.0 and later releases. a SEAGATE disk is added as a JBOD device by default. Continuiug the previous example, the commaud to define au allay of disks of this type as a JBOD would be:

3 Use the vxdctlenable command to bring the alyay under VxVM control:
ii ~,sdc/l enable

4 To verify that the al-ray is no\v snppol-ted, enter the follo~viug coluu~a~id:

The followiug is sample outpid from this c o m a ~ for the example array: d

VI D

............................................................. ............................................................. SEAGATE ALL P l D s 1 8 -1 36 12

PID

Opcode

P a g e Code

Page O f f s e t

SNO l e n g t h

5 To verify that the alray is recopized, use the vxd~~~paddisteuclosi~re a u d as showu iu the com followiuy salliple olltput for the example al-ray:

.................................................... ....................................................
OTHER-DISKS Disk OTHER-DISI(S Disk OTHER-DISl(S DISKS

ENCLR-NAME

ENCLR-TYPE

ENCLR-SNO

STATUS CONNECTED CONNECTED

The enclosu~re uaule and type for the m a y are both show^ as beiuy set to Disk. Yon cau use the vxdislilist ~ O I U I I I ~ to ~ I I display the disks ill tlie ar-ray:

DEVICE Disk-o Disk-1

TYPE DISK auto:none auto:none -

GROUP

STATUS online invalid online invalid

G To verify that the DMP paths are reco~Azed, the v x d ~ ~ ~ p a d m y e t d ~ ncolull~al~d s h o w iu use p ~ ~ o d e as
tlie followi~~y sample output for the example nl-ray:

NAME STATE ENCLR- TYPE PATHS ENBL DSBL ENCLR- NAME ............................................................... ............................................................... D i s k - ~ ENABLED D i s k 2 2 0 Disk 2 2 o Disk D i s k - 1 ENABLED D i s k
This shows thatthereare two pathsto thedisks in the array.

Placing disks under VxVM control

When you add a disk to a system that is r~uming VxVM, you need to put the disk onder VxVM coutrol so that VxVM cau control the space allocation on the disk. Unless you specify a disk group, VxVM places ilew disks in a default disk group. The method by uhich you place a disk under VxVM control depends on the ckcumstances: .If the disk is new. it must be iuitialized and placed under VxVM control. You can use the menu-based vxdiskadul utility to do this.

Caution: Iuitialization destroys existing data on disks.

.If the disk is uot ueeded imlnediately, it can be initialized (but not added to a disk group) and reserved for future use. To do this. enter uone \vl~enasked to name a disk group. Do uot confi~se type of this "spare disk'' with a hot-relocation spare disk. .If the disk was previously iuitialized for fi~ture by VxVM. it can be reinitialized and placed umder use VxVM control. .If the disk was previously iu use, but not under VxVM control. you may wish to preseive existiug data on the disk \vivhile still lettiug VxVM take coi~trol the disk. This can be accomplished using of encaps~rlatiou. Note: Encapsulation preselves existiug data on disks. .Multiple dislis on one or more coutrollers can be placed under VxVM co~ltrol sim~~ltaneo~~sly. Depeudiug on the circulnstances. all of the disks may not be processed the same way. It is possible to configure the \~disliadm utility not to list certain disks or coi~trollers being available. as iu where disk enclosures are visible to a number For example, this may be usefi~l a SAN envirouu~ent of separate systems. the devices To exclude a device f i o ~ u view of VxVM, select item I6 (Prevent i ~ ~ u l t i p a t h i n ~ S ~ ~ p p r e s s fiom VxVM's view) from the \.xdiskadm maiu menu.

Changing the disk-naming scheme

Note: Devices with veiy long device names (for example, Fibre C h a ~ ~ udevices that include el names. The operatioil worldwide name (WWN) identifiers) are always represented by enclost~re-based in this section has no effect ou such devices. Yon can either use enclosure-based naming for disks or the operating systenl's ua~niug scheme (such as c#t#d#s#). Select u ~ e n u item 20 fiom the vxdiskadm n~aiu menu to change the disk-naming scheme that you wmt VxVM to use. When proinpted, enter y to change the uallliug scheme. Tlus restarts the vxconfigd daemon to bring the new disk namiug scheme iuto effect. Altematively, yo11can chauge the m~anliug schenle from the collllnand line. The followiug couuna~~ds select enclosure-based and opaating system-based ~ m u h respectively: g
-.-

The chauge is hln~ediate wl~ichevermethod you use. The optional persistence argument allows you to of after disk select whether the i~ames disk devices that are displayed by VxVM remain ~mchauged hardware has been reconfigured and the syste~n rebooted. By defa~ilt, both euclosore-based naming aud operating system-based naming are persistent.

Discovering the association between enclosure-based disk names and 0s-based disk names
If you euable enclos~~re-based uaming, and use the vxp~int con~mand display the struchwe of a to volume, it shows ei~closure-based disli device uan~es (disk access names) rather than c#t#d#s# names. To discover the c#t#d#s# ualnes that are associated with a given enclosure-based disk name, use either of the followi~~g coiwnands:

For example, to fmd the physical device that is associated with disk ENCO-21, the appropriate c o ~ ~ l ~ u m d s be: would

To obtain the fiill pathname for the block and character disk device fro111these commands. append tlie displayed device name to Idevl~xldn~p ldevlvxlrdmp. or

Installing and formatting disks

De~ending the hardware capabilities of your disks and of your system. you may either need to shi~t on dow1 and power off yoiu system before iustalliilg the disks, or yo11may be able to hot-insert the disks illto the live system. Mauy operating systeins call detect the presence of the new disks on being rebooted. If the disks are u~sei-ted while the systeiil is live, you may need to eilter an operating systemspecific coi~ii~iai~d to notify the system. If the disks require low or intel-tuediate-level formatting before use, use the operating system-specific fo~lnattiug o n m a ~ ~ ddo this. c to Note: SCSI disks are osually prefolniatted. Refoilnattiug is needed ouly if the existing fo~lnatting has become damaged. The following sectio~is provide detailed examples of how to use the vxdiskadlu utility to place disks imder VxVM control in various ways and circumstances.

Displaying and changing default disk layout attributes

To display or change the default values for ii~itializiilg encapsulatu~g or disks, select menu item Z?(Changeldisplay the default disk 1ayouts)fiom the vxdiskadm main menu. For disk initializatiou, yo11 can chauge the default fo~mat the default leugtlth of the private region. For disk encapsulation, you and regious. can additionally change the offset values for both the private and pu~blic The attl-ibute settings for initializing disks are stored in the file, letcldefaultlvxdisk, and those for encapsolatiug disks in letcldefaultlv?tencap. See the vxdisli(1 M) and vxelicap(1M) manual pages for more infoi-tnation.

Adding a disk to VxVM

Fonnatted disks being placed under VxVM control iuay be new or previoosly osed outside VxVM. The set of disks call consist of all disks on the system, all disks on a controller, selected disks, or a co~ubination these. of Depaiding on the circumstances. all of the disks may not be processed in the same way. For example, soule iuay be initialized, while others may be encapsulated. Cantion: Iuitialization does not preserve data on disks. When initializing or encapsulating moltiple disks at one t h e , it is possible to exclude certain disks or cei-tain controllers. To exclude disks, list the llanles of the disks to be excluded in the file letcl~xldisks.excludebefore the iuitialization or encapsulation. You cau exclude all disks on specific controllers fro111initialization or encapsulation by listiug those controllers iu the file

letcl~xlc~ltrIs.exclode.

To initialize disks for VxVM use

1Selectlue11ttitelul ( A d d o r i n i t i a l i z e maiu mernl. o n e o r more d ~ s k s ) f r o m t h e v x d i s l i a d ~ ~

2 A t the following prompt, enter the disk device name o f the disk to be added to V x V M colltrol (or enter l i s t for a list o f disks):

Add o r i n i t i a l i z e d i s k s Menu: VolumeManager/Disk/AddDisks Use t h i s o p e r a t i o n t o add o n e o r more d i s k s t o a d i s k g r o u p . You c a n add t h e s e l e c t e d d i s k s t o a n e x i s t i n g d i s k g r o u p o r t o a n e w d i s k g r o u p t h a t w i l l be c r e a t e d as a p a r t o f t h e o p e r a t i o n . The s e l e c t e d d i s k s may a l s o be added t o a d i s k g r o u p as s p a r e s . The s e l e c t e d d i s k s may a l s o be i n i t i a l i z e d w i t h o u t a d d i n g t h e m t o a d i s k g r o u p l e a v i n g t h e d i s k s a v a i l a b l e f o r u s e as r e p l a c e m e n t d i s k s . More t h a n o n e d i s k Here a r e some d i s k all: c3 c q t 2 : c3tqd2: xyz-o : xyz- : o r p a t t e r n may be e n t e r e d a t t h e p r o m p t . s e l e c t i o n examples: 2

a l l disks a l l disks on both c o n t r o l l e r 3 and c o n t r o l l e r 4,target a s i n g l e d i s k ( i n t h e c # t # d # n a m i n g scheme) a s i n g l e d i s k ( i n t h e e n c l o s u r e based n a m i n g scheme) a l l d i s k s o n t h e e n c l o s u r e whose name i s xyz

S e l e c t d i s k d e v i c e s t o add: [<pattern- l i s t > , a l l , l i s t , q , ? ]

<pcittei.iz-list> can be a single disk, or a series of disks and/orcontrollers (with optionaltargets). If <pc~ttel.il-list>consist: of multiple items, separate them using white space, for example:

specifies fours disks at separate target IDS on controller 3.

If you enter Ii s t the system:

atthe prompt, t h e v x d i s k a d m program displays a list of the disks available t o STATUS online online online invalid online invalid online online

DISK DEVICE GROUP cotodo mydgoi mydg cotldo mydgoz mydg citodi ~3tod0 senao-o wydq-3 myd9 senao-1 rnydg 34 myd9 S e l e c t d i s k d e > ~ i c e St o add: [<pattern- list>,all, l i s t , q , ? ]

The phrase online iuvalid in the STATUS liue indicates that a disli has yet to be added or initialized for VxVM control. Dislis that are listed as oilline wit11 a disli name and disk gronp are already under VxVM control. Enter tlle device name or pattet-n of the disks that you want to iuitialize at the prompt and press Rehuu.

3 To continue with the operation, enter y (or press Reh11-n)at the following prompt:

Here a r e t h e d i s k s s e l e c t e d .
list of device names

Output format:

[Device]

Continue operation?

[y,n,q,?]

(default:

y) y

4 At the following prompt, specify the disk group to wI1ic11the disk sl~ould added. or none to reserve be the disks for f i ~ h ~use: re

You can choose t o add t h e s e d i s k s t o an e x i s t i n g d i s k g r o u p , a n e w d i s k group, o r y o u can l e a v e t h e s e d i s k s a v a i l a b l e f o r use b y f u t u r e add o r r e p l a c e m e n t o p e r a t i o n s . To c r e a t e a new d i s k g r o u p , s e l e c t a d i s k g r o u p name t h a t does n o t y e t e x i s t . To l e a v e t h e d i s k s a v a i l a b l e f o r f u t u r e use, s p e c i f y a d i s k g r o u p name o f "none". Which d i s k g r o u p [ < g r o u p > , n o n e , l i s t , q , ? ]
5 If you specified the name of a disk group that does not aheady exist, vxdiskad~n pronlpts for codu~nation you really \vaut to create this new disk group: that

There i s n o a c t i v e

d i s k g r o u p named disl:groupnan~c. ( d e f a u It: y) y

C r e a t e a new g r o u p named dislzgi.oup narne? [ y , n , q , ? ]

You are the11 prompted to confum whether the disk group should support the Cross-platfo~m Data Shariug (CDS) feati~re:

C r e a t e t h e d i s k g r o u p as a CDS d i s k g r o u p ? [y,n,q,?]

(default:

n)

If the new disk group may be moved between different operatiug system platfoims, enter y. Otherwise, enter n.

6 At the followii~g prompt, either press Retuil~ accept the default disli name or enter n to allow you to to define your ow11 disli names:
Use d e f a u l t d i s k names f o r t h e d i s k s ? [y,n,q,?] (default: y)

7 When prompted wllether the disks should become hot-relocation spares, enter n (or press Retmm):

Add d i s k s

as spare disks for

dishgroup iluine? [ y , n , q , ? ]

(default:

n) n
--.

8 When pl.ompted wlletheer to exclude the disks from hot-relocation use, euter n (or press Rehun).
Exclude disks f r o m hot- r e l o c a t i o n use? [ y , n , q , ? } (default:

n) n

9 You are next prolllpted to choose whether you want to add a site tay to the disks:

Add s i t e

t a g to d i s k s ?

[y,n,q,?]

(default:

n)

A site tag is usually applied to dish allays 01 enclos~~res, is not required 1111less want to use the and you Remote Minor feature. If you euter y to choose to add a site tag, you are prompted to the site name at step 11.

10 To coutiuue nit11 the operation, enter y (or press Retu~n) the followiug prompt: at
The s e l e c t e d d i s k s w i l l be a d d e d t o t h e d i s k g r o u p disf<grool)t~niitc,w i t h d e f a u l t d i s k names. list of device llalues Continue with o p e r a t i o n ? [ y , n , q , ? ] ( d e f a u l t : y) y 11 If you chose to tag the dislis with a site iu step 9, you are now pronlpted to enter the site uallle that shodd be applied to the dislis in each enclosure: The f o l l o w i n g d i s k ( s ) : list of device nallles belong t o e n c l o s u r e ( s ): list of enclosme uallles E n t e r s i t e t a g f o r d i s k s on e n c l o s u r e e~closm.c-uau1e [ < n a m e > , q , ? ] 12 If you see the followi~ig prompt. it lists any dislis that have already beeu iuitialized for use by VxVM; enter y to indicate that all of these dislis should now be used: The f o l l o w i n g d i s k d e v i c e s a p p e a r t o have been i n i t i a l i z e d already. The d i s k s a r e c u r r e n t l y a v a i l a b l e a s r e p l a c e m e n t d i s k s Output format: [Device] list of device names Use t h e s e d e v i c e s ? [ Y , h l , S ( e l e c t ) , q , ? ] ( d e f a u l t : Y ) Y Note that this prompt allows you to u~dicate "yes" 01. "no" for all of these disks (Y or N) or to select how to process each of these disks on an individual basis (S).

If you are sure that you want to re-initialize all of these disks, enter Y at the followillg proiilpt:

69

VxVM NOTICE V - 5 - 2 - 3 6 6 The f o l l o w i n g d i s k s y o u s e l e c t e d f o r use appear t o a l r e a d y have been i n i t i a l i z e d f o r t h e V o l u m e Manager. If y o u are c e r t a i n t h e d i s k s a l r e a d y have been i n i t i a l i z e d f o r t h e Volume Manager, t h e n y o u do n o t need t o r e i n i t i a l i z e t h e s e d i s k devices. Output format: [Device]
list of device uallles

Are y o u s u r e y o u w a n t t o r e - i n i t i a l i z e [Y,N,S(elect),q,?] ( d e f a u l t : N) Y

these disks?

13 vxdiskadm may uow indicate that one or more disks is a calldidate for encapsdation. Encapsulation allows you to add a 1 active disk to VxVM control and preserve the data on that disk. If you want to 1 preserve the data 011the disk, enter y. If you are slue that there is no data 011the disk that you want to preserve, enter n to avoid encapsulation.

VxVM NOTICE V - 5 - 2 - 355 The f o l l o w i n g d i s k d e v i c e has a v a l i d VTOC, b u t does n o t appear t o have been i n i t i a l i z e d f o r t h e Volume Manager. I f t h e r e i s d a t a on t h e d i s k t h a t s h o u l d NOT be d e s t r o y e d y o u s h o u l d e n c a p s u l a t e t h e e x i s t i n g d i s k p a r t i t i o n s as v o l u m e s i n s t e a d o f a d d i n g t h e d i s k as a n e w d i s k . Output format: [Device]
device ualne

Encapsulate t h i s

device?

[y,n,q,?]

(default:

y)

If yon choose to el~capsolate disk. vxdisltadn~confi~uls device llalue and prolnpts you for the its pe~missiou proceed. Enter y (or press Rehuu) to continue eucapsolation: to

VxVM NOTICE V - 5 - 2 - 3 1 1 The f o l l o w i n g disk device f o r encapsulation. Output f o r m a t : [ D e v i c e ]

device name

has been s e l e c t e d

Continue w i t h e n c a p s u l a t i o n ? [y,n,q,?]

(default:

y) y

vxdiskadm now displays an encapsolatiou status, and iufo~uls that yo11 most perfolm a sht~tdoull you aud reboot as soon as possible:

The disk device cleuice ltarne w i l l be e n c a p s u l a t e d and added t o t h e disk group dgrzaine w i t h t h e dis k name disk '~tarne.
You cau now choose whether the disk is to be foiu~aned a CDS disk that is poi-table betweeu as different operating systems. or as a non-poltable sliced disk:

Enter t h e d e s i r e d f o r m a t [ c d s d i s k , s l i c e d , q , ? ] (defau1t:cdsdisk)
Euter the foimat that is appropriate for your needs. Iu inost cases, this is the default fonnat, cdsdisk. At the followiug prompt, vxdiskadill asks if you waut to use the default private region size of 65536 blocks (32MB). Press R e h ~ m coilfiilll that you want to use the default value, or enter a different to value. (The m a x i u ~ ~ ~ l ~ lthat yo11 call specify is 524288 blocks.) value

Enter d e s i r e d p r i v a t e ( d e f a u l t : 65536)

region length [<privlen>,q,?]

If yon entered cdsdiskas the fo~mat, are proinpted for the action to be taken if the disk canuot be you convelted this folmat:

Do you want t o use ' s l i c e d ' as t h e f o r m a t should ' c d s d i s k ' ( d e f a u l t : y) f a i l ? [y,n,q,?]

If you enter y. and it is not possible to encapsulate the disk as a CDS disk, it is ellcapsulated as a sliced disk. Otherwise, the etlcapsulatiot~ fails. vxdiskadm then proceeds to ellcapsulate the disks.

VxVM INFO V - 5 - 2 - 3 4 0 The f i r s t s t a g e o f e n c a p s u l a t i o n has c o m p l e t e d s u c c e s s f u l l y . You s h o u l d now r e b o o t y o u r s y s t e m a t t h e e a r l i e s t p o s s i b l e o p p o r t u n i t y . The e n c a p s u l a t i o n w i l l r e q u i r e t w o o r t h r e e r e b o o t s w h i c h w i l l happen a u t o m a t i c a l l y a f t e r t h e n e x t r e b o o t . To r e b o o t e x e c u t e t h e command: shutdown' - go
-

i6

T h i s w i l l u p d a t e t h e / e t c / v f s t a b f i l e so t h a t v o l u m e d e v i c e s a r e . used t o mount t h e f i l e s y s t e m s o n t h i s d i s k d e v i c e . You w i l l need t o u p d a t e any o t h e r r e f e r e n c e s such as b a c k u p s c r i p t s , d a t a b a s e s , o r m a n u a l l y c r e a t e d swap d e v i c e s .

+ If you choose notto encapsulate thedisk:

vxd i s k a d m asks if you wantto initialize the disk instead of encapsulating it. Enter y to confirm this: I n s t e a d of encapsulating, initialize? [y,n,q,?] (default: n) y

vxdiskadm now confim~s those disks that are being initialized and added to VxVM co~ltrol with messages similar to the following. lu addition. you may be prompted to perfotm surface a~~alysis.

VxVM INFO V - 5 - 2 - 2 0 5 I n i t i a l i z i n g

d e v i c e device name

You crw now choose whether the disk is to be fo~matted a CDS disk that is portable between as different operatiug systeins, or as a nou-pottable sliced or simple disk:

Enter t h e desired f o r m a t [ c d s d i s k , s l i c e d , s i m p l e , q , ? ] ( d e f a u l t : cdsdisk)

Enter the foiluat that is appropriate for your needs. Iu most cases. tlus is the default fonuat, cdsdisk. At the followitlg prompt. vxdiskadm asks if you want to use the default private region size of 65536 blocks (32MB). Press Return to confinu that yo11want to use the default value. or enter a different value. (The maximun~ value that you can specify is 524288 blocks.)

Enter desired p r i v a t e r e g i o n l e n g t h [ < p r i v l e n > , q , ? ] ( d e f a u l t : 65536) v x d i s k a d m t h e n p r o c e e d s t o add t h e d i s k s . VxVM INFO V - 5 - 2 - 8 8 A d d i n g d i s k d e v i c e device itaiizeto d i s k g r o u p dislzgroupizn~~iei t h d i s k name disk w
naine.

To encapsulate a disk for use in VxVM

1 Select menu item 2 (Encapsulate one or more dislis) from the v x d i s k a h maiu menu.
Note: Your system may use device names that differ from the examples s h o w here.

At the following prompt, enter the disk device name for the disks to be eucapwdated:

Encapsulate one o r more disks Menu: VolumeManager/Disk/Encapsulate Use t h i s o p e r a t i o n t o convert one o r more d i s k s t o use t h e Volume Manager. This adds t h e disks t o a d i s k g r o u p and r e p l a c e s e x i s t i n g p a r t i t i o n s w i t h volumes. Disk e n c a p s u l a t i o n r e q u i r e s a r e b o o t for t h e changes t o t a k e e f f e c t . More t h a n one d i s k o r p a t t e r n may be e n t e r e d a t t h e prompt. Here are some d i s k s e l e c t i o n examples: all: c3 c4t2: c3tqdz: xyz-0 : xyz- : a l l disks a l l disks a single a single a l l disks on disk disk on both c o n t r o l l e r 3 and c o n t r o l l e r 4 , t a r g e t ( i n t h e c#t#d# naming scheme) ( i n t h e e n c l o s u r e based naming scheme) t h e e n c l o s u r e whose name i s xyz 2

Select disk devices to encapsulate: [<pattern-list>,all,list,q,?] device I I ~ I I I ~ Where <pattern-list> can be a single disk, or a series of disks andlor co~~trollers optio~~al (with targets). If <patteiu-list> co~~sists multiple items, those itenls IIILIS~ separated by white space. of be If you do not b o w the address (device name) of the disk to be encapsulated, enter 1 or list at the prompt for a complete listing of available disks.

2 To contiuoe the operation, enter y (or press Rehum) at the following prompt:
Here i s t h e disk s e l e c t e d .
device name

Output f o r m a t :

[Device]

Continue o p e r a t i o n ? [y,n,q,?]

(default:

y) y

3 To add the disk to a disk group, enter the uame of the disk group (this disk g o u p need not already exist):

You can choose t o add t h i s d i s k t o an e x i s t i n g d i s k g r o u p o r t o a new d i s k g r o u p . To c r e a t e a n e w d i s k g r o u p , s e l e c t a d i s k g r o u p name t h a t does n o t y e t e x i s t . Which d i s k g r o u p [ < g r o u p > , l i s t , q , ? ]

4 At the followillg pro~npt, either press Return to accept the default disk name or enter a disk name:

Use a d e f a u l t

d i s k name f o r t h e d i s k ? [y,n,q,?]

(default:

y)

5 To coutiuue with the operation, enter y (or press Reh~rn) the followiug prompt: at The s e l e c t e d d i s k s w i l l group w i t h default disk
device name

be e n c a p s u l a t e d and added t o t h e dgname d i s k names.

Continue w i t h operation? [y,n,q,?]

(default:

y) y

G To collfinn that encapsulation should proceed, enter y (or press Reh~rtl) tlle followillg prompt: at

The f o l l o w i n g d i s k has been s e l e c t e d f o r e n c a p s u l a t i o n Output format: [Device]

device llalue

Continue w i t h e n c a p s u l a t i o n ? [y,n,q,?]

(default:

y) y

A message similar to the following confirtus that the disk is being ellcapsulated for use h~VxVM aud tells you that a reboot is needed:

The d i s k d e v i c e device izan?e w i l l be e n c a p s u l a t e d and added t o t h e d i s k g r o u p diskgroupwith t h e d i s k name diskgroupol. 7 For uou-root disks. yoti can uow choose wlletlether the disk is to be fol~natted a CDS disk that is as portable between different operatiug systems, or as a uon-portable sliced disk: Enter t h e desired format [ c d s d i s k , s l i c e d , q , ? ] ( d e f a u l t : cdsdisk)
Enter the fonnat that is appropriate for your needs. hh most cases. this is the defanlt fonnat, cdsdisk. e t Note that only the sliced foi~uat suitable for use with root, boot or swap disks. is

8 At the following prompt, vxdiskadm asks if you want to use the default piivate region size of 65536

'<:ricks (32MB). Press K a t ~ u tol confu~n you want to use the default value, or enter a different ~ that ..iue.(The maxinlum value that you can specify is 524288 blocks.)

Enter d e s i r e d p r i v a t e r e g i o n l e n g t h [ < p r i v l e n > , q , ? ] ( d e f a u It: 65536)

9 I f you entered cdsdisk as the fo~mat step 7, you are pron~pted o ~ action to be taken if the disk h~ f the c m o t be converted this foimat:

Do you want t o use ' s l i c e d ' [y,n,q,?] ( d e f a u l t : y)

disli. Otherwise, the encapsulation fails.

as t h e f o r m a t should

'cdsdisk'

fail?

If you enter y, and it is not possible to encapsulate the disk as a CDS disk, it is encapsulated as a sliced
l o vxd i s k a d m then proceedsto encapsulatethe disks. VxVM NOTICE V - 5 - 2- 311 The clcuice encapsulation.
I I . U I , Ld i s k ~

has been c o n f i g u r e d f o r

VxVM INFO V - 5 - 2 - 3 4 0 The f i r s t stage o f e n c a p s u l a t i o n has completed s u c c e s s f u l l y . You should now reboot your s y s t e m a t t h e e a r l i e s t possible opportunity. The e n c a p s u l a t i o n w i l l r e q u i r e t w o o r t h r e e r e b o o t s which w i l l happen a u t o m a t i c a l l y a f t e r t h e next r e b o o t . To r e b o o t execute t h e command: shutdown - g o - y - i 6 This w i l l update t h e / e t c / v f s t a b f i l e so t h a t volume devices are used t o mount t h e f i l e systems on t h i s disk device. You w i l l need t o update any o t h e r r e f e r e n c e s such as backup s c r i p t s , databases, o r manually c r e a t e d swap devices.
Note: The origiual Ietclvfstab file is saved as /etc/vfstab.pre\~m.

At the following prompt, iudicate whether you waut to encapsulate illore dislis (y) or rehlru to the vxdiskadm main menu (n):

Encapsulate o t h e r d i s k s ? [y,n,q,?]

(default:

n) n

I$ Rootability

VxVM call place various files from the root file system, swap device. and other file systems ou the root disli under VxVM control. This is called rootability. The root disli (that is, the disli coutaiuiug the root file system) cau be put ~ u ~ VxVM co~~trol d e ~ through the process of encapsulation. E~lcapsulation collverts existing paltitions on that disk to vollunes. Ol~ce ru~der VxVM control, the root and swap devices appear as volu~mes provide the same characteristics as other VxVM volu~nes. and A volume that is colfig~red use as a swap area is refened to as a swap volume, and a volume that for contains the root fde system is referred to as a root vol~ume.

Cautiou: Only encapsulate your root disk if you also intend to mirror it. There is no benefit iu rootdisk encapsulation for its own sake.
It is possible to mnb-ror the rootvol, and swapvol vol~unes.as \veU as other parts of the root disk that are required for a successfi~l boot of the systeul (for exa~nple, Iusr). This provides co~uplete redr~uda~~cy and recovely capability iu the event of disk failure. Without VxVM rootability. the loss of the root. disks. swap. or usr partiti011 prevellts the system from being booted from su~rvivu~g Mhroring disk drives that are critical to bootiuq ensures that IIO siugle disk failure renders the system u ~ ~ ~ ~ ~ Aasuggested colfigu~ration to minor the c~itical s ble. is disk onto another available disk (using the vxdiskadu~ commaud). If the disk containing rootaud swvappartitions fails, the syste~n be rebooted can from a disk contaitiing minors of these partitions.

.pa3elda.r s! uaqa ysrp p a p g aqljo slualuo3 atll.1a~o3a.1 I asti nt?3noL .IO'tno.rj palooq aq 01 pamS1po3 aq tar11 Lsm 'a[qel!ns S! ys!p 01 ! a.teds arlljl ys!p Strpxua.1 no sasald aql mo.g Sn!Ldo3 Lq ys!p a.~eds no saxald papq arp saleal3a.r aql L11w!]m10~ e x A 'asn Sn!.nlp spej !Jo,L?m sl! .IOys!p 100.1 aql .1aq]!a pns palqena sy no!]e3ola.l-loq JI .ys!p a . ~ d auo 1s17-, .. ., -ro.u!m ys!p 100.1aq1 'ys!p 100.1palelnsde3ua atI1jo sls!s1103 1namaSueue s , v:ooq aql m sqs!p j o 1nam115!ssealq!ssod ano smoqs a~11Sy L ~ M O ~ ~ O . F ~ S s ! t ~.dl

Defining alternate boot disks

If required, you can define au alternate boot disk by enteiing the following collulland at the ok boot prompt:

of Where altboot-disk is the device ua~lle an alteinate disk froru which the systeill cau be booted. Alte~natively, the system is already u p w d ~ ~ u u l l lenter the follo~viviug if ~g, colluualld to defiue au alte~~late disk: boot

Removing disks
You c w remove a disk fiom a system aud move it to auotller system if the disk is failing or has failed.

To prepare your system for the removal of the disk

1 Stop all activity by applicatious to volumes that are configured on the disk that is to be removed. Unmo~mt syste~us shut down databases that are coufig~red11 the volumes. file aud 0

2 Use the followiug c o ~ ~ ~ ~ ustopdthe volumes: to m

# vxvol
[ - g d i s k g o ~ ~ p l s t ovolume1 volume2 p

...

3 Move the volumes to other disks or back up the volumes. To move a volume, use vxdiskadm to minor the volume ou one or more disks, then remove the origiual copy of the volume. If the volumes are 110 longer needed, they call be removed illstead of moved.
4 Check that any data on the disk has either been ~uoved other disks or is no longer ueeded. to

To remove the disk from its disk group

1 Select meuu item 3(Remove a disk) from the vxdiskadm main menu. 2 At the followiug prompt, euter the disk uame of the disk to be removed:
Remove a d i s k Menu: VolumeManager/Disk/RemoveDisk Use t h i s o p e r a t i o n t o remove a d i s k f r o m a d i s k g r o u p . T h i s o p e r a t i o n t a k e s a d i s k name a s i n p u t . T h i s i s t h e s a m e name t h a t you g a v e t o t h e d i s k when you a d d e d t h e d i s k t o t h e d i s k group. Enter disk name [ < d i s k > , l i s t , q , ? ] mydgoi

3 If there are any volu~nes the disk. VxVM asks yon whether they should be evacuated f i o n ~ on the disk. If you wish to keep the volumes, auswer y. Otherwise, answer 11.

4 At the followiug verification prompt. press Reh~ru continue: to

VxVM NOTICE V-5-2-284 Requested operation f r o m group mydg. Continue w i t h o p e r a t i o n ? [y,n,q,?]

is t o remove disk mydgol y)

(default:

The vxdiskadm utility renloves the disk from the disk group and displays the followiug success message:

VxVM INFO V - 5 - 2 - 2 6 8 Removal o f disk

mydgoi is complete

You caunow remove the disk or leave it on yot~r system as a replacement.

5 At the followiug prompt, indicate whetl~er you want to remove otl~el. disks (y) or reh1111 to the vxdiskadm main menu (n):

Remove another disk? [y,n,q,?]

(default:

n)

Removing a disk with subdisks

You cau remove a disk ou which some subdisks are defuled. For example. you can consolidate all the volumes onto one disk. If you use the vxdisliadm progralil to remove a disk, you call choose to move vollimes off that dish. To do tllis. ruu the vxdiskadm program and select item 3 (Remove a disk) fiom the main meno. If the disk is used by some subdisks, the followb~g message is displayed:

VxVM ERROR V-5- 2- 369 The f o l l o w i n g volumes c u r r e n t l y disk mydgoz: home usrvol

use part of

Volumes must be moved f r o m mydgoz before it can be removed. Move volumes t o other disks? [y,n,q,?] (default: n)

If you choose y, then all snbdisks are moved off the disk. if possible. Some subdisks are not movable. A subdisk lnay not be movable for oue of the follouii~g reasons: There is not enougl~ space on the remau~ing disks in the subdisk's disk goup. Plexes or striped subdisks callnot be allocated on different disks fiom existiug plexes or striped subdisks hl the volume. If the bxdisliad~u program camiot move some subdisks. remove some plexes fiom some disks to free more space before proceeding with the disk removal operation.

Renaming a disk
If yo11 do not specify a VM disk name, VxVM gives the disk a default name when yo11add the disk to VxVM couh.ol. The VM disk name is used by VxVM to identify the location of the disk or the disk To chauge the disk name to reflect a change of use or owiership, nse the followiug conmand:

. ..* ....

For example, you might want to rename disk inydg03, as S~IOWIIin the following ol~tput fiom vxdisk list, to 1nydgO2:
# i,.~di.~k fi.r/

DEVICE

TYPE

DISU

GROUP

STATUS

cotodosz cltodosz cltldosz

auto:sl iced a u t o : s li c e d auto:sliced

mydgol mydg03
-

mydg mydg

online online online

You wollld use the following c o ~ m ~ to ~ ~ d the disk: a rellalne

To coufiu~u the llaiue change took place, use the vxdisk list conmand agaiu: that
# l a d i s k lisf

DEVICE

TYPE

DISK

GROUP

STATUS

cotodosz cltodosz cltldosz

auto:s l i c e d auto:sl i ced auto:s l i c e d

mydgol rnydgoz -

mydg mydg

online online online

Note: By default, VxVM nallles subdisk objects after the VM disk on wllich they are located. Renaming a VM disk does not automatically rename the subdisl,~on that disk.

Reserving disks
By default. lib- . - -.:;kt command allocates space fiom any disk that has fiee space. You can reserve n set of dislis for special poqToses, such as to avoid general use of a particularly slow or a l~ai-ticularly fast disk. To resenre a disk for special piuyoses. use the followiug c o l l w ~ a ~ ~ d :

After you enter tlus co1l11naud. the vxassist program does not allocate space from the selected disk lmless that disk is specifically mentioned on the vxassist c o m a n d liue. For example, if mydg03 is reserved, use the followiug c o m a u d :

The vxassist c o m ~ n a ~ ~ d overrides the reservation and creates a 20 ulegabyte volu~ne mydg03. on However. the command:

does not use mydgO3, eveu if there is no ftee space on any other disk. off To ~LIIII reservation of a disk. use the following com~uaud:

See the vxedit(1 M) manual page for lllore iufolmation.

Displaying disk information

Before you use a disk, yo11ueed to know if it has been initialized and placed under VxVM control. You also ueed to h o w if the disk is part of a disk goup. because you calluot create volumes on a disk that is uot part of a disk group. The vxdislilist c o m a n d displays device names for all recoguized disks, the disk names, the disk gronp names associated with each disk. a d the stah~s each disk. of To display info~mation all disks that are blow to VxVM. use the followiug command: on

VxVM rehuus a display siluilar to the following:

DEVICE TYPE DISK GROUP STATUS cotodosz auto:s li c e d mydgoq rnydg online cotzdosz auto: s li c e d mydg03 rnydg online cot3dosz auto:s li c e d mydgoz mydg online SENAol-3 a u t o : s l i c e d online invalid SENAol-1 auto:sliced online invalid SENAol-2 auto:sliced . online invalid Note: The phrase online iuvalid iu the STATUS line uldicates that a disk has not yet beeu added to VxVM control. These disks may or nlay uot have been iuitialized by VxVM previously. Disks that are listed as onliue are already under VxVM col~trol.
To display details on a particnlar disk that is defined to VxVM. use the followi~lg coululaud:
# 1:~rlisk [-lq list diskrlurrie

The -v optiou causes the collunai~d additioilally list all tags a i ~ d values that are defu~ed the to tag for disk. Without this option. uo tags are displayed.

Module 5: Administering dynamic multipathing (DMP)

The dynamic multipathing (DMP) feature of Veritas Volulue Mauager (VxVM) provides greater reliability aild perfoiluailce by usiug path failover aud load balanciug. This feature is available for

85

moltipo~feddisk anays from various vendors.

How DMP works

Mnltipo~feddisk arrays c m be coullected to host systems tlnough multiple paths. To detect the va~ious paths to a disk, DMP uses a mechanism that is specific to each suppolfed amay type. DMF' can also differelltiate betweeu different ei~closures a supported alray type that are co~luected the same host of to system. The multipatl~ing policy used by DMF' depends on tlie characteristics of the disk array: Au ActivelPassive array ( A Panay) allows access to its LUNs (logical uuits; real disks or virh~al disks created usiug hardware) via the prima~y (active) path on a siugle coutroller (also h o w l as at1 access port or a storage processor) duriug uo~lual operation. Iu implicit failover mode (or autotrespass mode), an N P m a y automatically fails over by scl~eduliug I/O to the secouda~y (passive) path on a separate controller if the primary path fails. Tlus passive po~fis not used for I/O until the active pol? fails. Iu N P aiyays, path failover call occur for a suigle LUN if UO fails on the primary path. For Activepassive arrays with LUN group failover ( A P G arrays). a group of LUNs that are couuected through a coutroller is treated as a single failover entity. U~dike aiyays. failover occurs at the A/P controller level. aud not for individual LUNs. The primary aud seco~~dary controller are each couuected to a separate group of LUNs. If a single LUN in the prima~y controller's LUN g~.ou~p all LUNs iu fails. that group fail over to the secouda~y controller. Acti~~elPassive arrays iu explicit failover uiode (or oou-aototrespass mode) are te~ined P F anays. N DMP issues the appropriate low-level commaud to make the LUNs fail over to the seco~~dary patli. AIP-C. AIPF-C aud AIPG-C alrays are variauts of the A P . APlF aud N P G a ~ r a y types that suppoif C O I I C ~ I T ~ I/O and load balaucing by having multiple primmy paths iuto a controller. This fimctionality II~ is provided by a controller with lnultiple poifs, or by the hise~.tiouof a SAN hub or switch betweeu au a11.a~ a controller. Failover to the seconda~y aud (passive) patli occm.s o d j if all the active primary paths fail. An ActivelActive disk alray (MA anays) p e ~ ~ u iseveral paths to be used concu~~ently VO. Such ts for anays allow DMP to provide greater I10 throughput by balauci~~g I10 load unifo~iiily the across tlie multiple paths to the LUNs. I11 the eveut that oue path fails. DMP automatically routes I10 over the other available paths. AIA-A or Asymmeti-icActiveIActive alrays cau be accessed thou& secoudary storage paths with little performance degradation. Usually an MA-A array behaves like an A alray rather thau au N A array. & ' However, duriug failover. an NA-A alray behaves like an AIA anay.

Note: Au alray suppo~f library (ASL) inay defiue additioual array types for the alrays that it suppo~ts.
VxVM uses DMP ~iieta~iodes (DMP nodes) to access disk devices connected to the system. For each disk iu a supported a m y , DMP maps olie uode to the set of paths that are couuected to the disk. Additionally, DMP associates the appropriate multipathing policy for the disk alray with the node. For

'I! ssame 01 '0-03oa 'apon dKa a1Bms aql sasn I / V A ~ A 'a.~nsopna plq aql ys!p a15ms s 0) ls!xa '0p66)p prtsop661[3 'sqlsd o , a.Iar[rM a~dmsxa s ~ o q 'a.~uSg ~ ns s Or~p\o[[oj arH 'sZoo[aq ys!p "s.us q 3 n p 01 azn1Bo3a.1olnod sA%oIIe atuatps Bn!msn a! qs!p s s l n a m a ~ m~ x lsrp tap d

- , .... ..-.

. . <

I]::... .- 4-b

.--

-'

-1

.Xe.ue ys!p p a ~ ~ o d dsl s ys!p s ,103apon s dir slas m a ~ o sale.I,siqI! a.niSg 3rqa1loj arm m q .d~a~!padsa.~ durp/m/hap/ pnt! du~pl/mpap/ i;,:?:p sa!. aql m palsa.13 a.1s saporr -.I! 103 sa3pap yoo~q 1us.1 pm pa~todd~~srnn~ sys!p nt! rr! at11 qs!p s 01 papaan03 s! ~srll tllvd rpsa OJ apon a~s.~sdas e sdem &q(,

V*V fvl

Meppcd by DMP

+ b
cIIYSd3
O i a ~ n c l o s u r cn e ;:

D MP

?,

fiif93d3

- -.
d e p e n d i n g a n t l i c path

How DMP monitors UO on paths

In older releases of VxVM. DMP had one kenlel daemon ( e ~ ~ o rthat perfonued error processiug, and d) another (restored) that performed path restoration activities.
From release 5.0. DMP maultaius a pool of lie~uel tlueads that are used to perfom such tasks as enor processiug, path restoration. statistics collection. and SCSI request callbacks. The wd~npadmstat co~utuaud be used to provide iufomation about the threads. The names e l ~ o r d restored have can and bee11 retailled for backward compatibility. One lieluel thread responds to VO failures on a path by initiating a probe of the host bus adapter (HBA) that co~~espoudsthe path. k ~ o t h e thead then taltes the appropriate actiou according to the respouse to r fiom the HBA. The action take11cau be to rehy the 110 I.eqoest ou the path, or to fail the path aud rescheduIe the VO on au alternate path. Tl~e restore kernel thread is woken periodically (typically every 5 minutes) to check the health of the paths, aud to resume 110 ou paths that have been restored. As soule paths may suffer fiom iute~ruittent failure. 110 is ouly resluued 011a path if has remained healthy for a given period of time (by default, 5 mu~utes). The statistics-gathering thead records the s t a t aud eud time of each 110 request, and the uumber of 110 failures and retries ou each path. DMP call be collfigilred to use this infolluation to preveut the SCSI driver beiug flooded by 110 requests. This feature is h o w l as 110 throttliug. If an 110 request relates to a minored volume, VxVM specifies the FAILFAST flag. In such cases. DMP does uot retry failed I10 requests ou the path, aud instead marks the disks on that path as haviug failed.

.ds.rrs a~qovlai\!pv,103anop s! se s q ~ s d a y p s Xl)na.nn:, arp T~WSO.I~L? pamroj~ad! 8n!3ns[aq psol 'sLe.~~"-g,$pj pne 3 - 3 d j v '3-,$pj s .IOJ

'on )na.r1113i103 &~otldus ssapn sLs.rra ys!p a,1!ssad/a~!)3v .IOJpamroj~ad s! sqlad ~ ~ 0 . 1 3 s Kaq) )on %u!3nslsq pa01 ' i n i o p ~ o [ s a.IaAas It! st1nsa.r .raq)ow o) .rallo.rlno3 alro rnog S M ~ J O dys.rarnio 011 JO .raJsnsI) snonir!lno:, aq) s v .sq~sd hreprro3as .lo siged K.rarm.rd alqsl!ai\s "avo aqlol .IaAo paq3)+s S 011 'sl!t!~illsd L.rsm!.rd arIljI y)sd X.~sm!.rd aq) ~ r a o p ! luas s! 011 'sderm ys!p ai\!ssad/aA!pj r o . ~ y a d atlo Xna no psail.IaAo aq) a3npa.1 0) sipad a[qq!sAa atp sSO.1311palllq!.rJs!p s! a~ne.1 m q ) F aq) [lt?jlor1 saop laq) 011 le!lnanbas aS.rs7 .Si1!q3~3q3a.1) qs!p m0.g lyarraq 0) .rap.Io u! q)sd amas aq) m o p p a s s! a5ns.r u!a&ran t! n!q)p 8ir!).rels 011 1uttna11baS .srl~ud alqa[!sl\s llajo q l p ~ p w q w oaq) Smsn ~ l Kq ~udqSlio.ri1~ saz!tcqxsin On!3oolaq pa07 .SLRLIB 3 - g d w p~ 3 - d d w ' 3 - d / ~ 011 ys!p '~A!DVP,I!I~V .IOJ sil)" S S O J 5m3wlaq peol a p r ~ o r d m s ~ q 3 a m ~ ~ 01 rl)sd pa3nalaq arp s a w m a '~[nejap 43
.spaa33ns r p d aqj no 1sanba.1011 Zu!pw)s~nous J! .IOcqlad aql iro .ro.rra on s&rotla.~ ~ aqlj! qled aq) mo.y V H paAorna.1 s! Sm1~o.q) .sip" a[qaI!sAs laipo no papiparps a.Is qjsd lsq) 110 s~sauba.~ Sn!pna)s~110 ail1 011 at11 'q~ads o) pa!ldde s! Stnl~o.rip al!rlM q s d ail) no 1sanba.1011 11i~ssa33us agj an!s pasdsla lsal set1 a?) rra~!% .IO'an1aA L I ~ A ! ~paq3ea.r sarl s1sanba.1011 % ~ I ! ~ ~ I I ? I S ) I I O J O a s .raqnuirr aq) iraip .rarl)!a qlsd atp no )itas 5rrraq slsauba.1 011 Mail ~na,~a.rd pa.rnSrpo3 aq ne3 m a 'a,\!snodsa.r ssal amo3aq o) ssil )sip iped s rro d11 s p p q s1sanba.r 011 S n ~ p m ~ s ~ uraqrmln aq) put: GpalqstIa B t n l ~ o n l ~ ojo s!

.(Llpa.r103 sa3yap alp saz!r603a.r rira1sLs %rrga.~ado ~ s i lpap!,io.~d) pajooq L111g rraaq saq inalsLs aq) .raga aql ) sa3!~apaAoiira.1.lo ppa noh naqM pita 'pa.ropa.1 .ro pa.r!sda.~s! rio!13am103 e rtarp panrrop? osls s! m a ..Io)s.rlsnI!mpe aq) mog no!liraA.Ia1n! 1norlpn s~sa11ba.r 011 .IOJ [[lad alqsI!wa lxarr ail) spalas Klle3ysnro)ue m a c L a . ~ ~ q se p v s d e JO S S O ~ ! 01 aiIljo 1naAa aql nl .sLeria qs!p pal.~od!ylum ) p pas11 naqM /C1![!qa!ga.1 ma)sLs s a ~ n s q t ~ a ~ xa.rn)aaj m a a u q ~ ~ j o

'arimjrr03 0) )aeM uob .raq)aqM m n p o 3 0) pa)dnro.rd ale u o ' ~ l ~ 30 "a!A at[) mog a3!Aap s aplll3xa 0) lo f x ~ '(dmpm) .la.t!.rp ma ~ A X aqJ6q pail)sd!)lnm Sn!aq uroy a3!~ap e ~ n a ~ 01 warn nlem m p s y s ! p ~ A a~d aq) m0.g (May s . m x uroy sa3!nap s s a . r d d n ~ f i ~ ~ e d ! ) l u m ~ )naza.rd) L 1 7s" Iinaur palas 1

WXA alq!s!Au! sa+ap %u!yt:mput: Su!q~t:d!~lnm ol %o!lqt:s!a

' f l ~ x ~~j ao . taq) moy sa3!~apapnpxa .lo apiipxa 04 uob Molle osle ! sno!ldo imam asaqL .Brr!q)sd!lliinl alqerra .lo alqes!p 04 8 1 pne ~1 suo~ldo imam nrpep!pxt asli rw3 u o ~

saa!~ap3gpads JOJ fu!qlt:d!llnm

%u!lqt:uaput: %u!lqt:s!a

.ys!p eo) s q 1 ~ le3rsbqd Zm)s!xa arp 1 30 a.rom 10 airojo s s o l ~ s y a S e pamerlua s! Lu2qega.1ri~als/(s '>[s!p )oo.r aq) i3m.ro~r!m p ~ w Srrt)eliisds3oa b g .bene ys!p pavod!~liirue j o p d S! ys!p arlij! s q ~ e d ald!)lnat r l l y .ro .ys!p alSu!s e s! ) J qled ario !I q ) y a3!~ap ma e se passa33e ~ ~ ~ W ! ) W I O ~ I)! '[o.L)w~ ES! ~ X .Iapml pa3eld s! ys!p ) o o ~ n a l m A aq)

saqaap m

a m o g fu!looa

.be.ris EL aSp3.101~ arp no aporrr O I X ~ aq) a1qsna 01 o!sdm~ioddi~s-dm pnsrmno3 aql asn mis N sbs

'XX-gLZZI I P~"X-SI 1601 saq3)sd u! aIqel!eAe s! s b e . +EL pm! EL aSp31o)s .roj a.remmnj )sale1 aIll ~ ~ ~ '60-5 [ 160 I S! aps.~Sdu ,103q3)ed arll ' 8 ~ 1 . 1 a.rmrnJ EL aSp3,rols rnls at[) aps.rSdn )snm 1 1 0 ~ ST) o) .bs.rie arp no a3pap bnt! 04 sqled aldgli~nr aas IOU ~ X .Strqedypm salpmq ~ s o q no .raa.z!rpS ~ J aqj 'apom s ~q j.(ssedsa.q-oj~~enon A aql S JO .rai\opj ~ p q d x a apom 0 1 x m o) ~~.IIISIJ"O~ ) aq lsnm aSp3.10~~ arlj 'sno!)e.m81~"03 )soqypm UIIS

n+

.~tlamro.nAua pa.ralsnp-iiou e n! lsorl alZn!s e .ioj Sq)ed!)lnm alpneq o) pasn aq [re3 d w a .to .raA!.Ip (MISS) .~aStxmfl 1 3 " ~aSp3.1o)s nus arp .rarl)!g 3

m a W'MO I X ~ M u ! ~ n zI

4 5 6 7

Suppress a l l b u t one paths t o a d i s k Prevent m u l t i p a t h i n g o f a l l disks on a c o n t r o l l e r by VxVM Prevent m u l t i p a t h i n g o f a d i s k by VxVM Prevent m u l t i p a t h i n g o f disks by s p e c i f y i n g a VID:PID combination 8 L i s t c u r r e n t l y suppressed/non- m u l t i p a t h e d devices ? D i s p l a y h e l p about menu ? ? D i s p l a y h e l p about t h e menuing s y s t e m q Exit f r o m menus
Help text aud examples are provided ouscreeu for all the meun items. Select option 1 to exclude all paths tho11gl1 the specified controller fiom the view of VxVM. These the paths remain in the disabled state iu~til uext reboot, or mtil the paths are re-i~~cluded. Select option 2 to exclude specified patlis fi.0111 the view of VxVM. Select optiou 3 to exclude disks froiii tlie view of VxVM that match a specified Vendor ID and Product ID. Select option 4 to defiue a pathgroup for disks tliat are not u~ultipathed VxVM. (A pathgroup by explicitly defiues altelnate paths to the same disk.) 011ly oue path is made visible to VxVM. Select option 5 to disable multipatlhg for all disks on a specified controller. Select optiou 6 to disable m u l t i p a t l ~ ~ g specified paths. The disks that coi~espoud a specified foi to path are claimed in the OTHER-DISKS category and are uot mnltipathed. Select option 7 to disable multipatlhg for disks tliat ~ u a t c a ~ l specified Vendor ID and Product ID. to are in The disks that co~~espond a specified Vendor ID and Product ID co~iibi~iation clai~ued the OTHER-DISKS catego~y d are not multipathed. w Select optiou 8 to list the devices that are c ~ u ~ e n t suppressed or not mdtipathed. ly

+ + + +

+
+

Enabling multipathing and making devices visible to VxVM

Note: Some of tlie operations described in this section require a reboot of tlie system.
1 Select menu item 18 (Allow m u l t i p a t l h ~ ~ n s ~ i p p r devices from VxVM's view) from the ess

91

vxdiskadm ~ n a i u menu to re-enable multipathg for a device, or to make a device visible to VxVM to again. Yon are pro~upted confiim whether you want to contiuue.

2 Select the operation you want to perfoim from the displayed list:

paths t h r o u g h a c o n t r o l l e r f r o m VxVM's view Unsuppress a path f r o m VxVM's view 3 Unsuppress disks f r o m VxVM's view by s p e c i f y i n g a VID:PID combinat i o n 4 Remove a pathgroup d e f i n i t i o n 5 A l l o w m u l t i p a t h i n g o f a l l disks on a c o n t r o l l e r by VxVM 6 A l l o w m u l t i p a t h i n g o f a disk by VxVM 7 A l l o w m u l t i p a t h i n g o f disks by s p e c i f y i n g a VID:PID combinat i o n 8 L i s t c u r r e n t l y suppressed/non- m u l t i p a t h e d devices ? Display help about menu ? ? Display help about t h e menuing system q Exit f r o m menus
2

1 Unsuppress a l l

+ Select optioi~21 to ~ilakespecifiedthrooghvisible to VxVM. visible to VxVM. + Select option to make all paths paths a specified controller + Select option 4 to make disks visible todefinition. (Amatch a specified Vei~dorID and Product ID.to 3 to VxVM that + Select option remove a pathgroup pathgroup explicitly defiues altei-natepaths
the sanle disk.) Once a pathgroup has been removed, all paths that Lvere defined in that pathgroup become visible agaiu. Select option 5 to enable multipathing for all disks that have paths through the specified coi~troller. Select option 6 to enable multipathg for specified paths. Select option 7 to enable multipatlung for disks that match a specified Vendor ID and Product ID. Select option 8 to list the devices that are currently suppressed or uot moltipathed.

+ + + +

Displaying the paths to a disk

The \xdisk command is used to display the multipatliing infoinlation for a pai-ticular metadevice. The metadevice is a device representation of a pal-ticular l>hysical disk having mirltiple physical paths fiom one of the system's HBA conh.oliers. hl VxVM, all the physical disks ill the systein are repr~sented as metadevices with one or more physical paths. Y4~1 use the vxdisk path c o u u n a ~ ~ dul>play the relationships between the device paths, disli can to access names, disk media names w d disk groups on a system as s h o w here:
.,.

SUBPATH

DANAME

DMNAME

GROUP

citodosz cqtodosz citidosz cqtidosz

citodosz citodosz citidosz citidos2

rnydgol rnydgol rnydg02 mydgoz

rnydg rnydg mydg mydg

STATE ENABLED ENABLED ENABLED ENABLED

This shows that two paths exist to each of the two dislis, mydgO1 and mydg02, and also indicates that each disk is in the ENABLED state. information for a pal-ticularmetadevice, use the following commalid: To view m~dtipathing

For example, to view multipathing infolmation for c2tOdOs2, use the followii~g command:
i i*.~di,rk cZtOtl0.sZ ! list

Typical output from the vxdisklist couunand is as follows: Device devicetag t Pe Y host i d disk 9 ro u P flags pubpaths privpaths cztodo cztodo sliced aparaj i t a name=mydgol i d = 8 6 1 0 8 6 9 1 7 . 1 0 5 2 . a p a r a j i t a name=mydg i d = 8 6 1 0 8 6 9 1 2 . 1 0 2 5 . a p a r a j i t a o n l i n e ready autoconf ig autoimport imported block=/dev/vx/dmp/cztodos4 char=/dev/vx/rdmp/cztod0s4 block=/dev/vx/dmp/c~todos3 char=/dev/vx/rdmp/cztodos3 2.1 min=512 ( b y t e s ) max=zo48 ( b l o c k s ) s l i c e = 4 offset=o len=1043840 slice=3 offset=l len=iiig t ime=861801175 s e q n o = o . 4 8 0 248 count=i len=795 count=i len=lzo

version iosize public private update headers configs logs Defined r e g i o n s c o n f i g priv 000017- 0 0 0 2 4 7 [ 0 0 0 2 3 l ] : c o p y = 0 1 o f f s e t = o o o o o o e n a b l e d c o n f i g priv 000249- 0 0 0 8 1 2 [ 0 0 0 5 6 4 ] : c o p y = 0 1 o f f s e t = o o o z 3 1 e n a b l e d log priv 000813- 0 0 0 9 3 2 [ 0 0 0 l z o ] : c o p y = 0 1 o f f s e t = o o o o o o e n a b l e d Multipathing information: numpaths: 2 cztodosz state=enabled type=primary c i t o d o s z s t a t e = d i s ab l e d t y p e = s e c o n d a r y
III the Multipathing i~lfo~mation section of this outpi~t, ~lt~lupatl~s shows that there are 2 paths to the line the device. and the following two liues show that the path to c2tOdOs2 is active (state=enabled) and that the other path cltOdOs2 has failed (state=disabled):

The type field is showu for disks OII Actiw~eIPassive type disk arrays such as the EMC CLARiiON, Hitaclli HDS 9200 and 9500. Sun StorEdge Gxxx, and Sun StorEdge T3 allay. This field indicates the primary and seco~ldaly paths to the disk. The type field is not displayed for disks on ActivelActive type disk allays such as the EMC Symetiix, Hitachi HDS 99xx and S L I ~ StorEdge 99xx Series, and IBM ESS Series. Such allays haw:e uo concept of p~iluary secoadary patlls. and

Administering DMP using vxdmpadm

The vxd~npadm utility is a c o m a u d liue adllliuistrative iuterface to the DMP feature of VxVM. You utility to perfoivl the following tasks. can use the vxdu~padul Rehieve the name of the DMP device co~esl~oudiug a paiticular path. to Display the members of a LUN group. List all paths under a DMP device node, HBA controller or array port. Display idolmation about the HBA conhollers on the host. Display ido~matiou about euclosiaes. Display illfol~llatiou about amay poits that are couuected to the storage processors of enclosnres. Display illfollnation about devices that are col~trolled third-party nlultipatlhg diivers. by Gather VO statistics for a DMP node, enclosnre, pat11 or couholler. Coufigue the am-ibutes of the paths to an enclosure. Set the UO policy that is used for the paths to an a~closi~re. Enable or disable I10 for a path, HBA controller or array poit on the system. Upgrade disk conholler fu~uware. Rename an enclosure. Coufig~re how DMP responds to UO request failures. Configure the UO throttling mechauism. Couhol the operation of the DMP path restoration thread. The following sectious cover these tasks ill detail along with sample output.

... . ....

Retrieving information about a DMP node

The followiug c o ~ l u a n d displays the DMP node that coi~trols palticular physical path: a

The physical path is specified by alyomeut to the nodename attribute. ~vhich lnost be a valid path listed iu the Idevlrdsli directoly. The above cornland displays o i ~ t p such as the followi~g: ~~t

........................................................... ........................................................... c 3 t z d i s z ENABLED T3oo 2 2 0 enco

NAME

STATE

ENCLR- TYPE PATHS

ENBL DSBL ENCLR- NAME

Use the enclosme attribute with getdmpuode to obtaiu a list of all DMP nodes for the specified euclosiue.

NAME STATE ENCLR- TYPE PATHS ENBL DSBL ENCLR- NAME ............................................................... ............................................................... c z t i d o s z ENABLED T3oo 2 2 o enco c z t i d i s z ENABLED T3oo 2 2 o enco c z t i d z s z ENABLED T3oo 2 2 o enco

Specifying the UO policy

You call use the vxdmpadtusetam colnl~laud chauge the VO policy for distributi~~g load across to UO inultiple paths to a disk anay or enclosure. Yo11 can set policies for all enclosure (for example, HDSOl), for all enclosmes of a palficolar type (such as HDS), or for all enclosi~res a palficdar array type of (such as A/A for ActiveIActive, or A/P for ActivePassive).

Note: Stalfiug with release 4.1 of VxVM. UO policies are recorded in the file letc/\rxldmppolicy.info, aud are persistei~t across reboots of the system. Do uot edit this file yo~~rself.
The followi~~g policies may be set: .Adaptive This policy attempts to lnaxiinize overall VO thoughpot fromdto the disks by dyi~all~ically schedulii~g on the paths. It is suggested for use kvhere 110 loads can vary over time. For example. I10 I10 fiomlto a database ~ u a y ediibit both long trausfers (tabIe scans) aud sl1012 trausfers (random look ups). The policy is also useful for a SAN enviro~imeut wl~ere different paths may have differeut ui~mber of hops. No f111fher configuration is possible as this policy is auton~atically rnauaged by DMP. In this example, the adaptive 110 policy is set for the euclosi~re encl :
# vxdtnpadm setattr enclosure euc I iopolicy=adaptive

.Balanced [pa~titiousize=size]This policy is designed to optimize the use of caching in disk drives aud RALD controllers. The size of the cache typically ranges fro111IZOKB to 500I(B or more, depending on the characteristics of the pa~ticolar hardware. During normal operation, the disks (or LUNs) are logically divided into a t~u~nber regions (or paititions). and 110 fronllto a given region is sent ou only of one of the active paths. Should that path fail, the workload is auto~natically redistributed across the relnainiug paths.

:aom K S Jb m n t ~ ~ r01rL3yod 011 aql slas aldrnaxa 811puol[oj ar~.aiiaub p IsabIoqs aql I I ~ qled atp sarmpualap L~~e3ylaurolna ~ Z ma se a~qissods! I I O ! ~ ~ . I ~.Iaq&nijON ~' p x a lot1 saop ~IJ~O ar13w 39312." 111~3g*!s e a.Iaqu s a o w .IOsys!p pna-MO~~ oaIqel!lis s! S!IU ' ~ e .IOJana~ib m . j 7 aql sprtas L ~ l o d q b ~ n ~ r n w s m s)sanbn.l 011 Sn!pr~e~s~no~o m r i r ~ aql~ i \ q lstll s r ~ s d .xaqmuu r a uo

.S~];IAZ ,so spea.1 le!lrraubas jo Lpsom sls!suo3 leql I L I ~ U rCI!~!ve 011 11s .roJ ( m ~ 01 a ~C~ 9 9 1) S9301q ZLO'I EI 01 S ~ L ' Z E ln0.1~ L ~ . L I ~ O9GG S(M s! V/V !II3E)!H ne SOJ az!s no!l!l.rad palsaSSns arp 'aldmaxa .IOJ ' ( a w l ) sy30[q 8tOZJO az!s no!l!l.red llrlejap arIl 01 lualm!~iba s! OJO az!s no!l!&mt?d s SulLjpads 'an[&\ alqelda33e lsa.rean aq) o) twop papm1o.r L[lnal!s s! 230 . ~ a ~ o tIon s! leql a1ilsA v .(m1) le s~301q t . 0 ~ az!s no!lqred a q roj anleA lIIlqap a u 8 S!

mpriority This policy is usefill when the paths in a S A N have unequal perfonnance, and you want to ellforce load balauciug mauually. You call assigu priorities to each path based ou your howledge of the configuratiou aud perforulauce characteristics of the available paths. and of other aspects of your system. h tlus example, the I/O policy is set to priority for all SENA amays:
# vxd~npadol setam alrayuame SENA iopolicy=priority

mrouud-robu~This policy shares 110 equally betweeu the paths iu a rom~d-robiu sequence. For example. if there are three paths. the first I10 request would use one path, the second would use a different path. the third would be seut down the remau~uig path, the foul211would go down the first path, aud so ou. No further coufig~u.atiouis possible as this policy is automatically managed byDMP. The uext example sets the VO policy to rouud-robiu for all ActiveIActive allays:
# vxdmpadm setam anaytype AIA iopoIicq=ro~rud-robui

This is the default 110 policy for A/P aud Asylnlnetric ActivelActive (AIA-A) alrays. msiugleactive This policy ~.ontes down the siugle active path. This policy cau be co~~figured A/P VO for a m y s with one active path per coutroller. where the other paths are used in case of failover. If co~~figured AIA allays, there is no load balauciug across the paths. aud the alternate paths are ouly for used to provide high availability (HA). If the cul~eutly active path fails, VO is switched to au alte~uate active path. No further collfig~~ratiou possible as the siugle active pat11 is selected by DMP. is The followi~~g example sets the 110 policy to siugleactive for JBOD disks:
# vxd~npadm setattr anayname DISK iopolicy=siugleactive

Module 6:

Creating and administering disk groups

This chapter describes how to create and manage disk groups. Disk groups are named collections of disks thatshare a common configuration. Volumes are created within a disk group and are restricted t o using disks within thatdisk group.

Note: III releases of Veritas Volume Mauager (VxVM) prior to 4.0, a system installed with VxVM was collfigui. I.\. ith a default disk group, rootdg, that had to contain at least one disk. By default, operatioic \\dre directed to tlie rootdg disk group. From release 4.0 onward, VxVM cau function without auy disk group having bee11 configulred. Ollly when the fust disk is placed uulder VxVM colltrol must a disk group be configuued. There is no longer a requirement that you name m y disk group rootdg, and any disk group that is nalned rootdg has 110 special properties because of this name.
11

Additionally, prior to VsVM 1.0, some commands such as vxdisli were able to deduce the disk group if the name of an object was u~~liquel y defined ul one disk g o u p among all tlie inipol-ted disk groups. Resolution of a disk group in tlus way is no lo~lger suppol-ted for any command. For a discnssion of disk g o ~ ~ that are colnpatible with the Cross-platfolnl Data Sharing (CDS) ps feahlre of Veritas Volume Manager, see the Veritas Storage Fouudation Cross-Platfo~m Data Sharulg Admblistrator's Guide. The CDS feature allows you to lllove VsVM disks and objects between machiues that are ~x~mling uulder different operatiug systems. As system admillistrator, you cau create additioilal disk groups to arrange your system's disks for different purposes. Matly syste111sdo not llse niore than one disk group, unless they have a large ~ n ~ m bofr disks. Disks cal be initialized, reserved, and added to disk g o u p s at any time. Disks ueed e not be added to disk groups ~llltil disks are needed to create VxVM objects. the When a disk is added to a disk group, it is given a llaule (for exalqle, mydg02). This name identifies a disk for operations such as volume creation or m i ~ ~ o r i uThe name also relates directly to the g. underlyiug physical disk. If a physical disk is moved to a different target address or to a different controller, the name mydg02 contiuues to refer to it. Disks can be replaced by first associating a different physical disli with the uanle of the disk to be replaced aud then recoveriug auy vol~uue data that was stored on the origiual disk (from minors or backup copies). Having disli groups that contain mauy disks and VxVM objects causes the private regiou to fill. In the case of large disk groups that are expected to coiltain Inore than several huludred disks and VxVM objects, disks should be set op wit11 larger private areas. A major pol-tion of a private regiou provides space for a disk g o u p configl~rationdatabase that contains records for each VxVM object iu that disk group. Because each configuration record talies up approsinlately 256 bytes. the number of records that can be created in a disk group call be estimated fiom the configu~rationdatabase copy size. The copy size iu blocks can be obtained fiom the outpu~t the co~n~iiand of vxdglist diskgroup as the value of the p e l d e n parameter on the line stalling wit11 t l ~ e string "config:". This value is the snlallest of the leu values for all copies of tlie configuration database ui the disk group. The amouut of renlai~~iug free database is s h o w as the value of the free parameter. space in the collfigu~ration

Specifying a disk group to commands

Note: Most VxVM coinlnands require sluperuser or eqnivaleut privileges. Maily VxVM comluauds allow you to specify a disk group using the -g optiou. For example, the followiug command creates a volume in the disli group. lulitdg:
# vxassist -g d i d g make inktvol 5g

The blocli special device coi~espo~ldiug this vollume is: to

System-wide reserved disk groups

The followiug disk group uames are reserved, and cannot be used to ilalne any disli groups that yo11 create:
IT-

t-

bootdg

Specifes the boot disk group. This is an alias for the disk group that co~ltaius the volull~es are used to boot the system. VxVM sets bootdg to the appropriate that disli group if it takes c o ~ ~ t r ofl the root disk. Otherwise, bootdg is set to uodg (uo o disk grotup; see below).

Caution: Do not attempt to chauge the assigned value of bootdg. Doiug so may reuder your system onbootable. defaultdg Specifies the default disli group. This is an alias for the disk groop name that should be assumed if the -g option is i ~ o specified to a commaud, or if the t VXVMDEFAULTDG ei~viroimieut ~rariable lundefmed. By default, defaultdg is is set to nodg (uo disli group; see below). Specifies to an operation that no disk group has been defined. For example, if the root disk is not m~der VxVM control. bootdg is set to nodg.

nodg

Note: If yon have upgraded your system. yon may find it conveuieut to continue to coufigure a disk group uamed rootdg as the default disli groop (defaultdg). There is no requiemeut that both defaultdg aud bootdg refer to the same disli group, nor that either the default disli group or the boot disk group be named rootdg.

.pamjapml s! dno.18ys!p ,Ingap aq) 'pt1ammo3Zpllngaplppm arp 01 1naum5.re arn ss paypads s! 5ponj1 'dno.18 ys!p ~ o o q p ~ - m a l s L pamjap Lllna.~1113 a s aq) sa anras arp aq o) las st dno.15 ystp )Ingap arp 'p11~nnro3 01 laamn8.1e arp se pagpads s! Sp~ooq SR) j~

:duo.18 ys!p 11Ilejap arp Lelds!p 01 p~reurnro:, 5 1 r ~ o l l o j asn nu3 noL '.<la~!lenrally .paLslds!p s! Bporr 'pangap aaaq Ion serl duo.18 ys!p )111ejape j ~ aq)

:pnenrrr103Sn!Molloj alp asn 'dno.15 ys!p )Inejap app+uralsLs parigap L[lna.~1113 Lslds!p 0 atp 1

dno~8 ys!p qnqap apuc-ara~s6s Bu!Lpads par! Ba!6r!lds!a aq]

:pnemuro3 B ~ o ~arp asn 'duo.15 ys!p looq app+aia)sLs pangap K[~rra.~in3 Keldslp 0 ~ o j arp 1

dno.18ys!p ~ o o q apw-map6s aqJla!6alds!a

'1!ej Lem anren ~oafqo m0.g d110.15 ysrp aq, Bn!onpap ao L1a.r leql s)drr3g .papoddus .raZno~ rx on s! &!leno!l3mg s!q1 .pnsmn103 e Lq nod11 pala.rado Sir!aq s w )eq) ariren 13afqo atp .roj Bq3.reas Lq d1lo.13 qs!p aq) ampap 01 p a l d r ~ r a ~ e spueo1~103jo lasqns e 'UP 01 .IO!.I~ MXI\JO sasea1a.r q :oo!lnr3

. . .

.os op '(sp.ro3a.r ssame ys!p no no!)e.rado l!pa [re 'aldmaxa .roj) auisu duo.r8 xs!p e 5tynba.r ) n o q ) p a a ~ r o j ~ a d nu3 no!le.rado ar1)jIw ~ aq .pa![dde s! alnr ZUVO[~OJ 'pamjapml s! sege s g ~ j ~ aql %plpejap 'se!p dno.18 ys!p lInejap a p ~ - m a ~ aq) o) pa@sse naaq seq larll dno.15 ys!p aql a s n u Ls .pa!ldde s! ap.r 5 ~ ! ~ o [ [ o j 'pangapnn s! alqs!.rsA arp JI %pan .lo 'Sp)~nejap'5plooq :sawen aqj dn0.G ys!p a p ~ - u r a ) s b s pahJasa.1 aq)jo sno 01 ,as aq osle m o alqe!.le s g 1 ' ~ ) a l m v g g a - m ~ a[q"rtx ~rariruo.~!~na A p a p a d s s! )erl) aareo d1io.18ys!p )Ingap aql a s n u aql q :amen d11o.15ys!p e s a p a i a j a p I! 1!)ru1 .rap.ro r! sal1i.r 8 r v o l [ o j aq) sa![dde MAXI\ 'dno.18 ys!p arp L p a d s )on op 11oLj1.ao!ldo s!ql r p a p n a m m o ~ a ~1 s! 1 )da331! le11) spi1erm03WI\XA0) d110.18 ys!p a Ljpads 01 rio!ldo 8- arp asu uoL

dno.18ys!p qnqap aq] Bo!u!m.ralap aoj salna

Displaying disk group information

To display hlfol.~l~ation existing disk groups, enter the followii~g on coinu~aud:
# vxdg list

NAME rootdg newdg

STATE enabled enabled

ID 730344554.1025.tweety 731118794.1213. t w e e t y

To display more detailed u~fon~~ationa specific disk group. use the followiving command: on
# w d g list diskgro~ip

The output fiom this c o r n a n d is similar to the following:

Group: m~dg dgid: g6zglog60.loz5.bass import- id: 0.1 flags: 140 version: l o c a l - a c t i v a t i o n : read- w r i t e 512 ( b y t e s ) alignment : ssb: on detach- policy: local nconfig=default nlog=default copies: config: s e q n o = o . l 1 8 3 p e r m l e n = 3 4 4 8 f r e e = 3 4 2 8 templen=12 l o g l e n = 5 z z config d i s k c o t l o d o copy 1 l e n = 3 4 4 8 s t a t e = c l e a n o n l i n e config d i s k c o t l l d o copy 1 l e n = 3 4 4 8 s t a t e = c l e a n o n l i n e 109 d i s k c o t i o d o copy 1 l e n = g z z 109 d i s k c o t l l d o copy 1 l e n = g z z
Note: hl this exaulple, the aduliuistrator has chosen to uame the boot disk group as rootdg.

To verify the disk group ID and name associated with a specific disk (for example. to iillport the disk group), use the followiug c o r n a n d :
# vxdisk -s list devicename

This coiluna~ld provides outpiit that includes the followiug infolmation for the specified disk. For example, output for disk cOt12d0 as follows:

Disk: type: flags: diskid: dgname: dg id : hostid: info:

cotlzdo simple online ready p r i v a t e 963504891.1070. b a s s newdg g635048g5.1075.bass bass privoffset=128

autoconfig

autoimport imported

Displaying free space in a disk group

Before yo11add volu~uues file systems to youu system, make stwe you have enough free disk space to aud llleet your ueeds. To display free space iu the syskm, use the following colnlllaud:
# vxdg free
-.>

The following is example output:

GROUP myd9 myd9 newdg newdg oradg

DISK rnydgol mydg02 newdgol newdgoz oradgo1

DEVICE cotlodo cotlldo cotlzdo cotl3do cotlqdo

TAG cotlodo cotlldo cotlzdo cot13d0 cotlqdo

OFFSET

o o
o

LENGTH 4444228 4443310 4443310 4443310 4443310

FLAGS -

To display free space for a disk grou~p,. the follo~viug use command:
# vxdg -g diskgroup free

where -g diskgroup optionally specifies a disk grou~p. For example, to display the fiee space in the disk ~ ~ r o umydg. use the following command: p,
# vxdg -g mydg free

ou~tptd shows the aiiuouuit of free space in sectors: The followiug exa~iuple

DISK mydgoi mydg02

DEVICE cotiodo c0tlld0

TAG cotiodo cotlldo

OFFSET o 0

LENGTH 4444228 4443310

FLAGS -

Creating a disk group

Data related to a particular set of applications or a pa~ticular group of users ulay need to be made of accessible on another system. Exall~ples this are: A system has failed and its data needs to be moved to other systems.
w The work load i-h~nst balauced across a number of systems. be

Disks must be placed in one or more disk groups before VsVM can use the disks for volumes. It is iu~poltant you locate data related to pa-hticularapplications or users on an identifiable set of disks. that When you need to move these disks, this alloms you to lnove only the application or user data that should be moved. A disk gronp must have at least one disk associated with it. A ilew disk group can be created when you use menu item I (Add or iuitialize one or more disks) of the wdiskadm conlmai~d add disks to to VxVM control. p t to The disks to be added to a disk ~ o u must i ~ obeloi~g an existing disk group. You can also use the vxdiskadd colnuland to create a new disk group:
# vxdiskadd cl tOd0

wl-herecltOd0 in this example is the device name of a disk that is i ~ ocurrently assigned to a disk group. t Disk groups call also be created by using the mdgillit c o m ~ a u d :
# vxdg init diskgroup [cds=ou/offl disliuame=deviceuame

For example, to create a disk group named nlktdg on device cltOdOs2:

# vxdg hlit d t d g inktdgOl=c l tOdOs2

The disk specified by the device name, cltOdOs2. must have been previously initialized with vxdiskadd or vxdiskadm, and must not cui~ently beloilg to a disk group. Yon cru~ the cds attribute with the vxdgiuitconnnru-hdto specify whether a new disk group is use compatible with the Cross-platfollu Data Sharing (CDS) feature. lu Veritas Volume Mauaser 4.0 and later releases, newly created disk groups are colnpatible with CDS by default (equivalent to specifying cds=ou). If yon wru~t change this behavior. edit the file /etc/default/vxdg, and set the attribute-value to pair cds=off in this file before creating a new disk group. Alternatively, you can use the following command to set this attribute for a disk group:
# vxdg -g diskgoup set cds=ouloff

Adding a disk to a disk group

To add a disk to an existiug disk group. use menu item 1 (Add or initialize one or more disks) of the vxdiskahn c o m a n d . You cau also use the vxdiskadd commaud to add a disk to a disk group, for example:
# vxdisliadd c l t l do

where c It1 do is the device name of a disk that is not currently assigued to a disk group.

Removing a disk from a disk group

A disk that coutaius no subdislis can be removed f i o ~ u disk g o u p with this commatld: its
# vxdg [-g diskgroup] nndisk disliuame

For example, to remove mydgO2 from the disk grollp, mydy. use this co~uu~and:
# vxdg -g mydg ~uldisk mydgO2

If the disk has subdisks on it when you try to remove it, the followiug elyol. message is displayed:

VxVM v x d g ERROR V - 5 - 1 - 5 5 2 D i s k d i s f c i ~ u ~i s ~ e ~ used by one o r more subdisks Use - k t o remove d e v i c e a s s i g n m e n t .

Usiug the -k option allows you to remove the disk eve11 if subdisks are present. page. For more ulfonnation. see the vxdg(1M) ma~~lual
u Caution: Use of the -k optiou to vxdg can result i data loss.

Once the disk has bee11 removed fiom its disk group. you call (optionally) remove it fioin VxVM control completely, as follows:

For example, to remove cltOdOs2 from VxVM control, use these commands:

You cau remove a disk OII ~vllich some subdisks of volulnes are defined. For example. you call consolidate all the volumes outo one disk. If you ~~sevsdiskadm remove a disk, yo11 can choose to to move volumes off that disk. To do this, rtui vxdiskadm and select item 3 (Remove a disk) fro111the nlaiu menu.

If the disk is used by some volulmes, this luessage is displayed:

VxVM ERROR V - 5 - 2 - 3 6 9 The f o l l o w i n g volumes c u r r e n t l y disk mydgoz: home usrvol

use part of

Volumes must be moved f r o m mydgoz before i t can be removed. Move volumes t o other disks? [y,n,q,?] ( d e f a u l t : n)
If you choosey, then all volunles are moved off the disk, if possible. S O I I I ~ volomes may uot be n~ovable. i e most c o m o n ~.easons f \+by a volume may not be movable are as follows: There is not enou& space ou the remaiuing disks. Plexes or striped st~bdisks cannot be allocated on different disks fiom existing plexes or striped subdisks in the volume. If \.xdiskadmcaunot move some volllmes. you may need to remove S O I I I ~plexes from some disks to free more space before proceediug with the disk re111ova1operation.

*M~U

(IS!]

:$lne4ap)

[ i ' b 1 $ s ! ] ' < d n o ~ 6 > ] d n o l 6 y s ! p 40 a u e u ~ a $ u 3

. y s ! p a q $ 6 u ! ~ o u a l aJO4Jq y s ! p a q $ o$ ssa33e I l e a ] q e s ! p O $ $ U P $ J O ~ U ! S! $! 'sua$sr(s a u o s UO Sa3!AJp yS!p a l q e A o w a l l o j ' ( ~ a u ! l 4 4 0 ) P a l q e s ! P a4 P l n o 4 s sys!P a q l 4! Payse aq o s l e ll!M noA . d n o ~ 6 y s ! p e 40 a u e u a y $ l o 4 p a $ d u o ~ daq l l ! ~o, n) . a s o d l n d ~ a a u o s l o 4 d n o l 6 y s ! p e u ! 6 u ! u ! e u a l s y s ! p a y $ 40 I l e asn u 4! d n o ~ 6 y s ! p e $ l o d a p ' o s l v - u a $ s r ( s l a y l o u e o $ d n o l 6 ys!p e u ! sys!p aAoU 01 p u a $ u ! nor( J! d n o l 6 y s ! p t? $ l o d a a
01 JueM nor(

muam n!sm tnpsys!px.\ aq, mog (d1io.15ys!p s (4.1odap) 01 ssa33s a;\ottra~) tua)! nnam palas E 6

'(sassqslsp .lo smalsds aIg pa)mlour Lq 'aldmsxa ,103) asn u! a.w lerll samcqoA sn!slrro:, dno.rS ys!p atllx spsj toopabrodaa : a ) o ~ .samll[oA at11 no pa.111Syuo3ars lsq) sassqsjsp m o p p ~ t pus srrralsLs alg lmlomnn .pal.~odap ~s aq 01 s! let[) dlio.12 ys!p aql n! pa.1118yt103 am ~ s l satrmIo~\01 suo!la:,!ldds Lq ,Cl!~!131! 11s do)^ 1 p

5 At the following prompt, euter y if yo11 iuteud to remove the disks iu this disk group:

VxVM INFO V - 5 - 2 - 3 7 7 The requested o p e r a t i o n i s t o d i s a b l e access t o t h e removable d i s k group named newdg. This d i s k group is s t o r e d on t h e f o l l o w i n g d i s k s : newdgol on device c l t l d o You can choose t o d i s a b l e access t o ( a l s o known as " o f f l i n e " ) these d i s k s . This may be necessary t o p r e v e n t e r r o r s i f you a c t u a l l y remove any o f t h e disks f r o m t h e system. Disable ( o f f l i n e ) t h e i n d i c a t e d d i s k s ? [y,n,q,?] (default: n) y
G At the followiug prompt. press Rehn.11to cotltillue with the operatiotl:

Continue w i t h o p e r a t i o n ?

[y,n,q,?]

(default:

y)

Once the disk group is deported. the vxdisltadm utility displays the following message:

VxVM INFO V - 5 - 2 - 2 6 9 Removal o f d i s k group newdg was s u c c e s s f u l .

7 At the followiug prompt, iudicate whether you waut to disable another disk group (y) or rekiln to the vxdiskadm maiu meuu (u):

Disable another disk group? [ y , n , q , ? ]

(default:

n)

Alte~natively, cau use the vxdg coiumand to deport a disk group: you
# vxdg depolt diskgroup

Importing a disk group

huporti~ig disk group enables access by the systeni to a disk groap. To liiove a disk group from one a system to another, f i s t disable (deport) tlie disk group on the o~igi~ial system, and then move the disk between systems and enable (import) Llie disk group.

To import a disk group

1 Use the follo\Yiug co~ii~iiand ensure that the disks iu the deported disli gl.oup are online: to
# vxdisk -s list

2 Select menu item 8 (Euable access to (import) a disk group) fiom the vxdiskad~u ~naiii menii.
3 At the followiug prouipt, enter the liauie of the disk group to import (in this esaiill~le, newdg):

Enable access t o ( i m p o r t ) a disk group Menu: VolumeManager/Disk/EnableDiskGroup Use t h i s o p e r a t i o n t o enable access t o a d i s k group. This can be used as t h e f i n a l p a r t o f moving a disk group f r o m one system t o a n o t h e r . The f i r s t p a r t o f moving a d i s k g r o u p i s t o use t h e "Remove access t o ( d e p o r t ) a d i s k group" o p e r a t i o n on t h e o r i g i n a l host. A disk group can be i m p o r t e d f r o m a n o t h e r host t h a t f a i l e d w i t h o u t f i r s t d e p o r t i n g t h e d i s k group. Be sure t h a t a l l disks i n t h e disk group are moved between hosts.
I f t w o hosts share a SCSI bus, be very c a r e f u l t o ensure t h a t t h e o t h e r host r e a l l y has f a i l e d o r has d e p o r t e d t h e d i s k group.

I f t w o a c t i v e hosts i m p o r t a disk group a t t h e same t i m e , d i s k group w i l l be c o r r u p t e d and w i l l become unusable. S e l e c t d i s k group t o i m p o r t [<group>,list , q , ? ] (default:

the list)

newdg
Ouce tlie inpoi? is complete, the vxdiskad~u utility displays the followi~lg success message:

VxVM INFO V - 5 - 2 - 374 The i m p o r t o f newdg was s u c c e s s f u l .

4 At the followi~ig pro~i~pt, indicate whether you want to h p o ~ allother disk g o u p (y) or rehum to the t vxdisliadm u~aiu 1ue1i11 (u):
S e l e c t a n o t h e r disk g r o u p ? [y,n,q,?] (default: n)

Alternatively, you cau use the vxdg command to import a disk group:
# vxdg import diskgroup

Renaming a disk group

Only one disk group of a given name call exist per systelu. It is not possible to inipoit or depoit a disk group when the target system already has a disk group of the same nan~e. avoid this problem. To VxVM allows you to reuame a disk group during i~nport depolt. or To Yenaine a disk group dulling import, use the following command:
# vxdg [-t] -n newdg import diskgroup

If the -t option is iacluded, the inlpo1-t is temporaiy aud does ilot persist across reboots. I 1 this case. the 1 uuchanged ou its original host. but the disk g o o p is known by stored uaille of the disk group re~naius the llalne specified by ilewdg to the unporting host. If the -t option is not used. the name change is pe~manent. For example. this command temporarily renames the disk group. mydg. as mytempdg on iinpo~t:
# vxdg -t -n nlytempdg impoit mydg

To reuame a disk group during deport. use the followi~lg couunaud:

# vxdg [-I1 host~lame]11 ilewdg deport diskgroup -

When re~la~niug depoit. you ca11 specify the -11 hostnalne option to assigu a lock to an alteiuate host. on This ensures that the disk group is autonlatically imported wllell the alternate host reboots. For example, this command reuaines the disk group, mydg, as myexdg. and deports it to the host, jingo:
# vxdg -h jillgo
-11

tnyexdg deport mydg

Note: YON carnot use this method to rename the boot disk group because it coiltaias volu~ues are that iu use by mounted file systems (such as 1). To renaine the boot disk group, you must first umlli~~or aud u~~et~capsulate root disk. aud theu re-eucapsulate and remk~or root disk h~a different disk group. the the This disk groop becoiues the new boot disk group.

Destroying a disk group

Tl~e vxdg c o ~ n ~ u provides a destroy option that relnoves a disk group fro111the system and fiees the a~~d disks h~that disk group for reinitialization:
# vxdg destroy diskgroup

.-.

Caution: This coluluaud destroys all data ou the disks.

When a disk group is destroyed, the disks that are released can be re-used in other disk groups.

Module 7: Creating and administering subdisks

This chapter describes how to create and maiutaio subdisks. Sobdisks are the low-level building blocks in a Ve~itas Voltuue Maoanger (VxVM) collfig~~ration are required to create plexes and voliunes. that Note: Most VxVM comma~ids require superuser or equivalent privileges.

Creating subdisks
Note: Snbdisks are created a~~tomaticallyyou use the vxassist collunand or the Veritas Entelplise if Administrator (VEA) to create volulnes. Use the vx~nake command to create VxVM objects, such as subdisks:
# vxmake [-g diskgroop] sd st~bdisk diskname,offset.le~~gth

where: subdisk is the name of the su~bdisk, disk~~aluethe disk name, offset is the starting poiut is (offset) of the snbdisk w i t h the disk, aud leu,& is the leugth of the ssubdisk. For example, to create a subdisk na~ned mydg02-01 iu the disk group, nlydg, that starts at the beginning of disk mydg02 aud has a length of 8000 sectors, use the following command:
# vx~nake mydg sd 1uydg02-01 mydg02,0,8000 -g

Note: As for all VxVM couuuands. the default s u e unit is s. representing a sector. Add a suffix. such as k for kilobyte, ~n for megabyte or g for gigabyte. to change the imit of sue. For example, 500111 would represent 500 megabytes. If yon iuteud to use the new snbdisk to build a voltune, you must associate the subdisk with a plex. Snbdisks for all plex layouts (coucatenated. striped, RAID-5) are created the same way.

Displaying subdisk information

The v x p ~ uco~ll~nanc! ~t ili~plays iuforn~atiou about VxVM objects. To display general iufo~nation for all subdisks. use this couuuand:
# vxpriut -st

The -s optiou specifies information about subdisks. The -t option prints a single-line oatptd record that depends ou the type of object being listed. The following is example output:

SD SV sd sd

PLEX DISK DISI(0FFS NAME PLEX VOLNAME NVOLLAYR NAME m y d g o l - 01 v o l l - 01 m y d g o l o mydgoz- 01 v o l z - 01 mydgoz o

LENGTH LENGTH 102400 102400

[COL/]OFF DEVICE MODE [COL/]OFF AM/NM MODE 0 c o t l o d o ENA 0 c o t l l d o ENA

You cau display co~uplete hlfon~~ation about a partic~~lar sttbdisli by using this cornma~~d:

For example, the followiug C O I I I I U ~ I Idisplays all h~fo~matiou snbdisli mydg02-01 in the disk ~ for group, mydg:

'Illis couunand provides the followilly outpnt:

Disk g r o u p : Subdisk: info: assoc: flags: device:

mydg mydgoz- 01 disk=mydgoz o f f s e t = o len=zo5632 v o l = m v o l p l e x = m v o l - 02 ( o f f s e t = o ) enabled d e v i c e = c o t ~ ~ d o s path=/dev/vx/dmp/cotlldosz z diskdev=32/68

Moving subdisks
Moving a subdisk copies t11e disk space contents of a subdisk onto oue or more other subdisks. If the subdisk being moved is associated with a plex, theu the data stored on the o~igiual subdisk is copied to are the new subdisks. The old subdisli is dissociated from the plex, and the new st~bdisks associated with the plex. The associatio~~ at the s a n ~ e is offset within the plex as the sotlrce subdisk. To move a subdisk, use the following couunaud:
# vxsd [-g diskgroup] mv old-subdisk uew-subdisk [new-snbdisk ...I

For example, if 1nydg03 UI the disk group, lnydg, is to be evacuated. aud mydgl2 has enough room ou two of its subdisks. use the followil~g co~lunald:
# vxsd -g mydglnv mydg03-01 1nydgl2-01 1uydg12-02

For the subdisk move to work coi~ectly, following cotlditious must be met: the The subdislis u~volved lullst be the same size. The subdisk being moved must be part of a11 active plex ou au active (ENABLED) voltume. The new subdisli must uot be associated wit11 any other plex.

Splitting subdisks
Splittil~g subdisk divides a11 eexistiug subdisk iuto two separate ~~ibdislis. split a subdisk, use the a To followiug command:
# vxsd [-g diskgroup] -s size split st~bdisk ilewsdl newsd2

where subdisk is the name of the original subdisk, newsdl is the name of the fuxt of the two subdislis to be created and newsd2 is the ualne of the secoud subdisk to be created. The -s option is required to specify the size of the first of the two subdisks to be created. The secoud subdisli occupies the r e m a u h g space used by the origiual subdisk. If the original subdisk is associated with a plex before the task, upon co~upletioil the split, both of the of resulting subdisks are associated with the s a n e plex. couunand as many times To split the original subdisk ulto more than two subdisks. repeat the previot~s as necessary on the resulting subdisks. For example, to split subdisk mydg03-02, with size 2000 megabytes into subdisks mydg03-02, mydg03-03, mydg03-04 and mydg03-05, each with size 500 megabytes, all io the disk goup. mydg, use the followi~~g I I I ~ I I ~ I I ~ S CO
# vxsd -g ~ n y d g 1OOOm split mydg03-02 mydg03-02 mydg03-04 -s # vxsd -g mydg -s 5OOm split mydg03-02 mydg03-02 mydg03-03

# \xsd -g mydg -s 500111 split mydg03-011uydg03-04 mydg03-05

Joining subdisks
Joiniug subdisks coulbiues two or more existiug subdisks iuto oue subdisk. To joiu subdisks, the subdisks must be contiguous 0 1 the same disk. If tlie selected subdisks are associated, they ulust be 1 associated with the salile plex, and be co~ltiguous that plex. To joiu several subdisks, use the in followiug couunaud:
# vxsd [-g diskgroup] join subdiskl subdisk2 ... new-st~bdisli

For example, to join the contiguous su~bdisl~s mydg03-02, mydg03-03, mydg03-04 aud mydg03-05 as subdisk mydg03-02 i tlie dish group, uiydg, use the followiug command: u
# vxsd -g lnydg joiu mydg03-02 mydg03-03 rnydg03-01 1nydg03-05 mydg03-02

Associating subdisks with plexes

Associatiug a subdisk with a plex places the alnouut of disk space defined by the subdisk at a specific offset within the plex. The entire area that tlie subdisk fills nus st not be occupied by any polti011 of auotlier subdisk. There are several ways that subdislis call be associated wit11 plexes, depeudilig oil tlie overall state of the collfiguratioi~. If you have already created all the subdisks needed for a pa~ticular plex, to associate subdisks at plex creatiou, use the followiwing c o ~ n u ~ r u ~ d :
# vxlnake [-g diskgot~p] plex plex sd=subdisli,...

For example, to create the plex home-l and associate subdisks 1nydg02-01,1nydg02-00, aud mydg0202 with plex home- I, all iu the disk group, ulydg, use tlie followiug couunaud:
# vxmake -g 111ydgplex home-1 sd=mydg02-01.1nydg02-00,111ydg02-02

Subdisks are associated iu order sta~tilig offset 0. If you use this type of coimaud, you do not have at to specify the inultiple colnlnands needed to create the plex aud theu associate each of the subdisks with that plex. III this example. the subdisks are associated to the plex iu the order they are listed (after sd=). The disk space defuled as mydg01-01 is first, mydg02-00 is secoud, and mydg02-02 is third. This method of associating subdisks is conveuieut duriug iuitial coufiguratiou. Subdisks call also be associated with a ples that already exists. To associate one or Inore subdisks wit11 au existiug plex, use the followi~~g u ~ m a ~ ~ d : co
# vxsd [-g diskgol~p] assoc plex subdisk I [subdisk? subdisk3 ...I

For example, to associate subdisks uauled mydg02-01. mydg02-00, aud mydg02-02 with a plex named

home-1, use the followiug command:

# m s d -g mydg assoc home-1 1nydg07-01 mydg02-00 mydg07-0 1 If the plex is not empty, the new subdisks are added after auy s~tbdisks are already associated with that the plex, unless the -1 option is specified with the colllluaud. The -1 option associates subdisks at a the specific offset ~vithiu plex.

of The -I option is required if you previously created a sparse plex (that is, a plex with poltio~ls its address space that do not map to subdisks) for a particular volume. and subsequently waut to make the plex complete. To complete the plex, create a subdisk of a size that fits the hole hl the sparse plex exactly. Then, associate the subdisk wit11 the plex by specifyiug the offset of the begiuuiug of the hole i11 the plex, using the followiug collunaud:
# vxsd [-g diskgroup] -1 offset assoc sparseglex exact-size-subdisk

Note: The snbdisk must be exactly the right size. VxVM does uot allow the space defined for two subdisks to overlap within a plex.

For striped or RAID-5 plexes. use the following co~nmaud specify a coluuu~ to number and colullln offset for the subdisk to be added:
# w s d [-g disk~~,oup]coluu~#/offset -1 assoc plex subdisk ...

If oilly one number is specified with the -lol~tion striped plexes. the ilulnber is interpreted as a for c o l ~ u u ~ ~ and the subdisli is associated at the end of the colu~nu. uuulber Alternatively. to add M subdisks at the e ~ l d each of the N co1111llnsI a striped or RAID-5 volume. of n fol~n you call use the followi~~g of the vxsd co~mnai~d:
# n s d [-g diskgroup] assoc plex subdisk1:O ... subdisl;M:N-1

The followiug example shows how to append three subdisk to the ends of the three colulnns i a striped u plex, vol-01, in the disk group, mydg:
# vxsd -g mydg assoc vo101-01 ulydg10-01:O 111ydgll-0l:l nlydg12-01:2

If a subdisk is filliug a "hole" in the plex (that is. some poitio~l the volume logical address space is of mapped by the subdisk), the snbdisk is considered stale. If the volume is enabled, the associatio~l operatiou regenerates data that belongs ou the subdisk. Otherwise. it is marked as stale and is recovered when the volume is started.

Associating log subdisks

Log subdisks are defu~ed d added to a plex that 15 !a Lecolile part of a volume ou which dirty regioii w loggiug (DRL) is euabled. DRL is ellabled for a v o l u ~ ~w11e11the \:olu~uieis mirrored and has at least le oue log subdisk.

Note: Ouly one log st~bdisk be associated wit11 a plex. Because this log subdish is frequently cau witten, care should be take11to positiou it on a disk that is not heavily used. Placiug a log subdisl~ a on heavily-used disk call degrade system pe~formance.
To add a log su~bdisli au existing plex, use the following con~mand: vxsd [-g diskgroup] aslog plex to # subdisk where subdisk is the uame to be used for the log st~bdisli. The plex must be associated with a lnirrored volume before dirty region loggiug takes effect. For example, to associate a subdisk named 1iiydg02-01 with a plex named volO1-02, which is already vol01 in the disk group, mydg, use the followi~~g couuiand: associated with voluu~e
# vxsd -g mydg aslog volO 1-02 111ydgO2-01

You cau also add a log subdisli to an existing volume wit11 the following command:
# vxassist [-g diskgroup] addlog volume disli

This couunaud autouiatically creates a log stlbdisli within a log plex on the specified disk for the specified volu~me.

Dissociating subdisks from plexes

To break a established couuectiou between a subdisli aud the plex to \vliich it belongs, the ssl~bdisk 1 is dissociated fro111the plex. A subdisk is dissociated when the subdisk is removed or used in another plex. To dissociate a subdisk, use the following command:
# vxsd [-g diskgroup] 1:-o force] dis subdisk

For example, to dissociate a subdisk named u1ydg02-01 fiom the plex with which it is c n ~ ~ e u t l y associated i the disk group, mydg, use the following co~luna~ld: n
# vxsd -g mydg dis mydg02-0 1

You cau additionally remove the dissociated subdisks from VsVM control using the followil~g fo11u of the c o m a ~ d :
# vxsd [-g diskgroup] -0 11n dis subdisk

Caution: If the subdisk maps a portiou of a voltmle's address space, dissociatiug it places the volume iu DEGRADED nlode. hl tlus case, the dis operatio~l priuts a \vanling a ~ most be forced using the d

-oforce option to succeed. Also. if re~noving subdisk makes the vol~une the unusable. because another subdisk in the same stripe is unusable or missing and the vol~uule uot DISAElLED and empty. the is operation is not allowed.

Removing subdisks
To remove a subdisk. use the following coumand:
# vxedit [-g disligroup] 1111 subdisk

For example, to remove a snbdisli named luydg02-01fi.01~ disk group, ~uydg, the followiug the use comand:
# vxedit -g lnydg 1x1mydg02-01

Module 8: Creating and administering plexes

This chapter describes how to create and maintain plexes. Plexes are logical groupings of subdisks that create an area of disk space independent of physical disk size or other restrictions. Replication (mirroring) of disk data is set up by creating multiple data plexes for a single volume. Each data plex in a mirrored volume contains an identical copy of the volume data. Because each data plex must reside on different disks from the other plexes, the replication provided by mirroring preventsdata loss in the event of a single-point disk-subsystem failure. Multiple data plexes also provide increased data integrity and reliability.
.. ..

Creating plexes
Note: Plexes are created auto~natically you use the vxassist command or the Veritas Enterprise if Admiuistrator (VEA) to create vol~m~es. Use the vxniake commalid to create VxVM objects. such as plexes. When creating a plex, identify the subdisks that are to be associated wit11 it: To create a plex fiom existiug subdisks, use the following command:
# wmake [-g diskgrot~p] plex plex sd=subdiskl [,subdisk?, ...I

For example, to create a coucatenated plex lia~ued vo101-02 from two existi~ig subdisks n a ~ i ~ e d mydg02-01 and mydg02-02 in the disk group, ~ilydg, the following co~mna~td: use
# vxmake -g nlydg plex vo1O 1-02 sd=1uydgO2-01,11lydg02-02

Creating a striped plex

To create a striped plex, you must specify additional attributes. 1 For example, to create a striped plex named pl-01 11 the disk group, mydg, with a stripe width of 32 sectors and 2 columls. use the followi~iy command:
# vxuake -g u y d g plex pl-01 layont=stripe stwidtl1=32 ncolu11m=2 sd=mydyOl-Ol,mydgO?-01

To use a plex to build a volume, yon must associate the plex with the vol~ume.

Displaying plex information

Listiug plexes helps idei~tifj plexes for building volmnes. Use the plex (-p) option to the \.xprk~t free coiui~~ru~d iufo~vlation to list about all plexes. To display detailed information about all plexes ~ I the system, use the followii~g I coilmand:

To display detailed iufo~lnation about a specific plex, use the followiug c o m a i ~ d :

# vxprint [-g diskgroup] -I plex

T l ~ e option priuts a single liue of infomation about the plex. To list fiee plexes, use the followiug -t comwd:

The followi~~g section describes the il~eauing the various plex states that nlay be displayed UI tlie of STATE field of vxprint output.

Plex states
Plex states reflect \&ether or not plexes are coinplete and are consistent copies (mirrors) of the volume contents. VxVM utilities automatically maiutaiu the plex state. However, if a voluine should uot be witten to because there are changes to that volu~ne if a plex is associated mith that volume. you and can modify the state of the plex. For example, if a disk with a particular plex located on it begins to fail, you call temporarily disable that plex. A Note: A plex does not have to be associated with a vol~~me. plex can be created with the vxmakeplex command and be attached to a volt~lne later. VxVM utilities use plex states to:
m indicate whether volume coilteilts have bee11 ii~itialized a known state to

deteill~il~ea plex contains a valid copy ( m i ~ ~ oof)the volume contents if r track whether a plex was UI active use at the time of a system failure monitor operatioils on plexes This sectioi~ explaii~s individual plex states in detail. For more info~~natioii the possible the about transitions between plex states and how these are applied during volume recowrely

Plexes that are associated with a volume have one of the following states:
ACTIVE plex state
A plex cau be i the ACTIVE state iu two ways: n when the volume is started aud the plex f111lyparticipates iu IIOIYU~I vo1111l1eI10 (the plex contellts change as the c o u t e ~ ~ofsthe volume change) t wheu the volume is stopped as a result of a system crash and the plex is ACTIVE at the lnomeut of the crash

In the latter case, a systen~ failnre call leave plex coutents iu an i~~consistent When a volume is state.
started, VxVM does the recovery action to guarantee that the contents of the plexes nlarked as ACTIVE are made ideutical. Note: On a system rrmi~iug well. ACTIVE should be the most conm~on state yon see for ally volmne plexes.

CLEAN plex state

A plex is iu a CLEAN state when it is k n o w to coutaiu a consistent copy (inirror) of the volume As conteuts and an operation has disabled the volt~me. a result, when all plexes of a volume are clean, uo action is required to guarmtee that the plexes are ideutical when that volun~e started. is

DCOSNP plex state

This state indicates that a data change object (DCO) plex attached to a volume can be used by a snapshot plex to create a DCO volume duriug a snapshot operation.

EMPTY plex state

Volume cleation sets all plexes associated with the volume to the EMPTY state to iudicate that the plex is not yet iuitialized.

IOFAIL plex state

The IOFAlL plex state is associated with persistent state logging. When the mconfigd daemon detects an uuconectable U 0 failure on an ACTIVE plex. it places the plex in the IOFAIL state to exclude it fiom the recovery selection process at v o l ~ m ~ e time. start This state u~dicates the plex is out-of-date with respect to the volume, aud that it requires complete that recovery. It is likely that one or more of the disks associated uith the plex shodd be replaced.

LOG plex state

The state of a dirty region logging (DRL) or RAID-5 log plex is always set to LOG.

OFFLINE plex state

The vxlueudoff task indefinitely detaches a plex from a volume by setting the plex state to OFFLINE. Although the detached plex maiutaius its associatiou with the volume, changes to the volume do not update the OFFLINE plex. The plex is not updated until the plex is put oilline and reattached with the vxplex att task. When this occurs, the plex is placed in the STALE state. which causes its contents to be recovered at the uext vxvolsta~t operation.

SNAPATT plex state

This state iudicates a snapshot plex that is beiug attached by the snapstart operation. When the attach is co~uplete, state for the plex is chauged to SNAPDONE. If the system fails before the attach the completes, the plex aud all of its subdisks are removed.

SNAPDIS plex state

This state iudicates a snapshot plex that is fully attached. A plex in this state call be turned iuto a snapshot volume nith the vxplexsnapshot command. If the system fails before the attach completes. the plex is dissociated from the volume. See the vxplex( lM) manual page for more info~mation.

SNAPDONE plex state

The SNAPDONE plex state indicates that a snapsl~ot plex is ready for a snapshot to be talien using vxassist snapshot.

SNAPTMP plex state

The SNAPTMP plex state is used duriug a vxassistsnapstart operation when a snapshot is beiug prepared on a voliune.

STALE plex state

If there is a possibility that a plex does uot have the coiuplete and cun.ent volume contents, that plex is placed iu the STALE state. Also, if an 110 emor occurs on a plex. the ke~nel stops usullg and updatiug the contents of that plex, and the plex state is set to STALE. A vxplexattoperation recovers the coute~lts a STALE plex from all ACTIVE plex. Atomic copy of operations copy the coutents of the volume to the STALE plexes. The system admillistrator can force a plex to the STALE state with a vxplexdet operatio~l.

TEMP plex state

Setting a plex to the TEMP state eases some plex operations that callilot occur iu a truly atomic fashion. For example. attaching a plex to an enabled volu~ule requires copying volume contents to the plex before it can be cousidered fully attached.

A utility sets the plex state to TEMP at 11ieac.!iI of such a ope ratio^^ aud to an appropriate state at the 1 end of the operation. If the system fails for m y reason, a TEMP plex state iudicates that the operatio11is incomplete. A later vxvol start dissociates plexes it1 the TEMP state.

: ;... : .$

T.EMPRM plex state

A TEMPRM plex state is siiuilar to a TEMP state except that at the coinpletion of the operation, the TEMPRM plex is removed. Some subdisk operations require a temporary plex. Associating a subdisk with a plex, for example, requires updatuig the subdisli with the volume coutents before acttially associatiug the s~~bdisli. update requires associating the subdisk with a temporary plex, marked Thus TEMPRM, until the operation completes a i d removes the TEMPRM plex. If the systelll fails for a i y reason, the TEMPRM state indicates that the operation did not complete successfiilly. A later operatiou dissociates and removes TEMPRM plexes.

TEMPRMSD plex state

The TEMPRMSD plex state is used by vxassist w l ~ eattacliiiiy new data plexes to a voluiue. If the ~i syucl~ro~lization operatiou does not complete, the plex and its subdislis are removed.

Plex condition flags

vxprint may also display oue of the followii~g condition flags in the STATE field:

IOFALL, plex condition

The plex was detached as a result of au VO failure detected during llo~lual volume 110. The plex is outof-date with respect to tlie volume. and iu need of complete recovery. how eve^, this col~ditiol~ also indicates a likelihood that one of the disks ~ I system sho~tld replaced. the I be

NODAREC plex condition

No physical disk was fouud for oue of the subdislts in the plex. This implies either that the physical a disk failed, lnakiug it unrecogizable, or that the physical disk is 110 longer attached t h o i ~ g h kuowu access path. The plex caullot be used until this collditiou is fixed, 01.the affected subdisk is dissociated.

NODEVICE plex condition

A physical device could not be fouud correspoudilig to the disk ID in the disk ~nedia record for oue of the subdislis associated with the plex. The plex cau~lot used until this condition is fixed, or the be affected subdisk is dissociated.

RECOVER plex condition

A disk coi~espouding one of the disk media records was replaced. or was reattached too late to to prevent the plex fiom beco~uiug out-of-date with respect to the volu~ne. plex required complete The recovery fiom another plex iu the voluuie to synchronize its co~itents.

REMOVED plex condition

Set in tlie disk media record hvheu oue of the subdisks associated with the plex is removed. The plex c a ~ i ~ ibet used wtil this couditiou is fixed, or the affected subdisk is dissociated. o

Plex kernel states

The plex ke~nel state iudicates the accessibilib of the plex to the volmne driver wl~ich mouitors it. Note: No user iute~ventionis required to set these states; they are n~aiutahed iutemally. On a system that is operating properly, all plexes are enabled. The following plex lieme1 states are defined:

DETACHED plex kernel state

Mahtenauce is beiug perfo~lued the plex. Any write request to tlie volume is not reflected in the on plex. A read request f7om the vohuue is not satisfied from the plex. Plex operations and ioctl f~u~ction calls are accepted.

DISABLED plex kernel state

The plex is oMiue and caunot be accessed.

ENABLED plex kernel state

The plex is onliue. A write request to the volu~me reflected UI tlie plex. A read request from the is volu1111eis satisfied fioni the plex. If a plex is sparse, this is indicated by the SPARSE n~odifier being displayed in the outptd fioln the vxprint -t co~il~lland.

Attaching and associating plexes

A plex becomes a participatiug plex for a volume by attachiug it to a vol~un~e. (Attachmg a plex associates it with the volunle aud enables the plex for use.) To attach a plex to au existiug vol~uue, use the followiug c o m a u d :
# vxplex [-% diskgroup] att volume plex

For example, to attach a plex uamed vo101-02 to a vollume uamed volO1 iu the disk group, mydg, use the followi~lg o m ~ a n d : c
# vxplex -g lnydg att volOl vo101-02

If the volume does not already exist, a plex (or ulultiple plexes) can be associated with the voliune when it is created using the followh~g command:
# vxulake [-g diskgroup] -U usetype vol v o l ~ ~ plex=plexl [,plex2...I ~ue

For exa~nple, create a mu~ored, to fsgen-type volume ~ ~ a l n home. aud to associate two existing plexes ed ~lanled home-1 aud home-2 with home, iise the followiug command:
# vxmake -g mydg -U fsgeu vol holl~e plex=l~ome-,home-2 l

Note: You can also use the couunand vxassistmu~or volul~ne add a data plex as a ~nirror an to to existiug volluue.

Taking plexes offline

Once a volume has been created aud placed onliue (ENABLED). VxVM call temporarily disconnect plexes fiom the volume. This is usefill, for example. vheu the hardware on which the plex resides needs repak or when a vol~une been left lu~startableand a soilrce plex for the volume revive must has be chosen ma~l~lually. Resolvi~~g a disk or system failure iucludes taliing a vohune offliue aud attachiug and detacl~iug its plexes. The two co~l~nlauds to acco~nplish used disk failure resolution are vxmeud and vxplex. To take a plex OFFLINE so that repair or u~aintenancecau be perfo~med the physical disk on coutaiuiug subdisks of that plex. use the following couuuaud:
# vxlnend [-g diskgrotrp] off plex

If a disk has a head crash. put all plexes that have asqp-i~te.?suhdishs dn the affected disk OFFLINE. u 'l.ou~.mydg, had subdislis on a drive to be For example, if plexes volOl-02 and vo102-02 i ti, repaired, use tlie following command to take these plexas offline:

# winend -g mydg off volO 1-02 ~0102-02

This coulmaud places vo101-02 and vo102-02 in the OFFLINE state, and they remain in that state until it is changed. The plexes are not a~~tomatically recovered on rebooting the system.

Detaching plexes
To temporarily detach a l e data plex ul a anirrored volume, use the followirlg co~nmand:
# vxplex [-g diskgroup] det plex

For example, to temporarily detach a plex uaulled volO1-02 in the disli group, ~nydg, place it i 1 and 1 maintenance mode. use the followi~ig co~unand:
# vxplex -g mydg det vo101-02

TIUSconlmand ten~porarily detaches the plex, but n~aiutaius associatiol~ the behveeu the plex and its with the precediug command is volume. However, the plex is not used for VO. A plex detacl~ed recovered at svstem reboot. The nles state is set to STALE. so that if a vsvolstart collunaild is I.LIII on the appropriate v o l ~ ~ i (for exarnple. OII system reboot), the co~lteuts the plex is recovered and 111ade ne of ACTIVE.

Reattaching plexes
When a disk has been repaired or replaced and is agaiu ready for use, the plexes I I I L I S ~ pot back be online (ples state set to ACTrVE). To set the plexes to ACTIVE, use one of the followi~~g procediues dependmg on the state of the volume.
m If the voli~me c u ~ ~ e n tENABLED, use the followi~lg is ly co~nmaud reattach the plex: to

# vxplex [-g diskgroup] att vol~une plex

...

For example, for a plex named volOI-02 or1 a vol~une na~ned volOl in the disk group, mydg, use the following command:
# vxplex -g inydg an volOl vo101-02

As when returning an OFFLINE plex to ACTIVE, this command starts to recover the co~itents the of plex aud, after the revive is complete, sets the plex utility state to ACTIVE. If the volume is not in use (not ENABLED), use the followiug conmand to re-enable the plex for use:

# vxmeud [-g diskgroup] ou plex

For example, to re-enable a plex named vo101-02 in the disk group. mydg, enter:
# vxmend -g mydg 0 1 ~0101-02 1

111this case. the state of vo101-02is set to STALE. When the volume is ilext started, the data on the plex is revived from auother plex, w d incorporated iuto the volulne wit11 its state set to ACTIVE. If the vxiufo commaud shows that the volume is uustaltable, set one of the plexes to CLEAN usiug the followiug c o m a u d :
# vxmend [-g diskgou~p] cleau plex fix

Start the volume using the followil~g command:

# vxvol [-g diskgroup] start volume

Moving plexes
Moving a plex copies the data co~~teut the oi~ginal fiom plex onto a new plex. To move a plex. use the followi~~g command:
# vxplex [-g diskgroup] UIV originalglex n e w j l e x

For a move task to be successful, the followiug criteria must be met: The old plex must be au active pait of w active (ENABLED) volume. The ilew plex 111ustbe at least the same size or larger than the old plex. The new plex must not be associated with another ~oluine. size of the plex has several The in~plications: If the new plex is sinaller or Inore sparse than the origiual plex, an illcomplete copy is made of the data 0 1 the original plex. If an illcomplete copy is desired. use the -oforce option to 1 vxplex. If the uew plex is longer or less sparse t h w the original plex, the data that exists ou the origiual plex is copied onto the new plex. Auy area that is not on the origiual plex, but is represeuted on the new plex, is filled from other coinplete plexes associated with the same volume. If the new plex is longer thau the volu~ue itself. theu the remaining area of the new plex above the size of the volume is ilot iuitialized and remains ~mused.

Copying plexes
This task copies the couteuts of a volume onto a specified plex. The volum~e be copied nnist not be to enabled. The plex cwuot be associated with ally other volume. To copy a plex, use the followiug comaud:

# vxplex [-g diskgro~~p] volume newglex cp

After the copy task is complete, n e w j l e x is not associated wit11 the specified volulme vol~rme. The plex contaius a complete copy of the volun~e data. The ple.; that is being copied s h o ~ ~be the sallle size or ld larger than the vol~ume. the plex being copied is lager than the vol~mie, hcomplete copy of the If an For data res~dts. the same reason. newglex should riot be sparse.

Dissociating and removing plexes

When a plex is no loiiger needed, yo11 can dissociate it from its volrune and remove it as an object from VxVM. You might want to remove a plex for the following reasons: to provide free disk space to reduce the nu in be^. of minors in a voluine so you call increase the le~lgth another mi~ror its of and associated volonle. When the plexes and subdisks are removed, the resulting space can be added to other volmnes to remove a teniporary m i i ~ o that was created to back up a volmile and is no longer needed r to change the layout of a plex of Caution: To save the data on a plex to be renloved. the configuratio~~ that plex 1n11stbe k n o w . Paralneters fi.0111that collfiguration (stripe unit size and subdisk ordering) are critical to the creation of a new plex to coutain the same data. Before a plex is renloved, you must record its co~lfig~~ration. To dissociate a plex from the associated bo1111ne reiliove it as an object fro111 VxVM. use the and following colluuand:
# vxplex [-g diskgoop]
-0 IU

'

dis plex

For exauiple, to dissociate and remove a plex named vo101-02 iu the disk groop, mydg, use the followi~ig o ~ w d : c
# vxplex -g nlydg -0 IU dis vo101-02

This commaud removes the plex vol0l-02 aud all associated snbdisks. Alteruatively, you can first dissociate the plex aiid subdisks, ru~d then remove them with the following commands
# vxplex [-g diskgroup] dis plex # vxedit [-g diskgroup] -r 1111plex

ce When used together, these commands p r o d ~ ~ the same result as the vsplex -0 1111dis comiland. The -I option to medit ml recursively removes all objects from the specified object downward. In this way, a plex and its associated subdisks can be removed by a siugle vxedit colwand.

Module 9: Creating volumes

'Ibis chapter describes how to create vol~uues n Veritas Vol~une i Mauager (VxVM). Volumes are logical devices that appear as physical disk partition devices to data illailagement systems. Volun~es enhance recovely fiom hardware failure. data availability. performance. and storage co~lfiguration. Volu~ues created to take advaiitage of the VxVM collcept of virtual disks. A file systenl can be are placed 011 the volume to organize the disk space with files aud directories. L addition, you can u co~lfigure applicatio~~s as databases to organize data on volomes. such Note: Disks and disk groups lnust be initialized a i d defined to VxVM before vol~ui~ies be created can from them.

Types of volume layouts

VxVM allows you to create volumes with the followil~g layout types: Concatenated
A volume whose sobdisks are a l ~ a n g d both seqoe~ltially ~ coutipuo~~sly a d

witliiu a plex. C o n c a t e ~ ~ a t allows a volt~me be created fiom multiple regions io~~ to of one or more disks if there is not enough space for an entire volume on a single region of a disk. Striped A volt~me with data spread evenly across nlultiple disks. Skipes are equal-sized fragneuts that are allocated alteinately and evenly to the subdisks of a siugle plex. There must be at least huo subdisks in a striped plex, each of which must increases with the nuuber of disks across exist on a different disk. Thoogl~put which a plex is striped. Striping helps to balance 110 load iu cases where high traffic areas exist on certaiu sobdisks. A voluine with ll~ultiple data plexes that duplicate the illfolnlatiol~ contained in a voliune. Although a volune call have a siugle data plex. at least two are required for true llli~~oringprovide redtmdancy of data. For the redllllda~lcy be to to usefi~l, each of these data plexes shoold coutaiil disk space from different disks. d disks A volulne that uses striping to spread data a ~ parity- eveellly across ll~ultiple iu an array. Each stripe col~tains parity stripe unit and data stripe uuits. Parity a

Minored

IEI

.aurlr[o,\ S - a I a aqjjo smnrrloo arp ,103pas11 a.re lerp asorp mql .larpo sys!p uo s a s a ~ d pamSrpoo a.ra se sBo[ asaqL .sarmr[oi\ S - ~ V ~ ,C.rai\ooa.r Bu!.~upelep jo rro!ldrl.uoo luaaa.rd 01 pas11 ale sZo1 ~ - m J O .amn[ol\ 03a oz no!sla,\ a 30 $red sa .lo 'saxa1cl Sol 7aa se .laq)!a pa$roddrls a.ra sSo1 a s a u .qse.ro U I ~ ~ SeL S sarmiloh palo.rr!rrrjo L.ra~ooar aq) MoIIe sZo1 no!Sar /cl.rta .rage lsej .s)or1sdaus atnnlon lrre)sn! pazmn~do-aosdsprra paz!s-111ij .roj 3uLsaa)sed )rrals!s.rad pue Brr!890178(1 ~roddns MXA m paonpo.r)~ *O'P 'sauniloA 03a oz no!s.raA .loqsdans amuIoAjo adLjgo-yea.rq .ro.u!ru-pqtp Iaoo!)g)a.v aq) .roj orrLsa8jssd jnajs!s.rad $rodd~is p o samnloh 03a 0 no!s.raA L

.(onLsaalsed ltrals!s.rad) amuqoA

03a " $red se ys!p uo .IO '(ouLsaalsad )najs!s.~ad-no~) 0 L.roaram LC.laqj!a pa$rocld~ls sdam asaqL a.re
.s.ro.rr!mjo uo!)ez!rro.rr~onLsa.~ jna!oga prrs y3!11b nuoj~ad pasu a.re sdam onLsaa)sed 01 :samtqoA q j sdam pna sSoljo s a d 4 le.~a.~as as11 aqj s~~oddirs ~ jo .raSemm amcl[oA sejuaA

sdcw puc s8ol awnloa payoddng

'angjo .ro.nnn a.r!jna arg ao.10~ )or[ saop ys!p alSms e jo a.ml!q aq) se h r a ~ o o a.rajsg sapv\o.rd s q .samu[oA .~ ~ pa.ro.rr!ur Ia.raAas Su!leualaorroo bq pajearo s! amnloh .ro.rr!m-pajerrajeo~~oo v ,arnpjo xald pad!.qs a.njna IIB ao.10~ saop ys!p alZmsjo a.ln[!ej jot1 arp st? ,C.ra.\ooa.r .rafig sap!~o.rdI lro!l!ppe o[ .aroll[o.\ ad!.r~s-pa.ro.rrpr ! pa.raLe1 -uou a sa slganaq arnes atp s.rago j11oLe1s ! 'amuloA pad!r)s e j o srrrunloo at[! ~ sa sarrrnloh p a r o . r p IuraAas 811~.mByrroo palaa.ro s! arrrn[oA .ro.r~nr-pad!.r)sv Lq

.samnloA .ro.rrp~-palana)aonoo pne .rou!rrr-pad!.r)s a.18 samuloh pa.raLe1j o saldmexg ')noLe~[eo!So1jo smroj xaldmoo a.rom jo uo!jea.~oarp MoIle p11e '(samrilo~ aSe.~ojs mtorq) saurriIoA Bu!Lpapmlo) sys!pqns .naq) Su!ddam se Lq pajon.rjsooo ale sarnrlloh pa.raLal .sys!p 01 S ~ S ! P ~ I I .t!aql S ~ d d e nLq S r palon.qsooo are samnloh pa.1aLs1-rro~ .sarunIoA .rarl)o nro.tj pa~ou.r)srroo aurllIoh v

amnloA p a ~ a b r l

x l e p j o Lowpm~par pnuys!p ald!)~r~m ss0.13eelep Zmpealds Lq aonsmroj.rad pasaa.rorF a.re )11oLe1SF[IIJO saSesre~pe ar[L '(pad!rls .IOa[cIuns s! said aql .rarI)aqM rro Bmpnadap) Zrr!.ro.u!rn ,103sys!p ~ .raqjo a.rorrr .ro aoo prre Zqd!l)s .roj sys!p o w )seal sa.t!nba.r s g .an0 pad!.t)s at[! s.Io.u!rrr !ern xald .rar[jorrt!pne xald pad!ys a se pa.ruBgrroo s! lerp anrrqoh v

adyjs-pa~o~.r!,q

.pa.nubar aoeds jo )mlorne aq) saoupa.1Lowpn1ipa.r ejep ~rrarna[dm! Ll!.redjo asn arp 'Bn!.ro.r~!nr 01 nos!.radmoo m 'raAah\oH ol .passaooe s! ejep arm) qoaa pa~epdu 01 spaan no!lemroju! &!.red aoms aq sasea.oap sanm[o,\ S - ~ J )l~d$r~o.npal!.m 'satnnlon pad!.rlsjo aouemroj.rad O arp oj tros!.rednroo u1 y q s>~s!p arI)jo arroj! elep Ion.vsnooa.r 01 pasu aq nao

Creating a volume
You can create volumes using an advauced approach, au assisted approach, or the mle-based storage allocation approach that is provided by the hltelligeut Storage Provisiouing (ISP) feature. Each method uses different tools. You may switch between the advanced and the assisted approaches at will.
Note: Most VxVM commands require superuser or equivalent privileges.

Advanced approach
The advanced approach consists of a number of c o m w d s that typically require you to specify These couuuauds use a "buildil~g blocli" approach that reqtiies you to have a detailed detailed u~put. knowledge of the tu~derlyiug structure aud co~uponents n~anually to perfo~ni commands necessary the to accolnplish a certaiu task. Advwced operations are perfolvled using several different VxVM couunwds.

To create a volume using the advanced approach

1 Create subdisks using w o ~ a k e sd

2 Create plexes usiug vxmake plex, and associate subdisks wit11 them

3 Associate plexes wit11 the volmue usitig vxmalie vol

4 hutialize the volume usillg vxvol start or vxvol h i t zero

Assisted approach
Tlie assisted approach takes h ~ f o ~ - ~ ~ ~ a t i owhat you want to accomplish and then perfonns the about n necessary underlyi~~g tasks. This approach requires only minimal illput from you, but also pelnits more detailed specifications. Assisted operations are perfo~n~ed primarily thou* the vxassist commald or the Veritas Ente~yl-ise Adnliuistrator (VEA). vxassist aud the VEA create the required plexes and subdisks using o~lly the basic attributes of the desked volmne as input. Additionally, they call modify existing volumes wliile auto~natically modifying any tmderlyiug or associated objects. attributes, mlless you prokide specific Both vxassist and the VEA use default values for lnauy volm~ie

values. They do not require you to have a thorougl~ understandiug of low-level VxVM concepts, vxassist aud the VEA do not conflict with other VxVM commands or preclude their use. Objects ir'e:;operab!e 1ri;tL ol?jeqts ?.l.e?ted other by create~i \sassist and the VEA are compatibrs 1.;) VxVM com1;~1ds interfaces. and

1 Using vxassin [
You c w use the vxassist utility to create and modify volumes. Specify the basic reqoirerneuts for volume creation or modification, w d vxassist perfoms the uecessaly tasks. The advantages of using vxassist rather than the advanced approach include: Most actious require that yo11 enter only one command rather than several. You are required to specify ollly nlinimal hifolnlation to vxassist. If necessary, you can specify additional parameters to modify or control its actions. Operations result iu a set of configuration c h a ~ ~ gthat either succeed or fail as a group, rather than es do individually. System crashes or other intel~iuptions not leave htennediate states that you have to clew up. If vxassist fiuds an enor or an exceptional co~~dition,exits after leaving the systelu in the it same state as it was prior to the attempted operation. The vxassist utility helps you perf01111 the folloc\bg tasks: Creating volu~ues. Creating minors for existing volomes. Growing or shrinking esisting voliunes. Baclimg iup voliuues online. Reconfiglriug a voliume's layout online. vxassist obtaius no st of the i~lfonuation needs fiom sources other than your illput. vxassist obtains it iufolmation aboid the existing objects aud their layoots from the objects themselves. new For tasks reqaili~~g disk space, vxassist seeks out available dish space aud allocates it in the configaratiou that c o ~ l f o ~ m sthe layoat specifications aud that offers the best use of fiee space. to The vxassist c o m ~ a u d takes this folm:
# vxassist [options] keyword volu~ue [attributes...I

Where keyword selects the task to perfonn. The first algimlent after a wassist keyword, volmue, is a volome name, which is followed by a set of desired voliunle attributes. For example, the keyword malie allows yoit to create a new volume:
# vxassist [options] make voliuue length [attribi~tes]

z=ad!l~su-u!u 8 = a d !l1su-xeu suunlo3 # J~!JIS 8 PUP Z UaJMJJq aJPal3 J l n e j a p hq ' ~ u ! ~ ! J JJs l n 6 a l 104 # e Z=lOll!LllU SlO.lJ!U O M 1 aJPJl3 ' 6 U ! l o l J ! U UJqM # 1ool=dnol6 Jool=lasn =O'=~'MI=~=JPOUI awnlo/\ e 01 ssa33e 1001 h l u o M o l l e # uafis~=adh~asn SaunloA 5 -alVtl 6 u ! 1 e a l 3 u a q ~~ d a ~ x ' a d h ~a6esn ua6s4 aq1 asn # u6!1ey5!~ ' 6 0 ~ ~ 0 ! 6 ~ ~ 0 ~ ' 6 0 ~ 5 p ! e 1 ' 6 ! ~ u o ~ o u ' u e d s ' ~ d ~ ~ o s a ! l e p u n o q l a p u ! l h 3 uo s u o 1 1 e 3 o l l e u 6 ! l e # 601 e a ~ e a l 31,uop ~ U ! J O J J ! L~ J ! M '601 e a ~ e a l 3S - a l t j t l ~ J ! M# U SaA!Jp ueds 0) s U o ! ~ e 3 o l l e M O l l e # SaunloA p a d ! J ~ s u n ' p a l o l ~ ! l u u n a)eals # :JlneJap hg #

:pmmmoo ls!ssexi\ aqljo mroj Sn~zolloj as11 'ls!ssexi\/ll~igap/3la/aIg arll u plaq salnq!.rUa ~[riajap Lslds!p 0 arll ! aql 1 .s[!qap ,103 asad [elineur ( ~ ~ ) ~ s ! s s a111 wA 01 .rajax 'ant[ p r r e m o o ~s!sssxi\aql uo sno!ldo se pagoads asoql sa amas aql are s.r!ed an~ei\-aluq!.r~e asalK .Sam1 Man Lq pala.radas s.~!adanleh-al~iq!.~~ejo a s! alg slpiajap a u! sa!.r)najo laurroj a q l ls!l .a.ratpasla paogap anleh a pmj Iormao )!j! sasn I! ~ a slprgap y-q!nqjo las a saq osla ls!ssex,\ .aorrapa3a.rd sayel ~ g SLWIBan!( pusururoo aql no pagpads anlei\ llnqap v .no!ydo p- arll Bmsn L p a d s uoL 1sq) alg sllr~ajap alsnralle na m .to 'am[ posutru~oo no maq) apkua,\o loa op noLj! joaga aya) alg sm) I? pals9 s~lriajap aq) a q l ~~s!ssaxi\/)111gap/~a/ aq) rr! pagpads aq Laro sasu prnnnnoo ls!ssexl\ aql )ELI) sanlaA )pigap a r u alg

# f o r RAID-5, by d e f a u l t c r e a t e between 3 and 8 s t r i p e columns max_nraid5stripe=8 min-nraidsstr ipe=3 # by d e f a u l t , c r e a t e 1 l o g copy f o r b o t h m i r r o r i n g and RAID- 5 volumes nregionlog=l nraidslog=l # by d e f a u l t , l i m i t m i r r o r i n g l o g l e n g t h s t o 3zKbytes max_regionloglen=3zk # use 64K as t h e d e f a u l t s t r i p e u n i t s i z e f o r r e g u l a r volumes stripe_stwid=64k # use 16K as t h e d e f a u l t s t r i p e u n i t s i z e f o r RAID-5 volumes

Discovering the maximum size of a volume

To fuld out how large a volume yo11 cau create within a disk group, use the following f 11 1 of the o-1 vxassist co~lunmd:
# vxassist [-g diskgroup] mnxsize Iayout=layout [attrib~des]

For example, to discover the maximum size RAID-5 voliuue with 5 c o l m ~ ~ands2 logs that you call l~ create within the disli group, dglp, enter the fol lowiug collunand:
# vxassist -g d g p maxsize layout=raid5 1110g=2

You can use storage attributes if you nant to restrict the disks that wassist uses when creatulg volumes.
Note: The nlaximtuu size of a VxVM volulme that you can create is 256TB.

Disk group alignment constraints on volumes

Certaiu constraiuts apply to the length of voliumes aud to the uiuueric valoes of size attributes that apply to volumes. If a volume is created in a disk group that is compatible with the Cross-platfonn Data Sharing (CDS) feature, the volume's len@h and the values of volmue attlibi~tes define the that sizes of objects soch as logs or stripe imits, most be an integer multiple of the aligument valne of 16 blocks (8 kilobytes). If the disk group is uot compatible with the CDS featwe, the volume's length and attribute size values milst be multiples of 1 blocli (5 12 bytes). To discover the value ul blocks of the a l i g u ~ e uthat is set on a disli group, use this command: t
# vxplint -g diskgroup -G -F %align

By default, vxassist auto~uatically roimds up the volilme size and attribute size values to a midtiple of as the alignment value. (This is eqtdvalent to specifyiug the attribute dgalig~_checkiug=roiu~d an additioual argument to the \%assist command.) If yon specify the attribute dgaligl-checlting=strict to ~xassist, co~lunand the fails with an error if you specify a volume length or attribute size value that is not a mi~ltiple the a l i g ~ ~ n evalue for the disk of nt

group.

7 .

L..

Creating a volume on any disk

By default, the wassistmake commru~d creates a coucatenated volulue that uses one or more sectio~~s of disk space. Ou a fiagne~ited disli, this allows yo11to put together a volume larger thau auy individual section of free disk space available. If there is not enough space on a single disk. vxassist creates a spa1111edvolume. A spauued volu~ne a is concatenated volume 14th sectiolis of disk space spread across more than one disk. A spalmed volu~ne call be larger than any disk ou a system, since it takes space fiom more than oue disk. use To create a coucateuated, default voluu~e, the follo\ving folvl of the \-assist command:
# wassist [-b] [-g diskgroup] lnalte voluune length

Note: Specify the -b option to initialize the voliuue iu the backgrouud, this will make the voluune immediately available for nse. of For example. to create the collcatenated volume voldefault with a lengtl~ 10 gigabytes in the default disk groutp:
# vxassist -b make voldefault log

Creating a volume on specific disks

VxVM automatically selects the disks on w,l~icli each voltune resides. uuless you specify othelwise. If you wwt a voltune to be created on specific disks, you must desiguate those disks to VxVM. More thau oue disk cau be specified. To create a volume on a specific disk or disks. use the followilig comniand:
# vxassist [-b] 1:-g disligroup] make vollume length [layol~t=layol~t] disknaiiie ...

For example, to create the volume volspec wit11 length 5 gigabytes on disks mydg03 aud mydg04. use the followiug commaud:

# vsassist -b -g mydg make volspec 5g mydg03 mydg04

The vxassist conlu~aid allows you to specify storage attributes. These give you c o ~ ~ t rover. the ol devices, iucludulg disks. controllers aud targets, which vxassist uses to configure a voliuue. For example, you c w specifically exclude disk mydg05:
# wassist -b -g nlydg make volspec 5%!mydg05

or exclude all disks that are OII controller c2:

ivxassist -b -g mydg lnalie volsl~ec !clh.:c2 5g

or include ouly disks on controller c l except for target t5:

# vxassist -b -g mydg make volspec 59 ctlr:cl !target:cl t j

If yo11 waut a volume to be created using only disks fiom a specific disli goup, use the -g optiou to vxassist, for example:
# vxassist -g bigoue -b make vohnega 20g bigonel0 bigonel 1

or altenlatively. use the diskgroup attribute:

# wassist -b make vohnega 20g disligoup=bigone bigonel0 bigonel 1

Note: Any storage attributes that you specify for use mt~st belong to tile disk group. Otherwise. vxassist will not use theill to create a volume.
'. vu cau also use storage amibutes to control how massist uses available storage, for example, when calculating the maxin~ui~l of a voltune, wheu growiug a volulne 01. wheu removiug ~uinors logs size or from a voli~me. The follo\vblg example excludes dishs dgy07 and dg1p08wlleu calculatu~g the maximiuu size of RAID-5 vol~ume that vxassist cau create nsiug the disks in the disk grou~p dg:

# vxassist -b -g d g ~ y maxsize layout=raid5 ulog=2 !dg1p07 !dgrpO8

See the \.xassist(lM) mauual page for more itifo~u~ation about using storage athibutes.

Specifying ordered allocation of storage to volumes

Ordered allocatio~l gives you cornplete colltrol of space allocation. It requires that the number of disks that you specify to the vxassist co~lll~la~ld match the number of disks that are reqliied to create a must volu~ue.I l ~ e ' order in which you specify the dislis to massist is also sigificant. If yo11 specify the -0ordered option to vxassist when creating a volume. any storage that you also specify is allocated i the following orde~: u 1 Co~~catenate dislts. 2 Form CO~UIIIIIS. 3 Form III~ITO~S. For example. the following coulmand creates a ulil-rored-stripe volume with 3 c o l ~ ~ m d 2 mil-rors ws on G disks in the disk group, mydg:
# vxassist -b -g mydg -0 ordered make 111irstrvol l o g layout=u~i~-ror-stripe 11col=3mydgOl 111ydg02

mydg03 mydgO4 111ydgO5mydgOG Tllis conm~and places columns 1. 2 a t ~ d of the first min.or on disks mydg01. mydg02 and mydg03 3 respectively, and colu~~lus 2 and 3 of the second III~ITO~. disks myd&01. mydg05 and mydgOG 1. on respectively. This a ~ ~ a ~ l g e ~islillustrated in the following figure. l e~lt

'808pi(m rl8110.11~ g)8p.C11r sys!p !L! paItLIoj i(l.Ie[nIr!s natp a.re su~unlo:,asarIljo s.ro.Lr!m a t u 'z: ntu11103 01 t08pLtt1 m0.g salLqe8!8 Z: poe ~ 0 8 p L m 1no.g sa~qeS!S E ptle '1 turnlo3 01 ~08pLur 1uo.g sa~quZ!B z puq08pdu1 mog sa&@!8 E sag3olla pnertruro3 s!rl~

:stImtllo3 i. m y amuIoil ad!qs-pa.~o.~nm salea.13pnemmo3 Bnyolloj aq) 'a~dmesa I O ~ e . .strtm~lo:, oln! sys!p arll tro a x d s alenale3tro:, 01 ~ o Ljpads 01 aluq!.rUe r[3lys-[03 aql asn 11123 'Llleno!l!ppv q 11oL

+tunlo,\ ~ o i . i ! ~ ~ l - p a d ~ ~ i ~ ~
I

~0BpLm SyS!p

SSOJ3B

.toBpLm pne Z 1111111103P U '~oZpL1t1 10Zp/CtIISyS!p SS0.13B 1 U 1 1 1 3 S.IO.LI!ttI PUBUTttI03 S!qL U PtIB 1110

:smm1103 Z: q ) y atmqo,\ . ~ o . ~ r p - p a de salaa.~:, ~ r ~ s pmmcno:, Strp%o~~oj 'aldmxa aql .rod .samnIoil pa.raXe1-uon ,103se a8e.rols ale3olle 01 s a p ames arIl saqdde Jsrssexh 'sannqoh pa.ra.ie1.10~

-Striped plex

.--:r~dirror

'

- St:riped plex
L Mirrorerf-stripe volume

Other storage specificatiou classes for controlle~s.ellclowlres, targets aud trays can be used with ordered allocatiou. For example, the followhg coluuaud creates a 3-col~uuu minored-stripe volume between specified controllers:
# vxassist -b -g lnydg -0 ordered malie mirstr2vol 80g layot~t=lllinor-stripencol=3 cth:cl ctl1.:c2c t k c 3

ctlr:cl ctlr:c5 cth:c6 This co~nmai~d allocates space for coltmu~1 from disks on co~it~.ollers, for c o l u m ~ ~ cI 2 fiom disks on coi~troller a i ~ d ou as illustrated ~ I I followii~g c2, so the figure.

IPI

[ . ~ a q m n r ~ = r o . ~,eorroo-.~o~yin=~no/(s[ am1iroA aqeru [d11018ys!p O-] [q-] )s!ssexl\ # rn] qQna1

:pea.[ o) pneumoo aq) Aj!pom 's.rosr!m

jo )Ingap aql jo pw~sn!E r l ) ! ~ arnrlloh r! a)sa.ro 0 1 .~o.~~yur+r~oLel~ I I ~ayem 8pLur 8- q- )s!ssem # 85 . OA

2-olloj

aq) asu '8pAm 'dno.12 qs!p arp

:pwmmoo '.~!nrlo~ 'amn~oh pa.Io.rr!m arp a)ea.Io 04 'aldmexa .tog

[ah!)ov+~~~] [.raqrnnr~=~o.u~rn]o ~ ~ ) n oq)Bna[ amliloh aqeru [dno.~Bys!p8-1 [q-] )s!ssexh # .~ Asl :pnemnro3 B m , ~ o ~aq) asu 'an1111o~ ~oj paIo*lpm Man e alea.13 o~

.sl!ej SIO.LI!~I ~nanodn~oo ano qs!p e J! )so1)or1 s! epp sl! lsql sa.msna arnlqoA e S F I O . L ~ ~ s)!jo .S.IO.LI!UI 1aq)o m o g poe aruriloh aq)jo Cdoo lerr!Zpo aq) moy sys!p lrra.Ia.jj!p no pa.Io)s s! (.Io.LI!~ .to) Ldoo q3eg .e)ep S)!JO Ado3 at10 neq) alorn 8mme)noo Lq L3oepm1pa.t elep sap!.\o.td amrqoi\ paxo.rmn v

Creating a concatenated-mirror volume

A c o n c a t e ~ ~ a t e d - n ~ i ~ ~ o r is an exan~ple a layered \~olume volume of which c o ~ ~ c a t e ~ ~ a t e s several tmderlying u~ilror vol~unes. create a concatenated-minor \lol~uue. the followi~~g To use comiiand:

# wassist [-b] [-g diskgroup] make vol~uue leugth layotd=concat-111i1m[utuin.o~=u~~u~ber]

To create a volume with an attached DCO object and volume

1 Use the following co~ulua~ld create the volume (you may need to specify additioual att~ibutes to to create a vol~uue with the desired characteristics): # vxassist [-g diskgro~~p] uiake voltuile length layout=layoot logqpe=dco [ndcomui~~or=uu~uber] [dcole~~=size] [fastresyuc=on] [other attributes] For uon-layered volu~ues. default numbel. of plexes iu the minored DCO volume is equal to the the of of lesser of the llt~u~ber plexes in the data volume or 2. For layered volumes. the default m~unnber attribute to specify a differeut nluuber. It is DCO plexes is always 2. If required, use the ndcolni~~or recommended that yon coufig~u.e lllally DCO plexes as there are data plexes iu the volu~ue. as For when vollm~e. example, specify u d c o ~ ~ o r = 3 aeatiug a 3-way u u ~ o r e d The default size of each plex is 132 blocks onless you use the dcoleu attribute to specify a differelit size. If specified, the size of the plex must be a multiple of 33 blocks from 33 up to a maximum of 21 12 blocks.

By default. FastResync is not enabled ou newly created volumes. Specify the fastresyuc=on attribute if you want to ellable FastResyuc 011 the volmne. If a DCO object and DCO volun~e associated with are the v o l ~ ~ mPersistent FastResyuc is enabled; otherwise, Nou-Persisteut FastResyuc is enabled. e,
2 To enable DRL or seqoeutial DRL logging on the newly created volume. use the followiug comrna~d: # vxvol [-g disligroup] set logtype=drlldrlseq volulrte For more iufollnatiou, see the \xassist(lM) aud \~xvol(lM) manna1 pages.

If you use ordered allocatiou wheu creating a mirrored volruue on specified storage, you can use the optioual logdisk athibute to specify on which disks dedicated log plexes should bc created. Use the following f o m of the vxassist c o m a u d to specify the disks from which space for the logs is to be allocated:
# vxassist [-g diskgroup]
-0 ordered make volou~e leugth layout=u~i~+or logtype=log-type logdisli=disk[,disli....I storage-attributes

If you do not specify the logdisli attribute. vxassist locates the logs UI the data plexes of the volume.

Creating a striped volume

A striped volume coutains at least one plex that consists of two or more subdisks located on two or more physical disks.
Note: A striped volr~me requires space to be available on at least as Inally disks iu the disk group as the uruuber of colnnlus UI the \~olu~ne.

To create a striped voltu~ne, the following co~luliand: use

# vxassist [-b] [-g diskgror~p] 111alievol~ulne leugtli layor~t=stripe

For example, to create the 10-gigabyte sb iped volume volzebra, i the disk group, mydg. use the u followiug co~mnaud:
# vxassist -b -g mydg make vo1zebl.a log layout-stripe

This creates a striped \folame wit11 the default stripe Illlit size (64 kilobytes) and the default ntunber of stripes (2). You cau specify the disks on which the volonles are to be created by i n c l r ~ d i ~ ~ gdisk names on the the C O U U I I N I ~line. For example, to create a 30-gigabyte striped \rolnme 0 1 three specific disks, nlydg03. 1 1nydgO4, and tuydyO5, use the following co~nmalld:
# vxassist -b -g 111ydgmake stripevol 30g layout=stripe 1llydg03111ydgO41llydg05

To change the III--.'--* of c o l u ~ ~ orn s stripe width, use the ucolr~~lm striperluit modifiers \vith ~ the aud vxassist. For ex,. 111efollo\\ing c o u i a n d aeates a striped volu~lle with 5 colum~ls a 32and

kilobyte stripe size:

# vxassist -b -g mydg make stripevol30g layout=stripe stripeuuit=32li ucol=5

Creating a mirrored-stripe volume

A minored-stripe volume mirrors several striped data plexes.
Note: A ulurored-stripe volume requires space to be available on at least as many disks ill the disk group as the number of ~ u h ~ omilltiplied by the niimber of columus in the volume. rs To create a striped-dror volilme, use the following cowlaud:
# vxassist [-b] 1:-g diskproup] make volume length Iayoot=mirror-stripe [ ~ ~ r o ~ ~ o m b e r - m b r \o r s ]

[ ~ ~ c o l = ~ ~ u m b e r ~ o f ~ c oI:stripewidtli=size] lulm~s]

Creating a striped-mirror volume

A striped-milror volume is a11 example of a layered \ ~ o l ~ m ~ e stripes several underlying mirror which volumes.
Note: A striped-milror volulne requires space to be available on at least as many disks i the disk u group as the uiunber of coluums niultiplied by the nillnber of stripes iu the volume. To create a striped-minor volume, use tlie followiug command:
# vxassist [-b] [-g diskgroup] nlalie volume length.layout=stripe-mirror [ n m ~ r o ~ ~ u m b e ~ m i ~ r o r s ] \

[~~col=~li~mbe~of-columns] [stripewidtl~=size] By default, VxVM attempts to create the underlyu~g volumes by m i ~ ~ o l i n g subdisks rather than c o l u m ~ if the size of each colu~nu greater than the value for the attribute stripe-hror-col-splits is trigger-pt that is defmed in the vxassist defaults file. If there are multiple silbdisks per column. you cau choose to minor each subdisk iudividually instead of each column. To mi~ror the subdisk level, specify the layout as stripe-murorsd rather than stripeat mirror. To m i ~ ~ at r col~umn o the level, specify the layout as stripe-muror-col rather than stripe-mi~ror.

Mirroring across targets, controllers or enclosures

To create a voliune whose nlu~ored data plexes lie on different co~~trollers kuowu as disk (also duplexiug) or i different enclosures, use the vxassist commaud as described in this section. n lu the followiug command, the attribute mhrol=target specifies that volumes should be minored between identical target IDS on different coutrollers.

# vxassist [-b] [-g diskgroup] nnake volumne length layout=layout mu-ro~=target [attributes]

... . . . ..

Tlle attribute mi~-rom=ctlrspecifies that disks in one miror should not be on tlie same co~itroller disks as in other nliil.ors within the same volume:
# vxassist [-b] [-g diskgro~~p] make voltuue length layout=layo~~t iuirror=ctlr [attributes]

Note: Both paths of an active/passive ammy are not collsidered to be on different controllers when lnirromkg across controllers. The following c o m a u d creates a milrored volume with two data plexes in the disk group, mydg:
# vxassist -b -2 mydg malie volspec log layoutlllliiror II~I~ITOI-2 nninro~=cthctlr:c2 ctlr:c3

The disks u one data plex are all attached to controller c2, and the disks in the other data plex are all n attached to controller c3. Tlnis arrangement eusures conti~lued availability of the volume s h o ~ ~either co~~troller The ld fail. attribute mi-roi-enclr specifies that disks 11 one minor s h o ~ ~not be in the same enclosure as disks in 1 ld other inurors w i t h the same volunne. The following command creates a minrored volume uith two data plexes:

# vxassist -b make -g iuydg volspec 10:: lay011t=1uii-r0r1mljl~or=2 mu-ro~=eilch. ench.:encl enclr:enc?

The disks in one data plex are all taken fiom enclosure e ~ i c land the disks in tlie other data plex are all , taken fiom enclosure enc2. This n~raugemeint ensures continued availability of tlie volume should either enclosure beco~ne miavailable.

Creating a RAD-5 volume

Note: VxVM supports this feature for private disk groups, but not for shareable disk groups in a cluster euvuoluuent. A RAID-5 vol~une requires space to be available ou at least as many disks iu the disk group as the number of c o l ~ m iu the volume. Additional disks luay be required for any RAID-5 logs that are s created. by You can create RAID-5 volu~nes using either the vxassist coiuiinaiid (recommended) or the vs~uake couuuand. Both approaches are described below. A RAID-5 volume contains a RAID-5 data plex that consists of t h e e or more subdisks located on t h e e or inore physical disks. 011ly one RAID-5 data plex can exist per volnnne. A RAID-5 volume call also contain one or more RAID-5 log plexes, which are used to log idonnation about data and parity beiug \nitten to the volume. Caution: Do not create a RAID-5 volu~ne with more than 8 c o l ~ u ~ m s because the voluine will be uurecoverable in the event of the failure of more than one disk.

:aldmaxa .roj 'aarnloh a rro anla.1 Bsl ~sno!ldoPIIS QSJ panrat1 s !as ol puamnro3 aysmls!sssxl\ aql 1111~ alnq!.ma Be! aql asn m 3 noA .ap!uf) s..rola.rls!u!orpv mals,ts a p 5 sa)!.raA aL[) aas 'a.rlsaaj s!ql lnoqa uo!)sa~~oju! a.Ion1 . I O.a.ra/ylos ~ no!)apmlod aBs.rols aqljo a.m)aaj Sm.ra!~ aBa.ro)s ~ ! u I ~ Iaq) ~uamalda~! pasn a.Ia s8e) amlqoA IL~ 01

salnq!.~~s-aBa.rols [~~~~ys!p']ys!p=ys!pBo~ [qGnal-Sol=ualZol] \ [.1aqm11~r=8olu] [s~mru~o3-.1aqrr1nn=10311] sp!s.~=lr~oLslq s o a l amnloA aysm pa.lap.10 o- [dno.rSys!p 8-1 [q-] ls!ssam # :pals3olla aq 01 s! sBo[ aql .roj a x d s I ~ ! I ~ M o g sys!p arp L p a d s 01 pmrmnno3 ls!sssxl\ aqljo mroj m Bnpto[loj arll a s n .pa)aa.I3aq plnoqs saxald Sol s - a m at[$sys!p q3!qh\ no Ljpads o) a)nq!Jue ys!pZol at11 asu ISIIUI nod 'a8s.10)~ pag!3ads rro amulo;\ s - m a Brrgaa.13 rrarp rto!la3olle pa.rap.ro asn noLj1

'xald S - a w a arp JO az!s ad!.r)s arp s a r q 1a.laAas aq p111oqsSol arll 'La.ua s-ala aq) 01 ssams )ua.rru3no3~1odc111s ,arrrnlo,\arll .roj oo!lsrrnojo! 8n!%Sol aql JO Ldo3 alaldmo3 a sarl arnnloh o~ S - ( J I ~a r1)+ paly3osseSol j - a I m rpaa pua 'saxald pad!.rls .TOpa)snala3oo3 aq rla3 sBo1 s-(flm ,103pas11 aq 01 sqs!p aq) L p a d s 01 alnq!.rUa ys!pBo[ at[$asn lsurrr noL '~801 s

- m a~!nba.r11oLj1:a)oN

.saxald So1 aql

501 anojo )IIiqap aql m q l ratpal sBo1 s - r n OM$ salsa.13 os[e 1 'sysp jo .raqtmIn q u q a p aql no az!s l y l ad!.ys )Inejap aql qlpw amn[oA 5 - r n walaa.t3 s!rll 1

:pmmmo:, B ~ o l l oaq) asn 'amn1oa 5 - r n w1w.13 0 j 1

# vsassist -b -g mydg make \,ol~nil- layourt=iuii~or 5g tag=muvol=5g

To list the tags that are associated with a volu~ne, this co~nmand: use
# vxassist [-g diskgoup] listtag volume

To list the voluuues that have a specified tag name. use this co~nn~and:
# vxassist [-g diskgrotrp] list tag=tagame volume

character shings of up to 256 characters. Tag naiues cau Tag uames and tag values are case-sa~sitive cousist of letters (A tlu.ouiJl Z aud a t11rot1glIz). nt~mbers tluougl~ dashes (-), underscores (J or (0 9), periods (.) from the ASCII character set. A tag name must stai-t with either a letter or an uuderscore. Tag values cau consist of auy cl~aracter from the ASCII character set with a deciu~al value from 32 through 127. If a tag value includes any spaces, use the vxassist settag command to set the tag on the newly created voltme. Dotted tag hierarchies are uuderstood by the list operation. For example, the listing for tag=a.b includes all volumes that have tag names that stai-t with a.b. The tag names site. udid and vdid are reserved aud should uot be used. To avoid possible clashes with future product features, it is recomnended that tag nalnes do not stall with any of the follo\Ying striugs: asl, be, isp, nbu, sf, sylnc or \;x.

Creating a volu~ne using vxmake

As an alteinative to osing vxassist, you cau create a \loluuine tising the vxmake command to aimnge existiug subdisks iuto plexes, and then to f o i u these plexes into a volulue. The exsunple given in this section is to create a RAID-5 volume usiug vxmake. Creatiug a RAID-5 plex for a RAID-5 volume is siuular to creating stiiped plexes, except that the layout attiibtde is set to raid5. Subdisks can be iinplicitly associated in the same way as with striped plexes. For example, to create a fou~r-column RAID-5 plex with a stripe ulllit size of 32 sectors, use the following colmuand:
# vxmake -g mydg plex raidplex layout=raidj stwidth=32 sd=mydg00-01,mydgOl-00.mydg0200,mydg03-00

Note that because four su~bdislis specified, but the number of colu~n~nsnot specified, the vxmake are is couunaud assumes a four-colurnu~ RAID-5 plex and places one subdisk in each coluum. Striped plexes are created ush~g san~e the method except that the layout is specified as stiipe. If the subdisks are to be comlnand to create the plex: created and added later, use the followii~g
# mmake -g mydp n l ~ u raidplex layout-raid5 nco~unm=4 stwidtl1=32

Note: If no subdlal\, ;are specified, the ncolumn attribute luust be specified.

If each colmnn iu a RAID-5 plex is to be created fiom multiple subdisks which may spau several physical disks, you cau specify to which coltunu each subdisk should be added. For exalnple, to create a three-colimm RAID-5 plex usiug six stbdisks. use the following for~u the vxmake commaud: of
# vxmake -g mydg plex raidplex layout=raid5 stwidth=32 \

sd=mydgOO-OO:O,mydgOl-00: l,mydg02-00:2.mydg03-00:0, mydg04-00:1,mydg05-00:2

This commaud staclis st~bdisks mydg00-00 and mydg03-00 collsecutively in c o l t ~ ~ n usubdisks 0. mydg01-00 and mydg.04-00 consecntively in coluuu~1, and subdislis mydg02-00 and mydg05-00 iu columl~ Offsets call also be specified to create sparse RALD-5 plexes, as for striped plexes. 2. Log plexes may be created as default coucateuated plexes by uot specifyiug a layotrt, for example:
# vxmalie -g mydg plex raidlogl sd=mydgO6-00 # vxmake -g 111ydgplex raidlog2 sd-111ydg07-00

The followil~g o m a n d creates a RAID-5 volume. and associates the prepared RAID-5 plex aud c RAID-5 log plexes wit11 it:
# vxmake -g mydg -Uraid5 vol raidvol plex=1.aidplex.raidlogI,raidlog2

Note: Each RAID-5 volume has olie RAID-5 plex where the data and parity are stored. Auy other about data and plexes associated with the volume are used as RAID-5 log plexes to log info~~natiou parity beiug written to the volume. After creatiug a voln~ne nsu~g vxu~ake. mlrst iuitialize it before it call be used. you

Creating a volume using a vxmake description file

You cau use the vxmake c o m a u d to add a new volu~ne, plex or subdisli to tlie set of objects managed by VxVM. vxulake adds a record for each uew object to the VxVM co~ifig~rratiou database. Yon cau create records either by specifying parameters to vxmake 011 the co~nluaud liue. or by using a file wliich coutaius plain-text descriptions of the objects. Tire file can also coutain coum~ands perfolmiug a list for of tasks. Use the followiug fo1111 of the commaud to have vxmake read the file from the staudard iuput:
# vxmake [-g disligrotrp] < description-file

Alternatively, you cau specify the file to vxmalie usiug the -d option:
# vxmake [-g diskgroup] -d descriptiou-file

The followi~~g sample descriptiou file defu~es voltune, db, with two plexes. db-01 and db-02: a

#rty sd sd sd sd sd plex

#name #options rnydg03- 01 disk=mydgo3 o f f s e t = o l e n = l o o o o rnydg03- 02 dis k=rnydg03 o f f s e t = 2 5 0 0 0 l e n = l 0 4 8 0 rnydgoq- 01 disk=rnydg04 o f f ? t = o len=8000 rnydg04- 02 disk=rnydg04 o f t > .:t=~l;ooo len=8ooo rnydg04- 03 disk=rnydgoq offse:=30000 len=4480 d b - 0 1 layout=STRIPE ncolurnn=2 s t w i d t h = 1 6 k sd=rnydgo3- ol:o/o,rnydgo3- 02:0/loooo,rnydg04- o l : l / o , mydgoq- 02:i/800o,rnydgo4- 03:1/16000 sd rarndl- 01 d i s k = r a r n d l len=640 cornrnent="Hot spot f o r dbvol plex db-02 sd=rarndl- 01:40320 v o l db usetype=gen p l e x = d b - o i , d b - 02 r e a d p o l = p r e f e r prefnarne=db- 02 cornrnent="Uses r n e m f o r h o t spot i n l a s t

5rn

Note: The subdisk defu~ition plex, db-01, must be specified ou a single line. It is showm here split for across two hies because of space coustraints.

The fnst plex. db-01, is striped and has five subdisks on two physical disks. 1nydg03and uiydg04. The second plex. db-02. is the prefened plex in the nunor, and has oue sttbdisk. rand 1-0 1. on a volatile n~eluory disk. For detailed infolmatiou about how to use vxrnalie, refer to the vmalie(1M) manual page. After creating a vol~tme using vslnalie, you must initialize it before it cau be used.

Initializing and starting a volume

If you create a vol~nne using the vxassist command, \rxassist initializes and starts the vohune autolnatically lu~less specify the attribute iuit=noue. you When creatiug a volume, you can uake it immediately available for use by specifyiug the -b option to here: the vxassist command, as sl~owu
# vxassist -b [-g disligro~~p] make volume lengtli layout=minor

The -b option makes VxVM carry out any required initialization as a bacligrom~dtask. It also greatly speeds up the creatio~~ striped volumes by i ~ ~ i t i a l i zthe~ g of i ~ colmiins in parallel. As au alten~ative the -b option, you can specify the init=active attribute to make a new volll~l~e to illwiediately available for use. Lu tlus example, u~it=activeis specified to prevent VxVM from synchoniziug the euipty data plexes of a uew mirrored volume:
# vxassist [-g diskgroup] make volume length Iayoutt=mi~~or init=active

Caution: There is a very s~uall of e i ~ o r occui~iug risk s when the init=active attribute is used. Although written bloclis are guarailteed to be consistent. read errors can arise in the uulikely eveut that fsck attempts to verify uuiuitialized space iu the file system, or if a file r e ~ n a i uuiuitialized follo\ving a ~~s system crash. If in doubt, use the -b optioil to vxassist instead. This co~lliilarldwites zeroes to the entire length of the volume and to ally log plexes. It then makes the vol~lme active. You call also zero out a volluue by specifying the attribute iuit-zero to vxassist, as sl~owil this example: in
# vxassist [-g diskgroup] make volume length layout=laid5 iuit=zero

Note: You c m o t use the -b option to make this operation a backgrollud task.

Initializing and starting a volume created using vxmake

A volume may be iuitialized by runliirig the vxvol command if the vol~une was created by tlie vxmake commru~d lias i ~ oyet been initialized, or if the \~oltune been set to an uiiinitialized state. and t has To iuitialize and start a vol~une.use tlie followiug command:
# vxvol [-g diskgroup] stait volume

The followiug command cau be used to enable a voltuue without iuitializiug it:
# vxvol [-g diskgroup] init enable volume

This allows you to restore data ou the volume from a backup before using the followii~g o m a u d to c malie the volume fully active:
# vxvol 1-g diskgrot~p] i t active volume h

If you waut to zero out the conteuts of au entire voltume, use this coil~~llaud iuitialize it: to
# vxvol [-g diskgoup] illit zero \ r o l u ~ ~ ~ e

Accessing a volume
As soon as a volume has been created aud iuitialized, it is available for use as a virhial disli partition by the operatiug system for the creatiou of a file system, or by applicatiou prograins such as relational databases and other data management software. Creatuig a volume iu a disli group sets up block aud character (raw) device files that c w be used to

access the vol~~me:

/dev/vx/dsWdiskgrou~p/vol~~~~~e block device file for volulue /dev/vx/rdsWdiskgrou~p/voluu~~e character device file for volulue
The patlmames iuclude a directory ualned for the disk group. Use the appropriate device uode to create, moilut aud repair file systems, aud to lay out databases that require raw pal-titions. Note: As the rootdg disk group no longer has special significance, VxVM only creates volume device I nodes for this disk group ~ Ithe /dev/vx/dsWrootdg and /dev/m/rdsk/rootdg directories. VxVM does uot create device nodes in the /dev/vx/dsk or /dev/vx/rdsk directories for the rootdg disk group.

Module 10: Administering volumes

This chapter describes how to perfol~u o i ~ ~ maiuteuance tasks on volumes in Veritas Volume c on Manager (VxVM). This includes displaying volume iufonuation, ~ u o l ~ i t o ~ i i ~ y adding and tasks, removing logs, resiziug volumes. r e n ~ o v u ~ g luil-rors, relnoving voliunes, and chauging the layout of volumes without taking them offliue. Note: Yon can also use the Veritas 111tellige11t Storage Provisioning (1st') feature to create and administer applicatiou vo1~11ues. These volilmes are very similar to the traditional VxVM volumes that are described in this chapter. However, there are siguificant differences betweeu the fimctiouality of the two types of volumes that preveuts them from beiug used iuterchangeably. Most VxVM colmauds require superuser or equivalent privileges.

Displaying volume information

You c w use the vxpru~t coll~u~aud display infonnatioll about how a volmue is coilfig~red. to To display the volu~me, ylex, and subdisk record iufolluatiou for all voli~mes the system, use the in following c o r n a n d :

The vxprint commaud can also be applied to a single disk group:

# ~ x p r i n-g lnydg -hvt t

This is example output fiom this coilmand:

-u

P,lAttlE
NME

R J ; '

/:?SET!

CSK3TATE F:ST.L.TE
DISK

STXE STATB I'V;iLLAi7P.

LEFIG'I'H LEIFZTH

P.EADPCL LAYC'TJT [COL / I O F F

[ C < I L! i > F F ] [ i 3 L ?']OFF

FREFPLEH
LiCC.L( X I D DF,71i'E

CITY FE
lOOE

PL

VCnLCRIE

an

,, N ? M _:, ,.
SCi

P.I-U~TE N.4ME

F'LEII PLEV. FLEX

PAP.EHTVOL BNIIFT,:OL

D I S 6 1 3 F F 8 LE11,;TH LEII:2TH D I S R O F F S LEtF3TH

I.Ik3DE
I.l,2,EE lODE

'ii3UWJlE ; ' h.-HE

--

>X'NI.I
DFII'IIE

PZ N X E 6 P N.914E

LG'Ti?'.SL DC.2 SELECT CDNll AT 0

f sgen
R; : *
C 1tOllCl

EN.%

<.(>IK".T
.-

B E L ~ T

f sggn
J:F :

cltldrj

ENA

Here v is a \lolume. pl is a plex, aud sd is a sobdisk. The top few lilies iidicate the headers that ii~atch each type of output line that follows. Each volume is listed alo11g with its associated plexes aud sttbdisks.
Note: The headings for sob-volumes (SV), storage caches (SC), data clia~ige objects (DCO) aud snappoints (SP) can be iguored here. No soch objects are associated wit11 these volumes.

T o display volume-related infon~l;~tion a specific volume. use the following connnand: for
# vxpriut [-y diskgroup] -t volume

For example, to display iufo~~nation the \;oliune. voldef. in the disk group, mydg, use the about following comnland:
# vxpiiut -g 111ydg-t voldef

This is example output fioin this command:

.. v

EJAME

RT,?G! WET, CSKSTATE

ST-ATE

LEII.GTH

RE.?DPGL

FR-EFPLEZ

l.rryF4E

-:- \ r ~ l d s f . EEI.WLED ACTI'.;'E 204913 SELECT f 3gen Note: If you euable enclosure-based naming, and use the vxprht coululaud to display the striich~re a of volume, it shows enclosi~~e-based device names (disk access names) rather than c#t#d#s# names. disk The following sectiou describes the il~eauiug the v a r i o ~ ~ s of \:ol~m~e states that may be displayed.

Volume states
The following \ ~ o l u ~ n e may be displayed by VxVM coiluuai~ds states such as vxprint:

ACTIVE volunie state

The volume has beeu started (kemel state is c i u ~ e ~ ~ t l y ENABLED) or was h~ use (liemel state was ENABLED) when the ulachiue was rebooted. If the vol~mle cu~reutly is ENABLED, the state of its plexes at any lnomeut is not c e ~ t a u ~ (siuce the \rolume is in use). If the voluune is cu~~elltly DISABLED, this means that the plexes cauuot be g~arauteed be to cousistel~t, are made cousiste~~t but when the volillue is started. For a RATD-5 \:olume. if the volil~ne ci~i~eutly is DISABLED, parity callnot be gi~arauteed be to synchronized.

CLEAN volume state

The voliuue is not started (kernel state is DISABLED) and its plexes are syncluonized. For a RAID-5 voliuue, its plex stripes are co~~siste~lt parity is good. audits

EMPTY volume state

The voltune coutents are not iuitialized. The lie111el state is always DISABLED when the \~olrnne is EMPTY.

INVALID volume state

The contents of au iustaut snapshot volunle 110 louger represent a true poult-i~~-tilne ilnage of the original volilme.

NEEDSYNC volume state

The voluiue requires a resynclroizatioi operatiou the next time it is started. For a RAID-5volume, a parity resyuchonization operatioil is required.

REPLAY volume state

The volume is in a transient state as part of a log replay. A log replay occurs when it becomes necessaly to use logged parity and data. This state is ouly applied to RAID-5volumes.

SYNC volume state

The volulne is either in read-writeback recovely lnode (keinel state is currently ENABLED) or was i n read-writeback mode ~yllen luachine was rebooted (kernel state is DISABLED). With readthe writebacli recovery, plex cousisteucy is recovered by readiug data from blocks of one plex and writing the data to all other ~uitable plexes. If the volume is ENABLED, this lneaus that the plexes are beiug resynchollized thongh the read-witeback recovery. If the volume is DISABLED, it means that the plexes were beiug resyuchouized tho11gl1readwriteback when the machine rebooted and therefore still need to be syncho~~ized. For a RAID-5volume. the vol~une either undergoing a parity resynchronization (liemel state is is currently ENABLED) or was havh~g parity resyuchouized when the macliue was rebooted (keinel its state is DISABLED).
Note: The inte~pretation these flags doring volume startup is modified by the persistent state log for of the volume (for example. the DIRTYICLEAN flag). If the clean flag is set. an ACTIVE volume was not wittell to by ally processes or was not even open at the time of the reboot: therefore. it can be considered CLEAN. The clean flag is always set iu m y case where the volu~~ne marked CLEAN. is

Volume kernel states

The voluiue keinel state indicates the accessibility of the vol~une. vol~uue The keruel state allows a vol~unle have au offliue (DISABLED), maiuteuance (DETACHED), or ouliue (ENABLED) mode of to operation.
Note: No user iutervention is required to set these states; they are ~nah~taiued internally. that is operating poperly, all volu~mes ENABLED. are
011 a

systeul

The following volume keillel states are defmed:

DETACHED volume kernel state

Maiilteilailce is being perfonned on the volume. The vollune callnot be read from or witten to, but certain plex operations and ioctl fimction calls are accepted.

DISABLED volumekernel state

Tlle vol~une omiile and callnot be accessed. is

ENABLED volume kernel state

The volume is online and can be read fio~n written to. or

Managing tasks with vxtask

Note: New tasks take time to be set up, and so nlay not be immediately available for use after a comnmaud is iuvohed. Auy script that operates on taslis may need to poll for the existence of a new task. You can use the vxtash corn~lland administer operations on VxVM tashs that are ruuniug 0 1 the to 1 system. Operations inclitde listing tashs, modifying the state of a task (pausing. resumii~g, aborting) and modifying the rate of progress of a task. For detailed itlfoi~~~atiou how to use vxtash, refer to the about vxtask(1M) manual page. VxVM tasks represent long-tenn operations in progress on the system. E v e ~ y gives iufo~mation task on the t h e the operation started, the size and progress of the operation, and the state and rate of progress of the operation. The administrator can change the state of a task, giving coarse-gained control over the progress of the operation. For those operations that support it, the rate of progress of the task can be over the task. changed. giving more fine-grabled co~ltrol

vxtask operations
The vxtask collw~and suppoits the following operations: abort Causes the specified task to cease operation. In most cases, the operations "back out" as if an 110 enor occurred, reversiug what has been done so far to the largest extent possible. Lists tasks rimning on the syste~n one-line siummaries. The -1 option priuts tasks in UI long foimat. The -h option pints tasks hierarchically, with child taslis followiug the parent tasks. By default, all tasks ruuui~lg the system are printed. If a taskid arguinent on is supplied, the ol~tput lul~ited those tasks whose taskid or task tag match taskid. is to Tile remaining arguments are used to filter tasks and limit the taslis acti~ally listed. P ~ i n t iufonnation c o ~ ~ t i ~ ~ u o ~ ~ a l y or group of tasks as task idolmation s about s task changes. This allows you to track the progression of tasks. Specifying -1 causes a long listing to be printed. By default. short one-line listi~lgs printed. In addition to prii~ting are task i d o ~ u ~ a t iwhen a task state c l ~ a n g soutput is also generated when the task oi~ , completes. When this occms, the state of the task is printed as EXITED. task Puts a runni~lg iu the paused state, causiilg it to suspend operation. Causes a paused task to coi~tinue operation. there Changes modifiable parameters of a task. Cu~~.ently, is only one modifiable parameter, slow[=iodelay], which can be used to reduce the impact that copy operations

list

monitor

pause resume set