Table of Contents About This Course Course Goals, Preface-xiv Course Mapersnon Preface-xy ‘Topics Not Covered. Proface-xvi How Prepared Are You? -Proface-xvii Introductions Preface-xviiil How to Use Course Materials. Preface-xix Conventions Preface-xx. Icons. Preface-.x Typographical Conventions . Preface-xxi Sun Storage Concepts 4 Objectives ne 41 Disk Storage Administration Introduction .. 12 xVM Software Installation. 12 VxVM Initialization 12 13 1-3, 14 Interfaces for Sun Storage Devices 15 SCSI Overview. 215 1-6 SCSI Interface Standards Ay SCSI Priority. 19 SCSI Phases and the Move to Fibre Channel 9 Fibre Channel Te Fibre Channel-Arbitrated Loop Advantages of FC-AL.. Fibre Channel Compared to SCSI. RAID Techrology. ‘Host-Based RAID (Software RAID Technology) Controller-Based RAID (Hardware RAID Technology) ‘Copyright 204 Bun Mironylars, ne Al Rights Revarrod. Sun Services, Revaion ODisk Storage Concepts. Hot Swapping Storage Area Networking Multihost Storage Access Multipath Storage Access ‘Storage Configuration Identification...... Conducting Physical Inventory. Displaying Storage Configurations. Identifying Controller Addressing, Identifying Device Path Components. Identifying DMP Devices. Storage Array Firmware Fibre Channel HBA Cards. Verifying Fibre Channel HBA Firmware . Verifying SPARCstorage Array 100 Firmware. Verifying Sun StorEdge A5x00 Array Firmware. Verifying Sun StorEdge T3 Array Firmware Verifying Sun StorEdge A5x00 Disk Drive Firmware Firmware Upgrade Bost Practices... Exercise: Recording Your Storage Configuration Preparation... Task 1 ~ Reviewing Sun Storage Features. ‘Task2~ Identifying Host Adapter Configurations ‘Task 3 ~ Identifying Storage Array Configurations. Task — Verifying Storage Interface Firmware Revisions. ‘Task 5 ~ Verifying Array Disk Drive Firmware Revisions. Exercise Summary. CESSES: Seeee 2 passin LAT, Managing Data .. Objectives Virtual Disk Management RAID Terminology... RAID Level Common Features ‘Concatenation - RAID 0. Striping - RAID 0. Mirroring - RAID 1. Mirrored Stripe- RAID 041... Mirrored Concatenation ~ RAID 0+1 Striped Mirror ~ RAID 1+0. y VERITAS Volume Manager 4.0 Administration ‘Canyon 2004 Sus Merosysems, ne. ABRights Reserved. Sun Sane, Rvision ver St Stim eatin sets vr 3 RL: @@@SeSe TTTTTSCCCCSCTCHC SC ECCHOFEEECOSESFOC CESConcatenated Mirror — RAID 1+0. seeen Striping With Distributed Parity - RAIDS... Exercise: Optimizing System Configurations. Preparation. Task 1 - Reviewing Software RAID Features, Task2 - Identifying Availability and Pesformance Cabling 27 249 221 Task 5 - Optimizing RAID-5 Volume: Task 6 ~ Optimizing RAID 0+1 Volumes 2.29 Task 7 - Opt 13 RAID 1+0 Volumes 230 Task 8 - Identifying Effective Storage Utilization Task 9 - Seeding Disk D @eeeoeoeoeecs oe eososoooeade fo Exercise Summary , VERITAS Volume Manager Installation . Objectives Installation item Downtime. Storage Configuration Assessment... 2 Upgrade Resources... 3 | Licensing san. Zs Srnene Current System Checkpoint. 33 | Backups. Hoes 3 Testing the New Configuration 33 le Researching Software Patches, ot | Researching Current Patch Information 34 | Installing Patches 36 Vendor Software Patches 26 Installing VxVM Softwar 37 Software Distribution Overvie 37 } Softwa'e Package Installation 3.9 Software Installation User Interaction ..- 3:10 Initializing VxVM Using the vxinstal1 Utility 1313 ‘The vxinstall Utility Dialogue 313 Licensing Requirements. Bld Verifying Licensed Features 315 xVM Post-Installation Environment. 3-16 “‘VxVM System Files. System Startup Processes.. System and User Executable Files Verifying Initial Disk Drive Status 0... for VxVM Disk Drive Management Disk Drive initialization Process Disk Drive Encapsulation Process. “ ‘Conyran2004 Sun Meronyalems, ne Al ight Resariad. Sin Serves, Revision D OS cron ene ee ied ee ee ee eevi Son. Protecting Storage Devices From Usage. Global Exclusion Installing the VEA. VEA Software Initialization... VEA Client Software Startup Host Connection Window Resolving Low-Bandwidth Access Problems Using Basic VEA Features ‘Main Window Functi Resizing Display Panes.. Modifying Preferences Customizing the Grid Display. Examining VEA Command Logs Using the VEA Search Tool ... Decoding VxVM Error Messages Exercise: Configuring VxVM.. Preparation. Task 1 — Reviewing Key Lecture Poin Task 2 — Installing the VxVM Software Task 3 - Verifying the VxVM System Files Task 4 Evaluating the Storage Configuration., Task 5 ~ Installing the VEA Client Software. ‘Task 6 Starting the VEA Client Software.. Task 7 - Customizing the VEA GUI Appearance .. Task 8 — Navigating the VxVM Technical Manual Exercise Summary. 364 VERITAS Volume Manager Basic Operations. 44 Objectives 41 VxVM Disk Group Functions. 42 Primary Functions of a Disk Group .. 42 VxVM Disk Drives. 43 Standard VxVM Disk Grou; 44 ‘Shared VxVM Disk Groups. 45 Cross-Platform Data Sharing Disk Groups . 46 \VxVM Disk Group Operations Verifying Disk Group Siatus. Using the vadisk Command to Verify Disk Group Status... 48 Using the vxdg Command to Verify Disk Group Status....4-8 Administering Disk Groups Using the vicdi.skadm Utility oo. 49 Functional Overview... Creating a New Disk Group. Removing a Disk Drive From a Disk Group. VERITAS Volume Manager 4.0 Administration ‘Copyright 2008 Sun Microsystems Ine. All Rights Rosaria. Sun Service RevigonD M FOUCATIONAL SERVICES ser Sun.com/service/suned eeoeosetseeoeoeeoeeGaoaseeoegeseje @2O-2@OCO0Q OT HOCOFOO0S Sun Administering Disk Groups Using Command-Line Programs .. Using the vzdi skunsetup Command... Initializing Disk Drives Using the veg Command........ is Adding and Removing Disk Drives... Importing and Deporting Disk (oe Destroying a Disk Group Renaming VxVM Disk Drives...... Administering Disk Groups Using the VEA GUI... Creating a New Disk Group. ee Adding and Removing Disk Drives Deporting Disk Groups. : Importing Disk Groups. Destroying a Disk Grou Renaming VxVM Disk Drives... Displaying VEA Object Propertic ee Exercise: Performing VxVM Basic Operations... Preparation... x Task 1 - Reviewing Key Lecture Points... Task 2 ~ Verifying the VxVM Environment we .so.. ‘Task 3 ~ Verifying the Initial Disk Drive Status... ‘Task 4 ~ Setting the Default Disk Drive Format Task 5 - Initializing Disk Drives... Task 6 - Creating New Disk Groups... Task 7 ~ Viewing Command Logs... ‘Task 8 - Importing and Deporting Dis! Task 9 ~ Destroying a Disk Group. Task 10 ~ Renaming Disk Drives Task 11 - Using the vcdickadm U! (Operations (Optional) Task 12 - Verifying Ending Lab Status. Exercise Surnmary, VERITAS Volume Manager Volume Operations ‘Objectives... . i Interpreting Volume Structure Subdisks. Plexes .. Volumes. Volume Structure Examples. Volume Planning... ‘i Volume Distribution... Volume Naming Conventions... Space Allocation Planning Selecting Volume Types. Groups vil ‘Copyrignt 2904 Sx Miomaynema, Inc AL RightsReserved. Sun Services, Revision D SUN EDUCATIONAL SERVICES. www sun.cam/ae-vien sini}Creating Volumes Using the VEA GUI Dit Selecton Medion Using the Disk Selection Form........ Using the Volume Attributes Form. Using the Create File System Form... Creating Volumes Using the yxaseist Command The yxassist Command : Specifying Volume Size. 3.17 Using vxassist Comman. 5-18 Modifying Volume Access Attributes 5-20 Verifying Volume Ownership. 5-20 Modifying Volume Ownership and Per nissions. Adding a UFS File System to Existing Volumes... Using the VEA GUI to Add a File System Adding a File System From the Comman. Enabling the Solaris OS UFS Logging Feature 5-24 Administering Volume Logs 5-25 Using DRLs... 525 Using RAID-5 Logs. Planning Log Placement Adding « Volume Log From the VEA GU! 5-28, Adding a Volume Log From the Command 5-29, Removing Volume Logs Using the VEA GUI 5.30 Removing Volume Logs From the Command Line... 5-31 ‘Using the VEA GUI to Analyze Volume Structures. 5-32 Displaying Volume Layout Delails... 5-32 Viewing Disk Volume Mapping and Performance........ 5-33 Exercise: Creating Volumes and File Systems Preparation, i 5-34 Task 1 - Revi 5-35 Task 2 - Creating a Volume. 537 Task 4 ~ Adding a File System toa Volume. Task 5 - Adding a DRL... Task 6 — Resizing a Volume and File System. Task 7 — Creating a RAID-5 Volume. Task 8 - Analyzing Volumes Using the VEA GUI Task 9 - Verifying Ending Lab Status. VERITAS Volume Manager Advanced Operation: Objectives... Boot Disk Encapsulation and Mirroring, Optimizing the Boot Disk Hardware Configurator Boot Disk Encapsulation Prerequisites... Encapsulating the System Boot Disk. ix ‘VERITAS Volume Manager 4.0 Administration (Copyigh 2004 Sun Mcrosyams be. AL Rights Reserved Sun Sericas, Revlon D & Sn. NV EDUCATIONAL SERVICES vrmny.sun.convservieeisuned @-0_-B-3_8 0-6-6 6-0 6-68-66 6-@-6 © 6 0 © &-0-eMirroring the System Boot Disk . Verifying the Completed Boot Disk Configuration .. Creating a Best Practice Boot Disk Configuration. Establishing Boot Disk Configuration Policies Modifying an Existing Boot Disk eaten Administering Hot Devices Selecting Hot Device Operational Mode. Evaluating Hot-Device Configurations Administering Hot Devices Using Command-Line Programs. Administering Hot Devices Using the VEA GUI. Controlling Relocation Recovery Tim Evacuating a Disk Drive Identifying Evacuation Preparing for Evacuation Identifying Suitable Evacuation Disk Drives. Evacuation Using the vxevac Command Evacuation Using the VEA GUL... Evacuation Using the vxdickadm Utility . ‘Moving Disk Drives Without Preserving Dota Moving a Disk Drive Using the Command Lin Moving a Disk Drive Using the VEA GUI Moving Populated Disk Drives toa New Evaluating Disk Drive Involvement .. Saving the Configuration... Moving the Disk Drives toa New Disk Gr. Reloading the Volume Configuration. . Backing Up and Restoring Disk Group Configurations 631 Automatic Configuration Backup . Manual Configuration Backup and Restore Importing Disk Groups Aftera System Crash .. Innporting the xcotda Disk Group After a Crash ‘Volume Snapshot Operations... ‘ Snapshot Process. Using the VEA GUI to Create a Snapshot Using the Command Line to Create a Snapshot .. ‘Online Volume Relayout . Volume Relayout Prerequisites.. Volume Relayout Using the Command Line. Volume Relayout Using the VEA GUL Creating Layered Volumes. Layered Volume Disk Requirements. Evaluating Available Da Space. Creating Layered Volumes From the Command Line... 6-51 Creating Layered Volumes Using the VEA GUI. Identifying Layered Volume Subcomponents.. ‘Ceygh 2004 Sun Meroersema, ne Al Righta Reserved Sun Services, Raviion D SUN oo cosemronoe s DPOOSCCCHSCOTHSCHCSOSCHCCOCESSHESOHSGOOSDBasic Intelligent Storage Provisioning Administration Primary ISP Components. Using Storage Pool Set Templates . Using Storage Pool Templates. Using Application Volume Templates Creating Application Volumes Using the vxvoladm ‘Command. ‘ Creating Application Volumes Using the VEA Interpreting Application Volume Configurations Replacing Failed Disk Drives Failure Behavior. Evaluating Failure Severity ... General Disk Drive Replacement Process Exercise: Performing Advanced Operations Preparation.. ‘Task 1 - Reviewing Key Lecture Poin ‘Task 2 - Encapsulating the System Boo: Disk ‘Task 3 ~ Mirroring the System Boot Disk Task 4 — Performing an Online Volume Felayout. ‘Task 5 — Evacuating a Disk Drive ‘Task 6 - Moving a Populated Vol ‘Task 7 = Performing a Snapshot Backup Task 8 - Creating a Layered Volume. Task 9— Replacing a Failed Disk Drive... ‘Task 10— Using Intelligent Storage Provisioning, .. ‘Task 11 - Configuring a Best Practice Boot Dis Exercise Summary. 693 VERITAS File System Basic Operations. TA Objectives. PA Basic VxFS 72 7-2 File System Intent Logging... 73 Installing the VxFS Software. 74 Creating VxES File Systems. 75 Extended VxFS Mount Options Intent Log Behavior Error Handling Behavi Other VxFS Mount Opti x VERITAS \oluma Manager 4.0 Administration ‘Copyisht 2008 Sun Microsystems nc. Alfighis Reserved. Sun Services Ravin wynw.suin.comyservica/sunedi Exercise: Configuring VxFS a Preparatio: | Task 1 - Reviewing Key Lecture Point: Id Task 2- Installing the VxFS Software Task 3— Creating a VxES File System Task 4 — Resizing a VFS File System... : ‘Task 5—Defragmenting a VxFS File Syst ue s Task 6- Backing Up and Restoring a Vx ‘ile System. Task 7~Using VxFS Extended Mount Options. Exercise Summary. : VERITAS Volume Manager Performance Management. Objectives ann Performance Improvement Techniques «1... = Data Assignment Strategies... Volume Structure Strategies. ! , Read Policy Strategies |e lardware Configuration Strategies 1 |e Using Performance Analysis Tools Gathering Volume Performance Statistics .... @ Gathering Application Performance Statistics, om RAID-5 Write Performance : 2 e Read-Modify-Write Oper e Reconstruct-Write Operations. I. Full-Stripe Write Operation: Exercise: Demonstrating Performance Differences Preparation. megeereeecees ie Task 1 - Review’ ing Key Lecture Points........... 8-16 ‘Task 2- Performing a RAID5 Write Performance Test. 8-18 ‘Task 3~Performing a Striped Volume Write Performance Test... 8-21 Exercise Summary. 8-22 xi e ‘Copyright 2004 Sin Merenyatema, ine At Rights Reserva, Sun Berries. Revision D SUP voc cosssosovn sees @ @ ti 92922000289 08HTH89HTTHT THEO TOHOHDECHEOHH9OORO800 aww sun comvservice/suned sEEMICES. Zz c 5 = s ae6 e ° e ° Preface e e e e e About This Course ® e ® Course Goals © o ‘Upon completion of this course, you should be able to; e Install and initialize VERITAS Volume Manager (VxVM) software © Define VaVM objects \* © Describe public and private regions e © Start and customize the Volume Manager Storage Administrator | © VERITAS Enterprise Administrator (VEA) graphical user interface e (Gul) le * Perform operations using the command-line interface © Perform disk and volume operations le © Create redundant array of independent disk (RAID) yolumes | ‘Set up dinty-region logs (DRLs) ® Perform common file system operations using the VEA GUI » Create new disk groups, remove disks from group, move disks between disk groups, and deport and import disk groups between servers © Simulate disk failure and complete a disk recovery » Create and mange hot-spare pools ® Manage and disable the hat-relocation feature ® Perform basic performance analysis Pretace-riv (Covyrght2004 Sun Miconystes fc. Al Rights Renard. Sin S8hVERs, Revision a raw sun com/sarvicersune HE six covear @SQeCCOCHTOC EHS O2OSHSCourse Map Course Map The following course map enables you te: see what you have accomplished and where you are going in referencé to the course goals, Overview Sun Storage Cor Managing Data VERITAS Volurne Manager Introduction VERITAS Volume | | VERITAS Volume Manager Manager Basic Installation Operations VERITAS Volume Manager Operations ae vaERTAS ventas i lume Manager jo System boreal Advanced Basic ; Operations Operations Operations ol VERITAS File System Operations VERITAS renee 4 Management a) a a - all! all @ all @ a oy olf Proface-xv VERITAS Volume Manager 4.0 Administration a Copy 004 So conan ne A RONG Reserved Sun Servs Reon D & Sin SUN EDUCATIONAL SERVICES www sun, com/service/stuned :Topics Not Covered Topics Not Covered ‘This course does not cover the following topics. Many of these topics are covered in other courses offered by Sun Educational Services: © Solaris'™ Operating System (Solaris OS) administration — Covered in SA-239: Intermediate System Administration for the Solaris™ 9 Operating Environment and SA-299: Advanced System Administration for the Solaris™ 9 Operating Environnient © Storage system maintenance ~ Covered in $M-250: Sun™ Software RAID Storage Sustems Maintenance Refer to the Sun Educational Services catalog for specific information and registration. ol i ie OF of bE 6 o @ bE @ ef @ About This Course: Preface-xvi ‘ Se ame ence @ 4 Seq How Prepared Are You? How Prepared Are You? To be sure you are prepared to take this course, can you answer yes to the following questions? "| © Can you perform the following Solaris 9 OS administration 4 | ‘operations? © Configure environmental variables p © Control system run levels , | © Use basic OpenBoot™ commands © Can you physically configure the following Sun systems and 4 | peripherals? | © Desktop or server-class systems G © Con you use the following UNIX® administrative commands? © chmod, chown, and chgrp ; St pet 4 Cas . mkdir ° . nkfs/newfs 9 . mount: e| @ = patchadd @ © pkgadd and pkgrm a 5 3 e @ e @ SI e @ @ @ @ Preface-xvil VERITAS Volume Manager 4.0 Administration e Soe a ae of O Stitimuncaneme arc niceaeeveaeotes ol IIntroductions Introductions Now that you have been introduced to the course, introduce yourself to the other students and the instructor, addressing the following items: 2 Name © Company affiliation © Title, function, and job responsibility © Experience related to topics presented in this course «Reasons for enrolling in this course ¢ Expectations for this course ©oeeo 66 6 orn pine Nee era asec aepecee ree ae D> SUR, sis eoscancrn serv cs C200 OS 028000 0820006How to Use Course Materials How to Use Course Materials Profecexix D Stet seceesnaar eats To snable you to succeed in this course, these course materials employ a Jeaming module that is composed of the following components. * Goals ~ You should be able to accomplish the course goals after finishing this course and meeting all of its objectives. * Objectives - You should be able to accomplish the objectives after completing a portion of instructional content, Objectives support goals and can support other higher-level objectives. © Lecture - The instructor presents information specific to the objectives of the module. This information helps you learn the Knowledge and shills necessary to succeed with the activities © Activities - The activities take on various forms, self-checks, discussions, andl demonstrations, \ facilitate mastery of an objective. ties are used to Visual aids ~The instructor might use several visual aids to convey a concept, such as a process, in a visual form. Visual aids commonly contain graphics, animation, and video. ‘VERITAS Volume Manager 4.0 Administation Copyraht 2004 Sun Micronyatams. rc. Al Ries Reserved Sun Serves, ReviionD ‘www sun com/servica/sunedSCoeeoese e®eoeo 0. eee Oo eo Conventions ‘The following conventions are used in this course to represent various training clements and alternative learning resources. Icons Discussion - Indicates a small-group or class discussion on the current SR topic is recommended at this time. Note ~ Indicates additional information that can help students but G crucial to their understanding of the concept being described. Students should be able to understand the concept or complete the task without this information. Examples of notational information include keyword shortcuts and minor system adjustments. Gaution ‘of personal injury from a A nonelectrical hazard, or risk of irreversible damage to data, software, or the operating system. A caution indicates that the possibility of e hazard (as opposed to certainty) might happen, depending on the action of the user, About This Course Protace-rx ‘Cent 2004 Sun Meronystoms, ne. Al Rigs Reserved. Sun Services Reviioe SUN EDUCATIONAL SERVICES yew sun.comniseviculsuneConventions Typographical Conventions Courier is used for the names of commands, files, directories, programming code, and on-screen computer output; for example: Use 1s -al to list all files. systemt You have mail. Courier bold is used for characters and numbers that you type; for example: To list the files in this directory, type: #ils Courier italics is used (or variables and command-line placeholders thal are replaced with a real name or value; for example: To delete a file, use the xm £iJename command Courier italice boldis used to represent variavles whose values are to be entered by the student as part of an activity; for example: Type chmod avec £i2enane to grant read, write, and execute rights for £11enane to world, group, and us21s. Palatino italics is used for book titles, new words or terms, or words that you want to emphasize; for example: Read Chapter 6 in the User's Guide. These are called class options. Preface VERITAS Volume Manager 4.0 Administration ‘Copytgn 2004 Sun hicresynems ine. ABRghts Reserved. Sun Services Revision D SHIT cu eovexroun stneces wna un STROHGHG C6000 O08 GO O66. ©0006 60 Sun Storage Concepts Objectives Upon completion of this module, you should be able to: Describe the major disk storage administration tasks Describe Sun storage interface types Describe available RAID technologies including: * Host based RAID technology © Controller-based RAID technology Describe disk storage concepts that are common to many storage installations including: © Hot swapping © Storage area networking, e@ =©Multihost access © Multipath access Identify storage configurations including: © Conducting physical inventory ‘© Displaying storage configurations @ Identifying controller addresses © Decoding logical device paths Verify storage array firmware revisions 14 ‘Copyright 2004 Sun Mecrosysems, nz Al Rights Regard. Sn Services, RevsionD 5 KarsnteenDisk Storage Administration Introduction Installing, configuring, and managing 9 VxVM installation requires both Software and hardware knowledge. VxVM Software Installation Installing the VxVM software is Solaris OS application. You can GUL installation tools, essentially the same as installing any use either the standard command-line or VxVM Initialization When you install VxVM, at least one disk drive must be brought under VxVM control using the vxinstall utility. You can either encapsulate a disk, \chich preserves existing data on the disk, or you can infilize a disk, Which effectively destroys existing data, Required Hardware Knowledge The VaVM installation process is always the same, regardless of the system platform or storage technology used. However, you must be able {0 identify storage array device addresses and differentiate them frorn other types of disk storage addresses. If you are not familiar with the device address strategy in your particular installation, you might accidentally initialize the wrung disk drives. This error could destroy valuable data, including the operating system. VERITAS Volume Manager 4.0 Administration ‘Coryngh 2004 Sin Meosytems, Inc RightsReserved. Sun Sences. Revlon 0 & Sun SUN EDUCATIONA.. Se weww.sun com/service/sunedDisk Storage Administration Introduction RAID Volume Design 5 Generally, RAID volume structures are designed with one or more of the a following goals in mind: R © — Cost savings L © Performance © Availability | : © Maintainability | In most cases, compromises are made when choosing among cost savings, performance, availability, and maintainability. . Required Hardware Knowledge You must have a thorough understanding of interface types, addressing schemes, and intemal hardware structure to achieve design goals, It is q possible to design virtual volume structures without this background 6 Knowledge, but the result might perform poorly and might not have the reliability that is required for your application. ° é RAID Volume Creation of You can create RAID volume structures using the VxVM GUI or command-line programs, Command-line programs are sometimes a better {@ choice to use, especially when volume creation must be automated using script files. You can configure the GUI to display command-line equivalents for each operation. Required Hardware Knowledge Even though you might not be responsible for the design of your VxVM volume structures, you must still be familiar with most aspects of your particular storage devices, Faery _ Stree 2 ue canerepeeaee 7Disk Storage Administration introduction RAID Volume Administration 1-4 SN, In larger installations, the most common VxVM identifying and replacing failed disk drives. At the most ‘ask involves the use of a single VxVM utility, the vedi skecin utility. For rita storage platforms, you must use another utility, luxadm during the disk replacement process. administrative task is t basic level, this Most VxVM administrative tasks require analyzing e VXVM utilities, such as vaprint and vxdisk, Solaris OS commands. Fror messages using along with some basic Required Hardware Knowledge Administering RAID volumes requires a number of hardwore-related skills including: © Decoding device error messages © Relating device addresses to physical devices © Following hardware removal procedures that are appropriate for each particular disk storage technology VERITAS Volume Manager 4.0 Agministration Copa 2004 Sun thereto, oc. Al igh Reserved. Sun Sewvies, Revlon D EDUCATIONAL SERvices ww Sun.com/service/sunedInterfaces for Sun Storage Devices @ 2 @ Interfaces for Sun Storage Devices Sun storage devices are accessed through one of two basic interface types: ® Small Computer System Interface (SCSI) © Fiberoptic Each of the basic interface types has two or more variations, which have evolved over a period of several years. The interfaces have improved in the following areas: * Data transfer speed * Data transfer latency © Interface cable lengths @euveceeeceo SCSI Overview SCSI was initially implemented in the 1980s as a way of making the interface between the host computer system and the disks independent of the computer manufacturer. Prior to the introduction of SCSI, ell the computer manufacturers had their own way of connecting the host computer system to the disk drives. SCSI introduced the idea of intelligent disk drives where the host computer system requested the transfer of a block of data from the disk. The host system had noneed to know the underlying disk geometry, It issued a request to the disk for the transfer of a block of data. The shift of intelligence from the host computer system to the disk allowed the same disk to be used by d:fferent manufacturers, which ultimately led to +heaper, faster, and larger disk drives. The connection between the host system was by the SCSI bus, for which a i set of standards was agreed upon. The speed and data capacity of the | i 3CSI bus has been increased to allow for the higher demands of today’s i SF SCOCCOSTOCORE servers, One of the earliest problems faced with SCSI was the differing sable lengths from the host system to the disk drives themselves. For the 3(CSI bus to reliably operate over differing cable lengths, two electrical connections methods were defined: Single-ended (for short connection lengths) and differential (for connection over longer cables). | ‘Sun Storage Concents 18 ‘Capriht 2004 Sun Weryslems, ne AX igh Henares Sun Service, Revision D PSU or cou ace ts SERVICES wane sun. com/sprvinsveunerInterfaces for Sun Storage Devices SCS| Interface Implementation Both single-ended SCSI and differential SCSI are currently used with Sun storage products. Single-Ended SCSI As shown in Figure 1-1, each bit is transmitted using one signal, referenced to 0 volts, This allows cable lengths up to six meters with standard SCSI-1 devices, sa lg oo Figure 1-1 Single-Ended SCS} Differential SCS} As shown in Figure 1-2, the data bits are sent using two equal and ‘pposite voltages. These allow the signal to travel farther without degradation. Differential SCSI allows cable lengths up to 25 meters. Figure 1-2 Differential SCSI VERITAS Volume Manager 4.0 Administration Copyiet 2004 Sun Wioeyatems In. A Fights Reserved. Sn Services, RevenD OSU seeteterenee anonSCSI Interface Standards Interfaces for Sun Storage Devices A partial list of the SCSI-1, SCSI-2, and SCSI-3 standards currently used by Sun are shown in Table 1-1. Other SCSI standards are used by different manufacturers. Table 1-1 Sun SCSI Standards Data Rate Number pn Glock | Data | Command —_| of ue “s Rate) Devices SCSI SMHz | 8bits | 5Mbytes/sec | 8 (SCSI) FastScst [10MHz |8bits | 10Mbytes/sec | 8 (SCSI-2) WideSCs! |5MHz | 16bits | 10Mbytes/sec | 16 (SCSI-2) Fast/Wide 10 MHz. lébits | 20Mbytes/sec | 16 SCSI (ScSI-2) Ultra 20MHz | 16bits [40 Mbytes/sec | 16 Differential Wide SCSI (SCSI) ‘Sun Storage Concepis Hw ‘Copyrgnt20%e Sun Wironysims. ine. AX Rights Reerve. Bun Servces, Rcvon D wane sun.com/seniecisunedTable 1-2 SCSI-3 Standards Interfaces for Sun Storage Devices SCSI-3 Standards Currently, only recent Sun systems such as the Ultra™ 60 workstation, Ultra 80 workstation, and the Sun Blade™ 1000 workstations, have SCSI-3. compatible interfaces. The related specifications are: © Ultra 60 workstation - 68-pin connector, (SCSI-3), two channels (synchronous) © Ultra 80 workstation ~ 68-pin connector, (SCSI-3), two channels (synchronous) * Sun Blade 1000 workstation - One singl connector (16-bit Ultra/Fast /Wide, Fibre Channel ‘Table 1-2 shows some of the current SCSI-3 standards, 40-Mbyte/see Ultra SCSI 40-Mbyte/sec Ultra SCSI Je-ended 68-pin SCSI 40-Mbyte/sec), internal disks are Single |Vitts | Hele Type Speed Wisth Ended: | pyc cattal Ditfescntiat | T*Bets Length | ength Length Scsi3U_ | 20MB/see [sbi [ism [25m _ SCSI3U__|20MB/sec [ebis [3am |- = SCSISFW | 20MB/sec [Tebits Jom | 25m = 16 SCSISUW | 40MB/sec | Tébits | 5m = 16 Scst3uw | 40MB/sec [1ébits [15m | — = 8 Scsi3suWw | 40MB/sec |16bits_|3m |= = 4 SCSI3U2__ | 40MB/sec [Shits _ | — am 2m SCSI3 U2 80MB/sec | 16 bits as 3m 2m SCSI3 U2W | 80MB/sec | 16bis | - 2m 2m 16 [Scsisuaw | somB/scc [Tobie | 3m 3m 2 18 VERITAS Volume Manager$.0 Administration Sri, SUN EDUCA’ ‘Copiioh 2004 San Microsystems ine. All Right Reserved. Sun Services, visto D ONAL SERVICES we sun com/serviewisuned ————Interfaces for Sun Storage Devices SCSI Priority The bus arbitration mechanism for SCSI uses the SCSI target ID to determine priority. Narrow SCSI has target addresses 0-7. Target 7 has highest priority (usually the ID of the controller), and target 8 has the lowest. Performance can be affected through injudicious use of SCSI target addresses. Wide SCSI uses target addresses 0-15 in the following priority: 7, 6,5, 4, 3, 2, 1,0, 15, 14, 13, 12, 11, 10, 9, 8 Address 7 is the highest priority. SCSI Phases and the Move to Fibre Channel Although it appears as if SCSI has improved performance eight-fold, this is an exaggeration. SCSI has six phases, one of which is data transfer to or from the disk. Other phases include sense (status), command transfer, and bus arbitration. SCSI supports backward compatibility, so @ narrow, slow disk can run off a fast-wide controller. This capability is achieved by having the administration of SCSI run at 5 megahertz (MHz) on narrow cabling, Each device is allowed to negotiate upwards. That is, to be fast, ultra fast, wide, and so on. The data transfer phase benefits from the improved clock speed, but command transfer does not. It takes about 5 milliseconds (ms) on each form of SCSI ‘The last 10 years have witnessed a 10,000-fold increase in computer derformance. At the same time, requirements are increasing for more ‘obust, highly available, disaster-tolerant computing resources. Computer resourees continue to be pushed to their limits. Fibre Channel Technology CCCCECSCSCHCOCOCC EDO Fibre Channel technology is the answer to the growing problems of SCSI-based peripherals. Fibre Channel is a high-performance serial interconnect standard designed for bidirectional, point-to-point communications between servers, storage systems, workstations, switches, and hubs. It offers a variety of benefits over other link-level protocols, including efficiency, high performance, scalability, simplicity, ease of use and installation, and support for popular high-level protocols, Fibre Channel also offers a higher level of security and reliability through electrical isolation. There is no electromagnetic (EM) influence. ‘Sun Storage Concepto 19 Seeyrghtat0e Sunteicayavm. ine AB Nghe Renard. Sun Services. Revo 2S O20 066666 6"Interfaces for Sun Storage Devices Fibre Chennel-Arbitrated Loop An important enhancement to Fibre Channel technology has been the evelopment of Fibre Channel-Arbitrated Loop (FC-AT), which nae Heveloped specifically to meet the needs of storage interconnects, Using a loop topology, FC-AL can support basic configurations and sophisticated Fear ecments of hubs, switches, servers, and storage systems. furthermore, by using SCSI protocols over the much faster, more robust Fibre Channel link, FC-AL provides higher levels of performance without Faluiring expensive and complex changes to existing device drivers and firmware. Advantages of FC-AL The FC-AL. development effort is Part of the American National: ‘Standards instinute/International Organization for Standardization (ANSI/1S0) accredited SCSI3 standard. This standard helps to prevent the creation of Ron-conforming, incompatible implementations, Virtually all major System vendors are implementing FC-AL, as are all major disk drive and storage system vendors. FC-AL operates on both fiber-optic cable and copper wire, and it can be used for more than just disk input /output (I/O) ‘The Fibre Channel Specification supports high-speed system and network interconnects using a wide variety of popular protocols, including: + scsi © Internet Protocol (IP) ‘* Adaptation Layer for Computer Data (AALS) (ATM) © Fibre Channel Link Encapsulation (FC-LE) © Institule of Electrical and Electronics Engineeis specification for data link layer transmission (IEEE 802.2) VERITAS Volume Manager 4.0 Administration ‘C2PyraM 2004 Sun Micronyaera, te. Al Rights Reserved. Sin Services, ReviéonD BUN EDUCATION wwwesun comiservice/sunedInterfaces for Sun Storage Devices Fibre Channel Compared to SCSI &s shown in Table 1-3, Fibre Channel technology has many advantages @OCSCCOCEHOLCF LO FZL OC OCC S SECCSHOOEZOO SOSe Cosco scot sss ‘compared to SCSI Table 1-3 Fibre Channel Compared to SCSI Fibre Channel SCSI Full duplex operation Half-duplex operation 4) 105 Mbytes/sec 40 Mbytes/soc rescence not affected by | Performance can be negatively disk position. affected by the physical disk position. Multipath disk access is supported. A disk can connect to only one SCSI channel. Up to four hosts ean connect to an appropriate array. A maximum of two hosts can connect toa single SCSI channel. Serial data transmission Parallel data transmission Suitable for use ina SAN. It allows the use of switches and Unsuitable for use ina SAN It allows no use of switches ard hubs, hubs. Can connect 30 km (25 MHz)/ | Maximum distance is 25 meters 10km (100 MHz) maximum —_| with a differential SCSI. | distances. Sun Storage Ci foncepte ‘Seprreh 2004 Bin Meronuiems nc. AH ghia Maser. Sun Services, Revacn D PSU sr covcicens senvers wwwrw.sun.comise vieRAID Technology RAID Technology 112 &Sun RAID virtual date structures can be created and managed by software applications, or they can be a resident-hardware function of some storage devices. Host-Based RAID (Software RAID Technology) VAVM is a good example of software RAID technology. All Sun storage arrays can be used with VxVM. As shown in Figure 1-3, user applications SSress a virtual structure through a single path that is composed of thee a-cby Virtual volume Figure 13 Host-Based RAID Technology Atypical virtual volume path name would be similar to the following: (Sev /yx/ask/dga/volume-01 Although the physical paths to the three disk drives in Figure 1-3 still exist they are not accessed directly by users or applications. Only the virtual volume paths are referenced by users. Software that runs on the host system creates and manages the virtual software. VERITAS Volume Manager 4.0 Administration Copii 2904 Sin Microsyters, Ine. Al Rights Raserves. Sun Servs, Ravision D SUN EQUCATIONAL SERVICES ‘aw. 21in. com/service/suned| RAID Technology Controller-Based RAID (Hardware RAID Technology) a Controller-based RAID solutions use firmware that runs internally on | storage array logic boards to maintain virtual structures that are | composed of one or more physical disk drives. Sun hardware RAID a models include: Sun StorEdge™ 41000, Sun StorEdge A3000, Stun m StorEdge A3500, Sun StorEdge A3500FC, and Sun StorEdge T3 arrays )| 7 As shown in Figure 1-4, RAID configuration software (Sun StorEdge ey RAID Manager) running on the host system configures virtual strictures I! of in the array controller board. After initial configuration, the controller [ board firmware manages the virtual structures, ® e Host System Storage Array ° Host Bus RAID e Acapier Frmvare ‘ + i © Lo . isk | Oi ee Disk [Disk 1 |e Configuration Sofware Figure 14 Controller-Based RAID Technology Note The Sun Storfidge T3 array RAID structures are configured using sither the Sun StorEdge Component Manager software ot resident storage | array operating system commands. ee | | A typical hardware RAID device appears to be the same as any logical | device path, such as /dev/dsk/cotsdoso, Applications do not recognize the underlying RAID structures. 8 @ e Hardware RAID solutions can have better performance than host-based RAID solutions for some types of RAID structures, Hardware RAID e overhead calculations are performed at very high speeds by the controller-resident hardware, instead of on the host system as in 6 host-based RAID. Flardware-based RAID-5 write performance can bo @ much better than host-based RAID 5. $ @ e a ° ‘Sun Storage Concepts 1413 ‘Copyright 2004 Sun Miceayaemn, in. At ihe Reservas. Sun Service, Revision D SUN EDUCATIONAL SERVICES www Bun.comis° e | Disk Storage Concepts ® Disk Storage Concepts ‘ This section describes the following disk storage concepts that are ® common to many storage installations: é © Hot swapping © Storage area networking dq © Multihost access © Multipath access 4 q Hot Swapping | Most Sun storage arrays are engineered so that a failed disk drive can be ‘eplaced without interrupting customer applications, The disk-replacement process includes one or more software operations that can vary with each disk storage platform. General VxVM Disk-Replacement Procedure 11 its basic form, the process to replace a failed disk drive that is under VxVM control is as follows: 1. Use the VxVM vediskadm utility to logically remove the disk. 2. Use the VxVM vxaiskadm utility to logically install the new disk. I HiTchaa | Caution = Never hot-swap a disk that is under corirol of ViVM. Always & 4s use the vidiskacm uty or command-line equivalents. q | LL. Se dl fy f | 114 VERITAS Volume Manager 4.0 Administration at Conynant 2008 Sun Microsysen,e. Al ihs Reserved. Sun Service, Revlon Ly & DSH ca soscmnor scans trian son B2 2 @ TCCCCOCOCOCC CO GOGO SS S08 ec ee 6 oe Disk Storage Concepts Alternative Disk-Replacement Procedure ‘The VxVM disk replacement process is more complex for some storage arrays, such as the Sun StorEdge A5:00 array. The Sun StorEdge A5x00 array procedure is as follows: 1._Use the VxVM wsxai.skadn utility options 4 and 11 to logically remove the disk and place it offline. 2. Use the luxadm utility's reneve device command: 3. Use the luxadm utility's insert_ device command. 4. Run the vxdet1 enable command to read in the new configuration, 5. Use the VxVM vxdiiskacin utility option 5 to logically install the new disk. Note — You be familiar with the disk-replacement process for your Particular disk storage devices. ‘Sun Storage Concepts 115) ‘Gopyrignt 2004 Sun Wicoayaams, in. A Rights Reserved. Sun Services, Revision D OSU an tascsionicseaices vinsleareneen tarDisk Storage Concepts Storage Area Networking ‘The current Sun storage area network (SAN) implementation is composed of the following hardware and software: © Supported arrays are Sun Stordge A3500, Sun StorEdge, A5200, Sun Storfdge 13, and Sun StorEdge T3+ arrays © Sun Fibre Channel switches (8 and 16 ports) * Management software (fabric and switch management) SANS are usually based on the Fibre Channel data communications standard, Basic SAN Configuration Traditionally, data is made available through Network File System (NFS) mounts over Ethernet user networks. This configuration is referred to as networkattached storage (NAS), User networks can be overloaded by heavy data traffic. A SAN is a Fibre Channel network that off-loads data traffic from the user network. As shown in Figure 1-5, a SAN isa high- performance network composed of servers, storage devices, and interconnect devices, such as switches, hubs, cables, and converters. Swiches Sun Sega T3 rey Parr Pa xu -| 5 Eales (ee Host Adapter Fed cates, i Figure 1-5 SAN Components A SAN can enable gigabit-speed data transfer with high-availability (no single-point-of-failure). Redundant SAN sw itches ca be configured to have automatic failover capability. Data is automatically re-routed through a redundant switch, +10 VERITAS Volume Manager 4.0 Administration, ‘Copyngn 2004 Sin Microsystems ln. AL Rights Revered. Sun Services, Revi O Su os, UCATIONAL SERVICES ywww.sun.com/service/sunedNeale cored caine Disk Storage Concepts SAN Definitions ‘The SAN fabric. is composed of several elements, Without a basic understanding, the terminology can be confusing or meaningless. SAN Fabric Networks that use Fibre Channel switches are referred to as fabrics, The term fabric characterizes a network of multiple switches as opposed to a network with a single switch. Each connection in a fabric can use the full 100-megabytes per second (Mbyte/sec) Fibre Channel bandwidth, Switches in a fabric use a routing technique known as cul-through switching. Cut-through switching refers to the process by which the Fibre ‘Channel switch can route the incoming data frame almost immediately by reading its link-level destination ID (D_ID), It does not need to read the entire frame prior to transmitting it to its target. Fibre Channel Frames ‘The data elements ref-rred to as data packels in Transmission Control Protocol /Intemnet Protocol (TCP/IP) are referred to as frames in Fibre Channel. The basic Fibre Channel frame structure contains a 24-byte header followed by up to 2112 bytes of data. A key portion of the 24-byte header is a 3-byte link-level D_ID that defines the port address to which the data frame must be transmitted. Fibre Channel Devices There are two types of Fibre Channel devices, public and private A Fibre Channel private loop is a traditional storage configuration, such as one oF more Sun StorEdge A5200 arrays, connected to a host system either singly, in a daisy-chain configuration, or through a Fibre Channel hub. The devices are available on the loop only to the physically connected host. Private devices donot have full Fibre Channel addressing capability. They have only the Arbitrated Loop Physical Address (ALPA) portion of the Fibre Channel physical address. These devices exist only on loops, and, unless the Switch offers extra support, these devices cannot communicate outside their own loop. Sun Storage Concepts 117 ‘Conant 2004 Sun Wioaratama Ine. Al Righa Reserved. Sun Services, RevitonD wwew.sun conv!Disk Storage Concepts Public devices have full Fibre Chanel addressing capability and, therefore, can communicate with any other public device on the fabric They can be connected directly to the switch (one device per port) or arranged in an arbitrated loop with up to 127 nodes in the loop and the loop connected to the switch. Switch Port Functions You can configure the Fibre Chane! switch ports to function in several Ways using switch management sottware. The primary reason for different port functionality is to allow selective access between Fibre Channel devices and host systems. You should only use the following port configurations: © Fabric port (F_Port) — A fabric port connects a Fibre Channel switch toa fabric-aware nate port (or N_Port) on an end-device. © Segmented loop port (SL_Port) — Segmented loop ports provide support for private arbitrated loops on a Fibre Channel switch. All ‘segmented loop ports in the same SL zone behave as one private arbitrated loop (and so they share the same ALPA space). © Translated loop port (TL_Port) ~ Translated loop ports provide Support for public and private loop devices on a Fibre Channel switch. Translated loop ports translate between private and public addresses, allowing public devices and private devices to communicate with one another. © Trunk port (T_Port)— A trunk port connects a Fibre Channel switch to another Fibre Channel switch (this is known as cascading). Zones Zoning refers to the deliberate segregation of SAN resources from other SAN resources. Zones essentially create sub-networks that provide different levels of connectivity or addressability between different hosts and devices on the network. Routing tables control the access of hosts to devices. You can individually configure device ports to be accessible or inaccessible to other specific ports. 18) VERITAS Volume Manager4.0 Administration Cooyighi2004 Sun iosysiens, in. At Figs Reserwe. Sun Services: RevionD SUM oy vcononn. senvices wea eaeecnerate SOSHSSHHSHOHSHSHEHSHSSHSSHSHSHSHHOHTHSHHSHHKBHSHHH VOa a a Disk Storage Concepts ‘Sample SAN Configuration ‘The example in Figure 1-6 shows how a multihost SAN configuration might be arranged to support both private and public use of storage resources. Sun Store dae’ L180 (of Sun StorEdge™ 1700 FC Tape Library Sun Enterprise™ 420 Server ee Host Adapter Switch ‘Sun StorEdge T3 Array Partner Pairs EE 1 ‘Sun Enterprise™ 3500 Server. ‘Sun StorEdge S200 Array Figure1-6 Sample SAN Multihost Configuration Note —To take advantage of the multipath connections from each host, ystem, you must use 4 multipath product, such as VERITAS DMP or the un StorEdge Traffic Manager software. Sun Storage Concepts 1-19 ‘Conyigh 2004 Sun Mleoayaas, ne Al Rigs Resernd Sun Services, Revision www.sun.com/servica/sinedDisk Storage Concepts +20 SSun. ‘SAN Device Addressing ‘Traditionally, the Solaris OS has named storage devices based on the controller, target 1D, and logical unit number of the device. When large SANs with multiple paths to large storage arrays are constructed, thie naming convention could tead to thousands of targets per controller and storage identified more than once by different controllers and targets. The ew method incorporates the World Wide Name (WWN) of the device into the device name used by the host. The new names provide the benefit of uniquely identifying storage devices to the host. When using Sun StorEdge Traffic Manager software, a device with raultiple connections to a host is known to that host by one name. Old device path: /Aevices/peiet, 4000/pcies/stnm, qlcs4/tpa0, 0/sedea, 0 New device path: /devices/pcist, 4000/pcie4/SUNW,qlce4/ p90, 0/'ssdew50020£2000 00225, 0 Old symbolic device name: (Mev/ask/ctt3d0s2 New symbolic designation: /Aav/dsk/o450020¢2000002253052 ‘The number of storage devices that can be attached to a host can grow to the thousands with the advent of SANs with native fabric connectivity. Probing all these devices at boot time and creating device nodes can increase the boot time greatly. In addition, a host might not need access to ail of the storage devices it can access. The Sun StorEdge Network FC Switch-16, Version 3.0, no longer creates device nodes for every storage device attached. Instead, the administrator creates device nodes on demand by using the cEgacn utility. The device nodes, once created, are persistent across reboots VERITAS Volume Managar4.0 Administration Conyegh 2004 Sun Warosyatems ine. A Rights Reserve. Sin Services, Ravin IW EDUGATIONAL SERVICES wwen-sun comiservice/sunedDisk Storage Concepts Muitihost Storage Access With the advent of technology, such/as the Sun StorEdge A5200 array, as many as four different hosts can be connected to the same storage device. Multihost connections are also possible on some versions of the SCSI. Multi-Initiated SCSI ‘Sun StorEdge MultiPack storage devices support physical SCSI interface connections from two different host systems. The SCSI interface on each of the systems must have a different initiator identifier (ID) setting, which is system firmware configuration known as the scsi-initiator-id As shown in Figure 1-7, you must change the scsi -init iator-idon one of the host systems to eliminate the addressing conflict between the two host systems. Host System A Host System B. 4 Internal SCS! Bus fp Z Internal SCSI aap Internal SCS! Bus Internal SCS! Bus Gece > scsi sco! Cord Ce ms }-on | = Figure 1-7. Multi-Initiated SCSI Configuration ‘The SCSI initiator values are changed using complex system firmware commands. The process of changing these values varies with system hardware platforms. Sun Storage Concopis 121 ‘Copyright 2034 Sur Mernystare, ne Al Righe Renard Sin Sarvees. vision SUN EOUGATIONAL SERVICES yavw-cun.comiserviceisuned @¢ O02 60080808066 &Disk Storage Concepts Multihost Fiber-Optic interface Two different fiber-optic interface storage arrays support multiple host Sonnections, The SPARCstorage® Array 100 unit allows up to two host Systems to connect toa single storage array. The Sun Stortdge AS0QO, Sun StorEidge 5100, and Sun StorEdge 5200 (Sun SiorEdge A3z00) arays slow up to four host system connections. The serial optical channel (SOC) ‘connections are shown in Figure 1-8 soce ‘Sun StorEdge el host adapter ‘A5x00 Storage ‘Array Host 1 + Interface Board A Host 2 | —_ taste Bows Host 3 Host 1 Host 2. Figure 1-8 Multthost Fiber Optic Coniigurations 422 VERITAS Volume Managor4.0 Administration Sopyr9n 2004 San Mecoayatens In. ALRighs Reserved Sin Sarices, Revlon D @ SU1I0 .sesccsnoss semnces WnW.5un.com/service/suned oe ° ° ° oe ° ° ° o ° i) ie 9 e e je ;°@ 1@ |e ° ® e ° le e e ® @ @ e ® e @ ° ® e e ® @ ° eDisk Storage Concepts Multipath Storage Access ‘Multipathing is defined as dual connections to a storage array from a single host system. Multipathing can be used to provide redundant access paths in case of hardware failures and, in some cases, to perform load balancing between the two access paths. There are several different hardware and software schemes that can be used to implement multipath configurations Redundant Dual Active Controller Driver Some Sun storage devices allow dual connections to a storage array from a single host system. As shown in Figure 1-9, one host adepter can be configured as a backup if the primary access path fails. Stor PPeeeseeoecececes Arty Host Systom e ee Dive Drive @ e Figure 1-9 Redundant Dual Active Controller Driver ‘The Redundant Dual Active Controller (RDAC) driver is a special purpose driver that manages dual-interface connections. This driver is available with some of the Sun storage arrays, which include the Sun StorEdge A3500 and Sun StorEdge A3500FC array models, SCC eC HO oO Applications directly interface with the RDAC driver and are unaware of interface feilure. If one of the dual-controller paths fails, the RDAC driver automatically directs I/O to the functioning path cares Sree SER OC acne parte reas SUM soc eoccions. seavens A pao aeonsDisk Storage Concepts _ Note ~ The Sun StorEdge A3500FC ‘array uses a Fibre Channel interface Lyf, instead of the SCSI interface used on the other RDAC-controlied storage array Alternate Path Driver for the Solaris™ OS, The Alternate Path (AP) software for the Solaris OS works with Dynamic Reconfiguration (DR) to provide the ability to move all 1/0 off a system board before removal for upgrade or repair. AP is not applicable to all architectures. As shown in Figure 1-10, the AP software package contains user-level applications and kernel device drivers to allow the construction of metal /O devices from multiple controllers toa single physical device (disk or network). This function allows 1/O on active disk and network 1/0 adapters to be seamlessly redirected to a previously specified and configured 1/0 device. Failed I/O operations to a device are automatically retried on the alternate path BW sysiom intercornect — nae eed & ‘Dual-Poried Storage Device Figure 1-10 Alternate Path Hardware Configuration 4.24 VERITAS Volume Manager 4.0 Administration Corright 2008 Si Meronytars, Ie MARigha Rater. Sun Saves, Rr D ST ntcocano www suin.com/serview/suned@OC808O0CE OS 66066 SUI snscovcsrorss son Disk Storage Concepts Dynamic Multipathing Driver {The Dynamic Multipathing (DMP) driver is unique to the VVM product. His used only with fiber-optic interface storage arrays. As shown in Figure 111, the DMP driver can access the same storage array thronigh ‘more than one path. The DMP driver automatically manages multipie Paths to the storage array. Depending on the storage array model, the Paths are either used for load-balancing in a primary mode of operation or in.a backup mode of operation in the event of a failure, [lt HBAHost Bus Adagtor Figure 1-11, Dynamic Multipathing Driver Specific paths can be enabled and disabled with the VxVM «vedmpadim command. Nate — During a VxVM installation, you must take special steps to ensure that the DMP feature is compatible with AP, SAN, and the Sun. StorEdge Traffic Manager software. ‘Sun Siotage Concepts 425 ‘Copyright 2004 Sun Microsiatems, ne AL Rishs Rasarvad. Sun Services, Revision © 8 www Sun.comisenvicn/sinedDisk Storage Concepts | Sun StorEdge™ Traffic Manager Software The Sun StorEdge Traffic Manager software is a new architecture for representing and managing Fibre Channel devices that are accessible through multiple host controller interfaces (HCI), Sun StorEdge Traffic Manager software provides automatic load balancing and automatic failover to an alternate controller. A typical Sun StorEdge ‘Traffic Manager software configuration is shown in Figure 1-12. Bh System interconnect __ Board #1 Board #2 Ti cud es ta Dual ried Storage Bavice Figure 1-12 Sun StorEdge Traffic Manager Software Configuration The minimum software and hardware requirements for Sun StorEdge Traffic Manager sofeware are: © Solaris 8 OE Update 4 © VxVM32 © Solstice DiskSuite™ 4.21 software Sun StorEdge A5200 and Sun StorEdge TS arrays © Peripheral Component Interconnect (PCI) single- and dual-Fibre Channel network adapters VERITAS Volume Manager 4.0 Administration ‘Cooyih 2004 Sin Merosyteme eA fights Reserved Sun Sac, Rndion D SERVICES www.stin.com/serviea/sunedee r@eescooaoonosooens Multipath Software Summary ‘The RDAC, AP, DMP, and Sun StorFa coexist in some configurations, configure each interface for use Disk Storage Concepts ‘compares some of the multipathing software features. Table 1-4 Multipath Software Comparison ize Traffic Manager software can but you might need to selectively by only one of the applications. Table 1-4 @ Sun ‘Copyrgn 2006 Sun Mcrosyatems. Ine. Al Righs Reserved. SunSarviens, Revision D SUN EDUCATIONAL SERVICES Sun StorEdge | Alternate Fenctlonslity, | affe Mersaee Pathing DMP RDAC Vendor ‘Sun Sun VERITAS | LSI Logic/ Software Symbios Corporation Maximum ‘Two Two Four Two paths: Active/active _ | Yes No Yes No Active/passive | Yes Yes Yes ‘Yes ‘Automatic Yes Yes Yes Yes failover Supported SunStorEdge | SPARCstorage Any VxVM_ | LSI Logie devices A5200 array, Sun | Array 100,Sun supported devices StorEdge T3 StorEdge A5:00 (| disk only array array, Sun StorEdge ‘TS array Host bus FibreChannel | Fibre Channel only | SCSland | SCSland adapter type | only Fibre Channel | Fibre Channel, Comments | Cannot man Cannot run with | VxVM- LSI Logic/ with DMP DMP and not managed Symbios at this time supported on disks only | controllers Sun Fire™ servers only Naming Specialnames —_| Special names Special Native /éev/scsi_vhei | /dev/ap names names {dev/vs/enp Environment Solaris 8OE, Solaris 25.1 or Multiple Multiple Update 4 or higher operating —_| operating higher systems and | systems _{ levels and levels Sun Storage Concepts 27 wwww.sun,comiserviar/eunedStorage Configuration Identification Storage Configuration Identification To be an effective administrator, you must be able to identify storage configurations and decode logical device addresses. Conducting Physical Inventory ‘The first step in determining your storage configuration is to examine and record the number and types of storage arrays. You can trace cables from, a system to attached storage devices. It is helpful fo create a configuration diagram showing sll attached storage devices and any unique identification information associated with them, such as world wide numbers, IP addresses, or narnes. Displaying Storage Configurations 1-28 Sun The format utility and the luxadm wtlity are commonly used to display all available storage devices. Using the 1uxacim Command to Display Storage Use the 1uxacin probe option as follows to locate several types of Sun. storage arrays including Sun StorEdge T3 array logical unit numbers (LUNS). In the following example, two SENA type arrays were found along with two single-LUN T3 storaze arrays. The luxadm command does not identify the exact model of storage. luxadm probe Found Enclosure(s): SENA Name :AA Node WwN:5080020000034ed8 Logical Path: /dev/es/ses0 Logical Path: /dev/es/eea! Node WiN:50020£200000c193 Device TypeiDisk device logical Path: /dev/rdsk/c2tiaos2 Node WWN:50020£200000C367 Device Type:Disk device Logical Path: /dev/rdsk/c3tid0s2 VERITAS Volume Manager 4.0 Administration Copyigh 208 Sun tcresystoms, ADRES Reserve Sin Services, Ravan DUCATIONAL SERVICES ‘vow sun com/servicelsunadStorage Configuration Identification Using the format Command to Display Storage ‘The Solaris OS format utility is a reliable program for gathering basic storage configuration information, This utility reports all storage devices, regardless of type or model. The following sample output shows a configuration consisting of two internal disk drives and a single Sun StorEdge T3B array that is divided into six LUNs, 4 format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. e0kOdo /pciei£ ,4000/sc8i83/sd80, 0 1. cOt140 /pci@lé ,4090/scsia3/sde1,0 2. c2tid0 /pci6, 4000/peie2/suNn, ql.o8s /£pa0, 0/sedaws0020£230000c193,0 3. e2tidi /pc486, 4000/pcie2/SUNH, qLces /Epe0, 0/s8dews0020£220000C193,2 4. c2t342 /pci96, 4000/peie2/Stnw, ql cas /Epa0, 0/ssdew50020£230000¢193, 2 21143 /pci6, 4000/pcie2/SUNK, qlca5 /Eps0, 0/ssdews00201230000c193,3 6. c2tid4 /pei@6, 4000/peie2/SUNN, lce5/Epe0, 0/ssdews0020f230200¢193,4 7. c2:.A5 1p2196, 4000/pci@2/SUNH, qlc@5 /fp@0, 0/asdaw50020f230000¢193, 5 Specify disk (enter its number) : | 4.20 OSG rence Sun Storage Concepts {ooyigh\20%4 Sin Mleroyatams, ie. Ab Riga Raaarnd. Sin Sarvs, RavislonD way sun.com/senvico/sunedtIdentifying Controller Addressing When the Solaris OS software is first configured, all disk storage interfaces are assigned a unique controller number. As shown in Figure 1-13, controller numbers are a single point of attachment to a single storage device or hub, Host System ‘Sun StorEdge a 01000 array internal | Sun StorEege S100 Array PEPE FAL ie — 1 5300 Array [— Figure 1-13 Controller Address Numbering Using VxVM Commands to Display Controller Addresses After the ViVM software is instelled and licensed, you use the vxanpadm command to display the bas c controller configuration. The following is an example, 4 vedupadm Listotlr ai2 CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME, 0 Disk ENABLED 2 san ENABLED SEO 3 San ENABLED SENAL a B ENABLED 130 3. B ENABLED 31 4-30 VERITAS Volume Manager4.0 Administration Cory 2004 Sun Mercaystrs. Inc A RightsReserved Sun Serene Rien Sun ¢ EUUCATIONAL Ssun.com/serviow/suned8-0-@-0-6— -0 9-99-99 p 4 Storage Configuration Identification Identifying Device Path Components ‘To configure and maintain storage devices, you must understand the terminology that describes and locates storage interface boards, storage arrays, and disk drives within a storage array. Each disk drive in a non-hardware RAID Sun storage array is identified by two unique paths: * Physical device path (under the /devices directory) © Logical device path (under the /dev/dsk and /dev/xdak directories) System drivers and applications use the device paths to access specific disk drives. Physical Device Path Components Pt ysical paths describe the addresses of physical hardware components that connect to a particular device. A typical physical device path is: # 1s -1 /dev/dsk/cot0d0s2 lewarwenwx 1 Zoot root 41 Get 21 21:01 /dev/dak/cotodos2 ->. /evices/pci@if, 4000/sceisa/s890,0:¢ fi Is -1 /dev/asc/c2tidos2 Arwerwxrwx 1 root root 74 Oct 21 21 (dev/dsk/c2t1d0s2 ->. ./ /devices/pci@s 1000/pcia2/SUNW, qless /Epe0 ,0/ssd2wS0020£2300000193, 0c He -1 /dev/dsk/c3tidda2 lrwarwsrwx 1 root root 74 Sep 24 22:46 /dev/dsk/e2tid0s2 ->../.. /devices/pci@s, 4000/pci@s /SUNW, @lce4/£p20,0/ssd2w21000020370c055a, 0:c Physical device paths describe internal hardware paths in a manner that Varies depending on system type, interface type, and storage device type. The paths show the location and type of interface cards and also the type of software drivers used. ‘Use the man pages to research physical path components as follows: # man poi # man gic # man sed ‘Sun Storage Concepts sat ‘Ceoyroh 2004 Bur Mironyaams, ine. A Righia Ranarved Sin Barveos. Revision‘Storage Configuration Identification 1:92 & Quay Logical Device Path Components Logical device paths to disk drives are found under the /dev/dsk directory for block devices and under the /dev/xdskc directory for raw devices, ‘A logical device path is a more basic representation of a physical path. A typical logical device path is: Each logical device is linked to a physical device path: # 1s -1 /dev/dak/eit3d0s2 lrwerwerwe 1 root root’ «90 Dac 2 1998 /dov/dsk/eit3d0s2 -> /. ./eevices/ioundtet ,¢1200000/abie0, 0/SUNW, soca, 0/ SuNA, pliea0000800, 201cad7e/sade3,0:e The following path, /dev/dsk/cot3d0s2, is an example vf a typical logical device path. Standard logical device paths are composed of four ‘components © Controller address (co) Target address (¢3) © Device address (G0) Slice address (s2) ‘VERITAS Volume Manager 4.0 Administration ‘Comyrcht 20M Sun izesystems, Ine AERIgh Reserve. Sun Sanices Ravin D SV ESUUATIONAL SERVICES www sun.comservice/sunedeee0aeen @ © ® ‘Storage Configuration Identification Typical Storage Device Addresses ‘The number of devices associated with each target depends on the type of storage device. The relationship between target and device numbers for software RAID Sun storage is as follows: © SPARCstorage Array 100: © Thirty disks © Six targets, to-ts © Five devices (40-4) associated with each target © SPARCstorage® RSM™ array: © Two selectable target ranges © Soven disks © Seven targets, to-t6 or te-t14 © A single device (do) associated with each target © Sun StorEdge 11000 array: © Two selectable target ranges sks, tO-t3 and tB-t12 . . Twelve disks, t0-t5 and t8-t23 © A single device (do) associated with each target © Sun StorEdge A5x00 array: — Fourselectable target ranges téand tl © — Fourteen disks, targs £10 and e16-t26 Twenty-two disks, targets to © A single device (40) associated with each target © Sun StorEdge MultiPack array: ‘* Two selectable target ranges for a six-disk model © Six disks, targets, ¢ © Twelve disks, targets t2-t5 and t8-t15 -t6 or hots © A single device (40) associated with each target © Sun StorEdge MulliPack-FC array: © Fifteen selectable target ranges © Six disks, targets, re-t13 © A single device (do) associated with each target ‘Sun Storage Concopis 1-33 ‘Cenyigh2004 Si Meroryname, ne. AA Rights Reserve Sin Serveas, Revision D ERVIORS eww. sun.comfservica/suneu JGATONAL‘Storage Configuration Identification Identifying DMP Devices DMP connections can be identified using the format utility as follows: 0. cOLOdO /sbus#3 ,0/SUNW, fas93 ,8800000/sde0,0 Notice that the device paths for devices 1 and 2 have the same disk drive identifier, 20370c0de8. Because the controller numbers are different, devices 1 and 2 are connected to two different controller in erfaces in the same systera. 4-34 VERITAS Volume Manager 4.0 Administration Copy 2004 Sun Mies nc. At Fights Reserved Sv Services, Revlon D aww sun comiservioeleunad-@ LO-O-O-¢ Storage Array Firmware Storage Array Firmware Several Fibre Channel hardware components have resident firmware that can be at various revision levels. You must verify the minimum levels for this firmware before starting an installation. If necessary, you need to upgrade the firmware to an acceptable revision level. The related Fibre Channel components are: mre Channel HBA cards Storage array controller /interface boards ® Storage array disk dtives Fibre Channel HBA Cards There are several generations of Fibre Channel HBA cards including: © FC/S (also known as FC25/S or SOC cards) The FC/S HBAs are SBus-based cards that were used with the older SPARCstorage arrays and SBus systems. © FC100/S (also known as SOC+ cards) The FC100/S HBAs were faster versions of the FC/S cards and were also used with older SBus-based systems. ¢ — FC100/P and FC100/2P (ISP 2100 or ISP 2200 carits) ‘The FC100/P HBAs are PCI bus cards. The FC100/2 with ISP 2100 chips are single channel only. The FC100 cards with ISP 2200 chips can be single channel (/P) or dual channel (/2P). There are different firmware files for the ISP 2100 and ISP 2200 versions, © Compact PCI (cPCI) Dual Fibre Channel Adaptor Note = The numbers ISP 2100 and ISP 2200 are model numbers oF Uy integrated circuit chips on the interface cards. 1 i) ‘Sun Storage Concepis: 1.35 Sonate Skins Aa Retr Si Saves Rein SUM s roscnn some wy sun.com/service/sunedStorage Array Firmware @ SUM su coucanenns senvees Verifying Fibre Channel HBA Firmware Fibre Channel HBA card firmware revisions can be checked with the Luxada utility, which is a standard Solaris OS command that resides in the /usr/sbin directory. ‘There are different 1uxadim command options for each generation of Fibre Channel HBA cards. However, the most current version of Luxadm has a single option (£code_download) that can be used to verify and upgrade firmware on most Fibre Channel HBA cards. An example of the command ‘output follows. 4 /usz/sbin/luxadm fcode download -p Found Path Lo 0 FC/S Cards Complete Found Path to 0 FC100/S Cards Complete Found Path to 2 FC200/P, ISP2200 Devices Opening Device: /devices/pcies, 4000/SUNH, 1€pa2:idevct1 Detected Flode Version: FC100/P FC-AL dost. Adapter Driver: 1.9 00/03/20 ‘Opening Device: /devices/peies, 4000/SUNM, ifp@3 :devet] Detected Flode Version: FCLO0/P FC-AL Host Adapter Driver: 1.9 00/03/10 Complete ‘The firmware revision in the preceding example is 1. Caution — The same Tuxadm command option also downlo. firmware into the HBA cards. ‘VERITAS Volume Manager 4.0 Administration Copyright 2006S. Merexysaa, ne All Riis Reserved. Sur Servos, Rain D isun.com/servieg/suned J©2SSSSSCOSHSSOSSHSAOSTSHSESSSHERSVOHEHDAGCHEE SVE OSE= Storage Array Firmware Verifying SPARCstorage Array 100 Firmware “ou use the Luxacn display command to determine SPARCst \rray 100 controller board firmware revisions. You use address to identify the array you want to examine age the controller An example follows, # /usr/sbin/luxadm display ¢3 SPARCStorage Array 110 Config (luxadm version: 1.42 Sunos ration 6) Controller path: (devices/sbuses ,0/SUNN, «: ctlr cad, 10000/SUNH, p1niacd00000,78¢c£9 DEVICE STATUS TRAY 2 TRAY 3 rive Firmware Rev: 3.6 Serial mm: —_0900007ac Accumilate Performance Statistics: Enabled Sun Storage Concopte 137 (Gopyiot 2004 Sun Mernyaiae, be: Al Right Raserved. Sun Seca, Revition D OS eunniaucniteStorage Array Firmware Verifying Sun StorEdge A5x00 Array Firmware You can use the 1uxadm command to display the firmware revision of Sun StorEdge A5x00 array interface boards. An example follows. # luxadn display aA SBNA DISK STATUS : | SLOT FRONT DISKS Node Wil) REAR DISKS (Node wv) 0 Not Installed On (0.K.) 200000203704£9¢¢ 1 On (0.K.) 20000020370e05Sa Not Installed 2 Not Installed Not Installed 3 On (0.K.) — 20000020370dSe28 On (0.K.) 20000020370d54a9 4 Not Installed On (0-K.) _ 20000020370d528a 5 Not alled Not Installed 6 on 2000002037005676 On (0.K.) 0000020370cbia SUBSYSTEM STATUS 1D:0 Node int: Soa002 8 Enclosure Name AR Power Supplies (0,2 in fror 0 0.K. (rev.-02) 1 0.K. (rev.-02) 2 Not Installed Fans (0 in front, 1 in rear) 0 0.%.(rev.~-05) 1 ©.K, (rev.-00) ESI Interface board(IB) (A top, B bottom) Ar O.K. (rev,-04) , 1 in rear) BIC module (1 on left, 0 on right in 7B) 0 0.K. (nod. -05) Not Installed B: O.K. (rev.-04) GBIC module (1 on left, 0 on right in IB) 9 Not Installed 1 Not Installed Disk backplane (0 in front, 1 in rear) Front Backplane: 0.K. (rev. -04) ‘Temperature senscrs (on front backplane) 0:33°C 1:34°C 2:36°C 3:36°C 4:34°C $:33°C 6:36¢C (All temp Rear Backplane: 0 Tenperature sensors (on rear backplane) 0:36°C 1:36°C 2:37°C 3:34°C 5:36°C 6:37°C (All temperatures are NORWL.) Interconnect assembly 0.K. (rev. -02) Loop configuratien Loop A is configured as a single loop. loop B is configured as a single loop. 138 VERITAS Volume Manager 4.0 Administation Copyright 2004 Sun Mersin Al Rights Retard Su avis, Rin SIE nena eanes www sun.com/service/sunede _ Storage Array Firmware Verifying Sun StorEdge T3 Array Firmware The Sun StorEdge T3 arrays have internal configuration and control suftware (ps08) that you use to verify firmware revisions. You must perform a telnet command to a particular array, log in as user root, and use the ver (version) command to verify the current firmware revision. An example of a typical session follows. $ telnet 3 Trying 129.150.47.115 Connected to purpleis Escape characte: Login: root Paseword 7300 Release 1-00 1999/12/15 16:55:46 (129.150.47.118) £3:/:el> ver 7300 Release 1-14 1999/12/15 16:55:46 (129.150.27 Note =n the preceding example, the firmware vesion BE Sun Storage Concepts 4:39 (Copyioht 2004 Sin Merosyatams, ine Al ghia Pasarved. un Barvics, Revsen 0 SUI oy. UGATIONAL SERVICES yn. sun. cominerviecisunedStbiege Airey. inaware Verifying Sun StorEdge A5x00 Disk Drive Firmware You can use the 2wcadn command to verify the firmwate revision of the disk drives, as shown in the following example. The firmware is ‘upgraded using a special program that is contained in the related clisk firmware patch. W luxadm diep Aa, £2 DEVICE PROPERTIES for disk: AA,f1 Status (Port A): OK. Vendor: SEAGATE Product 1D ST19171PCs0N9 ,0¢ {aN (Node 20000020370d336£ Wine Port_A} : 21000020370a336¢ Revisions ae Serial Num: 981259750 Unformatted Capacity: 8637.338 MByte Read Cache: Enabled Minimm prefetch: 0x0 Maximan prefetch: Ox£Eft Location: In siot 1 in the Front of the enclosure named: AAA Path(s): /dev/rdsk/c2tidds2 /devices/pcies,4900/sunu, ifp@s/sedew21000020370d336£ , 0:c,rew Jn the preceding example, the disk drive firmware revision is 117E. Note ~ You can also use the format utility’s Enquiry command opiion to verify firmware revisions in selected disk driv Soe eine ee Su RSC GV 140) VERITAS Volume Manager 4.0 Administration [Sebytgh 2008 Sun Mrcayters, re. A Rh Reserved. Sun Sances Raven D BHI so eousnors ences wavy sun comiservice/suned @ ® ® ie e 6 ® e e es e e ® e e @ @ ® ® ® o e o e o @ @ @ @ ° e ® @ ® o e 6 8 ® ® @>o-¢-6-© Storage Array Firmware Firmware Upgrade Best Practices Updating storage array firmware can be a complex task. There are strict dependency rules and procedures that must be followed or permanent Gamage to interface cards can result. Check with your Sun field representative before attempting any firmware updates. The most current Versions of firmware are available through software patches 7 K requirements that should read all firmware-related patch README notes carefully. The ‘ADME notes frequently have specific warnings and procedure an help prevent extended s: stem. downtime In some cases, permanent HBA damage can result if you try to upprade firmware from an old version to a new version. Review the patch README notes for instructions informing, you to first perform an upgrade to an intermediate revision level. You should always idle your system when upgrading storage-related firmware. Usually, the firmware patch README notes will instruct you to place all systems attached to the storage in single-user mode Ask for help if you are not sure how to proceed Sun Storage Concepts 141 ‘Copyright 2004 Sun Mlroayatms Ine. Al Righia Reserved, Sun Services. Revision D www sun convservice/sunedExercise: Recording Your Storage Configuration Exercise: Recording Your Storage Configuration In this exercise, you complete the following tasks: Review Sun storage features Identify host adapter configurations Identify storage array configurations Verify storage interface firmware revisions Verify array disk drive firmware revisions Preparation Ask your instructor to identify the system and storage that is assigned for your use during this exercise. Task 1 — Reviewing Sun Storage Features 142 Sun Answer the Jollowing questions concerning the general features of Sun storage devices and tools, 1, List at Jeast four major administration tasks associated with VxVM. a. Multi-initiated SCSI b. Dynamic Multipathing Multihost fiber-optic d. Multi-level sequencing VERITAS Volume Manager 4.0 Administation Which of the following are not related to multihost storage access? Copyright 200¢Sua Merenysens, nc AB Rights Rasorved, Sun Serveas Revision D WN EDUCATIONAL SERVICES wew.siin,com/servicw/suned___ Exercise: Recording Your Storage Configuration 3. List four software applications that can be used fo configure multipath storage. | Se ee | ee en el I 4 List two applications that are used to administer contruller-based RAID storage It ae ee Which of the following tools assist with swapping out a failed disk drive? ! : a. vxdiskunsetup Db. vxdiskadm |/° © vxdiok it di. vxdet1 ! 6 e luadm, | |e 6. Which of the following apply to traditional SCSI interfaces? e a. They are SAN compatible. e b. They transfer data in parallel le © You can altach up to four hosts to a single storage unit. d. Maximum data transfer speed is currently 40-Mbytes/sec | . 7. What is the main advantage of differential SCSI interfaces? i f ae Sa ‘Sun Storage Concepts 443, ‘Gopyront 2004 Sin Mcrouyatme, ne Al igh Reserved. Sun Services, Ravan D & Sun Ww. 3un.comiservice/atinedExercise: Recording Your Storage Configuration 8. What is the primary reason for using SAN? 9. What SAN feature isolates data resource from general access? Access control lists (ACL) b. Partitioning © Zoning d. Segmentation €. Isolation protocol 10. What is the primary SAN data transfer mechanism? a. Packe b. Bitmaps Groups id. Frames Task 2 — Identifying Host Adapter Configurations Perform the following steps to determine the controller nuribers of the HBA cards in your classroom system, 1. _ Record the model number of your classroom system. Determine this by visual inspection and the uname -a command. Record the controller numbers of each HBA on your classroom system, Either inspect the /dev/dsk directory contents or use the fornat utility to examine your system. 1 VERITAS Volume Manager 4.0 Administration Copyright 200 Sn Merona ne AN Reserv. Sin Shrew Flea SUN sss corcsnone. seav www sun.com/servies/sunadExercise: Recording Your Storage Configuration Task 3 — Identifying Storage Array Configurations Each of the following sections is dedicated to a particular storage array / model and describes the most useful methods of gathering more specific | storage atray information, | 3 Before proceeding with this task, record the type of storage arrays attached to your classroom system and how many of each type there are Determine this by visual inspection q é ‘Type of Storage Arrays Number of Each 'lype a __ — | —— — ¢ it —— = /|< SPARCstorage Array 100 and Sun StorEdge A5x00 Array Use the luxadn utility to determine very specific information about both © of these storage devices. The most commonly used commands are’ # luxadm probe j # luxedn display controller number @ # luxadm display enclosure name | le # lueadn display logical pach # lweadn display enclosure name, disk location @ 4 lumadn fcode download -p ie For each storage array, record the WWN, the enclosure name Ce (Sun StorEdge A5x00 array only), the number of disks present, and the o controller number. | i WWN Enclosure Number of Controller e (12 or 16 digits) Name Disks Installed Number © ————— — a \ G = a’ eel if Note = For the Sun StorEdge A500 array, the WWN of the enclosure is § nol used in the physical path. You must use 1uxadn display command @ y to determine the WWN of the Sun StorEdge A5x00 units, naceecssen 145 ¢ Cet St en Merona na ALR enna son 9 IExercise: Recording Your St ‘Configuration Sun StorEdge D1000 Array The Luxadm utility does not recognize the Sun StorEdge 01000 array. Specific array information must be gathored using other tocls such as the format utility and visual identification. Use the format. utility to determine the controller number of each Sun StorEdge D1000 HBA card and the number of disks in each storage unit. Controller Number Array Number of Disks Task 4 — Verifying Storage Interface Firmware Revisions Use the luxadmn utility to determine the firmware revision levels of your room system storage interface components. 1. Record the firmware revision of each HBA card. Controller Number Host Adapter Firmware Revision Record the firmware revision of each SPARCstorage Array 100 controller board or Sun StorEdge A5x00 interface board. Controller Number Array Controlier/IB Finnware Revision 146 VERITAS Volume Managar 4.0 Administration ‘Copyright 2004 Sue Mecorysis, ie Al Figs Resereed. Sun Sw vies. ReienExercise: Recording Your Storage Configuration Task 5 — Verifying Array Disk Drive Firmware Revisions Use the 1uxacin utility or the format utility to determine the firmware revisions of your classroom storage artay disk drives. Record the firmware revision of at least one Sun StorEdge A5x00 disk drive if you have this array model. Controller Number Disk Drive Firmware Revision Sun Storage Concepts 15h ‘Copyright 2004 Sin Mierayalama. ne AT Rights Rasarved. Sun Services, RevisionExercise Summary Exercise Summary BY 148 Sin Discuss ° VERITAS Volume Manager 4.0 Administration Copyriit 2004 Sin Meresyatms In. Al igs Reserved. Sun Services, Reson 0 Experiences Interpretations Conclusions Applications n~ Take a few minutes to discuss what experiences, issues, or discoveries you had during the lab exercises. servios/suned22-2 Module 2 2.0.9.9 Objectives ©0600 0 Managing Data Upon completion of this module, you should be able to: ¢ List the advantages of using virtual disk management © Describe standard RAID terminology List the common features of each supported RAID level including: Concatenation - RAID 0 Striping - RAID O Mirroring ~ RAID 1 Mirrored Stripe - RAID 0-+1 Mirrored Concatenation — RAID 0+1 Striped Mirror - RAID 140 Concatenated Mirror ~ RAID 1+0 Striping with distributed parity - RAID 5 fe Describe the optimum hardware configuration for each supported RAID level Ccomyrh.2004 Sun Mleronyaama Ine. A Rights Reseed Sun Srvcas, RevisionVirtual Disk Management Virtual Disk Management Setvers today must meet high standards in the are: Performance, scalability, and maintainability of availability, Availability YAVM provides availability improvements in this area in the follo ways: ° Preventing failed disk drives from making data unavailable The probability of a single disk drive failure increases with the number of disk drives on a system. Date redundan Prevent failed disk drives from making data unave © Allowing file systems to grow while they are in use Allowing file systems to grow while they aré in uso reduces the system downtime and eases the system administration burden, * Allowing multipte-host configurations {na dual-host configuration, one host can take over disk drive franagement for another failed host. This configuration prevenis a failed host from making data unavailable. Performance Many applications today require high data throughput levels. The VaVM products can assist in this area by more efficiently balancing the 1/0 loed across disk drives. VERITAS Volume Manager 4.0 Administration ony 2008 Son Miczoaratems Ine At Rights Reserve Son Sarvces,RevionD ‘wnny.2un.com/serviceisuned @e6e0e @eee¢ eVirtual Disk Management Scalability Traditionally, file system size has been limited to the size of a single disk drive. Using VxVM techniques, you can create file systems that consist of many disk drives. The fect that there are multiple disk drives is transparent to all applications. The size limit of file systems is increased to the UNIX limit of 1 terabyte (Tbyte) Note = The size of a single file is limited to approximately 800 gigabytes: Y) (Gbytes) because of the space required {or file system overhead. Maintainability ‘Administering large installations can be much easier with the assistance designed tools. VxVM has both graphical and command-line tools administrators. 1 administration tool is called VERITAS Enterprise VxVM's graphi A offers complete management assistance for all Administrator (VEA). VI functions. xVM also has a number of command:-line programs and utilities that are useful and are preferred by many administrators. They can also be used in chell programs to perform virtually all administration tasks. Menaging Date 23 Cepyagnt 2004 Bun Meroayatem, ne Al ghia Ranarved, Bun Berean, Revision SUM 5. cose L SERVICES www.sun.cam/savice/sunedRAID Technology introduction RAID Technology Introduction The RAID concept was introduced at the University of California at Berkeley in 1987 by David Patterson, Garth Gibson, and Randy Katz, Their Boal was to show that RAID could be made to achiene performance Gimparable to or higher than the available performance on single, large expensive disk drives of the day. During the development phase of the project, it was determined thatit dak aa tannty 10 provide redundancy to avoid data loss due to frequent disk drive failures. This aspect of the project became of great importance to the future of RAID, Supported RAID Standards Many RAID levels are technologically possible but are not commonly used: The complete list of RAID levels includes: * RAID 0 - Striping or concatenation © RAID 1 ~ Mirroring * RAID O+1 ~ Mirroring plus concatenation or striping * RAID 1+0~ Concatenation or striping plus mirroring, © RAID 2—Hamming code correction * RAID 3-Striping with dedicated parity * RAID 4—Independent reads and writes © RAID 5 ~Striping with distributed parity © RAID 6~RAID 5 with a second parity calculation Note - RAID levels 23,4, and are not available with VxVM. They are Range nmonly implemented in commercial applications. RAID Ort aut RAID 140 are not true RAID levels but are abstractions composed of more than one RAID level. VERITAS Volume Manager 4.0 Administration \CoPyrih 2004 Sin Nicroayatams. Ine AS Right Reserve Syn Servees RevscnD V EOUGATIONAL SE} vay stin.com/service/suned ee eoRAID Technology Introduction RAID Terminology In the explanation of RAID levels in the following pages, a number of technical torms are used to describe RAID structure components. The following are some of the definitions: © Stripe unit refers to a sequential group of data blocks on a single disk drive. The stripe unit size is configurable. © The terms cist drive and column are synonymous in RAID discussions Stripe width is the stripe unit size times the number of columns. «Transfer rate and 1/O per second (IOPS) are performance metrics: Transfer rate is the speed (measured in Mbytes per second) at which a system can move data through its controller. In RAID systems, read and write transfer rates can vary considerably. High transfer rates are particularly yaluable for applications that must move large amounts of data quickly, such as document imaging, data mining, or digital video applications. @ 1OPSisa measure of the ability of a storage system to handle multiple, independent 1/O requests in a certain period of time. RAID systems with high transfer rates do not always have good IOPS performance. Database and transaction processing systems are examples of applications that typically require high 1/0 rate performance. ‘Managing Cate 25 ‘Copyrant 2004 Sin Merenyutera, nc. A Righin Resor. Sun Sarviens Revlon © @ SUN UCATIONAL SERVICES rw. sun,com/senvicosuined!RAID Level Common Features RAID Level Common Features 0x section reviews the common features of the following supported RAID levels: © Coneatenation - RAID 0 © Striping - RAID © Mirroring - RAID 1 © Mirrored Stripe ~ RAID 041 © — Mirrored Coneatenation— RAID 0+1 © Striped Mirror ~ RAID 140 © Concatenated Mirror RAID 140 © Striping with distributed parity ~ RAIDS Concatenation — RAID 0 ‘The primary reason for using concatenation is to create « virtual disk drive that i larger than one physical disk drive. Concatenation obtain ‘more storage capacity by logically combining portions of two ot mone physical disk drives. Concatenation also enables you tw grow a virtual mal physical disk drive space to it. This technique does not restrict the mix of different size drives and member disk drive by concatenating ad drives can be of any size. Therefore, no storage space is lost. ‘The example in Figure 2-1 on page 2-7 shows the concatenation of three physical disk drives. Each portion of the concatenation is managed by VXxVM and is called a sulisk. A subdisk is the basic unit that VeVM ves to assemble and control all data storage areas. 26 VERITAS Volire Mansoor 0 dination Capra nooo be AR hasta nen Rr Sun es IN EDUCATIONAL SERVICES Yany.sun.comiservice/sunad @®8Se08a @ eeee eeRAID Level Common Features The array management software is responsible for taking the three physical disk drives and combining them into one virtual disk drive. This disk drive is presented to the application as a contiguous storage area —— Physical | Block Dsk1 Block 1000 = Physical | Block 1001 Asay Management Disk 2 Sofware Biock 2000, Block 3000, Physical | Block 2007 le Virtual Disk Disk 3 | Block 9000 Figure 2-1 RAID-0 Concatenated Structure aj e The term block represents a disk drive block or sector (512 bytes) of data. Advantages by The following advantages can be gained by using concatenated structures: ey © Concatenation can improve performance for random 1/O because 1O4 the data is spread over multiple disk drives. lof © One hundred percent of the disk drive capacity is available for user \enil data. £ bo e @ be ° legen - $i ‘opp 30 Ben Mirani AI Riga Powered im Bric, Ril = aPPPCCHCHOSOLOCECLLHOEHC HOES SESa RAID Level Common Features Limitations ‘The limitations of concatenated structures include: * {fyou use only concatenation, there is no redundancy. Concatenated Volumes can be mirrored to achieve redundancy. ‘* _ Concatenation is less reliable because the loss of one disk drive results in the loss of data on all disk drives, + When the disk drives are ful, the data is spread throughout all the rrembers. However, when the disk drives are not full, the last disk drives are unused, thereby lowering the use of all the drives, Striping—RAID 0 The Piitnaty reason for using striping iy to improve IOS performance pie Performance increase comes from accessing the data th parallel, Parallel access increases 1/O throughput because all disk drives in the ‘irtual device are busy most of the time servicing I/O requests. i Atay management software is responsible for making the array look {kes single virtual disk drive, Striping takes portions of multiple physical disk drives and combines them into one virtual disk drive that ic Presented to the application As shown in Figure 2-2 on page 29, the I/O stream is divided into Segments called stripe units (SUs), which are mapped across two or more physical disk drives, forming one logical storage unit. The sripe unite oe interleaved so that the combined space is made altemately fram each slice and is, in effect shuffled like a deck of cards. The stripe units ave analogous to the lanes of a freeway: 2 Vena elon users 9 nes raga Sane ees Ses nein SUN ossroscaronn semnces i a Svea baleen ts SGSCECOSEOCHHPOREHSeae @eones @ eo ©eoo RAID Level Common Features There is no data protection in this scheme and, because of the way that striping is implemented, the loss of one disk drive results in loss of data on all striped disk drives. Therefore, while this implementation improves performance, it degrades reliability si sa Physiol Dbkt 5 fray Management | Physical ray Manag Dik 2 eae SS Passe Virtual Disk Physica! Disks SU= Stripe Unit Figure2-2 RAID 0 Striped Structure Advantages The following advantages can be gained by using a striped structure: ¢_ Performance is improved for large sequential 1/O requests and for random I/O. You can optimize stripe unit size for sequential or random access. © One hundred percent of the disk drive capacity is available for data Limitations Some of the limitations of striped structures are: © There is no redundancy. «Striping is less reliable, because the loss of one disk drive results in the loss of data on alll striped disk drives. Managing Date 28 Coprisn 2204 sun Niceaytama. ne Al Rihla Reservas Sun Sarces, Revision D Pi say eoucariOn ne SERVICES ww un.comiservicw/shinesRAID Level Common Features 240 Mirroring —RAID 1 the primary reason for using mirroring is to provide a high level of availability or reliability Mirroring provides data redundancy by recording data multiple times on independent spindles. The mirrored disk drives appear as one virtual dish, Grive to the application. In the event of a physical disk drive failure, the mirror on the failed disk drive becomes unavailable, but the system Continues to operate using the unaffected mirrors. The array management software takes duplicate copies of the data located ‘on multiple physical disk drives and presents one virtual disk drive to the application, as shown in Figure 2.3. Bleck t Block 2 Blocks > eae iceks oe <= Block? Blocks Blow? aloska Block 2 Virtual D ak Block 3 Block 4 Figure2-3. RAID-1 Mirror Stricture 'n VSVM, the mirror is seen as a single logical address, bloc: 0 to n blocks in length. Because of this, VxVM does not concem itself with the format of each individual mirror. One side of the mirror can be striped, and the other side of the mirror can be concatenated. This implementation can be used if there is 2 lack of enough physical disk drives or for performance reasons. VxVM can guarantee consistent data across both sides of the mirror, no matter what the format, because it writes toa given logical block address, YERITAS Volume Menayer 4.0 Administration ‘Copyrah 2804 Sin Mercy. I, ABIES Reserved Sun Seve RvissinD sveew suin.comiservice/suned @2O0068000 56 6 Oo ooo oo 0-6 9-—0-0-0-—o RAID Level Common Features Advantages “The following advantages can be gained by using a RAID-1 mirrored structure: @ There is a fully redundant copy of the data on one or more disk drives. If the mirror resides in a storage array that is attached to a different interface board, a high level of availability can be achieved. ® Alldrives can be used for reads to improve performance. Mirroring improves read performance only in a multiuser or multitasking situation where more than one disk drive member can satisfy read requests. Conversely, if there is only a single thread reading from the volume, performance is not improved. ® You can set up three-way mirroring, but there is a performance penalty. Write performance can suffer up to 44 per mirror. nt with a three-way Limitations Some of the limitations of using a RAID-1 mirrored structure are: © Mirroring uses twice as many disk drives, which essentially doubles the cos! per Mbyte of storage space. © Mirroring degrades write performance by about 15 percent. This is substantially less than the typical RAID-5 write penalty (which can degrade as much as 70 percent). Managing Dats 244 Copy 2004 Sum Miroaelams. ne AI Rah Reserved. Sun Barvieas, Ravin D JN FOUGATIONAL SERVICE: ww sun.cominenice'siinedRAID Level Common Features 22, @ SUM oy cosckroxn senress Mirrored Stripe - RAID 0+1 ‘The primary reason for using mirrored stripe volumes is to gain the Performance offered by striping and the availability offered by mirroring. Mirrored stripe configurations are a relatively high-cost installation, but many customers consider it a worthwhile investment As shown in Figure 2-4, two drives are first striped and then mirrored. ‘The reliability is as high as with mirroring. Because the technique of Striping is also used, the performance is much better than when using just mirroring awe] S03 Management }¢—} su |_Sottware | 3 Stiping Hee Vetual Diek Figure 24 Mirrored Stripe RAID Structure VERITAS Volume Manager 4.0 Administration (Sopnight 2004 Sun Mcconye,ne. Al Right Reserve. Sun Seven, Raison ‘wrivw.2un com/service/sunedRAID Level Common Features Advantages The primary advantage of mirrored stripe volumes is spreading data across multiple disk drives (improved 1/O per second) while providing acided redundancy of the data. Limitations Some of the limitations of using a Mirrored Stripe - RAID 0+1 are: © Mirrored stripe volumes suffer the high cost of mirroring, requiring twice the disk drive space of non-redundant volumes: ©The loss of a single disk drive disables a mirror and results in the loss of redundancy. Managing Date 213. Comyngh 2004 Bun Miyata, ie, Right Reserved. un Servens, Revion DRAID Level Comaton Features Mirrored Coneatenation — RAID 0+4 ‘The primary reason for using mirrored concatenation volumes is to gain the availability offered by mirroring while maximizing storage utllizstion. Mirrored concatenation volumes can be a relatively high-cost installation, but many customers consider it a worthwhile investment As shown in Figure 2-5, two drives are first concatenated ind then mirrored for increased reliability. Because the technique ol concatenation 's used, varied storage segments of dissimilar size can be combined 10 maximize storage utilization Z mao vapenent Ma cere a re Figure 2-5 Mirrored Concatenation RAID Structure Advantages The primary advantage of mirrored concaienations is increased reliability combined with maximized storage utilization. Limitations Mirrored concatenated volumes suffer the high cost of mirroring, requiring twice the disk drive space of non-redundant volumes: VERITAS Volume Manager 4,0 Aaminstration (Cenptgh 2004 Sun Monten, re Al Pigs Reserve, SunSenvces, Revlon D ware un, com/service/sunedRAID Level Common Features Striped Mirror — RAID 1+0 Striped mirror volumes have the performance and reliability advantages of mirrored stripe volumes, but can tolerate a higher percentage of disk drive failures without data loss. Striped mirror volumes also have a quicker recovery time after a disk drive failure because only a single stripe must be resynchronized insivad of an entire mirror. As a best practice, use striped mirror volumes for large i Volumes where failure recovery time and performance are issues. As shown in Figure 2-6, the concept of striped mirrors is fundamentally different from mirrored stripes. In a striped mirror configuration, each stripe is mirrored separately. Additional internal structures called € sub-volumes (SVs) are used to implement RAID 1+0 volumes. e ‘ Spe @ [wa] Management ¢ Sofware le rari . aro | Physica Disk . os = le Priel Dik vrvatonts [| manera —f ° steno Vira Disk © — e [peso ge ees Menagemnert = be een Saad e Gea 8 Figure 2-6 Striped Mirror RAID Structure ® Note - VxVM refers to the striped mirror configuration as alayered g volume or as a Pro volume structure. @ L) volume re. if ¢ € 6 I 9 Managing Data 215 | ‘engi fun Miconaams re. ARM Rete Sum Servers. Rison 8 SUP sos cox: aceRAID Level Common Features Advantages Tiss following advantages can be gained by using a Striped Mirror ~ RAID 140 structure: * Because each stripe is mirrored separately, a larger number of disk drive failures con be tolerated without disabling the volume. Availability increases exponentially with disk drive (stripe component) count. * Striped mirror configurations have the same performance benefits of mirrored stripe volumes. Limitations Some of the limitations of using a Striped Mirror ~ RAID 140 are: * Striped mirror volumes suffer the high cost of mirroring, requiring twice the disk drive space of non-redundant volumes * A'mirror cannot be detached and used to perform an online backup, With a RAID 0+1 volume, you can detach a mirror and back it up to tape Note ~ Do not detach a volume mirror to perform online data backups. The active data is not protected by redundancy during the backup Cae ee VERTIS Wane Narege 4. fmiaraton Sen bese eae ee aarareerpodeao AS © SEU css caves Soom parienlesiaets Ce.e @ee © eRAID Level Common Features Concatenated Mirror — RAID 1+0 Concatenated mirror volumes generally have a much quicker recovery time after a disk drive failure because only a portion of the concatenation must be resynchronized (instead of an entire mirror). Asa best practice, use concatenated mirror volumes for large volumes where failure recovery time is an issue. As shown in Figure2-6, the concept of a concatenated mirror yolume is fundamentally different from a mirrored concatenation volume, In 2 concatenated mirror configuration, each part of a concatenation is mirrored separately. Boat > + Block 1009 Miror Array |__| Management Software Block 3000) Virtual Disk Figure 2-7 Concatenated Mirror RAID Structure Note — VaVM refers to the concatenated mirror configuration as a layered volume and as a Pro volume structure. Maneging Data 27 Copii sh. #004 Bun Miconylams, ne. AL Rig Reserva. Sun Services Raion © HELE, Sun * DUCATIONAL SERVICES yn sun. conver vicersunedRAID Level Common Features S SX MN Advantages faacause each portion of the concatenation is mirrored separately recovery time is much faster: Limitations Some of the limitations of using a Cor tenated Mirror ~ RAID 140 are: ® Concatenated mirror volumes sulfer the high cost of mirroring, Fequiring twice the disk drive space of non-redundant volumes * A mirror cannot be detached and used to perform an online backup, With a mirrored concatenated volu ime, you can detach a mirror and back it up to tape. Note ~ Do not detach a volume mirror whe ‘performing online data packup>, The active data isnot protected by: redundancy during the backup operation VERITAS Volume Manager4.0 Administration Copyrghi2004 Sua Mcosystems In. At Rit Reserved. Sin Sarices, Rein D 3:IN EDUCATIONAL SERV SlOPSOOOCKHHHOHLOHO GH VOEOOE SOCOKHH OS ° C©eee6e eRAID Level Com Striping With Distributed Parity— RAID 5 RAID-5 configurations can be an attractive choice for read-intensive applications that require increased data protection Three of the RAID levels introduced by the Berkeley Group have been referred to as parity RAID because they use a common data protection mechanism. RAID 3, 4, and 5 all use the concept of bit-by-bit parity to protect against data loss RAID3, 4, and 5all implement the Boolean Exclusive OR (XOR) function to compute parity. Parity is implemented bit-by-bit to corresponding stripe units of member drives, and the result is written to a corresponding parity disk drive found in RAID 3 and 4. As shown in Figure 2-8, the parity (P) is distributed throughout all the member drives in RAID 5. Disk 1 Disk2 Disk3 ‘SU=Stripe Unt nae Virtual Disk Addit onal features include: © Independent access is available to individual drives. © Data and parity are both striped across spindles. © Reads per second car: reach the disk drive rate multiplied by the number of disk drives (minus the parity disk) in a column. Managing Date 240 ‘Gopyign "004 Sun Maryse, eA Riga Renard Bus Sarvs, Revlon OSU nexcarsueRAID Level Common Features Advantages ‘Some advantages of RAID-5 volumes are: Parity protects against single disk drive failure. RAID 5 requires only one additional drive beyond those used for data. © Read performance can be similar to a RAID 0 striped volume. Limitations Some limitations of RAID-5 volumes are: © A-minimum of three disk drives are required to implement RAID 5 in VxVM. © RAIDS cannot be mirrored using VkVM. Redundancy is provicled through the parity information. © Write-intensive performance is poo= ‘Overall random 1/0 performance is dependent on the percentage of Writes. If more than 20 percent of the I/O operations are writes, consider an alternative RAID option, such as RAID 1+0, © There can ve severe performance degradation with a failed disk drive in a write-intensive environment. 220 VERITAS Volume Manager 4.0 Administration ‘Copyright 2004 Sin Micoeysems. nc AB RightsReserved. Sun Services RevisonD SUT sas scsi nenvies aonlan rereExercise: Optimizing System Configurati Exercise: Optimizing System Configurations In this exercise, you complete the following tasks: «Review software RAID features © Identify availability and performance cabling © Optimize RAID-0 volumes © Optimize RAID-1 volumes © Optimize RAIDS volumes © Optimize RAID-0+1 volumes © Optimize RAID-1+0 volumes © Identify effective storage utilization i © Select disk drives for use Preparation The first several tasks in this exercise are group discussions about optimizing hardware configurations to suit particular volume structures. The last task involves identifying and recording your VxVM server configuration and selecting six disk drives for use during the remainder of this course. You should work on VxVM servers in small groups of two or three. Each group has six disk drives with which to work. Ideally, three of the disk drives are on one array, and three are on a different array. ‘You must examine your classroom setup and determine which disk drives you are going to use. Caution - More than one group might be working on the same server. It is A essential that each group is using their own disk drives and does not accidentally reconfigure disk drives thet are being used by another group. Managing Dale 221 eeyrght 2008 Gun Miroeytams, ne. A ighis Resorind. Sun Sarees, Revision PST crn liExercise; Optimizing System Configurations Task 1 — Reviewing Software RAID Features Answer the following questions concerning the general features of software RAID administration. 1. List four major areas of concer when using software RAID products. es 2. Which of the following RAID levels are not supported by VaVM? @ RAIDO b RAIDI c RAID? d. RAIDS © RAIDS f RAIDS & RAID6 Which of the following are characteristics of a RAID-0 concatenated structure? 3: High tolerance to disk drive failures b. Maximized disk space utilization € Enhanced write performance 4. Good random read. performance ©. Data storage space is contiguous VERITAS Volurne Manager 4.0 Administration Ctoyraht 2008 Sun Micrcayeam In. Al igh Rasarves. Gu» Servic, Rien D JN EOUCATIONAL SERVICES wan sun comiserviee/auned © © 2OFSCGOOSOHHOKOKEOTROTEGHHSOC.S S©G©CSSCCE BCH © eExercise: Optimizing System Configurations 4, Which of the following are characteristics of a RAID-0 striped structure? 3. High tolerance to disk drive failures b. Maximized disk space availability Enhanced 1/0 performance d. Good random read performance fe. Data storage space is contiguous Which of the following are characteristics of a RAID-1 mirrored structure? a. Enhanced tolerance to disk drive failures b. Maximized disk space availability c. Enhanced read performance 4. Enhanced write performance e. Data storage space is contiguous 6. Which of the following are characteristics of a RAID-O+1 mirrored stripe structure? a. Enhanced tolerance to disk drive failures b. Maximized disk space availability Enhanced 1/O performance 4. Poor write performance e. Data storage space is contiguous 7. What is the size of disk drive block? Managing Data 229 Copyript 2008 Bin Miryam Ine. Al Righis Ronerved. Sin Barns, evan DExoreiso: Optimizing System Configurations 8. Which of the following are characteristics of 9 RAID-140 striped ‘mirror structure? a Ahly I. Maximized disk spp © Enhanced 1/0 performance Ud. Poor write performance to disk alrive: hares, ty © Data storage space is contiguous % Which of the folowing ary charieteristics of a RANI-S strictury? 4. Enhanced tolerance to disk drive failures b. Maximized disk space availability Enhanced 1/0 performance d. Potentially poor write performance &. Data storage space is contigue 10. What is another term for s iping? Hl. Which of the following RAID structures has the highest tolerance to disk drive failures? a. RAID O41 b. RAIDS © RAIDI 4 RAID 140 © RAIDO r 224 VERITAS Volume Manager 4.0 Administration eByPGh 2004 Sun Merorytems inc. Al Rights Resarwa. Sun Seivices,Revaien D 41 om coucarionan Seavicns wi sun convearvica/aunedExercise: Optimizing System Configurations Task 2 —|dentifying Availability and Performance Cabling | For increased performance, availability, or both, you can distribute virtual volume components across system boards, host bus adapters (HBAs), and storage array targets, as shown in Figure 2-9 Host Sysiem | [System Board [HBA System Board [HBA cd Array Array Se Figure 2-9 Availability and Performance Cabling a eee ee Discussion ~ Consider the f Mowing: SR What are the general advantages of the physical configuration shown in Figure 29? TS Managing Data Gonrighcabo4 Bun Mironyalene. ne. Al gh Reamrved Sun Services Ravin D/ 7 ] | Exercise: Optimizing System Configurations Task 3 — Optimizing RAID-0 Volumes Each of the following volume structures represent some advantage. ‘The advantage might be cost reduction, simplicity, availability, or performance. Availability, performance, or both, can be improved for some RAID structures by optimizing the physical system configuration. For some RAID structures, such as the basic concatenation or stripe shown in Figure 2-10, you can improve performance but not availability = RAD 0 (Concalenatee Figure 2-10 RAID.0 Volume Structures Discussion ~ Consider the following: 1. What hardware configurations can improve the avail: bility or performance of either structure shown in Figure 2-10? What is the ideal hardware configuration assuming there are no hardware budget limitations? we VERITAS Volume Manager 4.0 Administration Cony 2004 Sun Misys, le Aa Pugh Reserved Sun Seve. Revalen D 'N EOUGATIONAL SERVICES nvew.sun.com/servicw/euned @eeeaee 02066 @e SSCS BE2G6O6 eee e @A he ie - scise: Optimizing System Configuratiors. | l ie Task 4— Optimizing RAID-1 Volumes | » * RAID-1 volumes consist of two mirrors, as shown in Figure 2-11. Each of ; the mirrors can be a concatenation, but that does not affect the optimized rs hardware configuration | x | e RAID 1 (Mirored) | x | " | | J Subdisk 1 ‘Subdisk 1 s t t 1 Suddisk 2! 1Subddisk 2! ° [ee SY eae sSubdisk 3! 1Subdisk 3! 1Subdisk 4! 1Subdisk 4! Mirror Mirror Figure 2-11 RAID-1 Volume Structures Discussion - Consider the following: | 1. What hardware configurations can improve the availability or performance of the structure shown in Figure 2-117 What is the ideal hardware configuration assuming there are no hardware budget limitations? a ee Managing Data 227 CCounign 2004 Sun Wiroaynams. ne. Al Fights Rasarved, Sun Services RevivonDExercise: Optimizing System Configurations Task 5 — Optimizing RAID-5 Volumes RAID-5 volumes are constructed in a fashion similar to a RAID-0 striped Volume, but they have the added complication of distributed parity. A typical RAID-5 volume structure is shown in Figure 2-12. mm RAIDS Dele] Dalal] Dew | daa Party | party | Party | Party Subsiak 1 Subsisk 2 Subdsk3 Subsisk 4 Figure 2-12 RAID-5 Volume Structures Discussion — Consider the following: |. What hardware configurations can improve the availability or performance of the structure shown in Figure 2-12? What is the ideal hardware configuration assuming there are no hardware budget limiiations? Hl pliner neh e@oee eos eo eo ®eee000n &e@6 @eeoe © S64 ee e oo 6= L < K h : $ M pf 4 i M Exercise: Optimizing System Configurations Task 6 — Optimizing RAID 0+1 Volumes As shown in Figure 2-13, RAID (+1 volumes combine mirroring and striping with the mirror components above the stripes. The primary shortcoming is that the loss of any stripe disables a mirror. Mirror Micror ubk | sun 2 |subciot sf 4| Subdisk +] sunaix 2) Supa 3| suns, ¢| ee | eee as i Figure 2-13 RAID 0+1 Volume Structure Discussion ~ Consider the following performance of the structure shown in Figure 2-13? 2. What is the ideal hardware configuration assuming there are no hardware budget limitations? ER 1. What hardware configurations can improve the availability or ‘Managing Data 2.29 PERM Soc Sun Mronysame Ine. Al Rights Renard Sun Servs, RevienOcorcise: Oplimizing System Configurations Task 7 — Optimizing RAID 140 Volumes As shown in Figure 2-14, RAID 140 volumes combine striping and mirroring with the stripe components above the mirrors. If the hardware 's properly configured, a RATD 140 volume can tolerate a higher percentage of hardware failures without disabling the volurte J Le ae Micor | {Mirror | Supaisk | | subcisk | Subdsk | | subdisk | Figure2-14 RAID 1+0 Volume Structure Discussion ~ Consider the following. C SQ What hardware configurations can improve the availabili'y or Performance of the structure shown in Figure 2-14? ss Penne eameneere Saeaeee PU Apo man ere lO @ SUI ssccovssncnas steces Swanterkadeats -OPOSHKGOSHEHO GE OE 9 a o eee | | \2 | o 9Exercise: Optimizing System Configurations Task 8 — Identifying Effective Storage Utilization The storage configuration shown in Figure 2-15 is sufficient to simultaneously configure an example of every supported RAID structure. HBA ce HEA ce GA ca HBA os ‘array Oaa@d E @Oaae array ‘Array Figure 2-15 Storage Utilization Study Circle the disk drives in Figure 2-15 that you would use to build the following RAID structures: «A three-disk RAID-0 striped volume ae ee isk RATD-0 concatenated volume © A two-disk RAID-1 mirrored volume ® A four-disk RAID-5 volume (no log) 2 Atwo. © A fourdisk RAID-0+1 mirrorstripe volume » A fourcdisk RATD-1+0 stripe-mirror volume 2. Ifall the disk drives in Figure 2-15 are 9 Gbytes in size, what is the approximate data storage available for each of the structures? Managing Data 24 Coyne 2204 Sun Mizonrsies ne AA ghia Rasered. Bun Sevews. RevalonD SUM sis v0.0 www. sun.comiaeniico/s.nedExercise: Optimizing System Configurations Task 9 — Selecting Disk Drives for Use Fach workgroup must select six disk drives for use during the rest of this course. The ideal configuration of disk drives is: © Three disk drives on one storage array * Three more disk drives on a different siorage array You create and destroy disk groups and several different volume structures, so it is important that the disk drives you selea are not being used by another group. Use the following commands to select and record the logical addresses of the Six disk drives that your group chooses: © luxadm © luxadn Record the logical paths to the six disk drives for your worsgroup in the form czt3aa Di Disk: Disk: Caution ~ If there are other workgroups using the same Vs VM server you must check with them to ensure that you are not using some of their disk drives VERITAS Volume Manager 4.0 Administration ‘ory 700 Sin irate, ne Al Rights Reser. Sin Sarven, iin D SIN EDUCATIONAL SERVICES vww.siun. comivervice/suned<= eet eee eee eee Pe Exercise Summary Exercise Summary Discussion - Take a few minutes to discuss what experiences, issues, or RR discoveries you had during the lab exercises. © Experiences Interpretations © Conclusions Applications Managing Date een in iccayuwne. ne AgtRanrd Sen teriem Raven BScVERITAS Volume Manager Installation Objectives ® SUM cs -vcarions Upon completion of this module, you should be able to: «List the key elements of pre-installation planning, © Research VxVM software patch requirements © Install the VxVM software @ Initialize the VxVM software © Verify the post-installation environment © Prepare for virtual disk drive management @ _ Install the VEA client software © Use the basic VEA features © Use the VxVM error numbering system 4 ‘coprign 200 Sun Miersyatra ne Afght asrves un Barca, RowenInstallation Planning Installation Planning 32 © SUN on eouchrox seevos VaVM installations vary in size from small desktop systems to large servers with Thytes of data storage, Regardless of the system size, the installation should be carefully planned in advance System Downtime During a new installation or an upgrade, some system downtime is always required. Usually you should schedule systim downtime so that it occurs during off-peak system-usage time. Thorough pre-installation planning usually minimizes the system downtime Storage Configuration Assessment You must decide which disks should be managed by VxVM, As you further configure VxVM, you must determine the logical organization or srouping of the disk drives. For example, 10 of the disk drives should be nllocated for accounting applications, and 20 disk drives should be allocated for marketing applications, You have the option of not placing certain disk drives unde: VxVM control. This option is useful if you have applications that are currently using file systems or partitions, and you do not want to update the applications’ references to these file systems or partitions In contrast, you might want to put your system disk under VxVM control 30 that it can be mirrored. Existing data on disk drives can be encapsulated. When data is encapsulated. the partition is added to VxVM's control, leaving the partition intact and maintaining the integrity of the data. This action can be done at installation or at a later time. You might also need to plan for new disk storage devices. In addition, you might need to add more memory and larger backup tape systems to compensate for the increased storage load. ‘VERITAS Volume Manager 4.0 Administration eeyigh 2008 Sun Merona, eA Righs Reserved, Sun Services, Resicn D own sun cum/seryice/sunad © e@ege ®Seeeesenve0e ooo e@eos ecoe ©e6 e ©eS oe) a= i. te ti sO VOT PT Installation Planning Upgrade Resources Some of the most frustrating installation issues can be discovering that you ate missing a CD-ROM, discovering that you do not have the needed patches, or discovering that you have misplaced the installation Focumenis. Having all the required CD-ROMs, patches on the appropriate media, and documentation minimizes your frustration, Not only should you have the documentation (for example, release notes and installation procedures), but you should read it. Reading the installation documentation js the only way to ensure that you have all of the required patches. Licensing VxVM uses license keys to control access. If you have a SPARCstorage Array 100 or a Sun StorEdge A5100 array attached to your system, VxVM automatically configures a basic-use license. You can also Configure non-array drives connected to the same host. Other storage arrays might require manual license installations, Current System Checkpoint When installing a new and complex application, such as VxVM, you must always be prepared to return your system to its original state Backups Not only must you have backups, but you must verify them. If there is @ hardware failure or not enough space to facilitate the upgrade, you must be able to recover or beck out the software. Perform a complete backup immediately prior to the installation process. Testing the New Configuration If his is a new installation, test it prior to going into production mode. It would be idea! to test all the components, including the storage Subsystem. During this time, any tssues related to patches and firmware can be resolved. VERITAS Volume Manager installation +3 Seoyran 2004 Sun ticrnystara. Ine AL Riga Renaend, Sun Serica, Revision D @ SUN. », yeww.sun.com/servicc/suned EDUGATIONAL SERVICES:Researching Software Patches Researching Software Patches A Before installing the VxVM software, you should research any patches that might be required. Your Sun field representative can assist you. Ensure that you read all of the README notes in all of the patches. Storage-related patches can require careful attention and knowledge because they frequently must be installed in groups and in an exact sequence, Array firmware patches usually install new software drivers that are sometimes designed to work only with a small range of array firmware revisions, Caution — If the mismaich between the system software drivers and the array-resident firmware is too great, the storage arrays can become unavailable, Correcting the problem can be difficult and might require Sun support and hours of downtime. Researching Current Patch Information (Current patch information can be obtained from the external Sun Web site at http: //patchpro. sun.com From the Web site, you can use the PatchPro Interactive too! to display a customized patch listing that reflects your system configuration. You can configure a PatchPro very to include the following information: © Solaris OS release ¢ Platform type (system model) «Disk arrays and disk drives Tape libraries and tape drives © Switches and HBA models : SAN products ‘* Software versions (common applications, such as VxVM) a rr ee ee reer ete ecaee oeo SOGOK9SSSSHSSHSSGHOSGHHHOHHOHOAOHBZGOO eeeeseeodoe @Researching Software Patches Currently, the information is organized and retrieved in separate categories, such as Enterprise Systems Products and Network Storage Products. Figure 3-1 shows a typical SunSoive™ PatchPro Network Storage Products listing for the following configuration: @ Solaris 9 12/02 Operating System © Sun Fire™ V480 server © Sun StorEdge A5200 arrays © Sun StorEdge T3B arrays @ X6799A (FC100/2P) Fibre Channel interface cards [Perches lieved wath « YELLOW backdrop ae interactive ornon-atandard patches, Please rend the asvocated [READIES tor coc patch carly or inoralanon istration | ro aah ee aes |G | 2 fammeoa|tie muane |Swosss an StarBldge Trafic Manager patch 4 feaoi6-01 [Pate [README [Son0SS9: fe Patch a { 7 nena pee [aman S055 get ee a ee ee enaal posh fr Sntaris 3 Figure3-1 SunSolve Program PatchPro Information Additional patches might be required or recommended by the application vendor. VERITAS Volume Manager Installation +5 Conyrigh 2004 Sun Nernst, ne. AN Riga Renaves. Gun Boric, Rviion ©Researching Software Patches Installing Patches ‘The following is a typical patch installation scenario for the configuration shown in Figure 3-1 on page 3-5: 1. Pay close attention to the PatchPro listing Legend section and the Patch Fixes column. The order of the patches can be critical. Firmware patches must be installed with care. You must carefully study all firmware patch README notes before taking any action, especially in the following areas: © Keyword and Synopsis section © Patches Required With This Patch section * WARNING and Patch Installation Instructions sections Examine the /var/sadm/patch directory to check for patches that ‘were installed after the operating system installation, You can also use the patchadd -p command, but it displays many screens of patches that are incorporated into the currently installed operating system 3. Verify all furmware levels before attempting to install firmware patches. Verifying firmwate levels varies according to system and storage types. Older products are checked using the luxadm command. Newer products, such as the Sun StorFdge 73 array, require you to use array-resident firmware programs to verily revisicn levels. Vendor Software Patches Patches that are distributed on vendor CD-ROMs or listed in vendor documentation are usually cut of date. Do your research before starting ‘patch installation. u VERITAS Yolume Manager 4.0 Administration Copyr9h 2004 Sun Meraysioms ec. iss Rewerved. Sun Savces, Raion D ‘ Bsn, EQUATION: SERVICES nw sun com/servies/eunad ° ° 9 ° Q 2 2 8 ° 2S e 3 ° ° eo ° ° ° 9 9 2 s ® Q 2 @ e 9 @ @ 2 @ ® 2 ® ° e ® eo e @_Installing VxVM Software Installing VxVM Software With every release of VxVM, there is an installation guide that accompanies the software. This guide is a comprehensive document that defines the various scenarios for installing and upgrading current VERITAS software products, as well as the Solaris OS. Software Distribution Overview ‘The VxVM software distribution CD-ROM contains the following top-level directories: © pkgs i ee The pkgs directory contains all the software files and documentation. ¢ scripts The scripts direclory contains script files to assist you in performing VxVM upgrades. These scripts (upgrade start and uparade_finish) are referenced in the upgrade procedures in the VxVM documentation. ———_ There are other scripts (Eixsetun, fixstartup, fixmountreot, and fiseanroot) that can be used to attempt recovery from difficult boot failure situations. The use of these scripts is not documented, and they should not be used without express instructions from technical support personnel. wins2 The win32 directory contains a single disk operating system (DOS) executable, SETUP EXE, for installing the VEA client software on Microsoft Windows systems. © patches The patches directory contains any patches that were critical at the time of the product release. a ea se ee eee © release notes The release notes directory contains s:veral small Portable Document Format (PDF) and Adobe® PostScript release documents Ot VERITAS Volume Manager Installation a7 [Copyright 2004 Sun Mzrouyatet he A Righa Reserved Sun Sarvs, RaviionDInstalling VxVM Software 38 BSI sierra cerioes © support The support directory contains a group of support tools used to gather configuration information. Use these tools only under the direction of technical support personnel. Sun technical support personnel use a different information gathering tool called Explorer. © veritas_enabled ‘The veritas_enabled directory contains many library files to support a wide range of Sun and third-party storage arrays. Software Package Summary The VxVM software distribution CD-ROM contains the software packages listed in Table 3-1. Installation should be performed in the order shown, Table 31 VxVM Software Packages Package Title vRTSviic | VERITAS licensing utili veTsvem | VeVM software VxVM user documentation VxVM manual pages VEA | ice cbgui_[ VEA VeiSalloe _ | Intelligent Storage Prov: joni vetsddipr _ | Device Discovery Layer vetSwmpro | VERITAS Volume Manager Management Services | Provider veISéspro _| VERITAS File System Management Services Provider The VERITAS File System (VxFS) package. VRTSEspro, is required even if you are not going to install the VaFS software. There are several other ‘YxPS packages on the distribution CD-ROM that are not discussed in this module, VERITAS Volume Manager 4.0 Administration Copy 2004 Sun erasers ie Al Rights Rasarvet Sun Series, Rovio \wwna.sun.comiservice/sunad FOOSGBSSOHCHSSSHSSOOHHHSHOHDHOHOHO GH OO 96a eS oe S6©SeeedsaInstalling VxVM Sofware Software Package Installation You should use the pkgadd command to install the VxVM software packages. To avoid package dependency messages, install the packages in the order shown in the following example 1. Install the license package and the basic VxVM packages # pkgada -d . VRTSviic VRTSvxvm VRTSvndoc VRTSvmman 2. Install the VEA software packages and reference the custom administration file, vTSobadmin, # pkgadd -a ../acripts/vRtScbadmin -d . vRTSob ‘VRTSobgui Install the remaining VxVM software packages. # pkgadd -d . VRTSalloc VRTSddlpr VRTSvmpro VRTSfapro Note - There is an additional localization package, VETSmucb, that adds some localized VEA information in French, Iapanese, or Chinese. ‘The ‘VRTSmucb package can be added at any time if needed, VERITAS Volume Manager installation 20 ‘Copyright 2004 Sun Nieroaystena Inc Al Right Resarved Sun Serica, Rison D @ SUN, snccovce www. sun, comise-vieo/si.nesInstalling VxVM Software Software Installation User Interaction ‘Throughout the xVM software installation, you are asked questions, and some warning messages appear. The following sections summarize required interactions by software package. ‘The vRTsvlic Package Installation Questions ‘This package contains scripts which will be executed with super-user permission during the process of installing this package. De you want to continue with the installation of [y.n,?] y The vRTSvxvm Package Installation Questions Install for which version of Solaris? [9, 8, 7) default: 9): 9 ‘hie package contains scripts which will be executed with cuper-user permission during the ling this package. Do you want ocess of inue with tallation of {y,n,?] ¥ ‘The viersvndoc Package Instailation Questions (None) ‘The VRTSvmice package does not prompt for any userinput during its installation. ‘The vrTSvmnan Package Installation Questions The folloving files axe already installed on the system and are being used by ancther package: /opt/VRTS fort NRTS/man Do you vant to install these conflicting files tyn,7@) yy 310 VERITAS Volume Monager 4.0 Adminisralon Cex 204 Ser Warepons ne AIR Raed ia Sevens RrvenD & §) QP OULM sn eoucanonaL services ww sun.comiservicetsuned eecen0 @eeoee0 @ee0006 @ eoo ee eeeoa00eee@ @e000 @ eInstalling VxVM Software The vRTSob Package Installation Questions The selected base directory m before installaticn is attempted. Do you want this directory The vrTSobgui Package Installation Questions ‘The verscbgui package does not prompt for any user-input during its installation. 1 | The VRTSalloc Package Installation Questions this package contains scripts which will be executed with euper-veer permission during the process of \ installing thi the instal lat: package. Do you want to continue with of [yin.7) ¥ The vrtsddlpr Package Installation Questions pts which will be executed ing the process of > wath super-user installing this } the installation of es which will be mecuted ‘user permission during the process of to continue with ay The vRTS£Spro Package Installation Questions The following f and are being ueed by another package sot /VRTSob [y,n,?] y. At this point, the VxVM software is installed but not operational. If you feboot the system, you see at least two VxVM error messages similar to the following: VaVM NOTICE V+S-2-3347 Volume Manager not ataxted VXVM NOTICE V-5-2-3365 VawM not started Va\M Provider initialization warning: Configuration daemon is not accessible Only the vxsve daemon is running. VxVM must be initialized using the vainstall utility before it can start successfully. a2 VERITAS Volume Manager4.0 Administration ‘Conyroht 2004 Sun Wiroayateme nc Al Rights Resend. Sun Services, Revson D @ SUN csr ecneron senices wor sun comiservcefsunedInitializing VxVM Using the vxinetal1 Utility Initializing VxVM Using the vxinstall Utility “The VxVM software cannot start correctly until it has been initialized using the vinstal1 utility. In previous VxVM versions, 2 disk group named rootdg containing at least one disk drive was a mandatory Fequirement for VxVM operation. The VERITAS Volume Manager 4.0 release has eliminated that requirement. The vxinstall Utility Dialogue [Ag of this release, the vxinstal1 utility no longer calls the vid skad ulility to configure an initial disk group. As a result of the vxinstall changes and the removal of the rootdg disk group requirement, the VxVM initialization process is now greatly simplified. The following is an example of the entire dialogue i vxinatall Vx uses License keys to control access. If you have a SPARCstorage Array (SSA) controLler or a Sun Enterprise Network Array (SENA) controller attachei to your system, then VxvM will grant you a lim tne liceneo automacically. The SSA and/or SENA license grants you unrestricted use of disks attached to an SSA or SENA controller, Put Gisallows striping, SA and non-SENA disks. you are not running an SSA or SENA controller, then you must ob license key to opera tain a censing infomr: systen host ID; 80960386 ost type: SUNW,Ultra-4 SPARCstorage Arcay or Sun Ent rise \ ework Array: found Do you Wont to use enclosure based nanes for all disk: fyn.q,?] (default: 5) a Sep 3 11:38:17 ns-east-104 vadmp: NOTICE: array DISKS, datyre = Disk added disk Sep 3 11:38:17 ne-enst-104 wcnp: array 5080020000034ed8, datype - Sep 3 11:38:17 ne-east-104 vxdmp: NOTICE: array 5080020000029270, datype = SENA Sep 3 11:38:27 ne-east-108 vadnp: NOTICE: VxiM vxcmp V-5-0-34 added disk array 60020£200000¢3¢70000000000000000, datype = TS M vxdap added disk AM vxdnp ied disk VERITAS Volurn Menagor installation 313 Jerr nzose tur Merenyteme. ine Af Riga Reversed. Sn Sarvees Raion O SUM, ous, covxrn 5:0 wwvews suin.com/s6-VhInitializing VxVM Using the weinstal1 Utility Sep 3 11:38:17 ne-east-104 vacdup: NOTICE: VXVM vcmp V-5-0-34 added disk array 600204200000e1930000000000000000, datype = T3 Sep 3 11:38:26 ns-east-104 vxdmp: WARNING: VxVM vxdnp V-S-0-336 Unlicensed array S/N 60020£200000c3670000000000000000 installed Sep 3 11:38:18 ne-east-104 vxdmp: WARNING: Ve vadnp V-5-0-336 Unlicensed array $/X 60020#200000e1930000000000000000 installed Do you want to setup a system wide default disk group? (y.n.q.?1 (dafaules y) a The installation is successfully completed. Licensing Requirements The configuration used in the following example features two Sun StorEdge T3B arrays. According to the restrictions outlined in the ‘veeinatall output, an additional license must be installed, If there are no automatically licensed storage arrays attached, the vxinstall utility prompts you for a license key. SPARCStorage Array or Sun Enterprise Network Array: No errays found, No valid licenses found. MM lite/full License(s) is needed to proceed with weinstall. See VERTIAS Volume Manager Installation Guide for more details on obtaining and installing the license keys. Are you prepared to enter a license key ly,n,q) (default: yy Sater your license key : 8ZYE-KJ4R-UPQ3-DOBL-PPO3-PNTS-PRVP Note - You can also use the sd icinst utility to manually installa license 4) key at any time. a \VERITAS Ve Manager 4.0 Adnistton Cah cot Sn aptoes ac ager Pen an oAhn Re Sun. IUCATIONAL SERVICES vote. Sun corn/serview/suined @ ° @ ° e ° 9 ° ° a ° e 2 ° 9 ° ® 8 6 oO e ® 9 eo o e e 9 9 @ ° @ ® © e i) ° ° e e @Initializing VxVM Using the wcinst.all Utilly Verifying Licensed Features [After the system is initialized using the viinstall command, you verify the licensed features using the vxdct1 1icense command. Following are examples of several licensed configurations. © Example 1— The following i a system with only Sun StorEdge 'A5200 arrays attached and an automatically generated license. # vxdetl License Licensed features Mirroring Root Mirroring concatenation Disk-spanning pup (miltipath enabled) Striping (restricted to Sun Enterprise Network Array’ AIDS (restricted to Sun Enterprise Network Array) © Example 2 ~ The following is a system with only Sun StorEdge |A5200 arzays attached and with an additional manually installed license. # widet license ‘All features are available Mirroring Root Mirroring Coneatenaticn Disk-spanning stiping RAID-5 srartS) pMp (multipath enabled) eSkample 3— The following is a system with only Sun StorEdge 738 arrays attached and with a manually installed license # vadeti license All features are available: Mirroring Reot Mirroring Concatenation isk-spanning striping RAID-S vxgmertSyne DMP (mltipath enabled) VERITAS Volume Manager instalation 245 Teretzn 2004 Son eroayslers, Ine, AH Rghs Resars. Sun Services, evan UGATICNAL SERVICES waww.sun.comiserviso/sinertVxV/M Post-instellation Environment VxVM Post-Installation Environment After the VxVM software is installed and initialized, you must be familiar ‘with the general environment to be an effective administrator. VxVM System Files During VxVM installation, the following changes are made to the ‘etc/system file, and VAVM startup files are added to several of the /ete nun-level directories Changes tothe /etc/systemFile Entries are appended to the end of the /etc/aystem file to force-load various VsVM drivers, as shown in the example: * veum_START {do not renove) forcelead: drv/vxdnp forceload: dev/vxspec * vxvm_END (do not remove) | Run-Level File Additions A number of script files are added to the /ete runlevel directories to control the VxVM software when the: ‘system is booted or shut down. © /ete/zcd.d/ksoieie’ This script file stops the ISIS service daemon (ixave) associated with the VEA graphical interface when transitioning to run level 0 during a system shutdown. @ = /ete/res.d/K29vxum-vashutdown ‘This script file sends a shutdown message to VEA clients © ©/etc/re8.4/Ks0isisad This script file stops the ISIS service daemon. (vxsvc) associated with the VEA graphical interface when transitioning to the single-user runlevel 316 VERITAS Volume Manager 4.0 Administration Copy 2004 Sun Microstar, Ine. Al Rigs Reserved Sun Sevces Raison ' QSL an covtsc semen sven asaveontanie — e ° ° e o 5 9° a oO oS 9 ° ° 2° 9 ° ° ° ® forceload: drv/vxio ° o o o ® oO e 8 ® 9 e 9 ® © ® ° e ® ° e e @\VxVM Post-Installation Environment © /ete/xes.d/S28v0m-sysboot ‘This script file runs early in the boot sequence to configure the / and /usx volumes. This file also contains configurable debugging parameters, @ /etc/ves.4/S3Svxvn-startupl This script file runs after the / and /use volumes are available. It also makes other volumes available that are needed by the Solaris OS early in the Solaris OS boot sequence, such as swap and /var. © /eto/xeS.4/S8Svxum-startup2 ‘This script file starts 1/O daemons, rebuilds the /dev/vx/dsk and dev [vx/eé0k directories, imports all disk groups, and starts all Volumes that were not started earlier in the boot sequience. © /ete/xes.4/s86vxvm-reconfig This script file contains commands to execute the fsck utility on the root partition before anything else on the system executes, © /ete/re2.4/sS0isisd This script file starts the ISIS service daemon (vasve) associated with the VEA graphical interface during the system boot sequence. © /x:2.4/S94am-vxnetd Thvs script file starts the vaneta daemon if the VVR software option is installed and licensed @ /ezc/rez.a/s9svemn-r cover This script file attaches and resynchronizes plexes and starts several VxVM watch daemons, including: vxrelocd, vxeached, and vtconEigbackupd. You can also modify this file to change the defeult VxVM disk drive failure response from hot relocation to hot sparing. © /etz/re2.d/ssevradmindg ‘This script file starts the vradmind dacmon if the VERITAS Volume Replicator (VVR) software option is installed and licensed. © fet 2.0/ssévxxsyncd ‘This script file starts the veersyncd daemon if VVR is installed and licensed. | VERITAS Volume Manager Insialiation a7 Consign 2004 Sin Mernystons, Ine. Al Rights Resereed Sun Services, evanxVM Post-installation Environment System Startup Messages When the Solaris OS is booted and the Vx¥M startup files execute, several important boot messages appear. In the following example, the key messages are in bold type. Rebooting with comand: boot Boot device: disk:a File and args Sun0S Release $.9 Version Generic _112233-03 32-bit Copyright 1963-2002 Sun Microsystems, Inc. All rights reserved Use is subject to license terne VxVM sysboot INFO V-5-2-3245 Starting restore daemon... VxVM syeboot INFO V-5-2-3242 starting in boot mode. NOTICE: VxvM vxdmp V-5-0-34 added disk array DISKS, datype = Disk NOTICE: VxVM vxdmp V-5-0-34 added disk array 5080020000034ed8, datype - SENA NOTICE: VxVM vadmp V-5-0-34 added disk array 5080020000029e70, datype = SENA NOTICE: VxVM vxdmp V-5-0-34 added disk array 60020£200000c3670000000000000000, datype = T3 NOTICE: VxVM vxdmp V-5-0-34 added disk array 60020£200000c1930000000000000000, datype = 73 Hostname: no-east-104 VxVit vavm-startup2 INFO V-5-2-503 VxVM general startup... ‘The systen is coming up. Please wait NIS domain name is Bod. Bast .Sun.cOM starting rpc services: rpcbind keyserv ypbind done Setting netmask of 100 to 258.0.0.0 Setting netmask of hmeO to 255.255.255.0 Setting default IPv4 interface for mlticas ns-east-104 syslog service starting. volume nanagement start ing. The system is ready. 1 add net 224.0/4: gateway ns-east-104 console login: a ere any enna La ee od saa & SN © sym EpucAn ‘wwew.sun.com/service/suned S©OKCHSHSHOHGHOHGOHROSGGSHSSOFGCEECOHOHHHLESHLOxVM Post-Installation Environment System Startup Processes The following is an example of typical VxYM processes to help you understand how they are started during a system boot operation. 4 ps -e |grep vx PID TTY TIME QD 13? 0:04 vxconfig —_(vxconfigd) 296 2 0:05 vxave 4732 vxrelocd 507 ? vxrelocd 495.2 0:00 vanotify 509 7 0:00 vanotity 513? 0:00 vnotify 474.2 0:60 vxeached 512? 0:00 vxcached 475? 0:00 vxconfig — (vxconfigbackupd) 494? 0:00 vxeonfig — (vecanfigbackupd) The vcconfigd Daemon ‘The volume configuration daemon (vxcon!igd) is started by the /etc/rcS.d/S25vxvm-systoot script early in the boot process. This daemon must be running for the VxVM software to function The vxsve Daemon The vxsve daemon is started by the /ete/¢c2.d/S50isied script. The vxsve daemon services requests from the VEA graphical interface. The vxrelocd or vxsparecheck Daemons: One o1 these daemons is started by the S85vamm-recover script during the boot process. The vxrelscd daemons monitor for VxVM failure ‘events and relocate failed subdisks. By default, the jete/cc2.d/S95vxmm-recover script file starts the newer vxrelocd processes, which provide hot relocation. You can edit the file so that it starts the older vxeparecheck process that provides only hot sparing, VERITAS Volume Manaiger instalation 349 ( Copy 2004 Sin Merosyatoma. ne Al Rights Reserved. Sun Savices Reisen O PSU orice eves\VxVM Post-installation Environment The vanotify Daemons ‘These daemons are staried by either the vereleed or the vxeparecheck daemons. The vxnct fy daemons display events related to disk and configuration changes, as managed by the VxVM configuration daemon, veconfigh The vxcached Daemons The vxcached daemons manage cache volumes associated with space-optimized snapshots. Cache space is added when needed. The vxconfigbackupa Daemons ‘The vxconfigbackupd daemons are started by the etc/r02.d/S98veum-recover script. These daemons reco! any VkYM disk group configuration changes in the /etc/vx/ebr/nk d rectory. The vxrecover Daemon ‘This daemon can be run by the /etc/reS.4/S35vium-startupl, /etc/x0s .a/S85vxm-startup2, or the /etc/rc2.d/S95viem-recover script files during a system boot, depending on the need for volume repair. The daemon terminates when the repair process is completed. Volume-repair needs differ depending on several variables, such as a system crash, The repair typically involves attaching plexes and resynchronizing mizrors, 3:20 ‘VERITAS Volume Manager 4.0 Administration ‘Copyrah2004 Suntticosystams. ne. AlRighis Resrvet Sun Sarces Revise D SUI os esecaronn seavees sdfashaeniemstepsing JOC SCHOKCHCHHVOHSCAHSCOCHOFCOECOOEOOLOHDOSEOSCO80System and User Executable Files BP SUP. cor eonemorse sor VxVM uses many different script and binary program files to perform management and administration functions. Many programs call other programs. Many of the script files and programs should not be directly run by a user. VxVM Software in the /opt Directory The following directories are present in the /opt directory after a standard VxVM software installation: © /opt/vets This directory contains the VxVM man pages . lopt /VRTSalloc This directory contains the VxVM storage allocation software known as Intelligent Storage Provisioning. © fopt/vR Sddipr This directory contains software to enable and disable the device discovery layer feature associated with the VEA application. i © /opt/VRTSfspro This directory contains VxFS registry information tised by the vxeve | daemon © fopt/VRTSob This directory contains the client and server software. © /opt/VRTSLic This directory contains VxVM license installation and verification programs © /cpt/vRTSvmpro ‘This directory contains VxVM registry information used by the vasve daemon. © opt /VRTS vam: This directory contains library files for a DMP plug-in. © /opt, RIS “This directory contains the VERITAS techni manu. VERITAS Volume Manager instalation 321 CConyright 2008 Su Wleroayatoms Ie. AU Rghis Reserves. Sue Seviews RevisnnVaVM Post-Installation Environment a2 SS: ,, VxVM Software in the /usr/sbin| Directory Although there are many VxVM program files in the /usr/ebin directory, only a few are commonly used. They include vxassist, vxstat, vxinto, vexprint, vatask, vxinstall, vxdg, vxdisk, and yxdiskadm # la /usr/ebin/vae xadn vadiskpr —vxpool vxatat vrassist vedmpadn — vxprint vxtask vxcache vaedit —_varecover vxtemplate yxchust vxemport varecover. wrap vxtrace vxondlog vxibe verelayout vatranslog veconfigd xeinfo —vmelink vxtune vxdeo vxinatall vxcaync vauser-enplate vader vxied vag vexvol vxddladn wowke — vxscriptleg —vxvoladn vxdg vomenstat vxed vavoladneask vxdisk vomend —vxsnap vevaee vxdiskadd = omerd—vxap widiskadn — vomotify yxopeshow vudiskeonfig vaplex yxstart_wr VxVM Software in the /etc/vx/bin Directory ‘The script and program files in the /etc/vx/bin directory ste called by higher-level user commands and are not commonly used directly. # 1s /etc/vx/bin egettxt vackdisken wedytoc vaxSvrfy stztovott vxeluat adn weeprom vazeattach uget txct vxelustipe mencap varelocd vashutdow © yxcntrllist —_vxevac. varesize vxaskchk YxconEigbackup vxldiskend vxroot vaapslice vxconfigbackupd wmirror —_vxrootmir vebadexcld vxconfigrestore wmksdpart vxelicer vebaddxcld — vxconvarrayinfo wmewdmame vxspare vabootdetup — vxoxcld vaparts vusparechecc vxcached vadarestore vapartadd —_vsplitlines vecap-part —vxdevlist vepartinfo vxswapct] vxcap-vol vdevpromm wartra —uxtaginfo vacdsconvert vxdisksetup © vgartrmall waunreloc ‘vecheckda vediskunsetup wertvtce — vmunroot vechkeundey wedxeld vorScheck VERITAS Volume Manager4.0 Administration Cerri 2008 Su Micreoyates, In All Rights Reserved. Sun Bavice, ison UPATIONAL SERVICES YHTSOSOVASTSSHOKBSHSSSCOCEBOHGOGOHORAGE DCE oe @xVM Post-installation Environment Verifying Initial Disk Drive Status After a fresh VxVM installation, you should immediately assess the ‘current disk storage status. You should carefully research any existing file systems before initiating encapsulation or initialization operations. “The vadisk utility shows the current VxVM status of all disks drives attached to the system. 4 vxdisk list Device ‘TPE DISK e0t0d0s2 —autoznone online invalid cOtidos2 aut o:ncnie : online invalid catidos2 none 2 online invalid c2t3dds2 —auto:none- online invalid c2tsd0s2 —auto:none online invalid catisdoe2 _auitornone testdg0i testdg online fad!” catiadds? aute:none - online invalid c2tz0dde2 auto:none : online invalid | c2tzad0s2 auto:none - : online invalid 33260: auto:none — - 5 online invalid e3t33d0s2 autos) ced - enline r c3r3sd0s2 auto:none- online invalid e3t37d0s2 © auto:none | - online invalid c3tsad0s2 —auto:none online invalid e3t82d082 auto:none - - online invali catii0s2 —auto:none 5 enline invalid 3d0s2 -auto:none online invalid Disks that show astatus of online invalid arenot under VxVM control. Disks that show a status of on! ine have been initialized, but are not assigned to a disk group. When online disks are added to a disk group, they are assigned a name which appears in the DISK column. By default, the clisk name is derived from the name of the disk group. ee What is not evident is that slice 7 of the disk c2t16d0 is mounted witha ystem. You must plan for all existing data before proceeding with Grive encapsulation or initialization. , 4 0 Oe 5 Mdes hase eh Crantle > M 4 VERITAS Volume Maneger instalation 323 ‘Seprrign 2004 Son Weryatens ne AI Riga Reserved, SunServees Revision D SUD on: cwrceronns servePreparing fot VVM Disk Drive Management Preparing for VxVM Disk Drive Management Disk drives can be placed under VxVM software control in two. fundamentally different ways, If a disk drive has existing file systems, VxVM will promp! you to encapsulate the disk, thereby preserving any existing data. An alternate method of placing disks under VxVM control 4s to initialize the disk drive, which destroys existing data. You configure special files to protect specific storage devices from inadvertent use by V)Preparing for VxVM Disk Di Management +teeG Disk Drive Encapsulation Process When any disk drive is encapsulated by VxVM, existing file systems are preserved and a small portion of the disk drive is used for VkVM. overhead. If the disk drive is the system boot disk, VxVM is aware of this distinction and takes special care to preserve all data. Generally, you do not encapsulate disk drives with existing data unless you want to increase availability or performance of the data through the use of software RAID structures tem) When a disk with existing data structures (such as a mounted file s is encapsulated, VxVM analyzes the disk structure and takes meastires preserve all existing data and the disk partition map found on block zero. Disk Drive Before Encapsulation d mount information of a The following shows the partition map Solaris OS disk drive with a mounted file system. For clarity, some output is omitted, # prtvtoc /dev/rdsk/cztisd0s2 First sn Tag Flags Sector t Mount tor Directory Partiti 5 a 0 nn) # nore /etc/vfstab |gvep Test | (dev /ask/e2tisdde? /dev/xdsk/c2t1éd0e? /Test ufs 2 yes - a 4 VERITAS Volume Manager Installation $27 Copyright 2004 Sun eronytars Ine, AB Rights Reser Sun Services Revision @ SUN, sux evcasePreparing for VxVM Disk Drive Management 3.28 & Sim Disk Drive After Encapsulation After encapsulation, using a VxVM utility such as vxdiscadm the disk’s partition map and mount information are modified as shown in the following example. # prtvtce /dev/rdek/c2tisdea First Sector Last ~— Mount. Partition Tag Flags Sector Count Sector Directory 17682084 17682093 4 17682084 17662033 15 01 17674902 7162 17682083 4} more /etc/vtstab |grep Test Gev/ve/dsk/testdg/Test /dev/vx/rdsk/testdg/Test Te ufa 2 yes - Test (/Test) encapsiilated partition c2t16dos7 VERITAS Volume Manager 4.9 Administration ‘Coppigh 2004 Sun Mlexoayin, We. Aight Resarve. Si Services, Rion D www sun.com/service/suned Ceoee ec SCSCSCSOeOeoeaoo000¢g90 e68e ©0000 066 eeo0o0d @Preparing for VxVM Disk Drive Management Protecting Storage Devices From Usage Before initializing or encapsulating storage devices, you can automatically exclude storage devices from VxVM use using two different methods. Depending on which method you use, the effects range from limited exclusion to total exclusion. The exclusion files prevent the vxciskadn utility and the VEA GUI from using the excluded devices. | Determining the VERITAS Storage Types Although the format utility displays all known storage devices, you must use the vxcimpadm commnand as shown to display the storage types and enclosure names for use in device exclusion. Wi vedmpadm 1etctlz all CTLR-NAME, ENCLR-TYPE 0 Disk cy SENA 3 SENA ca np 8 B 4) vadmpadn lielenclosure al ENCLR_NAME ENCLR TYPE ENCLR_GNO sTaTUS Disk Disk DISKS CONNECTED SENAO SENA 5080020000034ede CONNECTED SENAL SEMA 5080020000029e70 730 13 60020£200000¢3670000 71 73 60920£200000C1930000 CONNECTED =~ ‘The controller names (CTLR-NANE) and enclosure names (= used in tie appropriate exclude files. (CLR-NAME) are: The disk array type field (Gatype) displayed during the system boot process equates to the ENCLR_TYPE field displayed in the output of the yadmpeda command. VERITAS Velume Mansger Installation 329 Copyright 2004 Sun Meroayaama, ne AlRighs Renard. Sun Services, Revsicn D ® Sun HVICES wives sun.comise ‘iPreparing for VxVM Disk Drive Management Limited Exclusion You can exclude enclosure, controllers, or devices from us? by the veinetall and vxdi skedn utilities by manually modifying three special files in the /etc/vx directory. The following describes the three files and an explanation of their intent. © enclr exclude Each line of the enclr exclude file specifics an enclosure to be excluded, for example, sena2. © cntrls.exclude Each line of the cntris.exclude file specifies the address of a controller to exclude, for example, c2, © disks exclude Each line of the diske. exclude file specifies a disk drive to exclude, for example, cov3do. Caution — The three manual exclusion files do not preven: other Va commands from seeing and operating on the storage devices. You can still see and perform operations on all the devices using VxVM commands, such ig, vadisk, vxdisksetup, and vxassist. The manual exclusion files are used to protect specific storage devices from being initialized or encapsulated after an initial software installation. The exclusion files are also useful to protect specific SAN storage devices. You can remove or rename the manual exclusion files after you complete the initialization or encapsulation process. VERITAS Volume Manager 4,0 Administration ‘Conyeghi2034 Sun Microsyatams ne. Al Right Reserva. Sun Bares, Raion D yww.sun.com/service/sunad SGC COSOCHSHOSHOHCOGHSBSBEHSSEOKAEHHKELOE e SeeCeoove e ")(aes ee ee ee ee ee oe ee OSU sx cemensencen Preparing for VxVM Disk Drive Mai Manual Exclusion File Formats The following example shows the format using each of the different manual exclusion files. # more /ete/vx/enclr.exclude SENAG # more /etc/vx/cntrls.exclude 4 # more /etc/vx/disks.exclude cotodo cotido In the previous example, a Sun StorEdge A500 array (SENAO) is excluded, a Sun StorEdge 13 array connected to controller ca is excluded, and two internal system disk drives are excluded If you try to initialize all attached storage using the vcdi skeen utility, you see exclusion messages similar to the following; Select disk devices to add: [,all,1iet.q, 2] all Vx INFO V-5:2-426 This disk that you specified has been excluded by the /ete/vx/cntris.exclude file: des ox/rdmp/est 14082 These: disks that you specified have been (ete, vx/disks.exclude file: g cluded by the (Mev /vx/rdmp/c0t0d082 /dev/vx/rémp/eot 14062 Theec: disks that you specified have been excluded by the fetcwx/enclr exclude file: /dev/x/rée—/SENRO_082 _ /éev/vx/xdmp/SENN0_162 /dev /ex/ rep /SENRO_262 v /as/ xdamp/SENAO_4s2 (Sev /vx/cénp/SENAO_682 VERITAS Volume Nanagor instalation 331 ‘Copyright 2004 Sun Meoaytama, ne. Al RighlsReaarine Sin Sanvices, Revision OPrepering for VeVM Disk Drive Management 342 @> SUI sy covcsrorve senvces Global Exclusion There are two additional files, /etc/vx/voem.exclude and ‘ebe/sx/edmp.exclude, that should not be manually edited, They are modified indirectly using the vxdiskadm utility option 17, Prevent multipathing/Suppress devices from VxWM’s view Storage that is suppressed using the vadiskadm utility, is removed from the view of all VxVM software. This feature is intended for complex configurations that require the coexistence of AP, DMP, and SAN devices, The following is an abbreviated example of excluding a controller from. VxVM's view using the vxciekadn utility. # vxdisk list DEVIC Tyre DISK GROUP status c0t0d0s2 _autosnone - online invalid 0t1d082 auto:none online invalid c2tad0s2 — auto:none online invalid c2t3d0s2 - online invalid c2tsdos2 - : online invalid c2tiédde2 auto:none - z online invalid e2tiados2 cOsnone — online invalid 22t20d0e2 auto:none - - online invalid c2t22dds2 auto:one - - online invalid e3t32d0s2 auto:none - - online invalid c3t33d0e2 auto:none - - online invalid e3t35d0e2 - - online invalid o3t37d052 ©3t50d062__auto:none - €3tS2d0e2 auto:none - - invalid invalid invalid catides2 © autoznone - - invalid estid0s2 © auto:none - - invalid # vediskadm Select an operation to perform: 17 Exclude Devices Nenu: VolumeManager/Diek/ExcludeDevices VxVM INFO V-5-2-1239 VERITAS Volume Manager 4.0 Administration ‘Conyigh 200484 Meroryaiams Inc Al Rigs Rasarvad. Sun Services Reiion 0 vow: sun.comiservice/suned SCeCeCeod Ode eeoeod e S9SCOGHCOHOHHOHGHHOBHSOHE HOHE |ePreparing for VxVM Disk Drive Management This operation might 1éad to sone devices being cuppresced from Vavt's view or prevent then from being miltipathed by vxdmp (This operation can be reversed using the vxdiskacm command) Do you want to continue ? y,nyq.?) (default: y) ¥ Volume Manager Device Operations Nenu: VolumeWanager /Disk/BxcludeDevices Suppress all paths through a controller from|VxVM's view Suppress a path from VxvM's view Suppress disks from VxWM's view by specifying a VID:PID Suppress all bat one paths to a disk Prevent miltipathing of all dieks on a controller by Vx\W Prevent miltipathing of a disk by VxvM Prevent multipathing of disks by specifying a VID: List currently suppressed/non-multipathed devices 1D Select an operation to perform: 2 Excluce controllers from VxVi Mera; VolumeManager /Disk/BxeludeDevices/CTLR-VKWM Use this operation to exclude all paths throuch a controller fron vat. ter @ controller nate [,all,list,1ist- exeluce,4,2] 24 All paths to the following enclosures through controller cf will be hidden from VxWM as a result of this operation: T30 Continue operation? [y,n,q.2] (default: y) y Sep 11 14:21:57 ns-east-104 vad: NOTICE: WWM vxdmp V-5- 0-110 disabled controller /pcias, 4000/pcies/SUNH,alce4/fp@0,0 connected to €0020£200000¢36700000000 90900000 VAM NOTICE v-5-2-2323 ‘The controller c4 will be disabled. Th on contzoller cf will still be visible through vxvi utilities in a disabled state a reboot. After a reboot these entries will not be seen. k array VERITAS Volume Manager instaliaton 333 ‘Copyright 2004 Sun Ulcoujlama, nc. Al ght Reserve. Sun Services, Raison 0| Prepering for VkVM Disk Drive Management 4 reboot f vadisk list DEVICE croup sTAtUS cot odos2 - online invalid e6ridos2 - online invalid e2tades2 - online invalid c2u3dosz - online invalid c2tSdos2 auto:mone - = online invalid ©2t16d0s2 auto:one - - online invalid e2tiedds? auto:none - - online invalid ©2€20d0s2 auto:none - - online invalid c2tzados2 - - online invalid e3t32d0s2 autornone - - online invalid ©3t33d0s2 auto:none - = online invalid ¢3t35d0s2 auto:none - = online invalid ©3t37d0e2 auto:nene online invalid ©3850d062 auto:none - online invalid e3t52d0sz auto:none - - online invalid eSt1d0s2 © auto:none - - online invalid # mote /ete/vx/vevm.exclude exclude _all 0 paths fi controllers C4 /pclas, 4000/pciss /SUNH, qloet/Epe0, 0 # product # pathgroups # Note - The format utility stil sees the ca controller and can use normally. VERITAS Volume Manager 4.0 Adminstration (Copyront 2004 Sur Miorysioms Ine. Righs Rosarvad un Service, Revlon D SUN EDUCATIONAL SERVICES \wirw sun com/service/euned ° ° @ 9° ° 3 ° ® ® ® e o o 9 ° ° ° ° 6 o e 9 e o e o bo) 2 2 ° ° ® © 2 6 ® ® eo e 6Installing the VEA Installing the VEA The VEA software is composed of server and client software. The server software must reside on the VxVM server. The client software can be installed on the VxVM server, but it can also be installed on one or more remote administration systems. a -al VxVM administrative interface. ‘The VEA software is a graphi ‘As shown in Figure 3-3, you can use the VEA client spftware to: © Run the client software remotely on an administration system © Run the client software on the VxVM server and display the VEA GUI locally Run the client software on the VxVM server and display the VEA_ GUI remotely Remote System |_YM Server ial (ase) « Monitor) | 7 4 1 i e a 4 4 + | HN Disk Groups. Veumes Figure 3-3. VEA Server/Client Relatios “To remotely display an application, you set the local DISeLAY variable to point to.a remote system: setenv DISPLAY 129,148.152.93:0.0 238 VERITAS Volvme Mar Copyigh 2004 Sun Mironyatoma ne. ANFoghta Reserves. Sun Services Reicn ©| Instaling the VEA VEA Software Initialization The VEA GUL is a Java™ technology application that can be run locally on the VxVM server or remotely on any networked system. The VEA client software can run in any Java runtime environment. VEA Software Package installation The YRTSob and VETSobgui packages are both installed on the VxVM server, which includes the VEA client interface and the VEA server ! software. You can start the client software on the server. However, the VEA client software package, VRTSobgui, is more commonly installed on 4 remote administration workstation, VEA Server Software Startup The VEA server software daemon, vxsve, is automatically started at boot time by the /ete/re2.4/S80isied script You can manually stop and start the VEA server software on the VxVM server using the /etc/init.d/isisd stop(or start) command options. /ept /VetSob/bin/vxave program directly Table 3-2 The /opt/VRTSob/bin/vxsve Program Options ! | Table 3-2 shows the options you can use to control the | Option | Function +k Shuts down the vxsve daemon. -0 ‘Retums the current VEA service state. Prints the version of the VEA service. Specifies the registry file to be used, Disables client connection authentication. Starts the wesve daemon in the foreground for debugging. as varia lacie sie ut Seana Re Hi pros tnene llr nonrere ON ONY & Sun SUN FRUGATIONAL SERVICES aww stin.con/serviee/suned — SOSSHHHHOSOHOHHGSHOHOHGHHOSEHOOHHOHHOLROHA8C DO OGInstelling the VEA VEA Client Software Startup You start the VEA client software by manually running the /opt /VRTSvnisa /bin/vmea script file. The VEA client software can be started and displayed on the server, started on the server and remotely displayed on another system, or loaded and started on a remote system. Start the VEA client software by running the /opt /VRTSob/bin/vea script file: #1 /opt/VRTSob/bin/vea & You can also use the startup options shown in Table 3-3 as needed Table 3-3. Startup Options Option | Funetion 4 Prints the version of the VEA client software. | ~a_| Starts the client software in debug mode. -8 ‘Specifies the fully qualified classname for the skin. =¢ Specifies the absolute path of the configuration file for the current skin, A GUI to ‘Specifies the frequency (in minutes) for the V check the status of the VEA server processes -cp ‘Specifies the user’s class path (for libraries) to be appended to the application's class path. =DVA2 _| Specifies the environment variable to be set pointing to the Java software directory. This option works only on Microsoft Windows. VERITAS Volume Manager installation sar Cyriht 2004 Sun Meronytars, ne. A ighis Ronarved. Sun Services, RevinonInstalling Host Connection Window When the client software starts, a Connection window, as shown in Figure 3-4, is displayed. Enter the name of the VxVM server and the appropriate authentication information. Figure 3-4 VEA Host Connection Window If you enable the Remember password feature, the next tim: you connect you select the hostname from the pull-down menu. The Username and Password fields are automatically configured. oe VERITAS Volume Mansper 40 Adminsraton Sepp caac ase be eee hacsaveaciesain @ Stn 72 EDUCRTIONAL SERVICES ‘aww sun.eom/sarview/suned e@¢ SSECOGCHSSOSSSHSHHSSSCHOGHSSOHOSHOHDORSORSGODOS ODO ©PSUM. soicve Installing the VEA Resolving Low-Bandwidth Access Problems If you need to access a VxVM server using a low-bandwidth connection, such asa dial-up modem, you must take special measures to prevent fatal connection errors. Low-Bandwidth Download Failures During the initial VEA client-to-server connection cycle, approximately 7 Mbytes of VEA plug-ins are downloaded from the VxVM server into the client $#ome/. vRTSob d'rectory. In a low-bandwidth environment, the download process commonly fails approximately 15 minutes into the process with cryptic and misleading errors such as File System Full and Jave exception errors. Lov/-Bandwidth Corrective Measures Perform the following steps to permanently eliminate low-bandwidth download failures: 1. The first time you start the VEA client software, increase the host discovery frequency from the default value of 3 minutes to approximately 45 minutes, t vea -p 45 & Inthe VEA, on the Tools menu, perforin the following steps: a, Select Preferences, and then select General b. Disable the De ete temporary files on exit feature After the first-time download, the plug-in download files remain in the $HONE/.VRTSob directory and do not need to be downloaded again. 3, _ Initiate the connection to the VxVM server. ‘The first connection might take up to 20 minutes to download the plug-in files. Subsequent connections take less than 2 minutes, Administra operations response times are acceptable even through a 56-Kbyte modem. If the connection fails while performing administrative tasks, reconnect using the toolbar Connect icon VERITAS Volume Manager installation 339 opyrigh 2008 Sur Meronysara, ne. ALRgh Reverved. Sin Servens, Raison D HONAL SERVICES www sun.com’ senvico/eunedtUsing Basic VEA Features Using Basic VEA Features Before using the VEA GUI for administrative duties, you must be familiar with the VEA components and options Main Window Functional Areas The VEA GUI has distinet functional ares 8 shown in Figure 3-5 Meny bar Tool bar inanaperani Cantata Ed neeast 104 east © jpiConroters | Object ree Gia area Message area Figure3-5 VA GUI Note ~The Actions menu entries change according to the type of objects being displayed in the grid area. Some of the toolbar icons functions also change as different objects are displayed in the grid area. 240 VERITAS Vane Mangere Adenieston een ete cloacae & Sun * © SUN EDUPATIONAL SERVICES Www sun comiservice/sunad. ®eeo0ee @eeee0ge000 eee @CSSCHCOB6 ©e6e@Using Basic VEA Features Menu Bar Functions 6 8S 8st ste rsee The menu bar in the VEA GUI has the functions shown in Figure 3-6, The Actions menu entries change according to the type of objects currently displayed in the grid area ‘The tear off menu Opens a separate window relating to the tabs in the current grid area display. The tear off feature is useful when analyzing multiple aspects of a grid area display. | rise Admint erie BUDKKVOW 42 Volume Manager Alerts Figure3-6 Menu Bar Functions VERITAS Volume Managar instalation a1 e Copyriyt 2004 Sin Mironyaera. Ine. Al Fights Meae’ves. Sun Serres, Rien © DSU snionncenn: va lamUsing Basic VEA Features 342 SUN -. Toolbar Buttons The toolbar, shown in Figure 3-7, provides direct access to general VEA functions. Some of the toolbar selections change according, fo the type of objects being displayed in the grid area, Figure3-7 Toolbar Icons All the toolbar functions are available elsewhere in menus, but the toolbar offers a convenient way to access commonly used functions, The toolbar buttons perform the following functions: © Connect to'a VEA server © Disconnect from the current VEA server Create a new volume © Create a new disk group © Search for virtual objects by criteria VERITAS Volume Manager 4.0 Administration Conran 2004 Sun Miconyatems inc Al RightsReserved. Sn Sarvews, RavionD ATIONAL SERVICES wn. Sun.com/servica/suned SSOSSSSHSHSHOOSCSCHOOHOSCHOGCSCHHSO ECVE CPCS e@eeeeod a ec 6ee —s cee TEE) a a ee) Using Basic VEA Features Object Tree Pane The object tree window, shown in Figure 3-8, has an icon for every type of VEA cbject that is referenced during VxVM administration. The objects are arranged in a hierarchy starting with VxVM servers at the top. ‘You can expand small nodes on the object tree branches to display detailed information about the node's subject [B management Console % & > fgg) Controllers @~ 5) Disk Groups > fg] Disks ¢ Enclosures g Dik @ SENAOD ig SENAY & (Qi File Systems plates gal Volumes Control Panel & Blogs © @ Network & AD History Sy Favorite Hosts Figure3-8 Object Tree Expans VERITAS Voumo Manager instalation aaa Cony! 2004 Sun MerouyBOrn, lac At Rgita Reserve Sun Servos, Rowson DUsing Basic VEA Features Grid Area Pane. When you select an object tree icon with the first mouse button, expanded configuration information about that object appears in the grid area. | The grid area display, shown in Figure 3-9, results irom selecting . Enclosure in the object tree. ‘IBM AovUISeSIaS Yes Mc? —SENAD —/pcl@B,4000Inci@S/SUNW.alc@4Np@0.9 Yes MD«2 — SENAT —_fpeiGb.4000/pci@A/SUNW.ale@5GO,9 Yes Figure3-9 Grid Awa JS SCCOSHSSHSSHSCOSHOBHOSOCHOOTFPOGOGLEOLOSCLCOOCELELSO®| 344 VERITAS Volume Manager 4.0 Administration ‘Copyright 2004 Sun Merenyatens. nc Al Rigts Reserved, Sun Serves, Raion D DUGATIONAL SERVICES, werw.-sun,com/verviee/sunedUsing Basic VEA Features Resizinc Display Panes 4 The object tree and message areas, shown in Figure 3-10, have two types of pane resizing controls: arrows for fixed size changes and a slider for variable size changes. {Qlns eas: 104 east sun com [74 © jp] Controls Disk Groups sy ey bles |g] Disk Groups Narre © gu Enclosun je) Disks. © Bl file Systems (ie Enclosures ga) Saved Quer pal File Syste fron VERITAS Enterprise Administrator mst exist Do you want this direct eated now [y.n,?,a) ¥ Using as the package base directory ## Processing package information ## Processing sys! £0) # Verifying disk space requirenents. HH Checking for conflicts with packages al #H Checking for setuid/setaid programs. This package contains scripts which will be executed w permission during the process of installing this package Do you want to continue with the installation of [y,n,7] y VERITAS Volume Manager instalation 3.58 Copy 2004 Sun Wieraystana ie, Al Righs Reserves. Sun Sarices, Revlon3-60, @ SUN seosomour servers Exercise: Configuring VxVM_ Task 6 — Starting the VEA Client Software ‘To start the VEA client software, complete the following steps: 1. Start the VEA client software on your administration system: 4 Perform the following steps in the Session Initialization window, as yea & shown in Figure 3-14: a b. «, 4. Type the VxVM server host name. Type the user name root. ‘Type the password, Ensure that the Remember password box is checked. Figure 3-14 VEA Client Initialization The VEA GU initializes after a short delay. ‘VERITAS Volume Manayer 4.0 Administration ‘Copyright 2004 Sun Mezosyuters, Ie AlFighes Reserved. Son Services. Risin D ‘eew Sun com/service/suned Ia | Exercise: Configu Task 7 — Customizing the VEA GUI Appearance Perform the following steps to customize the appearance of the 1. Click the left mouse button on the Tools menu, and then select Preferences from the pop-up menu. In the Preferences wi \dow, click the Appearance tab, i a ae Click Items and select Toolbar. Click Ieons and Te Click OK. Task 8 — Navigating the VxVM Technical Manuals 5 l ? , ‘There are several technical manuals installed in the /opt /VRTSvxvm/decs directory. Perform the following steps to examine the content of the manuals: ad 7 1, Change to the VxVM manual directory, ve # ed /opt/YRtSvxva/docs e #is pite_ag.pdf cy Co] Ld 2. View the contents of the PDF manuals using the Adobe Acrobat ° Reader (acroread) program " ‘The hypertext links and search features of the Adobe Acrobat Reader sf are useful when you are looking for specific information in the od manuals. Use the ControLF sequence to enable the Adobe Acrobat Find window. le e ‘dl VERITAS Volume Menager instalation 264 CCopyrigh 2004 Sun Mleroxyabms ie. Righa Reserved. Sin Sarin, Reviien 1 ET RIE weW suIn.cony/e*iceveLinedExercise: Configuring VxVM 3. Use the Adobe Acrobat Find feature to answer the following questions for each of the indicated VxVM technical manuals Answer the following questions for the vim _hanotes .pat VxVM manual: 1. Which Sun storage array models are supported for boot disk mirroring? ea 2, What is the mirroring configuration requirement when you upgrade T3B firmware? SS se ee ee | dL b. Answer the following questions for the vxmm_ig.paf VxVM manual: | 1. Is the Solaris OS 26 release supported by the current VaVM software? 2. When is the installvm script used? CO OOSOOCSOHEHHTAGHGOOE LEO DOODDOLOOLCEOOLOCO©C 3-42 VERITAS Voure Manager 4.0 Administration 4 Ceoyth 2004 Su ony, ne Ati Rand Sun Sane, ReaenD DS eto aces sur romnicgoei a eee ee ee ee ee __ Exercise: Configuring VxVM i Task 9 — Using the VxVM Error Numbering System Perform the following steps to research the use of the VERITAS unique error numbering system. Use the Adobe Acrobat Reader (acroxead) program to review Chapter 5, Error Messages, of the VERITAS Volume Manager Troubleshooting Guide. Answer the following questions: | elds in the error message format? 1. What are the five 2. What are the six severity levels? 3 VERITAS Volume Maragor insialation 363 ‘Gonsri 3004 Sun Hereyatena. Ine AU Rights Renarved Sun Service, Ravilon 0 D> SUI wus vovomores servers ne soorg sro HoGTe TS TTL TTS TRIE TI ET TTExercise Summary Exercise Summary Discussion ~ Take a few minutes to discuss what experiences, issues, or discoveries you had during the lab exercises. © Experiences © Interpretations © Conclusions © Applications 3.64 VERITAS Volume Manager 4.0 Administration Cope 2004 Son Microstar ALR Retard Sin Sarvews RevitonD PSHM ssn cosernens ‘anww sun.com/serviceisuned eeveeecusneone0eeoge ed: ee @2eece6000 a 2 osVERITAS Volume Manager Basic Operations Objectives Upon completion of this module, you shoukt be able to: e _ Describe the function of YxVM disk grou fe _ List disk group administrative operations ineluating e Initialize disk drives for VxVM use «Create disk groups «Add and remove disk drives for a disk group, 6 Import and deport disk groups © Destroy a disk group. Rename VxVM disk drives «Administer disk groups using the vxdiskadm uiility e Administer disk groups using command-line programs e Administer disk groups using the VEA GUI epg 2004 son ieyaama, We. ANF Reered tun Baran Reston) 4xVM Disk Group Functions VxVM Disk Group Functions A disk group is a collection of VxVM disk drives that share a common configuration. Volume structures are created within a disk group and are confined to the disk drives that are associated with that disk group. Primary Functions of a Disk Group Disk groups hav two primary functions: . ist administrative management © Provide increased data availability Easier Administration Disk groups enable you to group disk drives into logical cellections for axiministrative convenience. You can group them according to department or application, For example, you can create separate disk groups for sales, finance, and development. Increased Data Availability You can move a disk group and its components as a unit from one host machine to another. This feature provides higher availability of the data in the following ways: © Ifone system fails, another system running VxVM ca import the failed system's disk group and provide access to it. ©The first system deporis the disk group © Deporting a disk group disables access to that disk group by the first system. Another host can then import the disk group and start accessittg all the disk drives in the disk group. © The second system imports the disk group and starts accessing it. © Abvst can only import disk groups with unique names. Therefore, all disk groups on all systems should be given uniqu? names, with the exception of the rootdg disk group. VERITAS Volume Manager 4.0 Administration Comitt 2006 Bun Wironatams ne. Alfigts Reserved Sin Serica, Revlon D 4 SUN. cw enscevionse sennces yan sun comiserview/suned e@eeeeaede eeece eo @68080669686 ©\VxVM Disk Group Functions VxVM Disk Drives There are tyvo phases to bringing a physical disk drive under VxVM control. Sometimes both operations are done in one step and you are unaware that the process is more complex. When you bring a disk drive under VxVM control, you can: @ Add it toa new or existing disk group fe Add it to the free-disk pool The easiest operation is to add a disk drive to the free-disk pool. The vxdisksetup command repartitions the disk drive into VxVM format, and then a blank header is written to the disk drive. If you add a disk drive toa disk group, the disk driveis assigned 3 unique media name and it is associated with a disk group object. This information is then written into the blank header on the disk drive. Disk Drive Media Names Unless you intervene, the default media names that are assigned to disk ‘drives are based on either the disk group name or the logical device path to the disk drive. Default disk group-based media names are similer to daX02 or DGao4. The default device path-based media names assigned by some command-line programs are similar to c3t0d16s2 or e5t4d0s2, Device path-based. redia names can lead to confusing status and configuration listings. ° § i i 4 a ° . J J dl : " : J * @ 3 VERITAS Volume Manager Basic Operations 43 San zoot bun eronttens. ne, Al ghia Reserved. Sun erees SUM can carci senvers .VAM Disk Group Functions Standard VxVM Disk Groups A disk group is a collection of VkVM disk drives that share a common configuration. Typically, the disk group contains volumes that are all ‘elated in some way, sich as file system volumes that belong toa Fotticalar department or database volumes that are all tables fora single database, Fach disk group is owned by a single host system. The current ownership is «written into all configuration records. Many of the disk drives in the disk group have a copy of the configuration record, ‘A disk group and all its components can be moved as @ unit from one host system to another. Usually, both host systems are connected to the same dual-ported storage arrays. As shown in Figure 4-1, even though a second host is attached to the same storage array, access is allowed only to the current owner of the disk group. A disk group can be deported from one host and iraported by a different host, but this is generally used as an emergency solution tore satastrophic host system failure. When a disk group is imported by a lifferent host, the name of the new host is written into tie disk-based VxVM configuration records. Host t X= Host 2 The disk group A at is owned by Host 1 Storage Array Figure 4-1 VxVM Disk Group Ownership 4 VERITAS Volume Manager 4.0 Administration . Copy 204 Sun Merosystens. re. Aight Reserved Su Sarees, Revon D SUI oo. ccceanonss sernces hi stn cemancala nt\VxVM Disk Group Functions Shared VxVM Disk Groups VxVM has an optional shared disk group feature that is licensed. The shared disk group feature allows two or more host systems simultaneous access to the same disk proup. The host systems are referred to as nodes in the SunPlex system environment, Shared disk groups are used in the Sun Cluster software environment to support the ORACLE? i Real Application Clusters (RAC) database application. Multiple ORACLE 91 RAC hosts can access a single database image. As shown in Figure 4-2, shared disk groups are owned by a cluster _nameand not by the name of a single host When a shared disk group is imported by any of the attached nodes, the name of the Sun Cluster software cluster (cluste ) is written into the disk-resident VxVM configuration records, and the disk group is automatically accessible by all of the attached nodes. Hom 1—, chee The disk group is owned by 3 cluster_name ‘Sun StorEdge 45200 Array Figure 42 Shared VxVM Disk Group Ownership, Note — To prevent data corruption, all write activity must be coordinated J), between the nodes. The ORACLE 91 RAC database uses a global lock- q management scheme to eccomplish this coordination. VERITAS Volume Manager Basic Operations: 45 Contig 2004 Sun Wicosystema, Ine. A ght Reserves Sun Services RevaionDXVM Disk Group Functions 3 2 Cross-Platform Data Sharing Disk Groups A new VxVM disk group format called Cross-Platform Data Sharing (CS) allows data residing on multi-host storage arrays to be utilized by different operating systems. The CDS feature is mot licensed by Sun but, by default, disk drives are initialized in the CDS format. The new unassicn unassigned backup unassigned unassi: unagai Overriding the CDS Format Technically, the ede: = 4923 dediisk partition map allocates all disk space to slice 7 as shown in the following example Blocks {0/0/0) ° (0/0/0) 0 43GB (4924/0/0) 17682084 (o/o/o) 0 (0/0/0) a (0/0/0} 0 (o/0/0 ° -4308 — (4924/0/0) 17682084 * format does not interfere with standard Vx¥M. operation. However, if you are not comfortable using the at your site, you can disable it so that the vudiskadm utili sliced format when initializing disk drives. Before initializing or encapsulating any disk drives for VxVM use, use the yaciskadm utility option 22, change/Display the defeult disk layouts, to modify the default disk format and private region size. The changes are stored in the /etc/default /vxdisk file. Use the following file format: # more /ete/default/vxdisk format=sliced VERITAS Volume Monager 4.0 Administration (Coerigh 2084 Sus Mcroxjams, In. A RightsReserved. Sun Sarvews, Revlon FOUCATIONAL SERVICES yawwsun.com/service/suned SeSeeeveeeoseeovvevevaveVxVM Disk Group Operations VxVM Disk Group Operations a ie Basic VxVM administrative functions are those that affect disk drives and ye disk groups. The VxVM disk operations are performed using a variety of ‘ programs including command-line and graphical The following list briefly summarizes each type of disk-related operation. © Placing disk drives under VxVM control > Removing disk drives from VxVM control "6 © Adding a disk drive to a disk group i © Removing disk drives from a disk group 1° © Renaming disk drives 5 © Creating disk groups a © Destroying disk groups A © Importing disk groups B © —_Deporting disk groups ul The most commonly used tools for basic operations include ! © The vxdisksetup and vxdiskunsetup commands Sees cen | @ The wiedit commana \ q © The vidiskacm utility © The VEAGUI ar VERITAS Volume Manager Basic Operations Copyright 2008 Sun Micronystema, ne, Al Fgh Rasarved, Sun Saviden RevisionVerifying Disk Gr Verifying Disk Group Status roup Status The most commonly used disk group status commands are vxdiak and ‘yada. Command-line status is usually more efficient than using the VEA. GUI. Using the vxdisk Command to Verify Disk Group Status # vxdiek list DEVICE coroai eoria cav3dos2 c2tsacs2 c2t16d0s2 e2tiado 2820062 o2t22d0e2 e3c32d0e2 e3t33dos2 o3t35d0e2 3t37d0s2 catsodos2 o3ts2doe2 Use the following vaci.sk command to verify the status of the vxdiiskadm changes, Disks that show a status of online invalid are not under VxVM control. Disks that show a status of online have been initialized but are not assigned to a disk group. When onl ine disks are added to a disk group, they are assigned a name which appears in the DISK column. By default, the disk name is derived from the name of the disk group. TYPE, DISK croup STATUS auto:none online invalid auto:none : online invalid auto:cdsdisk aSkdgor sdga auto:sliced —_aSkdgo2 sdga auto:simple aSkdg03 sdga auto:sliced _newDG01 news auto:none eS pdga pdga pdga neve auto:sliced —- - Using the vxdg Command to Verify Disk Group Status 48 & Sun Use the following vxdg command to verify the current status and unique 1D of all active disk groups. # vxdg List NAME STATE 1D sdga enabled 1064619733. 28 ns-east-104 pdga enabled 1065123027. 40.ns-east-104 VERITAS Volume Manager 4.0 Administration Conti 2004 Sin Micosrstem, ne. ight Revered. Sen Sarco, Revion SJN EDUCATIONAL SERVICES \wnw.sun.com/service/suned SCOCHHHOHOCOSOHE OT FOCOOLHO DO LOHOOGOHOOO« e @ eaa 6 is ee ee ae a ee ee ee) Administering Disk Groups Using the vxa! Administering Disk Groups Using the vxdiskadm Utility ‘The vxdickadn utility is a Bourne shell program that provides menu-based user operations. The following example shows that when the vidi skaamn utility is started, the following menu operations are available: 4 vxdiokadm Volume Manager Support Operat: Nem: VolumeManager/Disk 1 Add or initialize one or more disks Encapsulate one or nore dis) Renove a disk Remove a disk for replacement S Replace a failed or removed disk 6 Mirror volumes on a disk 7 Move volumes from a disk 8 Enable access to (import) a OUP 9 Remove access to (deport) a disk group 10 Enable (online) a disk device Li Disable (offline) a disk device 12 Mark a disk as a opare for a disk group 13. Tum off the spare flag on a disk 14 Unrelocate subdisks back to a disk 15 Fecluds a disk from hot-relocation use 16 take a disk available for hot-relocation use 17 ieevent mitipathing/Suppress devices from VxWM's view 18 Allow miles jonsuppress devices fron VxVM's ¥ » ly suopressed/non-miltipathed devices 20 sk naming schene 21 Get the newly connected/zoned disks in Vs 22 change/Dispiey the default disk layouts 23 Mark a disk as allocator-reserved for a disk group 24 ‘hum off the allocator-reserved flag on a disk list List disk information 4 view 22 Display help about the menuing system Select an operation to perform: 2 VERITAS Volume Manager Besle Operations Ceayrg2004 Sun Mireles, ne Ai igh Reserved: Su Serves, Revision D SUI sure ssvcasonse services ae my2G Oe 3 Aeministering Disk Groups Using the vxdli kaa Utility ® Functional Overview . The title displayed when the vxdiskacin utility starts up is Volume Menager Support Operations, The vadiskadm wility performs a wide ® range of support functions, but also offers assistance in performing a e number of common administrative tasks. = The basic disk-related vxdiskadm administrative functions presented in ® this module are: = * Option 1 Add or initialize one or nore disks ‘You use this operation to add one or more disk drives to a disk group. Nou can add the selected disk drives to an existing disk grouip or to.a new disk group that is created as a past of the operation, The disk drives are assigned a default media namie baied on the ame of the intended disk group. You can override thus default disk drive name if needed. {he selected disk drives can also be initialized withou! adding them toa disk group by entering a disk group name of noni. © Option 2 encapsulate one or more disks You use this operation to bring disks under VxVM control while preserving existing data. You can also use this operation if you intend to mirmur the data for increased reliability or stripe the dats for increased performance, © Option 3 Remove a disk You use this operation to remove a disk drive from a disk group and retum it to a pool for reuse. The disk remains ina VxVM format but its media name is cleared. © Option & Enable access to a disk group ‘You use this option to place a disk group online (imports) that was previously deported (taken offline). * Option 9 Remove access to a disk group You use this option to take a disk group offline (deports). None of the disk group volume structures are available while it is deported. DOSGOSSSFCOHOSSZOHBC0S e oo @ 4-10 VERITAS Volume Manager 4.0 Administration : Compra 2004 Sun Micosratems Ine At Rohe Reserve. fun Sonica, Reveion D © SUN os eorcenorne www Sun com/serviow/suned ®LJ Administering Disk Groups Using the vxdiskacmn Utlity Creating a New Disk Group Before croating a new disk group, you must know the logical address of at least one disk drive you want to be in the disk group. You should also select media names for any disk drives you intend to add to the new dis group. You use vxdiiskadn Option 1, shown in the following example, to create a new disk group and add one or more disk drives. Select an operation to perform: 1 Select disk devices to add: [,all,list.q.?) e2tsao Which disk group legroup>,none, list.q,?] (default: roctdg) mewoe Create a new group named new0G? [y,n,q)?] (default: y) y Use a default disk name for the disk? ly,n,q,2] (default: y) y Add disk as a spare disk for new0C? [y,n,q,2] (default: n) y i Snter the desired format {cdsdisk,eliced,simple.g,?) (default: sliced) sliced Enter desired private reaion length leprivlen>.q, 2} (de: + 2048) 2048 named newcc name newDG01 spare flag ating a new disk device c2t1éd0 with Add or initialize other dis! ee Note - For clarity, many informational messages are omitted from the | case : VERITAS Volume Manager Basic Operatons ant Copyright 2004 Sun vicosyatems, rc. Fuga Renerved. Sun Serves FvisonD SILI a scsscxaul secices‘Administering Disk Groups Using the vaedi skacm Utlity Removing a Disk Drive From a Disk Group You use wed akan Option 3 to remove a disk drive from a disk group, as shown in the following example. The disk drive is placed in the free-disk pool and is still under VxVM control. Select an operation to perform: 3 Remove a disk Menu: VoluneManager/Disk/RemoveDisk Enter disk name (,1ict,q,?] newocoa xVM NOTICE V-5-2-264 Requested operation 1s to remove disk new0G03 from group nevoo, Continue with operation? fy,n,q,?] (default: y) y VAVM INFO V-5-2-268 Removal of disk nevO0G03 46 complete. Remove another disk? ly.n,q,2] (default: n) n | 412 VERITAS Volume Manager4.0 Administration ‘Copyrght2004 Sun Microsystems ne. Al Fights Reserved. Sun Sandces. Revision O ‘ SUN on eorcsvonn seances ieronscortiscasaretey eeAdministering Disk Groups Using Command-Line Programs Administering Disk Groups Using Command-Line Programs Although there are many VxVM command-line programs, only a few are necessary for the most commonly performed operations. This section describes the basic uses of the following command-line programs: © vxdiekunsetup © vxdieksetup © yxdg a ee ee Note - Only selected options for each command are described in this module. When appropriate, other options are described in later modules: Using the vxdiskunsetup Command Caution —Be careful when using the vxdi sh A destrey existing data on disk drives During the VxVM software installation and initialization, you might see error messages, such as: | up command, You can + WARNING: Disk ¢3t35d0 found ARNING © found Disk YEW: Disk ee ee SS These errors can indi cate that there are disk drives that still contai configuration re a previous installation. You can clear these disk drives and return them to an uninitialized state by using the skunsetup command, as shown in the following example fi /ete/vx/bin/vxdickunsetup -c ©2340 The vxdiskunsetup command will not clear a disk drive if the VxVM configuration records indicate itis imported by some other host. The = d ‘option forces the de-partitioning of the disk drive in such a case. The disk drives are returned to standard Solaris O5 partitioning VERITAS Volume Manager Base Operations 413 CCopyigh!2004 Sun conyers, ne Al Righs Reserved Sun Serves, Reviion D‘Administering Disk Groups Using Command-Line Programs 44 © Sue .,, Initializing Disk Drives ‘The vaeekeatup command initializes disk drives for VkVM use, but foes not add them to a disk group. The disk drives remain in a free pool for future VxVM use. A typical vxdisksetup con.mand is. 4 vxdiskeetup -i catoao Without any options, the vzdisksetup command only reparttions the Specified disk drive into the VxVM partition format. With the -1 option, VAVM configuration records are written in the private region Note — Usually, the vadisksetup command Is not used directly. Tt is called by other VxVM programs. Using the vxdg Command Although the vada command has many options, only a few are presented in this module. You have already seen how the vacdiskacin utility creates new disk groups and adds disk drives to a disk group. Ycu can also use the wedg command to perform those functions, The vxdg command ‘options related to basic disk-group administration are: © vxdg init © vxdg adddisk © -vxdg mmdisk © vxdg import © vxdg depart © yxdg destroy Note ~ You must initialize a disk drive before it canbe added to am existing disk group using the vxdg command. VERITAS Volume Manager4.0 Administration Cepygte 204 Sun Merona, oe. AL Rights Reserves. Sun Senne Ravaion LICATIONAL SERVICES wore) sun.comizervice/sunedAdministering Disk Groups Using Command-Line Programs Using the vxdg Command to Create a New Disk Group To create a new disk group using the vce command, you must furnish the disk drive logical access name (accessname) of at least one disk drive to be added to the disk group. The VxVM accessnane is essentially the logical path to the disk drive in the form: c3t4d0. You should also specily a media name for the disk drive. If you do not specify a media name, it defaults to the accessname. The following shows a typical session to initialize a new disk drive and add it to a new disk group. # vxdioe List Gove STATUS online invalid ine invalid invalid | | 1 e2tidin2 e2t3don2 invalid | eatsdan2 : invalid 2164082 autosnone : invalid €2t184)s2 —auto:none 2220482 autornone catza: auto:none eavazans2 : 63t324082 invalid 3800: : invali ©3t37d082 invalid # vedisksetup -4 c2r1d0 # vedieksetup -i ¢2t340 4 vxdg init newDG ndg-O1-e2t140 ndg-02-c2e240 # vadisk -g newDG list TYE. auto:sliced auto:slic \VERITAS Volume Manager Basic Oporations 445 ‘Cepyight 2004 Sun Meronyttrs, ne ABRights Revered Sun Services, Revaion D @PSUID sore cosy-arcnn Preteens ens‘Administering Disk Groups Using Command-Line Programs Adding and Removing Disk Drives 446 & Sun The following shows an exam them to an existing disk grou} # vadisksetup -4 e2tsdo ple of initializing two disk drives, adding ip, and then removing one of therm. # vadisksetup -i c2tlédo 4 vudg -g newDG adddink ndg-03mc2tSd0 ndg-04ec2ti6a vadiok list Type auto: t16d0e2 auto: 2t18d0s2 autor: catzodds2 auto: 224082 auto: e3t32d0s2 auto: ©3t33d0s2 auto: c3t35d0e2 auto: ©3t37d0s2 auto: c3t50d0s2 auto: c3ts2d0s2 auto: none mone iced reliced sliced sliced none none none none none none none # vadg -@ newDG mick nag-04 The removed disk drive is still initialized and is available for future use. It 's in the free-disk pool and shows a status of auto:sliced and online with no DISK or GROUP entry. VERITAS Volume Manager 4.0 Administration Cortiaht 2904 Sen Merete, me Al Rigs Reserved. Sun erices,Revion $1N EDUCATIONAL GROUP = STATIS - online i online newos Line RewOS online newG online new online - online - online - online é online online - online - online - onli invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid www eun.com/service/sunad SGeeeeeooveoe Gen 2 J© O9SSSCHSSCHHOKSSFEHOHEGESEAESHGOHOSEAdministering Disk Groups Using Command-Line Programs Importing and Deporting Disk Groups At times it is useful to deport a disk group. This function makes the disk group unavailable and irvisible to most commands. If the disk group resides on dual-ported storage arrays, a different host can import the disk group. This action is useful if a host system fails. A different host system that is running VxVM can import the disk group and make the data available again to users. The following example shows the process of deporing a disk group. 4 widg list mie saga na-east-104 newts 4 104 pag. enabled £106 ’ 4 vag deport news # vxdg list na stare edga enab ns-eaat page enabl 3027.40.ns-east-104 When a disk group is deported, the host ID stored on all disk drives in the disk group is cleared (unless a new host ID is specified with -)). Therefore, the disk group is not reimported automatically when the system is rebooted. The disk group can be deported with the host ID unchanged oF you can change the host ID to another system during the deport operation. Use the vada in example: xt command option to import a disk group again. For 4 vxdg import newnG VERITAS Volume Manager Copyighiz094 Sun MeronystIm8, a7 ! Si oasiisicanouneancseAdministering Disk Groups Using Command-Line Programs Identifying Deported Disk Groups parenthesis. # vadisk -0 allege list DEVICE TYPE Disk croup STATUS cotod auto:none online invalid coriac auto:none online invalid c2t 1dos: autoredsdisk — aSkdgoi sdga ‘online nohotuse e2t3d0e2 —auto:sliced —_aSkdg02 sdga online noketuse catsdos2 imple _aSkda03 sdga online nohotuse catisdos2 autorsliced (newoo) online c2tisdos2 - ine ine online invalid odds 3 cdsdisk pagao2 pdga online e3t33d0s2 auto:cdsdisk pdgao2 doa online ©3035d0s2 avto:cdedisk —_pdga03 pdga online cat37q0e2 auto:sliced — — (rows) online e3ts0d0s2 — auto:none = online invalid e3t52d0s2 autorsliced = — - cnline You can also use the veci.skadn utility option 8, able access to (amport) a disk sroup, to identify deported disk groups. The following is an excerpt of the resulting output. lect disk list) list group to import (,list,q,?) (defeult: GROUP new0G (id: 1065455185 .<3.ns-east-104) DEVICES: c2ti6do c3t37d0 Note = The VEA interface also displays deported disk groups, 418 VERITAS Volume Manager 4.0 Administration Conia 2004 Sun Mcronyte fe. Al ighs Reserved. Sun Servers Reviain D @ SUN sscouseou servers — vewn-sun.com/service/suned SG9SSGOGGOSSBEKCHLOD ©o0e@ SeGe0000e00e00e oo ee0e00 60oAdministering Disk Groups Using Command-Line Programs Destroying a Disk Group Before destroying a disk group, you must he absolutely sure that none of tho data on the disk drives is important, A disk group cannot be destroyed if any yoluines in the disk group are in use. You can destroy only imported disk groups. The following is an example of using the vxdg commard to destroy a disk group. ? # vadg List PY NAME STATE 1D ao railed 1068619733. 28 ne-east-104 ® ewes enabled 1065465185, 43 .ns-east-104 E aga enabled 49.ns-east-104 ° # vxdg destroy newDG ©. 4 vxdg List » Name STATE 1D sdga enabled 04 S paga enabled 04 Renaming VxVM Disk Drives When disk drives are added to a disk group, the disk drives are given standard VxVM media names, such as ga01, dga02, and dgao3. You might want to rename the disk drives in a group so that there is no confusion about their intended use. You can use the following vxedit command to rename VxVM disk drives: # vxedit -g sdga rename aSkdg01 sdga0l # vxedit -g sdga rename aSkdg02 sdga02 A mmedit -g sdga rename aSkdg03 s4ga03 Note — Volume components such as plexes and subdisks are named according to the VxVM disk media name. If you rename a disk, the plex and subdisk names do not change accordingly. It is best to rename disks before creating volume structures on them. } VERITAS Volume Manager Basic Operations 419 Copyright 2004 Bun Wicronytame ne Al pha Revered. an Bervizes, Revision © TIONAL SERAdministering Disk Groups Using the VEA GUI Administering Disk Groups Using the VEA GUI ne following section describe a series of tasks using the VEA GUL Only key points and input forms are presented. Creating a New Disk Group You can use the VEA GUI to create a new disk group. Complete the following steps: 1 {f appropriate, you can pre-select disk drives in the grid area by simultaneously pressing the Control key and mouse button. Select the New Disk Group entry from the Actions menu. 3. Complete the New Disk Group Form, as shown in Figure 4-3, Disk names default to variations of the disk group name, such as newG01 or new0co2. Default disk names are usually acceptable. mite Clot ktc hot eee es New Disk Group Wi Ss ye inci rar Hak tid aang | |e casei $e] 21200082 Figure 4-3 New Disk Group Wizard 4-20, VERITAS Volume Manager 4.0 Administration Serna earch tea teeta ateachetaro SUI on coucrvoun senvees Hee areeeaeee Cm a ee DP SUM an exnsioni serves Administering Disk Groups Using the VEA GUI Cick Next to continue. As shown in Figure 4-4, Vx¥M informs you of potentially dangerous sitvations it detects, Click on Yes to continue or No to abort ese disks nay Pe In use cztv6dDs has ale stern eee disks ate ready te be used 31379052 Figure4-4 New Disk Group Warming 5. Complete the Organization window, as shown in Figure selecting a disk group organization principle of None. SC eee mune a Organization prince Select an organization eataporize the sorage wihin the iekgroup ‘ava Minorea Snapshots Mioring over Hardware Stiped Dats and Minored Snapztiot= Hardware Mirored Disa and Haréware Sted Snap stots stipes mirrored Dats ard Stined Snapshots Figure 4-5 New Disk Group Organization VERITAS Volume Manager Basic Operations. an Gepynghi 2004 Sun terorysar, ne AD Rha Reserved Sun Sorces Avision www sun.comee-viroisinedt/Acministering Disk Groups Using the VEA GUI Adding and Removing Disk Drives [itl disks to, or remove disk drives from, a disk group, complete the following steps 1. Select the disk group in the object tree, and then click the third mouse button. lect Add Disk to Disk Group from the pop-up menu, as shown in Figure 4-6. Figure 46 Disk Groups Disk Add Menu hem 422 VERITAS Volume Manag2r4.0 Administration \Sovyrgnt 2006 Sun Mzosystems, Inc. Al Rghs Reserved. Sun Series. Rvice PS csr seentes }vwsun comiservica/sunad SC SSCCHSSSSSOSSOSSHOSSOCSCOCAOGSCOGDFO200N 99000083. Complete the Add Disk wizard form, as shown in Figure 4-7. Tiara Nees [evo Te conse VERITAS Volume Menager Basic Operations ‘Copyrgh 2004 Sun Mizrayaiea, Ine. Al Righa Resend Sin Serves, Raver D Administering Disk Groups Using the VEA GUI 423Administering Disk Groups Using the VEAGUI Deporting Disk Groups To deport a disk group, complete the following steps: 1. Select the disk group in the object tree, and then click the third mouse buiton 2. Select Deport from the pop-up menu, as shown in Figure 48. Figure 4-8 Disk Groups Deport Menu Item 3, Complete the Deport Disk Group form, as shown in Figure 4-9, Usually, you do not modify the disk group name or host system ownership during a deport operation. Figure 4-9 Deport Disk Group Form Wat ceaenl eee aera aaa Se eee ee eee Seocesceceoooceesteagveovo0000G0 GG6666 Pe© O68 e808 66Administering Disk Groups Using the VEA GUI wee Importing Disk Groups To import a disk group, complete the following steps: 1. Display Disk Groups in the grid area, and then select the deported disk group Click the third mouse button on the deported disk group and setect Import from the pop-up menu, as shown in Figure 4-10. Depart Oiek Group Recover bisk Gros Figure 4-10 Import Disk Group Menu Item 3. Complete the Import Disk Group form, as shown in Figure 4-11 Typically, the Force option is necessary only after a system crash t , f t , a t : : pea He 3 iin Disk Gi cer) oz Figure 4-11 Import Disk Group Form YERITAS Volume Manager Batic Operations 4.25 Copght 2004 Sun Mezosystons, ne AIRighs Reserved. Sun Services. Raven O ® SUM ox es.cmions. see S RyW. sun, com/servine/skinedAdministering Disk Groups Using the VEA GUI Destroying a Disk Group A disk group must be imported before it can be destroyed. To destroy a disk group, complete the following steps: 1. Select the disk group in the object tree, and then click the third mouse button. Select Destroy Disk Group from the pop-up menu, as shown in Figure 4-12. oak oom aD ekfron Disk Groupe, ‘Uparsde Disk Group Version {Undo Hot Reweation.s- Figure 4-12 Disk Group Destroy Menu If there are mounted volumes associated with the disk group, the disk group destroy operation fails, as shown in Figure 413, Figure 4-13 Destroy Disk Group Failure 128 VERITAS Volume Manager4.0 Administration Caeycht 204 Sin eresyon, eA ig Ravarved. Su ens Revi oS STD Tae Neaein pees won gun com/serviea/suned e®eoeen0eoe ®26eCSoRO80860 o@é 66666 @ © 6 <¢a ee Aaministering Disk Groups Using the VEA GUI Renaming VxVM Disk Drives To rename VkVM disk drives, complete the following steps 1, To change the media name of a VxVM disk drive, complete the following steps: a, Display the disk group disk drives in the grid area. b. Select the disk drive to be renamed, as shown in Figure 4-14 : iternal na. | Croup @caisdds2 — nag_siski nag 1 c712000s2ndg_dick2 ng > 1@ c350d0s2 _ndg_disk3 _ndg Saas LI Figure #14 Disk Drive Media Name Listing | 2, Click the third mouse button on the highlighted disk, and then select Rename from the pop-up menu. 3, Complete the Rename Disk form, as shown in Figure 4-15, Figure 415 Rename Disk Form VERITAS Volume Manager Basic Operations 427 Copy gh 2904 Bin Meresystams in ANTUghin anarved Sun Sarvices Revalen OAdministering Disk Groups Using the VEA GUI Displaying VEA Object Properties. Most VxVM objects have associated properties that detail naming schemes, construction details, and current status. ‘To display the properties of « VxVM object, complete the following ste 1. Click on the object and the third mouse button. 2. Select Properties from the object's pop: up menu. ‘The Properties of a disk group is shown in Figure 4-16, Object Properties windows can have several tabs depending on the ‘complexity of the abject. eeeeeoeooeoooon recent hein Leas f Figure 4-16 Disk Group Object Properties Form 4 VERITAS Volume Manager 4.0 Administration ‘Cav 2004 Sun Meats, ine Al Fighes Reserved, Sin Sarvs, Raion D O SUM os conrvous siemces wivw sun com/vervice/euned PC SHSHSHKSHOHSSHSOSSOGEOHOS OR HEGOHHOGE =' Exercise: Performing VxVM Basic Operations Exercise: Performing VxvM Basic Operations In this exercise, you complete the following tasks: © Review key lecture points © Verify the VxVM environment * Verify the initial disk drive status © Set the default disk drive format * Initialize disk drives Create new disk groups * View command logs © Import and deport disk groups Destroy a disk group © Rename disk drives © Use the vedi skadin utility to perform basic o 1perations (optional) © Verify ending tab status VERITAS Volume Manager Basic Operations 429 Coeyrah 2004 Sn Mlronytara re AX Rights Reserve, Bun Seven, Reisen SUE scareExercise: Performing VkVM Basic Oparations 4:30 Preparation If the tasks in this exercise are performed by small groups using disk drives residing on a central VxVM server, each group must take care to not interfere with another group's storage resources and structures. Ask your instructor to provide two unique code letters for your workgroup (A and B, C and D, E and F, and soon). Workgroup codeletters: dg ag_ Copy the logical paths to six disk drives for your work group from the information in Module 2, "Managing Data” in “Task 9 Sclecting Disk Drives for Use” on page 2-32 Disk: _ - Die —____- Dis _ Disk: = = Disk: Z Disk: Many of the tasks are performed twice. The first time using the VEA GUI and the second time using command-line programs. For most tasks, you must destroy the structures before croating them agein. Destroying and deleting structures is part of regular VxVM administrative -asks. VERITAS Volume Menager 0 Administation Copyright 2004 Sus Meronyieme. nc. Al Rights Reserved. Sun Services Raison D www-sun com/serviee/sunad — eece@ ee S00 ° @® 6 ® @686 e@eo060 ooZ Exercise: Performing VxVM Basic Operations Task 1 — Reviewing Key Lecture Points Answer the following questions about the major areas of concern during the VxVM installation and initialization process. 1. What is the primary use for a shared disk group? a. Support for load balancing b. Support for multi-host storage access c. Support for parallel databases d. Support for multipath storage access 2. Which two answers best describe the VxVM disk-drive initialization process? a. Preserves existing file systems b. Places the disk drive in a free disk poo! © Adds the disk drive toa disk group d. Destroys existing file systems 3. Which of the following commands is not used to perform disk group administration? a. vxdisk b, G a kad e vxdisksetup 4. Which of the following commands is used to rename disk drives? a. vxdg b, vxassist ._vxdisk d vxedit § VERITAS Volume Manager fasle Operations re ‘eevrgh 2004 Sun eons i Al Right Revert. Bun Services, Ration RSH os cvicon aesExercise: Performing VxVM Basic Operations Task 2— Verifying the VxVM Environment Complete the following steps to verify the environment on the VxVM_ administration system and the VxVM server: 1. Log in to the VxVM server as user root and enter the env shell command. Verify that the following environment exists on the server: PATH= /usr/sbin:/usr/bin: /opt/VRTS/bin: /opt /VRTSalloc/bi A: /opt /VRTSv1ic/bin: /opt/VaTSmpro/bin:: /ete/vx/bin MANPATHs /ust /nan: /opt /VRTS/man: /opt /VRISlic/man 3. If you are working from a remote administration system, log out of the VxVM server. +. On the remote administration system, complete the following steps: a. ‘Type the env shell command. b. Verify that the /opt/VRTS/bin and /opt /VRTSo'/bin directories are part of the PATH variable. Verity that the /opt /VRTS/man directory is part o! the MANPATH variable. a2 VERITAS Veune Manager 40 Adinseaton Cone aan eeaen eo angmer as Ghent & Sun BUN EDUCATIONAL SERVICES. ‘wrrw.suin.com/servioe/suned — @ vove eeooe @ 9 8 3 @es s eseeces 60Exercise: Performing VxVM Basic Operations Task 3 — Verifying the Initial Disk Drive Status ‘To verify the initial status of your assigned disk drives, complete the following steps: 1. Log imas user root to the VxVM server. 2. Verify the status of your assigned disk drives. # vediak List Check the output carefully and verify that each disk drive assigned to your workgroup shows a status of online i If any of your assigned disk drives show a status other than online invalid, check with your instructor. If appropriate, use the yadiskunsetup command, as shown in the following example, to retum all of your assigned disk drives to an online invalid status # /ete/vx/bin/vediskunsetup -C c0t2240 XVM accessname of your disk drives. Do not proceed until all your assigned disk drives are uninitialized VERITAS Volume Manager Basic Onerations aay CCepyrgn 2004 Sun Micronaare, ine Al RighssRasarved Sun Sarvs, ReinsExercise: Performing VxVM Basic Operations Task 4— Setting the Default Disk Drive Format Set the default VVM disk initialization format on the VxVM server by completing the following steps: 1. Log in to the VxVM server as user root. 2. Complete the following steps: 2. Start the vieliekadm utility, b. Select option 22, Change/Display the Default Disk Layouts, 4 wedtotadin 3. Select option 1 from the Volume. Manager Preferences menu. 4. Select option 1 from the Disk Initialization Preferences menu and type sliced for the desired format. Select option 2 from the Disk Initialization Preferences menu and type 2048 for the desired private region length © Type gor quit at least twice to exit the vxdiskadm ulllity, Verify the default disk initialization format values are set correctly. # more /ete/detault/vxdisk tormat=sliced privlens2048 x only by command-line programs such as the vadiskadm ind vxasaist Caution ~ Values entered in the /etc/detault/vadisk ile are honored A utilities. The VEA GUI does not reference the /etc/defauit /vxdik file, ————$SERS not reference the /otc/defauiit /wediak file, oe (itis eeu 4 Asante oe een eee eee macho uaien SUM or eoucsnoun senvees etreniesbareauees @ 2 B 9 e e @ e e @ 8 g oa @ 9° ;@ ° > & @ 2 9 ® » S 6 o a ® ® 2 ® 9 @ 8 ® ® ® b e 8a as Exercise: Performing VxVM Basic Operations Task 5 — Initializing Disk Drives Perform the following procedures to initialize your assigned disk drives for use by VxVM. There are two procedures: one for using the VEA GUI and one for using command-line programs. Using the VEA GU! to Initialize Disk Drives \ To initialize three of your assigned disk drives using the VEA GUL. complete the following steps: | ee ee 1. Expand the VxVM server node in the object tree and click Disks 2. Select three of your assigned disk drives in the grid area by simultaneously pressing the Control key while using the mouse button. Click the third mouse button on one of your highlighted disk drives, and select Initialize Disk in the pop-up menu, 4, In the Initialize Disk form, click Yee To All Aftera short delay, three of your assigned disk drives should appear in the grid area with a status of Free. 5. Complete the following steps: a, Use the wwedis):unsetup command to return each of your assigned disk drives to an uninitialized state. b. Replace the aczessname variable in the following command with the address of your disk drives (for example, c4t3d0). # vxdiskunsetup -C accessuane 6. Verify that the status of your assigned disk drives is once again invalid # vxdiek list VERITAS Volume Manager Basic Operations 438 Conyrgh2004 Sun Meronyaar, in. AX Rpts Rasarvas. Sun Services RavinonD SERV) waver sun.com/aervicw/sunedExercise: Performing VxVM Basic Operations Using Command-Line Programs to Initialize Disk Drives To initialize your remaining three disk drives using the vadisksetup ‘command-line program, complete the following steps: 1. Use the vxdisksetup command to initialize each of your assigned disk drives, replacing the accecename with the adklress of your disk drives (for example, c4t340), # vxdiskeetup -i accessnane 2. Verify the status of your assigned disk drives is online, 4 vadisk list Task 6 — Creating New Disk Groups In this section, you create a disk group containing three of your assigned disk drives, Name the disk group according to your first assigned workgroup letter, For example, if your assigned work group letters are A and 8, then this first disk group should be named daa. Using the VEA GUI to Create 2 New Disk Group To create a new disk group using the VEA GUL complete the following steps: 1. Click New Group in the Toolbar. ‘The initial New Disk Group Wizard form appears. 2 Click the Do not ehow this page next: cine box, and then click Next. The disk selection form appears. 3. Complete the disk selection form as follows: a. Type the name of your new disk group. 5. In the Available disk column, select three of your assigned disk drives, and then click Add, Do not enter disk names. Click Next, ‘The organization principle form appears. 436 VERITAS Volume Manager 4.0 Administration Beli tpncenotar pm enna © SUM se scucleoun carmces Wheasarreaniaciastaee z @ e o ® ° e @ ® ° ° e ° ° e 9 2 e e @ 2 ) e e ® a 6 @ @ 9 @ ° @ ° e ® , @ 16 , © ® e eee ee DPI ay ccmoniarn Exercise: Performing VxVM Basie Operations Complete the organization principle form as follows a. Select the None organization principle. b. Click Next. ‘The summary form appears. Click Finish on the suimmary form to create the new disk group. 6. Verify that your new disk group appears in the VEA object tree. Using the vxdg Command to Create a Disk Group Use the veg command to create a second disk group that contains your three remaining assigned disk drives. Name the disk group according to your second workgroup letter. For example, if your work group letters are A and 8, then this second disk group should be named dap. Complete the following steps: 1. Use the vdg init command to create a second new disk group and add one of your remaining assigned aisk drives. # vxdg init dgname medianame-accessnane For exemple vadg init dgB dgp-o1=c20340 | Add the two remaining assigned disk drives to the new disk drive Broup. 4 vxdg -g dgname adddisk medianane-accessname For example: vadg -g daB adddisk dgB-02=c2e5dd deb-03. 3. Use the wxprint command to verify the status of your new disk group. 4. Use the vxdg xmdisk command to remove one of the disk drives feom your new disk group. § vadg -g dgname rodisk medianane For example: vxdg -g G38 rmdisk dgB-03 5. Use the viedg adddick command to add the came disk drive back into your disk group. 2b6do VERITAS Volume Manager Sasic Operations 437 ‘Copan 2004 Sin tcroyeme, Ine Al Fights Reserved, Sun Sarvens Reiien D viww-sun.com/senvine/eusedExercise: Periorming VxVM. Basic Operations Task 7 — Viewing Command Logs ‘The command log records the command-line programs used to accomplish VEA tasks. It is a good learning tool. ‘To view the command log file, complete the following steps: 1. Log in to the VxVM server as user root. 2. View the command log file. # cd /var/vx/isis #15 alertlog state vea_ portal command.1og swap vxiais.lock savedqueries tasklog vxisis log # more . /command. log Task 8 — Importing and Deporting Disk Groups Im this task, you deport and import one or both of your disk groups. Using the VEA GUI to Import and Deport Disk Groups e e ° ° e o °o oe ° eo 9 ° °° ° e ° o oe e ° To import and deport disk groups using the VEA GUI, complete the following steps: 1. Display disk groups in the grid area 2. Click the name of one of your disk groups and select Deport Disk Group from its pop-up menu, ‘The Deport Disk Group form appears. an rename a disk group during a daport operation. You can also assign ownership to a different host. You might do this if you needed to take the current host down for maintenance and wanted a different host system to manage the disk group for a while. You migitt also rename the disk group if the second host alreedy had a disk group with the same ee) 3. Click OK. ise sarsmintenermmane See eee tne caae PSII cas cosernonr serves eens e °o ° 8 e ) 9 °o @ 9 @ ® © ® © 2 e ® ® e,Exercise: Performing VxVM Basic Operations 4. Complete the following steps: 4 Click Browse and highlight the disk group you want to deport | b. Click OK The status of grid area dis disk group should change to Deported in the lay 5. Click your deported disk group in the grid area and select Import from its pop-up menu. Using Command-Line Programs to Import and Deport Disk Groups To import and deport disk groups using command-line programs, complete the following steps: 1, Log in to the VxVM server and use the vxdg_ deport command to deport either of your disk groups. # vxdg deport dynane For example: vxdg deport daa. 2. Use the vxdi sk command to identify the deported disk group. # vadiek -0 allags list 3. Use the vids import command to import your disk group again. # vxdg import dgnane For example: vxdg import dgA VERITAS Volume Manoger Basic Operations 39 Cony 2004 Sun Meonyalens ine Al Righa Reaured 9ur Services, HavenExercise: Performing VxVM Basic Operations Task 9 — Destroying a Disk Group } In this task, you destroy one of your disk groups. Using the VEA GUI to Destroy a Disk Group Todestroy a disk group using the VEA GUI, complete the following steps: | 1, Display Disk Groups in the grid area 2. Click one of your disk groups and sclect Destroy Disk Group from its pop-up menu. 3. Click New Group in the Toolbar and recreate the disk group you destroyed. Using Command-Line Programs to Destroy a Disk Group To destroy one of your disk groups using command line programs, compete the following steps: 1, Use the vxég command to destroy one of your disk froups # vadg destroy dgname For example: vxdg destroy aga Recreate the destroyed disk group using the tool of your choice, Task 10 —-Renaming Disk Drives In this task, you rename one or more of your assigned disk drives. Using the VEA GU! to Rename Disk Drives To rename disk drives using the VEA GUI, complete the following steps: 1. Display the disk drives from one of your disk groups in the grid area 2. Click one of the disk drives and select Rename Disk from its pop-up menu. 3. Entera unique media name for your disk drive. zs, shia re eae oars ee nae @ SHI socoucaronn sernces wile asinacicaleined eB jeSSSCSHOHSHSCHSHSHOHGCSHESHOXFOHOHCXOHHOLOLOOKH OOOO SECSExercise: Performing VxVM Basic Operations Using Command-Line Programs to Rename Disk Drives ‘To rename disk drives using command-line programs, complete the following step: Using the vxedit cor drive you modified i page 4-40. mand, restore the original media name of the disk “Using the VEA GUI to Rename Disk Drives” on } ! 4 vxedit rename oldname newane po For example: vxedit rename 2x12 daB-03 Task 11 — Using the vxdiskadm Utility to Perform Basic Operations (Optional) ‘Ask your instructor if there is enough time to perform this optional task To recreate your disk groups using the vedi skadm utility features, complete the following steps: 1. Use the vida command to destroy both of your disk groups # vadg destroy dgnane 2, Use the vediskacn utility option 1 to recreate bath of your assigned disk groups 3. Use the vxdiskadm utility option 3 to remove a disk drive from each of your disk groups. 4. Use the vxdiskadn utility option 1 to add the previously removed disk drives into your disk groups 5. Use the vidi skacin uti groups. 6. Use the vxdiskadin utility option 8 to import one or both of your assigned disk groups. VERITAS Volume Manager Basic Operations 444 ‘Conyrgnt 2004 Son Mizorynas, In. Al Righs Resend Sun Sarveas Revision D SUN or covenExercise: Performing VxVM Basic Operations. Task 12 — Verifying Ending Lab Status To verify your system configuration, complete the following steps: 1. Use the vaiisk List command to ensure that both of your disk ‘groups are still complete and meet the following guidelines: © You have two disk groups name dgxand day © Each disk group contains three disk drives * None of your assigned disk drives are designated as hot spares. Note —Substitute your workgroup codes for the Xand Yin agxand a5 rey SS Use the vmprint command to verify that there are no subdisk structures in cither of your disk groups. a Yeas eke ance <0ycoioen SS eea ea slr @ SUM soc covearonn seneces toca esaoaeatias a SCeeeee Cen oe eo SCHOKCHKOKOSHSHOKEHOSHKOHKDE 66 ©6806 e éExercise Summary Exercise Summary Discussion ~ Take a few minutes to discuss wh at experiences, issues, or discoveries you had during the lab exercises © Experiences * Interpretations © Cone © Applications VERITAS Volume Manager Basic Oparations 443 (Copyiht 2004 Sun Mctoystama Ine Al Righs Reserved. Sun Services RriionSOCSOSTHHHOSCHASGSSSHOEDOOEE CeaPe2e2eGC0@0000009 : i EDUCATIONAL SERVICES:Module 5 VERITAS Volume Manager Volume Operations Objectives Upon completion of this module, you should be able to © Interpret volume structure listings @ Describe volume planning activities volumes using the VEA GUI volumes using the vxas: command © Modify volume access attributes © Add file systems to existing volumes © Add and remove volume logs Use the VEA GUI to analyze volume structures bt ‘copyrih 2008 9unwieoaranm in. Pgh Reserved. Sn Sarnn Reson D SUM, sercccuenrionss servcesInterpreting Volume Structure Listings Interpreting Volume Structure Listings VERITAS VxVM volume structures are composed of three primary, components: subdisks, plexes, and a volume name. The components are assigned names based on default conventions or can be manually chosen. Subdisks A subdisk is a set of contiguous disk blocks. A subdisk must reside entirely on a single physical disk drive. The public region of a disk drive ina disk group can be divided into one or more subdisks. The subdisks cannot overlap or share the same portions of a public region. The smallest possible subdisk is a single sector (512 bytes), and the largest subdisk is the entire VxVM public region, By default, subdisks are named based on the VxVM media name of the disk drive on which they reside. This relationship is shown in Figure 5-1 SSCHSSSSHTHCHHOHGOCVGO OH HOe _ Disk Soup oe) | vance | | Prywen oak | : ened 1 j 1 ' ' 1 1 1 | | _Vambisk | ' i + | faiaeeaeay | | Pry isk | i carzide 1 [aiskoa-o2] | 1 ' ' | | aeaeeas) | | 4 ‘ \ t Figure 5-1 Subdisk Naming Conventions SCOSCAS8SSOHBHSCHEGOSEOHSE 52 VERITAS Volume Manager 4,0 Administration Copyright 2004 Sin Microsystems. he. Al Rights Reserved. Sun Services, Revision D BO SUIN os exscanonn. senoces seocieranrisorisaean = ie @Interpreting Volume Structure Listings Plexes The VxVM application uses Subdisks to build virtual objects called plexes {A plex consists of one or more subdisks located on one oF more physical dick drives, Figure 5-2 shows the relationship of subdisks to plexes in a disk group named DGa. Plex Physical Disk, auako-08 Siakor-o2 HY eereserer aiakon ! \ ee i ainkO 1 _VAV ish Pox ‘we | [aie aiek02-02 Be [Roente Figure S-2 Plex Configurations The dita to be storéd on the subdisks of a plex can be organized by using any of the following methods: © — Concatenation © Striping Striping with parity (RAID 5) be plex can contain a maximum of 4096 subdisks, Ta ATT VERITAS Volume Manager Volume Operations 53 Re aOR Sun ieroeysns, Ie AH ite Racer. Sun Servean, vilenD PSUM soccosseu SERVICES yevew,sun.com’se viecisinedInterpreting Volume Structure Listings Volumes A volume consists of one or more plexes, By definition, a volume with two plexes is mirrored. Figure 5-3 shows the relationship of plexes in a ‘mirrored volume in a disk group named Da. 1 ' ' ‘ ' ! | ‘ ‘ Physical Disk 7 ' exeazao }+ i ‘ ; [eam] | | ' Saas) | | Liao ||! ' | _vavM ois Plex ' | 1 | [Bisxoran aiexo-02 H Prysealdiek | i it3380 acon aiamiao]| | | " : 1 | [atar=os soe J) 1 1 | aienoa J |___ voto t \ ‘ Figure$-3_ Mirrored Volume Structure You should understand the following important points albcut volumes: ¢ Volumes can have more than two mirrors, © RAID-5 volumes cannot be mirrored. * Aplex can also be a logging structure that is not used for data ee a esi en hereto ea eo oes OSU erates eats Ter arecaavaaie ——Interpreting Volume Structure Listings Volume Structure Examples The following veprint output shows an example of two volumes that belong to the same disk group. The vol_02 volume is a simple concatenation and the vol_02 volum mirrored across two ‘The listing indicates the following details: © Both volumes are 2 Gbytes in size (42943) controllers, blocks/sectors) © vol_01 is composed of a single plex and associated subdisk © vol_o2 is composed 4 wepeint -g newG n 4g gegeo3 pl sa ph sd NAME new0G newDGOL new0G02 newbGo3 newbG04 newDG05 newDG0S yol_o1 vol_01-02 newOG01-01 vol_02 yol_02-02 new0G04-01 vol_02-02 newh@01-02 PSU... assoc newDG cat16dos2 e2t18d082 eat20d0s2 e3t32dosz e3t33d0s2 e3t35d082 fegen vol_ol vol_01-01 fegen vol_o2 vol_02-01 vou02 vol__02-02 KSTATE ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED LENGTH PLOFS 17679776 - 17679776 17679776 17679776 17678776 17679776 4194304 4194304 4194304 a 2: 0: 04 431 4194303 4194304 of two plexes each with an associated subdisk ACTIVE ACTIVE syc ACTIVE The following vxdg output shows the amount of available disk space. The OFFSET column represents the amount of space currently used and the LENGTH column represents the amount of free space. 4 vxdg -g newDG free DIsk newDGOL newDs02 newDG03 newDG04 newDG0S newDG0S DEVICE catiédos2 o2b18d0s2 catz0d0s2 c3t3zd0s2 o3t 334082 e3t35d082 TAG c2t16d0 e2t1edd e2t20d0 e3t32d0 o3t33d0 at: OFFSET 9368608 ° ° 4194308 VERITAS Volume Manager Volume Oparations evr 2004 Sun Meenas nc ALRighia Reserved. Sun Services, Ravion UGATIONAL g2giles - 17679776 - 17678776 - 13485: 17679776 17679776 - wauw sun comseriicnisiniedVolume Plans 9 Volume Planning Creating volume structures is easy to do. It is also easy to make mistakes unless you understand each aspect of the volume creation process, Volume Distribution 56 & Sun Fammon mistake is to place all the disk drives in a single disk group. The configuration records for a disk group cannot contain information for more than 4096 objects. Each volume, plex, subdisk, and disk driv considered to be an object and requires 256 bytes of space in the private region. The default private region length is 2048 blocks, nother reason for organizing disk drives into separate disk groups is that you might want to deport a disk group and import it to snother Connected host system. This action can be part ofa disaster recovery plan ora load balancing measure. You can design a disk group so that it is better for particuler tasks. Each disk group shown in Figure 5-4 has three disk drives, and each disk drive is ina different storage array. Host System ‘Arey ‘Aiay ‘Array Figure 5-4. Striped Volume Disk Groups VERITAS Volume Manager 40 Administration Coby 2004 Sun Microsyars In. A Rpts Reserved. Sun Services Revision D UN EDUCATIONAL SERVICES werw sun com/setviow/sunad — SeSHOOHR8SOSH2HOCeHGe ee SSOGCGOSSCZOSHOCO e© ols Volume Planning Disk groups organized in this manner are good for creating striped volume types (such as RAID 5) and for mirrored volumes. The most important feature is that each disk drive in the disk group is in a separate enclosure and on a different controller. Noie = Exereise care with dik groups lhal span élovage arrays You must be sure that the loss of an entire array does not disrupt both mirrors in a volume or more than one column in a RAID-5 volume. Another disk group structure, such as the one shown in Figure 5-5, would be belter used with simple concatenated volumes. Hoat System: Figure 5:5 Concatenated Volume Disk Groups If the volumes are large, static, read-only structures that need only @ period:c backup to tape, they do not need any higher level of reliability or availability VERITAS Velume Manager Volume Operations St Copyright 2004 Sun Merenyntems, ine AlRighs Reserved Sun Sorican, Faviion D OSU si encimon sennces \wew.sun.com/service/sunedVolume Planning 58 SIM vos ccvcsronas senses Volume Naming Conventions thin a disk group, the VkVM software requires a unique name for each New volume that is created, The volume names are usually systematic, such as voL03, vol 02, vol03, and so on. Naming conventions can be used to reflect volume attributes, such as: © The volume structure © Which department uses them ¢ With which database they are associated * Special purposes within a workgroup Although naming conventions might not seem to be of much importance, they can help establish priorities during emergency situations, such as major power outages. Space Allocation Planning Although cheosing general size for a volume is frequen'ly dictated by the application, administrators frequently want to use as much space as is practical on a set of disk drives. There are several ways to ullocate space for a volume. Among them are: © Let the VxVM software automatically find the space © Limit the search for space to selected disk drives in a group. © Research available space with command-line programs. Note=The VEA GUI New Volume Wizard also has limited space research” capabilities during new volume creation. Automatic Space Allocation ° If you do not specify disk resources when creating volumes, the VxYM software automatically finds portions of unused disk space and assembles them into a volume. This action can lead to a disorganized structure and ‘create poor performance for some volume types. VERITAS Volume Manager 4.0 Administration Copyright 2004 Sin Micxosytaa, ne Al Rights Reserved. Sia Services RevidenD vow. sun.com/service/suned — POSGHGCVCSCSHEHOCCEOBEOLCHOBLOHMEH BROCE ®6e80 eeeoe ie @Volume Pianning Restricted Space Allocation Rather than letting VxVM find space anywhere within a disk group, itis frequently better to direct VxVM to use a particular disk drive for a new volume. ‘The disk group shown in Figure 5-6 can be used in several different ways depending on the type of volume structures you require: © A RAID-5 volume might use disk drives di, d2, and 43 © A concatenated volumie might use disk drives 41, 44, and 7, © A mirrored and concatenated volume might use disk drives di, d4, and a7 for one mirror and disk drives 3, a6, and 49 for a second mirror. Host System fesiiesiea G60 dd 000 Figure 5-6 Selecting Disk Drives for a Volume rs - YERTAS pura Margene natnVolume Planning Researched Space Allocation Analyzing free disk space before creating a yolume is sometimes beneficial. Look for patterns of free space that fit your needs. The following examples show how to research free space in a disk group. The vxdg command gathers a rough estimate of available disk space, The following is an example of using vxdg on a 9-Gbyte disk drive H vxdg -g newDG free DISK ndg-02 ndy-02 adg-03 ndg-04 DEVICE Tac OFFSET LENGTH = FLAGS e2tidds2 = catido. ° 17674902. - eat3dos2 —c2tsdo Q 37674902 - estazd0s2 —c3t32d0 Q 37674902 - e3t33d0s2 303340 o 17674902 Aiter creating a 6Gbyte mirrored volume using the ndg-0:- and ndg-03 disks, the following disk space is available: 4 weg -g news free DISK nidg-02 ndg-02 ndg-03 ndg-04 DEVICE TAS OFFSET LENGTH «= FIAGS s2cidos2 ct ado 12586455 Sossag7 e2tsd0s2 cat ado 0 17674302 - e3t3zd0e2 33240 12586455 Sosega7 63033082 33340 ° 27673902 - Alter rough planning, you use the veassist maxsize command to research more detailed information. The following examples show how to use the vxassist command: # veassist -g newDG maxsize \ layout=nomirror,nostripe ndg-01 adg-02 ndg-03 nég-08 Naximun volume size: 45524992 (22229Mp) # vxagsist -g newDG maxeize \ Jayout-raidS molog adg-01 ndg-02 nég-03 ndg-04 Naximum volume size: 20353024 (9938Mb) 5.10 @ SUM sn coscmoncseeuces ss sensors The wsassist_maxeize command is not usually heeded unless you have especially limited disk drive spece and need to maximize its use. [tis a g00d practice to leave a small amount of space for log placement. VERITAS Volume Manager 4.0 Administration Copii 2004 Gun Mirena. i. ANRighs Reserved Su Sarees, Raven= Volume Planning Selecting Volume Types ‘The VxYM application supports several types of volumes. Each volume type has a specific layout specifier. The following sections briefly describe each volume type and its associated layout specification Concatenated The advantages of concatenated volumes are efficient use of storage space and easier hardware requirements. Layout specification: concat Striped ‘The advantages of striped volumes are improved read and write performance. 2 ee Layout specification: stripe Mi tored Concatenation The advantage of a mirrored concatenation volume is improved availability through data redundancy. Layout specification: mizror- neat Mirrored Stripe ‘The advantages of a mirrored stripe volume are improved availability and increased read and write performance. Layout specification: mizror-stripe ee ae ae Cd VERITAS Volume Manager Volume Operations a (Copyright 2004 Sun Micronytoms. in. AX Rights Rasorad. Sun Services. RavenVolume Planning B12 PSU cor eoscsrsa senvices Concatenated Mirror (Layered Volume Type) The advantages of concatenated mirror volumes are improved availability and faster recovery time. This is because only a portion of a mirror must be recovered. Layout specification: concat mirror Striped Mirror (Layered Volume Type) ‘The advantages of striped mirror volumes are improved performance, foster recovery times, and high disk drive failure tolerance. Layout specification: stripe-mirror RAIDS The advantage of RAID-5 volumes are somewhat improved availability with limited negative impact on disk space utilization. Layout specification: raid5 (ox xaidsnolog) VERITAS Volume Manager 4.0 Administration (Sopriht 2004 Sun Wicrsyatem, ic, Al gh Raseres. Sn Series, ReviionD vor suin.com/service/sunedCreating Volumes Using the VEA GUI Creating Volumes Using the VEA GUI A New Volume Wizard is initiated in the VEA GUI using either of the following methods: © The menu bar's Actions menu New Volume item © The toolbar’s New Volume button Disk Selection Method ‘The initial New Volume Wizard form prompts you to select the disk selection method to be used. The default is to let VxVM decide which disks to use. However, when creating complex volumes, itis a best practice to enable manual disk selection, as shown in Figure 5-7. eels een Canc) Choose the method by which to select Disks for this Volume Ifyou choose automatic, ihe Volume Manager will choose the disks to use for this volume. Ifyou choose manual, you will be [i ie able to specify which disks you would like Volume Managerto La use for this volurre. Figure5-7 New Yolume Wizard Disk Selection Method VERITAS Volume Manager Volume Operations 513 Covyrighi2004 Gunteroystoms te Al ighla Reserved Sin Serices. Revision OSGI sree sence yaw sun.com/servico/sunedCreating Volumes Using the VEA GUI 544 B® SHIT oc covcancnn. services Using the Disk Selection Form As shown in Figure 5-8, the New Volume Wizard disk selection form assists you in locating and selecting st eee er Select Disks touse for Volume ‘Youhave chosen to manually epecty the disks to use for his volume. You can Choose to Include or exclude nidvidus) cisks, me aieks on a controler, orthe disks in an enciosure newer {@newoooe 264022 SBnewooo2 <2tieaos2 @rewoors «206082 Brewer en20087 Figure 5-8 New Volume Wizard Disk Selection The Mirror Across and Stripe Across check boxes let you choose how you. want stripes or mirrors distributed across your storage con‘iguration. The Mirror Across Tray applies to specific storage array model: that have separate disk drive trays in a single array. Unless you later specify a stiped or mirrored volume structure, these features do not perform any tuseful function. The Ordered check box is an advance d function that uses the specified storage first to create concatenation, then form columns, and finally to create mirrors. Ordered allocation is an advanced subject presented later in this course, VERITAS Volume Manager 4.0 Adminietration Ceayght 7004 San Wcroetams. n= AlRighs Reserved. See Sarvews, Revision) wwwsun.con/servicelsuned SSGSOROBOOBHO SFO SCCCSOCSOHHTCSOHOSFOPHLVOOD OOO jee ©Creating Volumes Using the VEA GUI Using the Volume Attributes Form ‘The New Volume Wizard volume attributes form, shown in Figure 5-9, assists you in defining the name, size, and type of a volume structure, Now Volume Wizard ‘Selec! the atnbutes for this veiurm. Figure 5-9 New Volume Wizerd Attributes Consider the following points when configuring new volume attributes i Name volumes according to their purpose 2 Use Maxsize after you have configured everything else. The Maxsize function calculates space based on the volume layout spec ‘The space available varies widely depending on the target volume | configuration. @ Use the Columns and Stripe unit size functions when you are eating volumes that have columns such as striped or RAI volumes, © Note that the Mirrored check box is automatically enabled when Coneatenated Mirrored or Striped Mirrored structures are selected. | & Manually selecting Concatenated, and then selecting Mirrored, creates a different structure than selecting Concatenated Mirrored. Janne eaetnsoeeen et verison aan eS, enhondCreating Volumes Using the VEA GUI Using the Create File System Form As shown in Figure 5-10, the New Volume Wizard File Systom form Prompts for file system type (UNIX file system [UFS) or VxFS) and mount ‘options. VEA automatically creates the mount point, modifies the /etc/véstab file, and initializes and mounts the new file system. The New File System Details button enables naw£s and mks option entry. ‘The Mount File System Details button allows volume ownership and protection entry. eeate Fle System You ean cteate a fe oystemonthis volume Please spect he desired ontons Figure 5-10 New Volume Wizard File System Form Note ~ The VEA server logs the commands that perform all functions in Y the /var/vx/isis/command.1og file. The log file is a useful learning tool. fe Har/ex/isis/comand. 169 file. The log file isa useful learning tool. 516 VERITAS Volume Manger 4.0 Administration ‘Copyiht 204 Sun Mherenytane, ne. AR ight Reserve. Sus Services Reon D © SUD os cascsonn sernces Swww stun com/vervice/sunedist Command Creating Volumes Using the Creating Volumes Using the vxassist Command The vxassist program performs a wide range of volume-related tasks Without the complexity of lowerlevel programs, such as vevol. The easaist program also protects against many mistakes that can be made when using lower-level command-line programs, The vxassist Command a8 many options. Most of the options use The vxassist command hi y entered, default values if values are not explicit The most basic form of the veasaist command, which creates a volume, is: 4 vaasaist make vol02 Sém fh this format is that is assumes the following: ‘The problem © Adefault disk group, if one is configured e Thedefault volume type is a basic concatenation © Any disk drives that have available space might be used st command probably cannot If you do not specify options, the vxassi performing volume or give you what you need, Itcan also create a poorly sontribuite to poor performance of other volumes. Specifying Volume Size Volume sizes can be specified using the following units: @ » (blocks) © a (gigabytes) © (kilobytes) e _ m(megabytes) © 5 (sectors) « VERITAS Volume Manager Vole Oprations sar 1 YERITAS Volume Marg ve taguanmares Se Sarin Aven cCreating Volumes Using the vxassist Command Using vxassist Command Options If you furnish even a few options with the vxassist. command, the outcome is more clearly defined. A typical command using limited options is: # veassist -g dg2 make newvol 2g \ layout=raids,noleg disk0i disk02 diok03 ‘This form of the vxas the following are trus © The disk group that is used is dg2. © Thename of the volume is newvol st command is more explicit and guarantees that © Thesize of the volume is 2 Gbytes. © This is @ RAIDS volume without a log and with three columns © Alldisk space comes from disk02, diskoz, and disko3. Although there are many vxassist command options, only a few are commonly used, Some of them require careful study. Always read the ‘manual (man) pages and related documentation before attempting, to use ‘most of these options. ‘The vxintroand vxassist man pages contain useful information that is difficult to find elsewhere. Default Option Values Pay close attention to the default values of command options. When specifying volume layouts, ensure thet you understand the default value or configuration for a particular volume type. The following examples ‘show some layout specifications for RAID-5 volume types: ‘Jayouteraids (creates a RAID-5 log by default) layoutsraidSleg layout=raid5,nolog Jayout=noraidslog The first two variations are equivalent and create the same volume structure. The last two are also equivalent. 518 VERITAS Volume Manager 4.0 Agmnistration Copyrh 20% Sun Wicoepuea, nc AB ghia Rebarved. Sin Seevees, Revlon D @ SUM sweovcsvons stuaces NoreeuceanteeCreating Volumes Using the vxaseist Command Examples of vxassiet Command Options The following examples show each type of supported volume structure. The layered volumes require a larger minimum number of disk drives to implement. ewvol 20m \ H vaaseist -g dg3 make layout=concat disk01 # vxaseist -g dg3 make newvol 20m \ layoutsstripe disk0l disk02 # vxassist -g dg3 make newvol 20m \ layout=mirror-concat disk0l disk02 # vaacoiet -g dg3 make newvol 20m \ layout=mirror-atrip disk0l disk02 disk03 disk04 # vxassist -g dg} make newvol 20m \ layout=concat-mirror disk0l disk02 disk03 diskos 4 vaaseist -g dg3 make newvel 20m \ layoutestripe-mirror disk0l disk02 disk03 dieko4 # veassist -g dg} make newvol 20m \ ayouteraidS,nolog disk0l disk02 disk03 The vxassist command can frequently determine the best way to use the specified disk drives (media names) in a volume structure. (ee ee ee eee ee ee ee Oe VERITAS Volume Manager Volume Operations (Copyright 2004 Sun eroayatars, in. Al Rights Reserves. Sun Services RisonModifying Volume Access Attributes Modifying Volume Access Attributes When new volumes are created in a disk group, they are given a set of default access attributes that include: © Owner © Group * Mode The owner, group, and mode are usually those of the root user. For some Volumes, especially raw volumes that are used by a database, the volume ownership must be modified. Volume attributes, This is because the attributes revert to their original Valles after each system reboot. Change raw volume attributes using VxVM commands. Caution ~ Do not use the chown, chgrp, or chmod command to set aw Verifying Volume Ownership The ownership and permissions of raw volumes can be chesked like ordinary system files. You use the 1s command to examine the raw volume files in the /dev/vx/rdsk/dg_name directories. # le -1 /dev/vx/rdek/newDG/testvol Grwcw----- 2 Oot rook 198,73000 Feb3 20:37 /dev/vx/rdsk/nestG/teatvol Modifying Volume Ownership and Permissions ‘Torun applications, such as ORACLE 9i RAC, it might be necessary to change read/write permissions and ownership of the raw volumes, You use the vxedit command to change the raw volume’s permissions or ownership, # vaedit -g tpcs set user=oracle group=dba mode=660 acctos Note — You can also use the VEA GUI New Volume Wizard fo set volume Y, Ownership and permissions during initial volume creation. Or, later, you can use the Actions menu File System entry to create a file system and configure mount information for an existing volume. SSS EE Santon Soranloaiing 5 VERTAS Vue Manager4.0Adinisaton Reina @ Sun . ICATIONAL SERVICES ‘yavw.sun.com/serview/suned >COSCOHRHTOCOHCEOHEOHLECTHOHKXOOH OOOO 00; ©8066080 ecAdding a UFS File System to Existing Volumes. Adding a UFS File System to Existing Volumes Adding a UFS filesystem to a volume is easy to do. You can fill out a form using the VEA GUI, or you can create a file system from the command line using standard Solaris OS commands. Both methods are described in 4 this section. Note = VxVM also supports the VxES file system type, but the VaF features are licensed separately. & ® ! | ‘ { ° Using the VEA GUI to Add a File System | 6 } it To add a new file system to an existing volume using the VEA GUI, I + highlight the target volume in the grid area and select File System New \ pt File Svstem from the Actions menu. The resulting Create File System | if Form js identical to the New Volume Wizard Create File System Form Pi a New File System Details Form | a Using the New File System Details Form, shown in Figure 5-11, you can ‘8 y' P’ make fundamental file system changes. af Semel a s ° e dl Figure 5-11 New File System Details Form You enter a comma-separated list of mi£s file system options in the Extra options text field, Consult the mks and mk£s_ufs man pages for more detailed option information. VERITAS Volume Manager Volume Operations 5.21 oprah 2004 aun toca ne At Rghs Reserves. Sun Sanicas Rvaon D SUN, suv cou sora sewers vw sun. comsa ! Adding a UFS File System to Existing Volumes Mount Details Form You can enter valid file system mount options, as shown in Figure 5-12. SSOSOSCHOHKFHHSBSEGHLHH O40 Figure 5-12 Mount Details Form 672 VERITAS Volume Menagar 4.0 Administration Copia 2008S Merosysins In. i Fights Reserved. Sun Services, Rosen D EDUCATIONAL SERVICES ww sun com/service/suned SOCSSHHOCHOHHGHEOOHGXOHHOO =Adding @ UFS File System to Existing Volumes Adding a File System From the Command Line @ Sun When a new file system is initialized from the command line, you can adjust certain file system parameters to make more efficient use of available space. They are: © — Minimum file system free space © Number of bytes per inode File System Free Space By default, the newfs: utility calcul: the minimum free space based on partition size (64 Mbytes + partition size x 100), rounded down to the nearest integer. The default value is limited to between 1 percent and 10 percent. ‘When the file system is full, the free space can only be accessed by user root. Il can act as an emergency overflow. # newEs -m 10 /dev/vx/rdsk/new0¢/vol_01 In very large file systems, you can safely set the minimum free space ti smaller percentage, Number of Bytes per Inode The news utility calculates the number of bytes per inode based on file system size. By default, the newfs utility calculates the number of inodes as follows © 2048 bytes per inode for 0-1 Gbyte file system size © 4996 bytes per inode for 1-2 Gbytes file system size © 6144 bytes per inode for 2-3 ytes file system size © 8192 byies per inode for file system larger than 3 Gbytes If you intend to create a large file system that will contain a small number of very large files, you might be able to decrease the total number of inodes, for example: # mew£e -i 10240 /dev/vx/rdsk/newD¢/vol02 VERITAS Volume ManagerVelume Operations 523 Conyrigh 2004 Sun Miconyalams ie AX Rights Reservas. Sur Services, Revision D SUN ROUGATIONAL SERV! www sun.com’service/\ined.& Adding @ UFS File Systemto Existing Volumes r: Enabling the Solaris OS UFS Logging Feature UFS logging is a standard feature of the Solaris 8 OS, If the logging option is specified for a file system, then logging is enabled for the duration of the mounted file system. Logging is the process of storing transactions (changes that make up a complete UFS operation) in a log before the transactions are applied to the file system. After a transaction is stored, the transaction can be applied to the file system. This Process prevents file systems from becoming inconsistent, therefore eliminating the need to run the fsck command. Because the £ack command can be bypassed, logging reduces the time required to reboot a ‘System if it crashes or after an unclean halt. The default behavior is no logging. The log is allocated from free blocks on the file system, ancl it is sized at approximately 1 Mbyte per 1 Gbyte of fle system, up to a maximum of 64 Mbytes. Logging can be enabled on any UFS, including root (/). The {eg created by UFS logging is continually flushed as it fils up, The log is totally flushed when the file system is unmounted or when the Jockts -£ command is used. Example of File System Commands ‘The following commands summarize the types of operatiors that must be performed to manually create a UFS logsing file system on an existing VxVM volume. # newEs /dev/vx/rdsk/newDG/testvel # mkdix /Teat Ht vi /ete/vistab /Gev/wx/dsk/newG/testvel /dev/vx/edsk/newG/teatvol /Test ufs 1 yes logging # mount /Test Note = The default file system behavior is nologging, fa Veta hen bene Loman Se ee © SUI oe tascstovobscsnces ‘Sse aseieliagaaeAdministering Volume Logs Administering Volume Logs Both mirrored volumes and RAID-5 volumes can have logs. However, the logs for RAID 5 perform an entirely different function than the mirrored volume log, which is called a DRL Using DRLs A DRLis a VcVM log file that tracks data changes made to mirrored volumes. The DRL speeds recovery time when a failed mirror must be synchronized with a surviving mirror. A DRL is a small, special-purpose plex attached to a mirrored volume which has the following features: ¢ [tis log that keeps track of the regions within volumes that have changed as a result of write operations toa plex. It does this by maintaining a bitmap and storing this information in a log subdisk. 4 After a system failure, only the regions marked as changed (dirty) in the DRL are recovered The following example shows a mirrored yolume with a DRL. Notice that the tog subdisk does not reside on either of the mirror disk drives. 4 vepeint -g news mirvol Ty OME Assoc STATE LENGTH PLOFFS STAT pl mirvol-01 sd ndg-01-01 pl mirvol-02 sd ndg-03-01 pl mirvol-03 sd ndg-02-03 4096 7182 RABLED LOOONLY RUSLED 33 DRLs are very small compared to the volume data storage ‘VERITAS Volume Manager Volume Operations 525 ‘Copyrigh 2904 Sun Mleroayatoms ine. Al Rghis Reserved. Sun Serceas. Raison 0 OSU site noncucsenion ootcenv used‘Administering Volume Logs Using RAID-5 Logs RAID. logs help prevent data corruption in case a system crashes during 2 Mrite operation. Without logging, ifa system fails during a write Operation, there is no way to tell if the data and parity were both written to the disk drives. This could result in corrupted data When RAIDS logging is used, a copy of the data and parity are written to the RAIDS log before being written to the disk drive, RAID S logging is optional, but RAID-5 logs are created by default, You should always run a system with RAID-S logs to ensure data integrity. {ite following example shows a RAID-5 volume with a log. Notice that the log subdisk does not reside on either of the stripe disk drives, # veprint -g newDG raiavol TY NAME Y raidvo! pl vaidvol-01 8d ndg-02-02 sd ndg-01-03 sd_ndg-03-03 pl raidvol-o2 ad ndg-04-02 526 Sun ASSOC KSTATE LENGTH PLorrs stare raids ENABLED 4096 ACTIVE raidvol BRELED 7168 ACTL rad 01 BUBLED 3591 - raidvel-01 RU@BLED 3591 Faidvol-01 ENABLED 359) raidvol BUBLED 3591 raidvol-02 ENABLED 3591 erecc: ‘The size of RAID“ logs is automaticaly set by VxVM. It is dependent on the stripe width of the volume. The larger the stripe width (not volume), the larger the RAID log. The RAID-5 log is intended to huld several full-stripe writes simultaneously. The default log size for a RAID-5 volume is four times the full stripe width (the stripe unit size x the number of stripe columns). VERITAS Volume Manager 4.0 Administation ‘Copia 2008 Sun Mcrcrytes in i Rights Reserved. Sun Saves Ravin 0 UN EDUCATIONAL SERVICES Wanw:siin Com/servicw/sunedAdministering Volume Logs Planning Log Placement Although logs can be very beneficial to volume recovery after a system crash, if they are not properly managed they can create I/O bottlenecks that negatively impact system performance. You should plan for both RAID-5 logs and DRIs in advance. You should take special care with RAID-5 log placement because the data written to all RAID-5 stripe units is also written to the log, As shown in Figure 5-13, leaving a small amount of free space at the end of al! disk drives ensures that you always have alternate locations for log placement or relocation Volume 01 oe oa Vai2eg | | vegSpace | | Log Spece | | Lop Spece Volume 02 Th) wwasece} [toasmace J [Teasieee’) Vaoros Figure 5-13 Log Space Allocation i ® i e aa 2 ty 2 e My ry id If possible, a log should rot reside on the same disk drive as its related volume. Note — Log si software, Resins eens ets y VERITAS ume anna OE ntsAdministering Volume Logs Adding a Volume Log From the VEA GUI Usually, DRL and RAID-5 logs are added when a new volume is created, However, in some cases it might be preferable to run performance tests before deciding on the placement of logs. To add 9 DRI. or RAID-5 log to an existing volume, click the volume in the grid area, Next, click the Actions menu and sélect Log Add from its Pop-up menu As shown in Figure 5-14, you can either let VxVM automatically assign a suitable log disi or you can enable manual disk assignment. Avail css faa eit e0s2 reo cmeeosz @newooo2 — e2 ats ©e8e SOo6os eoeee ° |eUsing the VEA GUI to Analyze Volume Structures Viewing Disk Volume Mapping and Performance 72 view volume-to-disk mapping and performance, click on a disk group in the VEA GUI and select Volume Disk from the pop-up meri The Volume Disk Map, shown in Figur volume and its associated disk drives, 517, displays a map of each You can also enable crude performance monitoring by clicking on the View menu and selecting Collect Statistics from the pop-up menu. The disk icons change color to indicate basic levels of 1/O activity File Action View Oo Help sieht rea Seigees! Diss Ral Disk Group dg ‘olumes Figure 5-17 Volume Disk Map VERITAS Volume Manager Volume Operations 53 ‘Cooyricht 2006 Sin Miroaytems ne. AX RIghi Reserves. Sun Service, Reval 0 ‘Exercise: Creating Volumes and File Systems Exercise: Creating Volumes and File Systems In this exercise. you complete the following tasks: © Review key lecture points © Create a volume Add a volume mirror Add a file system to a volume Add a dirty-region log. Resize a volume and file system Create @ RAIDS volume Analyze volumes using the VEA GUL Verify ending lab status ee eee Preparation ‘The purpose of this lab is to have you create and destroy V | © To speed up volume mirror resynchronization D ¢. To control file system access 3 To prevent internal volume corruption ® 7. Whats the purpose of RAID-S logging? 2 To increase volume write performance a / b, To prevent file system corruption a } © 1p speed up volume mirror resynchronization ie d._ To control file system access ® © To prevent internal volume corruption ® | ° £27 | © a 2 ® G 8 ° 9 5:36 VERITAS Volume Manager 4,0 Administration ® \Conyrit 7004 Sun Microsytee, ne. ANRighis Revorved Sin Senos, RevisonD SUM on covennons seances Neste ateeee — eesExercise: Creating Volumes and File Systems a Task 2 — Creating a Volume ca Perform both variations of this task in the order they occur. Using the VEA GUI to Create a Volume sé To create a volume using the VEA GUI, complete the following steps 1. Display your first disk group (dg) in the grid area. 2. In the toolbar, select New Volume. 3. Configure the New Volume Wizard as follows: © — Manually select disks to use for the volume. sks for use in the new volume. © Select only one of the © Enter your assigned concatenated volume name. © Select the Concatenated layout. © Select Maxsize. © After the Maxsize calculation has completed, type 200 in the Size window and select MB from its pull-down menu. © Select No file system. © Review the final configuration parameters and click Finish, ee Note ~The Maxsize feajure can be useful when you are trying to ma dmize the size of a new volume and when you have limited dlisk drive 4. Check the status of the new volume by using the vaprint command. 5. Verify that your new volume has a single plex with one subdisk and that the volume and plex are NABLED and ACTIVE. 6. Display the new volume in the grid area 7. Click the new volume in the grid area and select Properties from its pop-up menu. 8. Examine the volume's properties and click Cancel when you are finished. VERITAS Volume Manager Volume Operations 5:37 (Copy ght2004 Sun Miconysiams, ic. Al ighs Resarved. Sun Services RevlonExercise! Creating Volumes and File Systems 4p 1) gy Using the Command Line to Create a Volume ‘To create a volume using the command li necessary, to complete the following steos: » use the man pages, as |. Open a window and use the rlogin or telnet command to log into the VaVM server as user root. Stop the volume you created in the previous procedure. # vavol -¢ disk group stop volume name 3. Recursively remove the volume. f veedit -g disk group -rf mm volume nane What is the purpose of the vxedit -£ option? 4. Re-create the 200-Mbyte concatenated volume again by using the vxassist command. You must specify the following, items: ¢ The disk group the volume should be in (-g dink_group) «The make option ¢ The name and size of the volume (volnane 200m) © The volume layout (1ayout=concat) © The disk drive (media name) you want to use 5. Record the command you used to create the volume. Note ~ It is not necessary to use the layout option for a concatenated volume. The default layout is a concatenation. Any other layout requires a ‘specific layout option. For example, layout =mirror or layout=raids. 6 Use the vaprint command to verify the volume status is showing ENRBLED and ACTIVE. Note - If there is any problem with your new volume, consult with your instructor. ee eee Se 3h vena wise weap hameee oe eee ees SUN ss ccucrvense seqnees ocrnccor eonsExercise: Creating Volumes and Fil Systems Task 3 — Adding a Volume Mirror Perform both variations of this task in the order that they occur, Using the VEA GUI to Add a Mirror ‘To add a mirror to an existing volume, complete the following steps 1. Display your new volume in the grid area and click the volume 2, Click the Actions menu and select Mirror Add from its pop-up menu, as shown in Figure 5-18, Wena nes ! Figure 5-18 Add Mirror Menu VERITAS Volume Manager Volume Operations 530 {Copia 2004 Sun Mironytama Inc. Al Fughis Reserves, Sun Service, Reviien DExeicise: Creating Volumes and File Systems hol I eS Sea tak EEE 3. Leave the first Add Mirror form configured with its default values which should include the following: *¢ Number of mirrors to add: 1 «© Layout=Concatenated ‘¢ Let Volume Manager decide which disks to use 4. On the VxVM server, check the status of the mirror resynchronization by using the vxtask List command. On the ViVM server, verify the state of your new mirvor by using the veprint command. ‘You should now see two plexes in your volume. Large mitrors take a while to synchronize, Until the resynchronization is complete, the related plox is in a TEMPRMSD state. Consult the vxinfo man page for volume state definitions. Note - Remember that you can review the command-line operations in Yyy the /vax/vx/isis/comand. log file on the VxVM server. se Using the Command Line to Add a Volume Mirror ‘To remove a mirror from a volume, and then create a new. mirror, complete the following steps 1. Ensure that both plexes (mirrors, in the volume you added are fully synchronized and show a status of ENABLED and ACTIVE. 2. Use the vxassist command to remove one of the mirrors from your volume. For example: # wwaseist -g dgk remove mirror vol_o1 3. Use the vaprint command to verify that your volume now has 2 single plex and subdisk. 4. Use the vxassist command to re-create the mirrored volume. 5, Use the alloc= parameter to specify the disk media name on which the new mirror is to be created. For example: # vaassist -¢ dgX mirror vol_01 allocwdgxo3 540 VERITAS Volume Manager 4.0 Adminitraton Corarint 2004 Sin Meronysoms. ne Al Rights Reserved. Sue Services Revlon D @ SUN oo esvcsvown seevces waw sun.com/service/suned SOSH OHCTORYVODELC OR OLOXOOOCO RECO eee ee @oeece ©@ SUM xn sovcsmenns senvecs Exercise: Creating Volumes and File Systems 6. After the vxassiet returns, use the veprint command to verify the volume has two plexes and its status is ENABLED and ACTIVE, Consult with yor instructor if you are having problems. Note— You can also move @ volume mirror to a different disk drive if itis Task 4 — Adding a File System to a Volume Perform both variations of this task in the order they occur. Using the VEA GUI to Add a File System To add a file system using the VEA GUI, complete the following steps 1. Click your mirrored volume in the grid area, and select File System New File System from the pop-up menu, Configure the New File System form as follows: ‘© Ensure that the File system type is ufs. @ Leave the Allocation at its default value (1024). » Enter your assigned mount name » Select Create mount point Deselect Read only and Honor setuid. » Select Add to file system table and mount at boot © Set the feck pass number to 2 » Examine the New file System Details menu e Examine the Mount File System Details menu. © Click OK. 3. Cn the VxVM server, verify that the following are irve: ‘The mount point is present in the root directory, © Your file system is mounted. ‘© The mount entry is in the /ete/vEatab file. The dé -k1 output seems appropriate for the volume size. VERITAS Volume Manager Volume Operations: 541 ‘Cooyrah 2004 Sun Wieronyatoma Ine AL Righis Reserved. Sun Sandcas, Raion O# mkdir /dunk © SUTT cease seiyces Exercise: Creating Volumes and File Systems 4 Create some test dota in the volume’s file system. # mkEile im /mountpoint/mytite Using the Command Line to Add a File System Review the command-line operations performed by the VEA software in the previous section. Complete the following step: Review the VEA command-line operations recorded in the log file on the VAVM server. # tail -45 /var/vx/isie/command.1og ‘The most recent commands are appended to the end of the file, Not all the details are logged in the ccamand file, such as the edits to tre /eto/vestab file. The following is a summary of using the command line tc add a file system to an existing volume, # akfs -F ufs /dev/vx/rdsk/dgX/xvol-01 409600 H vi /ete/vEstab (Gov /ex/ d8k/S3%/ 701-0 /dev/vx/x88k/daK/xv0l-01 /Tunk ufs 1 yee losging # mount -F ufs -o logging /dev/vx/dsk/dgx/svol-01 /Junk Note ~The file system vEstab and mount options enable the UPS hgging feature. UES logging is not necessary, but it offers additional file system protection and is part of the Solaris OS. VERITAS Volume Manager 4.0 Administration Corr 2004 Sun Microsites. nc. AL Rights Rasared Sun Services RevisonD wewwesun.corn/servica/suned oe *©OSOHOC GOOCH HOH HBO @ POCCSHOHSCHCHHOHTHOX OCF EDOE @ ee2e0e4 , " Exercise: Creating Volumes and File Systems Task 5- Adding a DRL Perform both variations of this task in the order they occur. Using the VEA GUI to Add a DRL To add a DRL using the VEA GUL, complete the following steps: 1. Verify there is a disk drive available for the DRL within the same isk group that does not contain cither plex of the mirrored volume. 2. Display your volume in the grid area and click it with the third mouse button. 3. Select Log Add in the volume pop-up menu, 4. In the Add Log windor a. Click Manual disk a complete the following steps: ignment b. Select a disk drive that is not part of the misrored volume. «Click OK 5. Return to the command line on the VxVM server and use the vxprint command to verify the following The mirrored volume now has a log plex © The log isnot on the same disk drive as either of the volume mirrors Note = Look at the subdisk entries to determi 6. Inthe VEA GUI, complete the following steps: a. Click the volume in the grid erea. b. Select Properties from the pop-up menu ©. Examine both the General and File System tabs. VERITAS Volume Manager Volume Operations 543 CConyint 20c4 Sun eronyaloms, Ine. Al Rights Reserved. Sun Services RevitonD CSU cece sun.conv/sarvigersunedExercise: Creating Volumes and File Systems Using the Command Line to Add a DRL The following example shows the command sequence to remove and add 2 DRL toa volume. Practice removing and adding a DRL from your volume using the command line. The disk media name you specify should be on a different disk drive than the disk drives used by the volume mirrors. ve joist remove log volume name # vaassist addlog volume nane media nane ant VERT Vee uaa do pacha Seer eee orca coe ea : @ SUM su coscrrorn seneces Ieraeleleaenee —s See S8COGTGHCABHOOBOS e @ eeo606Exercise: Creating Volumes and File Systems Task 6 — Resizing a Volume and File System Tfavolume has a file system, you can increase the size of both the volume and the file system by using either the we ‘command or the VEA GUI Note - There are other methods of increasing a volume’s size ard a file system's size. However, the VEA GUI and vxresize command reliably increase the size of both the volume and its related file system at the same time. The volume to be resized should be of the type fsgen. The vxprint ‘command displays the volume type Perform both variations of this task in the order they bccur. Using the Command Line to Resize File Systems To resize file systems using the command line, complete the following steps 1. Add 2 Mbytes to the size of your mirrored volume and file system by using the following command: # vxxesize -F ufs -g disk group volume name +2m You can also express the +2m as a ne\ ‘olume length without the plus sign. There are also -s and -x options that ensure the requested size value is appropriate. You can also specify disk media names (for example, isk01, disk02) that you want to be used for the new space. 2. Examine the new volume and file system to ensure that the changes have taken place. Large changes can take a long time. Noie = You cannot shrink a volume with a file system unless system is of VxES type. Read the veresize man page for a complete description of restrictions. VERITAS Volume Manager Volume Operations 55, Gopyrght 2004 tun ercaysome, ne. Ai Righa Ratarvad. Sun Servens, Ravan| ise: Creating Volumes and File Systems x, | Using the VEA GUI to Resize File Systems | To resize file systems using the VEA GUI, complete the following steps: 1. _In the grid area, complete the following steps: a. Display your volume. b, Select Resize Volume in the pop-up menu. your volume with the third mouse button. 2. Configure the Resize Volume form, shown in Figure 5-19, as follows: | © Enier 2 in the Add By window and select MB from its pull- down menu. ‘+ Let VSVM decide which disks to use for the additional space, | © Click OK COCSSHOOSOSCHHOEHGCHHOCDOBR OOH OOOe Figure 5-19 Resize File System Form | 3. After the task has completed, verify the results. 546 VERITAS Volume Manager 4.0 Administration Copii 2004 Sin theroeystoms, ne ABRs Reserved Sun aries, Rein SUD a sischcsioni'senoces vnsimetemawesies S©SGCHCOHOSEBSExercise: Creating Volumes and File Systems Task 7 — Creating a RAID-5 Volume In this task you create a three-column RAID-5 volume with a separate log disk (four disk drives total) in your second disk group. Complete the following steps 1. On the VxVM server, complete the following steps a. _Unmount the mirrored volume file system, b. Stop the volume ee ee Remove its mount entry from the /ete/véstab file. Destroy the mirrored volume disk group (da%). 4 vxdg destroy disk group 3. Click the remaining disk group with the third mouse button and select Add Disk to Disk Group from its pop-up menu. Using the Add Disk Wizard, add the three disk drives from the destroyed disk group to the remaining disk group. 5. On the VxVM server, calculate the available disk space using four of the disk drives in a RAID-5 volume with a log, For exaraple: 4 vxassist -g dgB maxsize layout=raidSiog ég801 dgB02 dgB03 dga04 Maximum volume 35348480 (17260Mb) A 6. Display the disk drives in your disk group in the grid area. 7. Select four of the disk drives by simultaneously pressing the Control key while using the left mouse button 8. Select the New Volume button in the toolbar. 9. Configure the New Volume form as follows: © Enter your assigned RAID-5 volume name. @ Enter 200 in the Size field. : : © Select MB from the Size pull-down nnenu. Choose RAID 5 in the Layout area. The Number of Columns field should automatically be set to 3 with logging is enabled. © Leave the default Stripe Unit Size at 32. © Click Next. Veale eae oe VERS youne anne krnCemo necro© Click Create a File System, and complete the following steps: © Select a FS Type of uts. © Enter your assigned mount point. + Click Add 10 File System Table, Mount at Boot and set the fsck ass to 2 10. Click Next in the Create File System form | Exercise: Creating Volumes and File S | 11. Click Finish in the Summary form after you verify that the configuration is correct. 12. On the VsVM server, check the status of the new RAID-5 volume by using the vxprint command. 4 vaprint -g dgB xaievol TY NAME assoc KSTAT2 LENGTH PLOFFS TATE | vy. raidvel raids ENABLED 409600 - ACTIVE pl raidvel-01 raidvol ENABLED 416512 — ACTIVE Sd dg301-01 raidvel-o1 | EIABLED 208271 0 - sd dgB0¢-01 © raidvol-o1 ENABLED 208278 0 - ed dga05-02 © raidvol-o1 ENABLED 208278 0 - | pl raidvol-o2 raidvol ENABLED 3591 - os ° ed dgu0s-01 —raidvol-02 ENABLED 3591 Note - You can add the log later to better control its placement. The disk drives are not necessarily used in the order you selected them. 13. On the VxVM server, examine the volume creation commands. # tail -25 /var/vx/ieis/ccemand.0g | 14. In the VEA GUI, click the volume with the third mouse button and select Properties from its pop-up menu. | 15. Examine both the General and File System tabs. 16, Cancel the Volume Properties window. 17. Edit the /ete/yéstab file, and comment out or delete the obsolete ‘mount entry from the earlier mir ored volume file system mount, ‘You must remove or comment out obsolete mount entries because they cause errors at boot time: | 548, VERITAS Volume Manager 4.0 Adminictration oprah 2004 Sun Weroeatas. In Al Rights Rasared. Sin Sonics, Raion SUN EDUCATIONAL SERVICES Yiw.suin.com/service/euned SHCTCHSSCHOHHSHGOHODHAO HTH TEGHHFHOOBHOHGCOLOSFOVOHEHBOSi 4 F ee i @ Sun Exercise: Creating Volumes and File Systems Task 8 — Analyzing Volumes Using the VEA GUI The following sections detail different VEA GUI features that are used to analyze the structure and performance of VxVM volumes, Displaying Volume Layout Details To display volume layout details, complete the following steps: 1, Display your volumes in the grid area and complete the following, steps: a. Click your RAID-5 volume with the third mouse button b. Select Layout View from the pop-up menu ‘As shown in Figure 5-20, use the third mouse button to highlight volume component and examine its properties. auerors Exige S23 5 [Usage RAID-5 0% [Subdisk eg805-01 lSue 204600 IBeume: “2 Figure 5-20 Volume Layout Window VERITAS Volume Manager Volume Operations 549 Copyright 2008 Sun wicrosyslams ne Agha Resacved. Sun Servees, Raven SUN EDUCATIONAL SERVICES www.sun.com/senviau/siunedExercise: Creating Volumes and File Systems 3, Examine the pop-up menus for each of the different components, 4, Close the Volume Layout window. Viewing Disk Volume Mapping and Performance ‘To view volume-to-disk mapping and performance, complete the following steps: 1. In the grid area, click your disk group with the third mouse button, and select Volume/Disk from the pop-up menu, The Volume/Disk map, shown in Figure 5-21, assists In volume planning and disk utilization assesment. Figure 5-21 Volume/Disk Map 2. Click the View menu with the third mouse button and select Data Gathering Options from the pull-down menu. 550 VERITAS Volume Manager 4.0 Administration Copyright 2004 Sur hhereyatere, ne Al Rigs Reserved Sun Survives, ReiionD @ een G@SG@SOCHH HEEB eo e@be ° __Exercise: Creating Volumes and File Systems 3. Perform the following steps: a. Modify the Refresh Interval to 5 seconds and 5. Requests from the pull-down menu, as shown in b. Click OK. ee ee } | Wg Tirre (micrseconis) / Read Blotk Figure 5-22 Data Gathering Options VERITAS Volume Manager Volume Operations. 554 ‘Cepyigh 2004 Sun Meronynters he AX Rights Reserved. Sen Services Revbion DExercise: Creating Volumes and File Systems 4, Enable performance monitoring by performing the following steps: a, Click the View menu with the third mouse button. b. Select Collect Statistics from the pop-up menu, as shown in ; Figure 5-23. P| east—104.cast— Volume S©SCSCHOSGHSHGHHCHOHBKEOHCOOE, 2 5 > 9 Figure 5-23 Enabling Performance Monitoring ® When performance monitoring is enabled, the relative 1/O activity of each volume disk drive is indicated by color changes > in the small disk icons shown in Figure 5-23. i Red indicates the highest level of I/O activity or slowest performance. This information can be used to identify basic e performance bottlenecks in disk group volumes. cs 582 VERITAS Volume Manager $.0 Administration Gooyignt 2008 Son Wiereys ne A Rigs Reanered. Sen Services, Revlon , OSU si escusga ot ices yawn sun comiservice/aunad