100 002687 A

CONFIDENTIAL - NOT FOR DISTRIBUTION
Veritas Storage
Foundation 6.0 for
UNIX: Install and
Configure
100-002687-A
COURSE DEVELOPERS Copyright 2012 Symantec Corporation. All rights reserved.
Bilge Gerrits Symantec, the Symantec Logo, and VERITAS are trademarks or
James Kenney registered trademarks of Symantec Corporation or its affiliates in
Carly Storrie the U.S. and other countries. Other names may be trademarks of
their respective owners.
THIS PUBLICATION IS PROVIDED AS IS AND ALL
LEAD SUBJECT MATTER EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS
EXPERTS AND WARRANTIES, INCLUDING ANY IMPLIED
Brad Willer WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
TECHNICAL SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR
CONTRIBUTORS AND INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
REVIEWERS CONNECTION WITH THE FURNISHING, PERFORMANCE,
Margy Cassidy OR USE OF THIS PUBLICATION. THE INFORMATION
Steve Evans CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT
Joe Gallagher NOTICE.
Freddie Gilyard No part of the contents of this book may be reproduced or
Graeme Gofton transmitted in any form or by any means without the written
Tony Griffiths permission of the publisher.
Gene Henriksen Veritas Storage Foundation 6.0 for UNIX: Install and Configure
Kleber Saldanha Symantec Corporation
Kalyan Subramaniyam World Headquarters
Anand Raj Vengadassalam 350 Ellis Street
Stephen Williams Mountain View, CA 94043
Randal Williams United States
http://www.symantec.com
Copyright 2012 Symantec Corporation. All rights reserved.

2
Table of Contents
Course Introduction
What is storage virtualization? ................................................................ Intro-2
Introducing Veritas Storage Foundation.................................................. Intro-5
Veritas Storage Foundation curriculum ................................................... Intro-9
Lesson 1: Virtual Objects

Operating system storage devices and virtual data storage ........................ 1-3
Volume Manager storage objects............................................................... 1-11
VxVM volume layouts and RAID levels ...................................................... 1-13
Lesson 2: Installing Storage Foundation and Accessing SF Interfaces

Preparing to install Storage Foundation ....................................................... 2-3
Installing Storage Foundation..................................................................... 2-11
Storage Foundation resources ................................................................... 2-19
Storage Foundation user interfaces ........................................................... 2-23
Lesson 3: Getting Started with Veritas Operations Manager (VOM)

Veritas Operations Manager overview ......................................................... 3-3
Installing the VOM management server ..................................................... 3-11
Installing additional functionality using VOM add-ons ................................ 3-16
Changing Storage Foundation hosts to managed hosts ............................ 3-19
Lesson 4: Creating a Volume and File System

Preparing disks and disk groups for volume creation................................... 4-3
Creating a volume and adding a file system .............................................. 4-11
Displaying disk and disk group information ................................................ 4-15
Displaying volume configuration information.............................................. 4-21
Removing volumes, disks, and disk groups ............................................... 4-24
Lesson 5: Working with Volumes with Different Layouts

Volume layouts............................................................................................. 5-3
Creating volumes with various layouts ......................................................... 5-9
Creating a layered volume ......................................................................... 5-12
Allocating storage for volumes ................................................................... 5-20

Using the Storage Provisioning add-on in VOM......................................... 5-21
Lesson 6: Making Configuration Changes

Administering mirrored volumes................................................................... 6-3
Resizing a volume and a file system .......................................................... 6-12
Moving data between systems ................................................................... 6-17
Renaming VxVM objects ............................................................................ 6-21
Managing disk group versions and formats................................................ 6-23

3 Table of Contents iii
Lesson 7: Administering File Systems
Benefits of using Veritas File System ........................................................... 7-3
Using Veritas File System commands .......................................................... 7-8
Logging in VxFS ......................................................................................... 7-15
Controlling file system fragmentation.......................................................... 7-19
Using thin provisioning disk arrays ............................................................. 7-26
Appendix A: Labs
Lab 1: VMware Workstation Introduction..................................................... A-7
Exercise 1: Starting virtual machines (VMware Workstation)............... A-10
Exercise 2: Logging on to virtual machines (VMware Workstation) ..... A-12
Exercise 3: Adjusting the VMware view (VMware Workstation)........... A-13
Exercise 4: Running basic commands (VMware Workstation)............. A-14
Lab 1: Hatsize Introduction ........................................................................ A-17
Exercise 1: Connecting to the lab environment (Hatsize) .................... A-20
Exercise 2: Connecting to additional virtual machines (Hatsize).......... A-23
Exercise 3: Running basic commands (Hatsize).................................. A-25
Exercise 4: Restarting virtual machines (Hatsize)................................ A-28
Lab 2: Installing SF and Accessing SF Interfaces ..................................... A-31
Exercise 1: Verifying that the system meets installation requirements A-33
Exercise 2: Installing Veritas Storage Foundation................................ A-36
Exercise 3: Performing post-installation and version checks ............... A-38
Exercise 4: Optional lab: Setting up Veritas Enterprise Administrator . A-40
Exercise 5: Optional lab: Text-based VxVM menu interface ................ A-42
Exercise 6: Optional lab: Accessing CLI commands............................ A-43
Lab 3: Getting Started with VOM ............................................................... A-45
Exercise 1: Installing the VOM management server (MS) ................... A-47
Exercise 2: Adding managed hosts to the MS ..................................... A-49
Exercise 3: Adding the active management add-on............................. A-51
Lab 4: Creating a Volume and File System ............................................... A-53
Exercise 1: Creating a volume and file system: VOM .......................... A-54
Exercise 1: Creating disk groups, volumes and file systems: CLI........ A-55
Exercise 2: Removing volumes and disks: CLI .................................... A-57
Exercise 3: Destroying disk data using disk shredding: CLI................. A-58
Exercise 4: Optional lab: Creating disk groups, volumes, and file
systems: VOM ...................................................................................... A-60
Exercise 5: Optional lab: Removing volumes, disks, and disk

groups: VOM ........................................................................................ A-62
Lab 5: Working with Volumes with Different Layouts................................. A-63
Exercise 1: Creating volumes with different layouts: CLI ..................... A-65
Exercise 2: Optional lab: Setting up Storage Provisioning: VOM......... A-67
Exercise 3: Optional lab: Creating layered volumes............................. A-70
Exercise 4: Optional lab: Creating volumes with user defaults: CLI..... A-71
Lab 6: Making Configuration Changes ...................................................... A-73
Exercise 1: Administering mirrored volumes ........................................ A-75
Exercise 2: Resizing a volume and file system .................................... A-77
Exercise 3: Renaming a disk group...................................................... A-78

4 iv Veritas Storage Foundation 6.0 for UNIX: Install and Configure
Exercise 4: Moving data between systems........................................... A-79
Exercise 5: Optional lab: Resizing a file system only............................ A-81
Exercise 6: Optional lab: Converting a non-cds disk group .................. A-83
Lab 7: Administering File Systems ............................................................. A-85
Exercise 1: Preparation for defragmenting a Veritas File System lab... A-87
Exercise 2: Defragmenting a Veritas File System................................. A-88
Exercise 3: SmartMove......................................................................... A-91
Exercise 4: Thin reclamation................................................................. A-92
Exercise 5: Optional lab: Testing the Mountlock feature....................... A-94
Exercise 6: Optional lab: Reading the file change log (FCL) ................ A-95
Exercise 7: Optional lab: Defragmenting a Veritas File System ........... A-97
Appendix B: Lab Solutions

Lab 1: VMware Workstation Introduction .................................................... B-7
Exercise 1: Starting virtual machines (VMware Workstation) ............... B-10
Exercise 2: Logging on to virtual machines (VMware Workstation)...... B-14
Exercise 3: Adjusting the VMware view (VMware Workstation) ........... B-16
Exercise 4: Running basic commands (VMware Workstation) ............. B-17
Lab 1: Hatsize Introduction......................................................................... B-23
Exercise 1: Connecting to the lab environment (Hatsize) ..................... B-26
Exercise 2: Connecting to additional virtual machines (Hatsize) .......... B-29
Exercise 3: Running basic commands (Hatsize) .................................. B-34
Exercise 4: Restarting virtual machines (Hatsize) ................................ B-40
Lab 2: Installing SF and Accessing SF Interfaces...................................... B-45
Exercise 1: Verifying that the system meets installation requirements . B-47
Exercise 2: Installing Veritas Storage Foundation ................................ B-55
Exercise 3: Performing post-installation and version checks................ B-59
Exercise 4: Optional lab: Setting up Veritas Enterprise Administrator .. B-63
Exercise 5: Optional lab: Text-based VxVM menu interface................. B-68
Exercise 6: Optional lab: Accessing CLI commands ............................ B-70
Lab 3: Getting Started with VOM................................................................ B-73
Exercise 1: Installing the VOM management server (MS) .................... B-75
Exercise 2: Adding managed hosts to the MS ...................................... B-80
Exercise 3: Adding the active management add-on ............................. B-83
Lab 4: Creating a Volume and File System................................................ B-87
Exercise 1: Creating a volume and file system: VOM........................... B-88
Exercise 1: Creating disk groups, volumes and file systems: CLI ........ B-89
Exercise 2: Removing volumes and disks: CLI..................................... B-94
Exercise 3: Destroying disk data using disk shredding: CLI ................. B-95
systems: VOM....................................................................................... B-98
groups: VOM....................................................................................... B-104
Lab 5: Working with Volumes with Different Layouts ............................... B-107
Exercise 1: Creating volumes with different layouts: CLI.................... B-109
Exercise 2: Optional lab: Setting up Storage Provisioning: VOM ....... B-114
Exercise 3: Optional lab: Creating layered volumes ........................... B-119

5 Table of Contents v
Exercise 4: Optional lab: Creating volumes with user defaults: CLI... B-121
Lab 6: Making Configuration Changes .................................................... B-125
Exercise 1: Administering mirrored volumes ...................................... B-127
Exercise 2: Resizing a volume and file system .................................. B-130
Exercise 3: Renaming a disk group.................................................... B-132
Exercise 4: Moving data between systems ........................................ B-135
Exercise 5: Optional lab: Resizing a file system only ......................... B-140
Exercise 6: Optional lab: Converting a non-cds disk group................ B-143
Lab 7: Administering File Systems .......................................................... B-147
Exercise 1: Preparation for defragmenting a Veritas File System lab B-149
Exercise 2: Defragmenting a Veritas File System .............................. B-151
Exercise 3: SmartMove ...................................................................... B-159
Exercise 4: Thin reclamation .............................................................. B-162
Exercise 5: Optional lab: Testing the Mountlock feature .................... B-167
Exercise 6: Optional lab: Reading the file change log (FCL).............. B-170
Exercise 7: Optional lab: Defragmenting a Veritas File System......... B-174
Appendix C: Using the VEA

Creating a disk group and a volume and adding a file system .................... C-3
Displaying disk, disk group and volume information.................................... C-6
Removing volumes, disks, and disk groups............................................... C-10
Performing basic administration tasks on volumes and file systems......... C-11
Index

6 vi Veritas Storage Foundation 6.0 for UNIX: Install and Configure
7
Course Introduction

What is storage virtualization?
Storage virtualization is the process of taking multiple physical storage devices
and combining them into logical (virtual) storage devices that are presented to the
operating system, applications, and users. Storage virtualization builds a layer of
abstraction above the physical storage so that data is not restricted to specific
hardware devices, creating a flexible storage environment. Storage virtualization
simplifies management of storage and potentially reduces cost through improved
hardware utilization and consolidation.
With storage virtualization, the physical aspects of storage are masked to users.
Administrators can concentrate less on physical aspects of storage and more on
delivering access to necessary data.
Benefits of storage virtualization include:
Greater IT productivity through the automation of manual tasks and simplified
administration of heterogeneous environments

Increased application return on investment through improved throughput and
increased uptime
Lower hardware costs through the optimized use of hardware resources

8 Intro2 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
How is storage virtualization used in your environment?
The way in which you use storage virtualization, and the benefits derived from
storage virtualization, depend on the nature of your IT infrastructure and your
specific application requirements. Three main types of storage virtualization used
today are:
Storage-based
Host-based
Network-based
Most companies use a combination of these three types of storage virtualization
solutions to support their chosen architecture and application needs.
The type of storage virtualization that you use depends on factors, such as the:
Heterogeneity of deployed enterprise storage arrays
Need for applications to access data contained in multiple storage devices

Importance of uptime when replacing or upgrading storage
Need for multiple hosts to access data within a single storage device
Value of the maturity of technology
Investments in a SAN architecture
Level of security required
Level of scalability needed

9 Course Introduction
Intro3
Storage-based storage virtualization
Storage-based storage virtualization refers to disks within an individual array that
are presented virtually to multiple servers. Storage is virtualized by the array itself.
For example, RAID arrays virtualize the individual disks (that are contained within
the array) into logical LUNS, which are accessed by host operating systems using
the same method of addressing as a directly-attached physical disk.
This type of storage virtualization is useful under these conditions:
You need to have data in an array accessible to servers of different operating
systems.
All of a servers data needs are met by storage contained in the physical box.
You are not concerned about disruption to data access when replacing or
upgrading the storage.
The main limitation to this type of storage virtualization is that data cannot be
shared between arrays, creating islands of storage that must be managed.
Host-based storage virtualization

Host-based storage virtualization refers to disks within multiple arrays and from
multiple vendors that are presented virtually to a single host server. For example,
software-based solutions, such as Veritas Storage Foundation, provide host-based
storage virtualization. Using Veritas Storage Foundation to administer host-based
storage virtualization is the focus of this training.
Host-based storage virtualization is useful under these conditions:
A server needs to access data stored in multiple storage devices.
You need the flexibility to access data stored in arrays from different vendors.
Additional servers do not need to access the data assigned to a particular host.
Maturity of technology is a highly important factor to you in making IT
decisions.
Note: By combining Veritas Storage Foundation with clustering technologies,
such as Veritas Cluster Volume Manager, storage can be virtualized to multiple
hosts of the same operating system.
Network-based storage virtualization

Network-based storage virtualization refers to disks from multiple arrays and

multiple vendors that are presented virtually to multiple servers. Network-based
storage virtualization is useful under these conditions:
You need to have data accessible across heterogeneous servers and storage
devices.
You require central administration of storage across all Network Attached
Storage (NAS) systems or Storage Area Network (SAN) devices.
You want to ensure that replacing or upgrading storage does not disrupt data
access.
You want to virtualize storage to provide block services to applications.

Introducing Veritas Storage Foundation
Symantec storage management solutions address the increasing costs of managing
mission-critical data and disk resources in Direct Attached Storage (DAS) and
Storage Area Network (SAN) environments.
At the heart of these solutions is Veritas Storage Foundation, which includes
Veritas Volume Manager (VxVM), Veritas File System (VxFS), and Veritas
Dynamic Multi-Pathing (DMP) products. Independently, these components
provide key benefits. When used together as an integrated solution, they deliver
the highest possible levels of performance, availability, and manageability for
heterogeneous storage environments.
What is Veritas Volume Manager?

Veritas Volume Manager, the industry-leader in storage virtualization, is an easy-
to-use, online storage management solution for organizations that require
uninterrupted, consistent access to mission-critical data. VxVM enables you to

apply business policies to configure, share, and manage storage without worrying
about the physical limitations of disk storage. VxVM reduces the total cost of
ownership by enabling administrators to easily build storage configurations that
improve performance and increase data availability.
Working in conjunction with Veritas File System, Veritas Volume Manager creates
a foundation for other value-added technologies. such as SAN environments,
clustering and failover, automated management, backup and HSM, and remote
browser-based management.

Intro5
What is Veritas File System?
A file system is a collection of directories organized into a structure that enables
you to locate and store files. The main purposes of a file system are to:
Provide shared access to data storage.
Provide structured access to data.
Control access to data.
Provide a common, portable application interface.
Enable the manageability of data storage.
The value of a file system depends on its integrity and performance. Veritas File
System is an extent-based, intent logging file system. It is designed for use in
operating environments that require high performance and availability and deal
with large amounts of data.
What is Veritas Dynamic Multi-Pathing?

Veritas Dynamic Multi-Pathing is designed to manage seamlessly multiple access
paths to a single storage device. It provides improved storage I/O performance and
availability across heterogeneous server and storage platforms using intelligent
algorithms and load balancing for faster throughput and path failover.

Benefits of Veritas Storage Foundation
Commercial system availability now requires continuous uptime in many
implementations. Systems must be available 24 hours a day, 7 days a week, and
365 days a year. Veritas Storage Foundation reduces the cost of ownership by
providing capacity, availability, and performance enhancements for these
enterprise computing environments.
Capacity
VxVM, VxFS, and DMP provide consistent management across Solaris, HP-
UX, AIX, and Linux platforms.
Storage Foundation provides additional benefits for array environments, such
as inter-array mirroring and hardware independent dynamic multipathing.
Hosts can be replaced without modifying storage.
Hosts with different operating systems can access the same storage.
Storage devices can be spanned.
Performance
I/O throughput can be maximized by measuring and modifying volume layouts
while storage remains online.
Extent-based allocation of space for files minimizes file level access time.
Read-ahead buffering dynamically tunes itself to the volume layout.
Aggressive caching of writes greatly reduces the number of disk accesses.
Direct I/O performs file I/O directly into and out of user buffers.
With VxFS, certain features are available for maximizing performance in a
database environment.
With VxFS, you can create a multi-tier storage environment where you benefit
from using a mixture of high-end disk arrays, solid state disks, low-end disk
arrays, and JBODs.
Availability
Management of storage and the file system is performed online in real time,
eliminating the need for planned downtime.
Online volume and file system management can be centralized through an
intuitive, easy-to-use Web console that is implemented using Veritas

Operations Manager.
Through software RAID techniques, storage remains available in the event of
hardware failure.
Recovery time is minimized with logging and background mirror
resynchronization.
Logging of file system changes enables fast file system recovery.
A snapshot of a file system provides an internally consistent, read-only image
for backup, and file system checkpoints provide read-writable snapshots.

Intro7
Benefits of VxVM and RAID arrays
RAID arrays virtualize individual disks into logical LUNS which are accessed by
host operating systems as physical devices, that is, using the same method of
addressing as a directly-attached physical disk.
VxVM virtualizes both the physical disks and the logical LUNs presented by a
RAID array. Modifying the configuration of a RAID array may result in changes in
SCSI addresses of LUNs, requiring modification of application configurations.
VxVM provides an effective method of reconfiguring and resizing storage across
the logical devices presented by a RAID array.
When using VxVM with RAID arrays, you can leverage the strengths of both
technologies:
You can use VxVM to mirror between arrays to improve disaster recovery
protection against the failure of an array, particularly if one array is remote.
Arrays can be of different manufacture or type; that is, one array can be a
RAID array and the other a JBOD.
VxVM facilitates data reorganization and maximizes available resources.
VxVM improves overall performance by making I/O activity parallel for a
volume through more than one I/O path to and within the array.
You can use snapshots with mirrors in different locations, which is beneficial
for disaster recovery and off-host processing.
If you include Veritas Volume Replicator (VVR) or Veritas File Replicator
(VFR) in your environment, VVR and VFR can be used to provide hardware-
independent replication services.

Veritas Storage Foundation curriculum
Veritas Storage Foundation for UNIX: Install and Configure training is designed
to provide you with comprehensive instruction on making the most of Veritas
Storage Foundation.

Intro9
Veritas Storage Foundation for UNIX: Install and Configure overview
The Install and Configure training provides comprehensive instruction on
operating the file and disk management foundation products: Veritas Volume
Manager (VxVM) and Veritas File System (VxFS). In this training, you learn how
to combine file system and disk management technology to ensure easy
management of all storage and maximum availability of essential data.
Objectives
After completing the Install and Configure training, you will be able to:
Identify VxVM virtual storage objects and volume layouts.
Install and configure Storage Foundation.
Administer the SF environment from a centralized Web console using Veritas
Operations Manager (VOM).
Configure and manage disks and disk groups.

Create concatenated, striped, mirrored, and layered volumes.
Configure volumes by adding mirrors and logs and resizing volumes and file
systems.
Perform file system administration.

Veritas Storage Foundation for UNIX: Manage and Administer
overview
The Manage and Administer training provides instruction on device management,
performance monitoring, and advanced configuration and administration for users
of Veritas Storage Foundation.
Objectives
After completing the Manage and Administer training, you will be able to:
Monitor VxVM and change volume layouts to improve performance.
Manage the dynamic multipathing feature.
Resolve hardware problems that result in disk and disk group failures.
Create and manage point-in-time copies for off-host and on-host processing.
Use the compression, deduplication and FileSnap features of Veritas File
System to optimize storage utilization.

Remotely mirror your data across different sites.
Use SmartTier, previously known as dynamic storage tiering, for optimal
storage allocation.
Replicate a Veritas file system using the Veritas File Replicator.

Intro11
Additional course resources
Appendix A: Lab Exercises

This section contains hands-on exercises that enable you to practice the concepts
and procedures presented in the lessons.
Appendix B: Lab Solutions

This section contains detailed solutions to the lab exercises for each lesson.
Appendix C: Using the VEA

This section contains instructions on how to perform administrative tasks from the
Veritas Enterprise Administrator Graphical User Interface.
Typographic conventions used in this course

The following tables describe the typographic conventions used in this course.

Typographic conventions in text and commands
Convention Element Examples

Courier New, Command input, To display the robot and drive configuration:
bold both syntax and tpconfig -d
examples
To display disk information:
vxdisk -o alldgs list
Courier New, Command output In the output:
plain Command protocol_minimum: 40
names, directory protocol_maximum: 60
names, file protocol_current: 0
names, path Locate the altnames directory.
names, URLs
Go to http://www.symantec.com.
when used within
regular text Enter the value 300.
paragraphs.
Courier New, Variables in To install the media server:
Italic, bold or command syntax, /cdrom_directory/install
plain and examples:
To access a manual page:
Variables in
man command_name
command input
are Italic, plain. To display detailed information for a disk:
Variables in vxdisk -g disk_group list
command output dm_name
are Italic, bold.
Typographic conventions in graphical user interface descriptions
Convention Element Examples

Greater than (>) sign and Menu navigation paths Select File > Save.
bold font
Initial capitalization and Buttons, menus, windows, Select the Next button.
bold font options, and other interface Open the Task Status
elements window.
Remove the checkmark

from the Print File check
box.

Intro13

Lesson 1
Virtual Objects

21

22 12 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
1
Operating system storage devices and virtual data storage

The different UNIX flavors supported by Storage Foundation each have their own
unique way of detecting and using storage devices. Some platforms, such as
Solaris and Linux, use a partition table and disk partitions to organize data on the
physical disks and others, such as AIX and HP-UX, use OS-native logical volume
management software to detect disks as physical volumes.
Storage Foundation hides the complexity of the device management layer by
introducing a virtual data layer that works the same on all of these UNIX
platforms. The way Volume Manager uses disks to organize data is explained in
detail later in this lesson.
However, the key point to note is that Volume Manager can only use a device if it
is recognized by the operating system on the Storage Foundation host. Therefore,
if a disk device is not visible in Volume Manager, you first have to ensure that the
operating system detects it correctly.
Use the following OS-specific commands to list storage devices on individual

platforms. Refer to manual pages for specific command syntax.
Operating system Command to use

Solaris format
Linux fdisk
HP-UX ioscan
AIX lsdev

23 Lesson 1 Virtual Objects
13
Operating system disk naming
Solaris
You locate and access the data on a physical disk by using a device name that
specifies the controller, target ID, and disk number. A typical device name uses the
format: c#t#d#.
c# is the controller number.
t# is the target ID.
d# is the logical unit number (LUN) of the drive attached to the target.
If a disk is divided into partitions, you also specify the partition number in the
device name:
s# is the partition (slice) number.
For example, the device name c0t0d0s1 is connected to controller number 0 in the
system, with a target ID of 0, physical disk number 0, and partition number 1 on

the disk.
HP-UX
Traditionally, you locate and access the data on a physical disk by using a device
name that specifies the controller, target ID, and disk number. A typical traditional
device name uses the format: c#t#d#.
c# is the controller number.
t# is the target ID.
d# is the logical unit number (LUN) of the drive attached to the target.

For example, the c0t0d0 device name is connected to the controller number 0 in
the system, with a target ID of 0, and the physical disk number 0.
With HP-UX 11iv3, a new method called agile view has been introduced. The new
convention uses the /dev/[r]disk/diskN name where N is the decimal
instance number for the disk. This is called a persistent device special file name. 1
The persistent device special file names are not available before HP-UX 11iv3.
AIX
Every device in AIX is assigned a location code that describes its connection to the
system. The general format of this identifier is AB-CD-EF-GH, where the letters
represent decimal digits or uppercase letters. The first two characters represent the
bus, the second pair identify the adapter, the third pair represent the connector, and
the final pair uniquely represent the device. For example, a SCSI disk drive might
have a location identifier of 04-01-00-6,0. In this example, 04 means the PCI bus,
01 is the slot number on the PCI bus occupied by the SCSI adapter, 00 means the
only or internal connector, and the 6,0 means SCSI ID 6, LUN 0.
However, this data is used internally by AIX to locate a device. The device name
that a system administrator or software uses to identify a device is less hardware
dependant. The system maintains a special database called the Object Data
Manager (ODM) that contains essential definitions for most objects in the system,
including devices. Through the ODM, a device name is mapped to the location
identifier. The device names are referred to by special files found in the /dev
directory. For example, the SCSI disk identified previously might have the device
name hdisk3 (the fourth hard disk identified by the system). The device named
hdisk3 is accessed by the file name /dev/hdisk3.
If a device is moved so that it has a different location identifier, the ODM is
updated so that it retains the same device name, and the move is transparent to
users. This is facilitated by the physical volume identifier stored in the first sector
of a physical volume. This unique 128-bit number is used by the system to
recognize the physical volume wherever it may be attached because it is also
associated with the device name in the ODM.
Linux
On Linux, device names are displayed in the format:
sdx[N]
hdx[N]
In the syntax:
sd refers to a SCSI disk, and hd refers to an EIDE disk.
x is a letter that indicates the order of disks detected by the operating system.
For example, sda refers to the first SCSI disk, sdb refers to the second SCSI
disk, and so on.
N is an optional parameter that represents a partition number in the range 1
through 16. For example, sda7 references partition 7 on the first SCSI disk.
Primary partitions on a disk are 1, 2, 3, 4; logical partitions have numbers 5 and up.
If the partition number is omitted, the device name indicates the entire disk.
15
Disk arrays
Reads and writes on unmanaged physical disks can be a relatively slow process,
because disks are physical devices that require time to move the heads to the
correct position on the disk before reading or writing. If all of the read and write
operations are performed to individual disks, one at a time, the read-write time can
become unmanageable.
A disk array is a collection of physical disks. Performing I/O operations on
multiple disks in a disk array can improve I/O speed and throughput.
Hardware arrays present disk storage to the host operating system as LUNs. A
LUN can be made up of a single physical disk, a collection of physical disks, or
even a portion of a physical disk. From the operating system point of view, a LUN
corresponds to a single storage device.
Multipathing
Some disk arrays provide multiple ports to access disk devices. These ports,
coupled with the host bus adaptor (HBA) controller and any data bus or I/O
processor local to the array, compose multiple hardware paths to access the disk
devices. This is called multipathing.
In a multipathing environment, a single storage device may appear to the operating
system as multiple storage devices. Special multipathing software is usually
required to administer multipathed storage devices. Veritas Dynamic Multi-
Pathing (DMP) product which is part of the Storage Foundation software provides
seamless management of multiple access paths to storage devices in heterogeneous
operating system and storage environments.
1
Example array structure

In an array, the LUNs are a virtual presentation. Therefore, you cannot know
where in the array the actual data will be put. That means you have no control over
the physical conditions.
The array in the slide contains slots for 14 physical disks, and the configuration
places 12 physical disks in the array. These physical disks are paired together into
6 mirrored RAID groups. In each RAID group, 12 logical units, or LUNs, are
created. These LUNs appear to hosts as SAN-based SCSI disks. The remaining
two disks are used as spares in case one of the active disks fails.

17
Virtual storage management
Veritas Volume Manager creates a virtual level of storage management above the
physical device level by creating virtual storage objects. The virtual storage object
that is visible to users and applications is called a volume.
What is a volume?
A volume is a virtual object, created by Volume Manager, that stores data. A
volume consists of space from one or more physical disks on which the data is
physically stored.
How do you access a volume?

Volumes created by VxVM appear to the operating system as physical disks, and
applications that interact with volumes work in the same way as with physical
disks. All users and applications access volumes as contiguous address space using
special device files in a manner similar to accessing a disk partition.
Volumes have block and character device nodes in the /dev tree. You can supply
the name of the path to a volume in your commands and programs, in your file
system and database configuration files, and in any other context where you would
otherwise use the path to a physical disk partition.

1
Volume Manager-controlled disks

With Volume Manager, you enable virtual data storage by bringing a disk under
Volume Manager control. By default, Volume Manager uses a cross-platform data
sharing (CDS) disk layout. A CDS disk is consistently recognized by all VxVM-
supported UNIX platforms and consists of:
OS-reserved area: To accommodate platform-specific disk usage, 128K is
reserved for disk labels, platform blocks, and platform-coexistence labels.
Private region: The private region stores information, such as disk headers,
configuration copies, and kernel logs, in addition to other platform-specific
management areas that VxVM uses to manage virtual objects. The private
region represents a small management overhead:
Operating System Default Block/Sector Size Default Private Region Size

Solaris 512 bytes 65536 sectors (32M)

HP-UX 1024 bytes 32768 sectors (32M)
AIX 512 bytes 65536 sectors (32M)
Linux 512 bytes 65536 sectors (32M)
Public region: The public region consists of the remainder of the space on the
disk. The public region represents the available space that Volume Manager
can use to assign to volumes and is where an application stores data. Volume
Manager never overwrites this area unless specifically instructed to do so.

19
Comparing CDS and other VxVM disk formats
In addition to the default CDS disk format, Volume Manager supports other
platform-specific disk formats. These disk formats are used for bringing the boot
disk under VxVM control on operating systems that support that capability.
On platforms that support bringing the boot disk under VxVM control, CDS disks
cannot be used for boot disks. CDS disks have specific disk layout requirements
that enable a common disk layout across different platforms, and these
requirements are not compatible with the particular platform-specific requirements
of boot disks. Therefore, when placing a boot disk under VxVM control, you must
use a non-default disk format (sliced on Solaris and Linux, hpdisk on HP-UX).
For nonboot disks, you can convert CDS disks to other disk layout formats and
vice versa by using VxVM utilities.

1
Volume Manager storage objects

Disk groups
A disk group is a collection of VxVM disks that share a common configuration.
You group disks into disk groups for management purposes, such as to hold the
data for a specific application or set of applications. For example, data for
accounting applications can be organized in a disk group called acctdg. A disk
group configuration is a set of records with detailed information about related
Volume Manager objects in a disk group, their attributes, and their connections.
Volume Manager objects cannot span disk groups. For example, a volumes
subdisks, plexes, and disks must be derived from the same disk group as the
volume. You can create additional disk groups as necessary. Disk groups enable
you to group disks into logical collections. Disk groups and their components can
be moved as a unit from one host machine to another.
Volume Manager disks

A Volume Manager (VxVM) disk represents the public region of a physical disk
that is under Volume Manager control. Each VxVM disk corresponds to one
physical disk. Each VxVM disk has a unique virtual disk name called a disk media
name. The disk media name is a logical name used for Volume Manager
administrative purposes. Volume Manager uses the disk media name when
assigning space to volumes. A VxVM disk is given a disk media name when it is
added to a disk group.
Default disk media name: diskgroup##

111
You can supply the disk media name or allow Volume Manager to assign a default
name. The disk media name is stored with a unique disk ID to avoid name
collision. After a VxVM disk is assigned a disk media name, the disk is no longer
referred to by its physical address. The physical address (for example, c#t#d# or
hdisk#) becomes known as the disk access record.
Subdisks
A VxVM disk can be divided into one or more subdisks. A subdisk is a set of
contiguous disk blocks that represent a specific portion of a VxVM disk, which is
mapped to a specific region of a physical disk. A subdisk is a subsection of a disks
public region. A subdisk is the smallest unit of storage in Volume Manager.
Therefore, subdisks are the building blocks for Volume Manager objects.
A subdisk is defined by an offset and a length in sectors on a VxVM disk.
Default subdisk name: DMname-##
A VxVM disk can contain multiple subdisks, but subdisks cannot overlap or share
the same portions of a VxVM disk. Any VxVM disk space that is not reserved or
that is not part of a subdisk is free space. You can use free space to create new
subdisks.
Conceptually, a subdisk is similar to a partition. Both a subdisk and a partition
divide a disk into pieces defined by an offset address and length. Each of those
pieces represent a reservation of contiguous space on the physical disk. However,
while the maximum number of partitions to a disk is limited by some operating
systems, there is no theoretical limit to the number of subdisks that can be attached
to a single plex. This number has been limited by default to a value of 4096. If
required, this default can be changed, using the vol_subdisk_num tunable
parameter. For more information on tunable parameters, see the Veritas Storage
Foundation and High Availability Solutions Tuning Guide.
Plexes
Volume Manager uses subdisks to build virtual objects called plexes. A plex is a
structured or ordered collection of subdisks that represents one copy of the data in
a volume. A plex consists of one or more subdisks located on one or more physical
disks. The length of a plex is determined by the last block that can be read or
written on the last subdisk in the plex.

Default plex name: volume_name-##
Volumes
A volume is a virtual storage device that is used by applications in a manner
similar to a physical disk. Due to its virtual nature, a volume is not restricted by the
physical size constraints that apply to a physical disk. A VxVM volume can be as
large as the total of available, unreserved free physical disk space in the disk
group. A volume consists of one or more plexes.

1
VxVM volume layouts and RAID levels

RAID
RAID is an acronym for Redundant Array of Independent Disks. RAID is a
storage management approach in which an array of disks is created, and part of the
combined storage capacity of the disks is used to store duplicate information about
the data in the array. By maintaining a redundant array of disks, you can regenerate
data in the case of disk failure.
RAID configuration models are classified in terms of RAID levels, which are
defined by the number of disks in the array, the way data is spanned across the
disks, and the method used for redundancy. Each RAID level has specific features
and performance benefits that involve a trade-off between performance and
reliability.
Volume layouts
RAID levels correspond to volume layouts. A volumes layout refers to the
organization of plexes in a volume. Volume layout is the way plexes are
configured to remap the volume address space through which I/O is redirected at
run-time. Volume layouts are based on the concepts of disk spanning, redundancy,
and resilience.
Disk spanning
Disk spanning is the combining of disk space from multiple physical disks to form
one logical drive. Disk spanning has two forms:

113
Concatenation: Concatenation is the mapping of data in a linear manner
across two or more disks.
In a concatenated volume, subdisks are arranged both sequentially and
contiguously within a plex. Concatenation allows a volume to be created from
multiple regions of one or more disks if there is not enough space for an entire
volume on a single region of a disk.
Striping: Striping is the mapping of data in equally-sized chunks alternating
across multiple disks. Striping is also called interleaving.
In a striped volume, data is spread evenly across multiple disks. Stripes are
equally-sized fragments that are allocated alternately and evenly to the
subdisks of a single plex. There must be at least two subdisks in a striped plex,
each of which must exist on a different disk. Configured properly, striping not
only helps to balance I/O but also to increase throughput.
Data redundancy
To protect data against disk failure, the volume layout must provide some form of
data redundancy. Redundancy is achieved in two ways:
Mirroring: Mirroring is maintaining two or more copies of volume data.
A mirrored volume uses multiple plexes to duplicate the information contained
in a volume. Although a volume can have a single plex, at least two are
required for true mirroring (redundancy of data). Each of these plexes should
contain disk space from different disks for the redundancy to be useful.
Resilience: A resilient volume, also called a layered volume, is a volume that
is built on one or more other volumes. Resilient volumes enable the mirroring
of data at a more granular level. For example, a resilient volume can be
concatenated or striped at the top level and then mirrored at the bottom level.
A layered volume is a virtual Volume Manager object that nests other virtual
objects inside of itself. Layered volumes provide better fault tolerance by
mirroring data at a more granular level.
Parity: Parity is a calculated value used to reconstruct data after a failure by
doing an exclusive OR (XOR) procedure on the data. Parity information can be
stored on a disk. If part of a volume fails, the data on that portion of the failed
volume can be re-created from the remaining data and parity information.
A RAID-5 volume uses striping to spread data and parity evenly across
multiple disks in an array. Each stripe contains a parity stripe unit and data
stripe units. Parity can be used to reconstruct data if one of the disks fails. In
comparison to the performance of striped volumes, write throughput of RAID-
5 volumes decreases, because parity information needs to be updated each time
data is accessed. However, in comparison to mirroring, the use of parity
reduces the amount of space required.

1
Labs and solutions for this lesson are located on the following pages:
Appendix A provides complete lab instructions.
Lab 1: VMware Workstation Introduction, page A-7
Appendix B provides complete lab instructions and solutions.
Lab 1: VMware Workstation Introduction, page B-7
115

Lesson 2
Installing Storage Foundation and Accessing
SF Interfaces

37

2
Preparing to install Storage Foundation

OS version compatibility
Before installing Storage Foundation, ensure that the version of Storage
Foundation that you are installing is compatible with the version of the operating
system that you are running. You may need to upgrade your operating system
before you install the latest Storage Foundation version.
Check the Veritas Storage Foundation Release Notes for additional operating
system requirements.

39 Lesson 2 Installing Storage Foundation and Accessing SF Interfaces
23
Storage Foundation packaging
For the Unix and Linux platforms, Storage Foundation 6.0 is available in three
different product levels:
Veritas Storage Foundation Basic:
Intended for smaller systems, Storage Foundation Basic provides the same
robust storage management features of Storage Foundation Standard, but is
designed for system workloads that do not exceed four volumes and/or four
file systems, and/or two processors/sockets in a single physical system. This is
a free license, support subscription version of Storage Foundation.
Veritas Storage Foundation Standard:
This option includes Volume Manager, File System, Veritas Operations
Manager (VOM), Dynamic Multi-pathing (DMP), Cross-platform Data
Sharing (CDSalso known as portable data containers: PDC), SmartTier
(previously known as Dynamic Storage Tiering), and file system data

compression.
Veritas Storage Foundation Enterprise:
This option includes everything from the SF Standard version including
Volume Manager, File System, VOM, DMP, PDC, SmartTier, and data
compression and adds support for FlashSnap, storage checkpoints, importing
LUN snapshots, the site awareness feature, FileSnap, and file system
deduplication. These features are described in detail later in the course.

2
Other products with Storage Foundation

Storage Foundation licenses are also available in combination with other products:
Storage Foundation Standard High Availability license includes the Veritas
Cluster Server product with the database and application agents as well as
Storage Foundation Standard. The enterprise version of this product is also
available.
The disaster recovery version enables global clustering with VCS and also
includes the replication agents with automatic fire drill capability.
The Storage Foundation Cluster File System product provides cluster volume
manager and cluster file system capability for concurrent access to data from
multiple systems.
The Storage Foundation for Oracle RAC product is used in parallel Oracle
database environments.
The Symantec VirtualStore product provides datastore capability for VMware

environments with very high storage optimizations.
Veritas Replicator is an additional option that includes both Veritas Volume
Replicator (VVR) and Veritas File Replicator (VFR) options. Veritas Volume
Replicator enables synchronous or asynchronous data replication across
multiple SF sites.
Veritas File Replicator is also available as a separate option on its own. VFR is
new with the 6.0 release and provides periodic file system replication support
on Linux platforms.

25
Licensing selection
During SF installation after you select the product to install, you are prompted to
agree with the End User License Agreement. The agreement is provided in the
EULA.pdf file on the distribution media. The installation utility quits the
installation if you do not reply y to this question.
The diagram in the slide shows the two possible paths for licensing SF 6.0. The
boxes at the lower part of the slide show the traditional licensing methodology
based on the same keys used in 5.0 and earlier versions of Storage Foundation.
The path at the top of the slide shows how the installer handles the keyless
licensing option.
When keyless licensing is selected, the user is not required to type a license key. If
the system being installed is immediately configured as a managed host connected
to a Veritas Operations Manager management server, the license is considered
valid and no future action is necessary.
Note: Veritas Operations Manager is an additional free centralized management

solution that you can download and install to manage multiple SF servers
from a single management console.
Adding license keys

If you do not want to use the keyless licensing capability available with SF 6.0,
you must have your license key before you begin installation, because you are
prompted for the license key during the installation process.
License keys are non-node locked.
In a non-node locked model, one key can unlock a product on different servers
regardless of Host ID and architecture type.
In a node locked model, a single license is tied to a single specific server. For
each server, you need a different key.
Generating license keys

The Symantec licensing Web site (http://licensing.symantec.com) is a
self-service online license management system. The licensing web site supports
production license keys only. 2
Note: The VRTSvlic package can coexist with previous licensing packages, such
as VRTSlic. If you have old license keys installed in /etc/vx/elm,
leave this directory on your system. The old and new license utilities can
coexist.
Administering license keys

To add a license key after product installation, type:
vxlicinst
License keys are installed in the /etc/vx/licenses/lic directory. To view
installed license key information, type:
vxlicrep
Displayed information includes:
License key number
Name of the product that the key enables
Type of license
Features enabled by the key

27
Installation and Upgrade service at Symantec Operations Readiness
Tools (SORT) Web site
The Symantec Operations Readiness Tools (SORT) Web site
(https://sort.symantec.com) is designed specifically for Symantec
enterprise products. It automates and simplifies some of the administrator tasks
associated with these products.
You can use this site to:
Determine if your systems are ready to install or upgrade
Download, search, and set up notifications for patches
Search for UMI code descriptions and solutions
Check your product and system configurations for upgrade readiness or risk
exposure
Gather licensing information
Get the latest information about your SFHA and VCS products
The Installation and Upgrade service at the SORT Web site intends to help SF
administrators analyze their environment for suitability to install or upgrade SF.
This service can either be used to create a preinstallation checklist based on the
information provided by the user or to perform a set of checks on the SF server to
create a detailed custom report.

2
How to use the Installation and Upgrade service from SORT?

The data collector utility combines the various services provided by SORT that
require data collection from the live systems into a single interface and is built
using the same code base (Perl) as the SF installation scripts. As a result it has the
following benefits:
Can be installed on any UNIX machine on the network and is supported on all
UNIX / Linux versions
Can test multiple systems at the same time
Can test multiple operating systems
Follow the steps on the slide to execute the data collector utility. Note that you can
use the utility to test multiple systems at the same time. By default, the data
collector utility uses passwordless ssh to access remote systems. If you want to
use remote shell, you need to start the data collector utility with the -rsh option.

29
What does the utility check?
The Installation and Upgrade service provides complete checking for fresh
installations as well as for existing installations on the following items:
Operating system
Server name, version, and architecture
File system free space
Disk Space
OS patch levels
Number of CPUs, CPU type, CPU speed, and memory
NICs and link speed
Correct OS packages installed
Correct SAN hardware
Upgradability (current Symantec packages and patches)
Symantec licenses
When the utility completes, it creates two files in the ./sort/reports
directory:
hostname_IAS_date_time.txt
This file is for immediate review on the server.
hostname_IAS_date_time.xml
This file can be uploaded to the SORT Web site to display detailed reports as
shown on the slide.
Other reports may also be generated if you choose different services while running
the data collector utility.
2
Installing Storage Foundation

The Installer is a menu-based installation utility that you can use to install any
product released as part of the Veritas Storage Solutions. This utility acts as a
wrapper for existing product installation scripts and is most useful when you are
installing multiple Veritas products or bundles, such as Veritas Storage Foundation
or Veritas Storage Foundation High Availability.
Note: The example on the slide is from a Linux platform. You may have other
products available on other platforms.
Note: The Veritas Storage Solutions installation media contains an installation

guide that describes how to use the installer utility. Symantec also
recommends reading all product installation guides and release notes even
if you are using the installer utility.
To add the Storage Foundation packages using the installer utility:

1 Log on as superuser.
2 Mount the Veritas Storage Solutions installation media.
3 Locate and invoke the installer script:
cd /installation_media_location
./installer

211
Note: If you are planning to perform non-local installs on remote systems, ensure
that the remote systems are configured for passwordless access using either
ssh or rsh. The installer first tries ssh and then rsh to access remote
systems. If you want to use rsh specifically, start the installer script
using the -rsh option.
4 If the licensing utilities are installed, the product status page is displayed. This
list displays the Veritas products on the installation media and the installation
and licensing status of each product. If the licensing utilities are not installed,
you receive a message indicating that the installation utility could not
determine product status.
5 Type I to install a product. Follow the instructions to select the product that
you want to install. Installation begins automatically.
When you add Storage Foundation packages by using the installer utility, all
packages are installed. If you want to add a specific package only, for example,
only the VRTSob package, then you must add the package manually from the
command line.
Methods for adding Storage Foundation packages

A first-time installation of Storage Foundation involves adding the software
packages and starting Storage Foundation processes for first-time use. You can add
Veritas product packages by using one of three methods:
Method Command Notes

Veritas Installation installer Installs multiple Veritas products
Menu interactively.
Installs packages and starts Storage
Foundation for first-time use.
Product installation installvm Install individual Veritas products
scripts installfs interactively.
installsf Installs packages and configures SF
for first time use.
installdmp
Native operating pkgadd (Solaris) Install individual packages, for

system package swinstall (HP-UX) example, when using your own
installation custom installation scripts.
installp (AIX)
commands First-time Storage Foundation
rpm (Linux)
configuration must be run as a
Then, to start SF separate step.
processes:
./installer \
-start

2
Installation input
The interactive installation prompts the user for information, such as the package
set to be installed, system names, licensing selection, license keys (if traditional
licensing is selected), and other configuration information, such as the product
mode or additional options. These answers are then stored in the
installer-timestamp+3characters.response file in the installation
log directory:
/opt/VRTS/install/logs/installer-timestamp+3characters
The .response file can then be used to install other systems non-interactively
using the ./installer -responsefile filename option. For details on
using a response file during installation, refer to Veritas Storage Foundation
Installation Guide.
Note: SF 5.1 and later provide a Web user interface to the installation utilities.
The Web installer is explained in more detail later in this lesson.
Note: If you want to install more than one system using the installer utility,
provide the system names separated by space when prompted.

213
Viewing installation results
The best way to find out what exactly the installation utilities have performed on
the SF servers is by reviewing the installation log files. Each time you invoke the
installer utility, it creates a corresponding log directory under
/opt/VRTS/install/logs and stores detailed log files in this directory as
shown on the slide. Note that the timestamp used with the log directory and file
names is YYYYMMDDhhmm.
In addition to the key log files mentioned on the slide, individual log files exist for
the installation of a software package (the install.software.system log
files) and the starting of a Storage Foundation process or daemon (the
start.SFprocess.system log files).
During the installation, the related installation utilities are copied to the
/opt/VRTS/install directory on the SF hosts. You can use the installation
utilities in this directory to verify the version of the SF product installed on your
system using the -version option as shown on the slide. This option finds out
which packages are installed on the system and attempts to connect to the SORT
Web site to get the latest version and patch information about the product installed
on the system.
If you want to verify which packages are installed on the system, you can also
view information about installed packages by using OS-specific commands to list
package information.
Solaris
To list all installed packages on the system:

pkginfo
To restrict the list to installed Veritas packages:
pkginfo | grep VRTS
To display detailed information about a package:
pkginfo -l VRTSvxvm
HP-UX
swlist -l product
2
To restrict the list to installed Veritas packages:
swlist -l product | grep VRTS
To display detailed information about a package:
swlist -l product VRTSvxvm
AIX
lslpp
To restrict the list to installed Veritas packages, type:
lslpp -l 'VRTS*'
To verify that a particular fileset has been installed, use its name, for example:
lslpp -l VRTSvxvm
Linux
To verify package installation on the system:
rpm -qa | grep VRTS
To verify a specific package installation on the system:
rpm -q[i] package_name
For example, to verify that the VRTSvxvm package is installed:
rpm -q VRTSvxvm
The -i option lists detailed information about the package.

215
Other installation script options
The installer utility can be invoked using a variety of options some of which
are displayed on the slide. To get detailed usage information type ./installer
-help.
Solaris Note
VxFS often requires more than the default 8K kernel stack size, so entries are
added to the /etc/system file. This increases the kernel thread stack size of the
system to 24K. The original /etc/system file is copied to
/etc/fs/vxfs/system.preinstall. If the /etc/system file is
modified during installation, the installation utility does not start SF processes and
prompts you for a reboot. If you receive a message to reboot at the end of the
installation, reboot your system and when the system boots back up, start SF
processes using the -start option to the installation utility.
Support for native operating system installation methods

SF 6.0 supports product installation through the native operating system
provisioning tools, such as jumpstart and flash archives on Solaris, kickstart and
yum on Linux, ignite on HP-UX, and NIM on AIX.
You can create installation scripts for these OS-native methods, using options
specific to each platform. For example, to create a custom Solaris jumpstart finish
script, use the -jumpstart option. Note that the resulting finish scripts are not
complete and must be modified before being used for system installation
operations. For more information on using OS-native methods for installation,
refer to the Veritas Storage Foundation Installation Guide on the specific platform.

2
Using the Web installer

SF 5.1 and later include a Web-based interface to the CPI installer. The key
components of the Web installer architecture are shown in the diagram in the slide.
The Web browser can be run on any platform that supports the browser
requirements and can connect securely to the Web server.
The supported browsers are Firefox 3.x and later, Internet Explorer 6, 7, and 8.
The Web server runs the xprtlwid daemon, which is started using the
webinstaller command on the distribution media. The Web installer uses
the CPI installer scripts, and the software packages. Therefore, the system
acting as the Web server must have access to the SF distribution media.
The Web server must be able to connect to the installation target systems using
rsh or ssh.
The installation targets are the systems on which the SF software is installed
and configured.
When you run the webinstaller command to start the Web server, the URL is
displayed so you can connect from a browser. On some browsers, you must accept
a security exception and authenticate using the root account and password for the
system running the Web server. After you connect to the Web server, you can
select tasks, products, and systems to start installing and configuring the target
systems.
Note: The webinstaller command is located at the root directory of the

software distribution media.

217
Administering keyless licenses
You can manage license keys using the CPI installer script with the
-license option or using the vxkeyless utility. Examples of some common
tasks are shown in the slide.
Use vxkeyless to change the current licensing selections. For example, if you
want to upgrade to an additional product level, say SF standard to SF enterprise,
use the vxkeyless set SFENT command.
If you want to remove keyless licensing, use the vxkeyless set NONE
command to clear all keyless licenses from the system. This operation may disable
the Veritas products unless a valid license key is installed. Use the vxlicinst
command to install valid traditional license keys for the Veritas products that you
want to continue to use.
Files used by keyless licensing include:
Most recent license keys that are added to the system:

/etc/vx/licenses/lic/.keyless.diff
This file is removed if you remove keyless licensing.
License keys: /etc/vx/licenses/dat/licenses.dat
License log: /var/vx/licenses/.keyless.log
Veritas Operations Manager (VOM) configuration files (used for verifying
managed host configuration):
/etc/default/sfm_resolve.conf
/var/opt/VRTSsfmh/scheduler.conf

2
Storage Foundation resources

Version release differences
With each new release of the Storage Foundation software, changes are made that
may affect the installation or operation of Storage Foundation in your
environment. By reading version release notes and installation documentation that
are included with the product, you can stay informed of any changes.
For more information about specific releases of Veritas Storage Foundation, visit
the Symantec Support Web site at:
http://www.symantec.com/business/support
and select Storage Foundation for UNIX/Linux in the Product Finder.
This site contains product information, a searchable knowledge base of technical
notes, access to product-specific news groups and e-mail notification services, and
other information about contacting technical support staff.

219
Other services available from Symantec Operations Readiness Tools
The SORT Web site provides other services in addition to the Installation and
Upgrade service:
Downloads
This tab enables you to find and download patches, array specific modules,
such as Array Support Libraries (ASLs) and Array Policy Modules (APMs) for
UNIX servers, product documentation, high availability agents for Veritas
Cluster Server product, and VOM add-ons and documentation.
Systems
This tab lets administrators view and manage their Symantec enterprise
product configurations, track configuration changes, and share that information
with others. Note that before you can use SORT's Systems features, you must
create at least one custom report and upload it to SORT.
Reports
Use this tab to view and manage uploaded reports.
Notifications
This tab enables you to set e-mail alerts for being notified about the latest
information released about the Symantec enterprise products in your
environment.
Support
Use this tab to access detailed information about all Symantec resources from
product support to Symantec forums, from documentation to product training.

2
Accessing product documentation

The SORT Web site makes it easy to find product information from compatibility
lists to manual pages or product guides. Navigate to the Downloads > Documents
page on the SORT Web site and use the filtering capabilities provided to narrow
your search as shown on the slide.
Note that other Web sites that used to provide product documentation, such as the
Storage Foundation DocCentral site
(http://sfdoccentral.symantec.com/), are being deprecated in favor
of the additional filtering and search capabilities of the SORT Web site.

221
SORT patch services
The Patch Finder service, accessed by selecting Downloads > Patches on the
SORT Web site, aims to make finding patches easy by providing filtering
capabilities for product version, platform, and the Symantec product itself. When
you find the patch you need, you can display detailed information about that patch
or you can download it using ftp.
Note that not all patches may be available at this site. If you cannot find the patch
you are looking for, contact Symantec support services.

2
Storage Foundation user interfaces

Veritas Operations Manager
Storage Foundation provides central management capability by introducing a
Veritas Operations Manager (VOM) Management Server (MS).
Veritas Operations Manager is a comprehensive management platform, for Storage
Foundation and Cluster Server environments, that helps you optimize your data
center assets, with a solution to centralize visibility and control, ensure availability,
scale operations, increase storage utilization, and maintain compliance. It is
available as a free download for SF customers from the
http://go.symantec.com/vom Web site.
An introduction to VOM is provided in the Getting Started with Veritas
Operations Manager lesson in this course. For more information, refer to the
Veritas Operations Manager Administrator's Guide.

223
Storage Foundation user interfaces for single host administration
Storage Foundation supports three user interfaces which can be used to administer
one host at a time. Volume Manager objects created by one interface are
compatible with those created by the other interfaces.
Command-Line Interface (CLI): The command-line interface (CLI) consists
of UNIX utilities that you invoke from the command line to perform Storage
Foundation and standard UNIX tasks. You can use the CLI not only to
manipulate Volume Manager objects, but also to perform scripting and
debugging functions. Most of the CLI commands require superuser or other
appropriate privileges. The CLI commands perform functions that range from
the simple to the complex, and some require detailed user input.
Volume Manager Support Operations (vxdiskadm): The Volume
Manager Support Operations interface, commonly called vxdiskadm, is a
menu-driven, text-based interface that you can use for disk and disk group
administration functions. The vxdiskadm interface has a main menu from

which you can select storage management tasks.
Veritas Enterprise Administrator (VEA): Veritas Enterprise Administrator
(VEA) is a graphical user interface to Volume Manager and other Veritas
products. VEA provides access to Storage Foundation functionality through
visual elements, such as icons, menus, wizards, and dialog boxes. Using VEA,
you can manipulate Volume Manager objects and also perform common file
system operations. A single VEA task may perform multiple command-line
tasks.

2
Using the command-line interface

The Storage Foundation command-line interface (CLI) provides commands used
for administering Storage Foundation from the shell prompt on a UNIX system.
CLI commands can be executed individually for specific tasks or combined into
scripts.
The Storage Foundation command set ranges from commands requiring minimal
user input to commands requiring detailed user input. Many of the Storage
Foundation commands require an understanding of Storage Foundation concepts.
Most Storage Foundation commands require superuser or other appropriate access
privileges.
Accessing manual pages for CLI commands

Detailed descriptions of VxVM and VxFS commands, the options for each utility,
and details on how to use them are located in VxVM and VxFS manual pages.
Manual pages are installed by default in /opt/VRTS/man. Add this directory to

the MANPATH environment variable, if it is not already added.
To access a manual page, type man command_name.
Examples:
man vxassist
man mount_vxfs

225
Using the vxdiskadm interface
The vxdiskadm command is a CLI command that you can use to launch the
Volume Manager Support Operations menu interface. You can use the Volume
Manager Support Operations interface, commonly referred to as vxdiskadm, to
perform common disk management tasks. The vxdiskadm interface is restricted
to managing disk objects and does not provide a means of handling all other
VxVM objects.
Each option in the vxdiskadm interface invokes a sequence of CLI commands.
The vxdiskadm interface presents disk management tasks to the user as a series
of questions, or prompts.
To start, you type vxdiskadm at the command line. The vxdiskadm main menu
contains a selection of main tasks that you can use to manipulate Volume Manager
objects. Each entry in the main menu leads you through a particular task by
providing you with information and prompts. Default answers are provided for
many questions, so you can select common answers.
The menu also contains options for listing disk information, displaying help
information, and quitting the menu interface.
The tasks listed in the main menu are covered throughout this training. Options
available in the menu differ somewhat by platform. See the vxdiskadm(1m)
manual page for more details on how to use vxdiskadm.
Note: vxdiskadm can be run only once per host. A lock file prevents multiple
instances from running: /var/spool/locks/.DISKADD.LOCK.

2
Using the VEA interface

The Veritas Enterprise Administrator (VEA) is the graphical user interface for
Storage Foundation and other Veritas products. You can use the Storage
Foundation features of VEA to administer disks, volumes, and file systems on
local or remote machines.
VEA is a Java-based interface that consists of a server and a client. You must
install the VEA server on a UNIX machine that is running Veritas Volume
Manager. The VEA client can run on any machine that supports the Java (1.4 or
later) Runtime Environment, which can be Solaris, HP-UX, AIX, Linux, or
Windows.
Some Storage Foundation features of VEA include:
Remote Administration
Security
Multiple Host Support

Multiple Views of Objects
Setting VEA preferences

You can customize general VEA environment attributes through the Preferences
window (Select Tools > Preferences).

227
Installing the VEA server and client on UNIX
If you install Storage Foundation by using the installer utility, and select either the
recommended or the all package sets, the VEA server package (VRTSob) is
automatically installed. The VEA client package (VRTSobgui) must be
downloaded from the Symantec Web site displayed on the slide and installed on a
server with Java Runtime Environment. Use the native OS installation commands,
such as pkgadd on the Solaris platform, to install the VEA client software.
Starting the VEA server and client

In order to use VEA, the VEA server must be running on the UNIX machine to be
administered. Only one instance of the VEA server should be running at a time.
With SF 5.1 and later, the VEA server is no longer started automatically during
installation. You must use the /opt/VRTSob/bin/vxsvcctrl activate
command to configure the VEA server to start up automatically at system boot up.
On the Linux platform, you also need to execute the vxsvcctrl start
command to start the server process after activating it.
The VEA client can provide simultaneous access to multiple host machines. Each
host machine must be running the VEA server.
Note: Entries for your user name and password must exist in the password file or
corresponding Network Information Name Service table on the machine to
be administered. Your user name must also be included in the Veritas
administration group (vrtsadm, by default) in the group file or NIS group
table. If the vrtsadm entry does not exist, only root can run VEA.

2
Lab 2: Installing SF and Accessing SF Interfaces, page A-31
Lab 2: Installing SF and Accessing SF Interfaces, page B-45
229

Lesson 3
Getting Started with Veritas Operations
Manager (VOM)

67

3
Veritas Operations Manager overview

Increased complexity in data centers
Change is the only constant in todays data center environments. All IT
administrators have to manage change going forward. There are many reasons for
this constant change. Some of the main reasons are as follows:
Server move from one vendor to another due to insecurity or cost, as well as
technology
New projects involving new application deployment or setup of a new
datacenter
Storage move due to growth, price, or technology, such as thin storage arrays,
Solid State Devices, or tiering implementations
Standardization into a new technology searching for efficiency and better
business practices
All this makes todays data center increasingly more complex; there are too many
disparate tools, too many manual processes, and adopting new technologies, such
as virtualization, introduces its own set of challenges.

69 Lesson 3 Getting Started with Veritas Operations Manager (VOM)
33
The result of this complexity is reduced visibility and control of your
infrastructure, increased challenge in scaling operations, reduced utilization of
storage assets, and an increased risk of unplanned downtime.

3
Symantecs management solutions

Symantec has a unique portfolio of storage management solutions that will enable
you to manage a heterogeneous and complex data center environment and address
the challenges that have just been described.
Symantecs base offering, which is free with Storage Foundation High Availability
products, is Veritas Operations Manager (or VOM). VOM maximizes your SFHA
investments with centralized visibility and advanced control.
Symantec also offers other management solutions that carry the benefits to further
levels and other environments with or without Storage Foundation software.
CommandCentral Storage assesses storage utilization with capacity
management and chargeback reporting across your heterogeneous
environment.
DataInsight for Storage manages unstructured data growth and implements
chargeback, helping you to reclaim misused storage.

Disaster Recovery Advisor conducts automated, non-disruptive HA/DR testing
across your heterogeneous environment.
Note that with the release of Veritas Operations Manager 4.0 and later, Symantec
has added the CC Storage functionality to the same single pane of glass for storage
management through the release of a new product called VOM Advanced, which
installs on top of the basic VOM.

35
Maximizing SFHA value with Veritas Operations Manager
Veritas Operations Manager (VOM) ties together the various features in the
Storage Foundation products in a centralized, standardized way, so your data
center can run more efficiently.
Not only can the VOM operator visualize an individual host and the storage behind
it; he or she can also see all instances of Storage Foundation that are running in the
data center, across multiple operating system platforms. In this way the operator
can understand and manage everything that is happening throughout the entire data
center.
Veritas Operations Manager discovers UNIX and Windows managed hosts and all
associated resources and applications building a complete picture of the SF
environment from databases and VCS clusters down to the physical disk and host
bus adapter level. Relationships between objects enable the system administrators
form business entities which are collections of related objects that are used by
applications with all the resources on which the applications depend. This enables
business entity-specific management and reporting capabilities.

3
Veritas Operations Manager architecture

VOM is based on a distributed client-server architecture. It consists of the
following:
Management server (MS)
Components of the MS are:
Management server
Authentication broker (for OS/public domain-based user authentication)
A database server
Web server
One or more managed hosts, each consisting of an agent
An agent is a process that collects status information from network resources
and relays that information to VOM.
Typically, a managed host is a production server on which different
components of SF products are installed and running. A typical data center can
have thousands of such hosts using some or all of the SF products.
Optional external authentication brokers (ABs) for additional domain support.
An AB is a system with Symantec Product Authentication Services (SPAS)
installed that provides access to user authentication with public domains, such
as Active Directory, NIS, or NIS+.
In a centrally managed deployment, managed hosts relay information about
storage resources and applications to the MS. The Management Server then
coalesces the data it receives from the managed hosts within its database.

37
Management server architecture
The management server has administrative rights in the Storage Foundation
environment it is managing. Therefore, it is important for the MS to have a secure
infrastructure. Security aspects of the MS are maintained by the embedded
Symantec Product Authentication Service (or SPAS), which enables secure
communication with public key infrastructure (PKI) and the secure sockets layer
(SSL) protocol. The SPAS also enables the MS to work as an authentication broker
system to integrate with public domain user name spaces. The embedded
authentication broker cannot be disabled on the central management server.
The following network ports are used in a Veritas Operations Manager
environment:
TCP Port 5634 is used for management server communications with the
managed hosts.
TCP Port 14161 is used for access to the Web console.

TCP Port 14545 is used only if any secondary authentication brokers are
added.
The MS itself does not store any user information. It only assigns certain privileges
to users depending on the configuration.
Veritas Operations Manager 4.0 and later also have the capability to be placed in a
VCS cluster for high availability of the management interface.

3
VOM support for virtual environments

Veritas Operations Manager supports the following virtualization technologies:
VMware virtualization technology
Solaris Zones
Solaris Logical Domains (LDom).
With VMware virtualization technology, a designated Control Host discovers the
VirtualCenter servers in the datacenter. This discovery displays the ESX servers
that the VirtualCenter server manages and the virtual machines that are configured
on the ESX servers. Veritas Operations Manager can also discover the ESX servers
that VirtualCenter servers do not manage.
With the Solaris zones virtualization technology, the Zone agentlet that is present
in the VRTSsfmh package, which is installed on a Solaris managed host discovers
the Global Zones that are configured on the host. This discovery displays the non-
global zones that are configured on the Global Zone.

With the Solaris LDom virtualization technology, the LDom agentlet that is
present in the VRTSsfmh package, which is installed on a Solaris managed host
discovers the LDom Server that is configured on the host. This discovery displays
the LDoms that are configured on the LDom Server.

39
What is Veritas Operations Manager Advanced?
VOM Advanced provides several additional capabilities over the standard VOM
product.
It includes Enterprise Server Advanced Reporting, which has the ability to roll-up
data from multiple VOM management servers to provide an enterprise-wide view.
It also has a robust and flexible data model to build complex custom reports.
It includes several built-in reports for:
Capacity utilization
Chargeback
Trending
Storage reclamation
And licensing
It also includes support for hosts that do not have Veritas Storage Foundation,
Cluster Server, DMP, or ApplicationHA.

3
Installing the VOM management server

VOM 4.1 platform support
The platforms supported for the management server and the managed hosts with
Veritas Operations Manager 4.1 are displayed on the slide. For the most recent
information on system requirements, use the Symantec Web site for VOM.
Note: For RHEL 6.0 on x86 64-bit, and RHEL 6.1 on x86 64-bit, the 32-bit glibc
package must be installed.
The system used as the management server needs to have sufficient system
resources, such as memory, processing power, and disk space to collect and
process data from all managed hosts. As the size of the managed environment
increases, the demand on the central management server also increases. For
information on suggested system resource sizes, refer to Veritas Operations

Manager Release Notes.

311
Web browser requirements
The Veritas Operations Manager console is a graphical user interface that displays
reports and other tabular and graphical information for users of the Storage
Foundation products through a standard Web browser. The requirements for the
Web browsers that the VOM console supports are listed on the slide. Note that the
Web console host must be able to access Veritas Operations Manager over the
network through TCP port 14161.

3
Installing the management server

VOM is a free license management tool for Veritas Storage Foundation. You can
download VOM packages from the following URL:
http://www.symantec.com/vom
The installation is performed by executing the self-extracting binary on the server
that will become the central management server. This binary extracts and installs
two software packages:
VRTSsfmcs: VOM package that is required on management server
VRTSsfmh: VOM package that is required on the managed host
The package installation is performed without any input request from the user. You
can verify the installation by checking if the VOM daemons have been started on
the server as follows:
ps -ef | grep xprtld

ps -ef | grep vxdclid
After the installation completes successfully, you need to perform the initial
configuration by connecting to port number 5634 on the management server using
a Web browser.
Note: The MS fully qualified hostname must be resolvable using domain name
services (DNS) for a successful installation.

313
Configuring the management server after installation
When you connect to https://systemname:5634 to perform the initial
configuration, you may first need to create an exception to accept the digital
certificate for the product. You are then prompted for management servers root
user name and password. The root user has full administrative capabilities on the
management server and all of the managed objects by default.
In the Server Setting page, verify the displayed server name and the server IP
address.
On the Database Setting page, you can either accept the default database location
or enter a new directory for the MS database.
Finally, you are asked if Symantec can collect non-personal product usage
information to enhance the product. If you do not wish to enable the analytics
gathering feature, uncheck the box next to Enable Analytics Gathering. Click
Finish to start the configuration.

When the configuration completes successfully, click the Launch Web Console
button to log in to the management server.

3
Connecting to the VOM management server

To connect to the VOM management server, use a supported Web browser and
type:
https://fully_qualified_systemname_or_IP_address:14161
When you connect to the MS, you are presented with a summary view called the
Dashboard. The dashboard displays status information for the entire managed
environment organized into application groups, servers and storage. It also
provides a list of faulted applications and the most recent alerts with critical or
error status.
The menu at the top of the main page provides access to other parts of the
management server. Note that there are also in context links on the page that will
immediately allow you to browse to the associated information.
After the initial configuration, you would only see one host (the management
server itself) when you connect to the MS console. You need to add other SF
servers as managed hosts to populate the database and start the discovery process.
Note: If you are using pop-up blockers (including Yahoo Toolbar or Google
Toolbar), either disable them or configure them to accept pop-ups from the
Web server to which you will connect.

315
Installing additional functionality using VOM add-ons
VOM solutions
Veritas Operations Manager solutions are independent and optional feature packs
that you can download and use to enhance the functionality of Veritas Operations
Manager. These solutions are grouped into the following categories according to
their purposes and formats:
Add-on
Package
Patch
Hotfix
The solutions can be installed on VOM management server and the managed hosts
from the Settings > Deployment Management page. To deploy these solutions
you must have domain administrative privileges. The status information for the
solutions is maintained in the management server database.
There are two prebundled add-ons for VCS and SF administration. The rest of the
add-ons must be downloaded and deployed before being used.
The scope of an add-on indicates whether the add-on is installed on the central
management server only or on the managed hosts only or on both. For a full list of
available add-ons and their functionalities refer to the Veritas Operations Manager
Administrators Guide.

3
Installing the active management add-on for UNIX/Linux managed

hosts
The active management add-on for UNIX/Linux managed hosts provides
additional functionality on top of the pre-bundled SF administration add-on. Note
that this add-on is installed only on the management server and does not need to be
deployed on managed hosts.
You can only upload one add-on at a time. After you upload the add-on
successfully in steps 4 and 5 on the slide, the add-on is added to the Repository
table and its status shows as Not Installed. You then need to continue with
deploying the add-on as explained on the next page.
For more information on deploying other add-ons, refer to the Veritas Operations
Manager Administrators Guide.

317
After the add-on is available in the Repository on the MS, select it and click the
Install link in the Actions menu to start the deployment.
You then confirm the installation by clicking the Install button in the Install
Solution window to start the deployment process. The wizard informs you that the
deployment request has been submitted and asks you to restart the Web server on
the MS after successful deployment because the installation is performed on the
MS itself.
When you click OK to close the wizard, you are directed to the Deployment
Summary window where you can observe the status of the deployment request.
When the solution status changes to Enabled, restart the Web server on the MS:
/opt/VRTSsfmcs/bin/vomsc restart sfmcswd
Veritas Operations Manager Web Console
(sfmcswd).....................................[STOPPED]

(sfmcswd).....................................[STARTED]

3
Changing Storage Foundation hosts to managed hosts

Preparing an SF host for VOM management
Before you install the VOM host management component on a host to be managed
by the VOM console, ensure that the system meets or exceeds the requirements for
managed hosts. Download the required VRTSsfmh software to the system and
install using the OS tools specific to the platform of the managed host.
After the installation is complete, verify that the xprtld daemon is started.

319
Methods used for adding managed hosts to the management server
After the VRTSsfmh software is installed on an SF host, you can add the system to
the management server as a managed host either directly from the VOM console
itself or by executing a script on the managed host. This script is generated by
running the gendeploy.pl script on the management server as displayed on the
slide.
Note that it is also possible to download the script to the SF host by connecting to
the VOM console using a Web browser and selecting the Auto Configure button
from the Actions menu in the Host Management view.

3
Changing back to an unmanaged SF server

Changing a managed Storage Foundation host back to a standalone server is a two-
part process. In the first part, you remove the server from the list of managed hosts
on the management server. To do that, first log in to the management server.
Then navigate to the Host Management page by selecting Settings > Host
Management.
Place a check mark next to the host name in the Host Management table and click
the Remove Host(s) link in the Actions menu. Confirm when prompted.
In the second part, log in to the SF server and remove the managed host package
using the OS-specific tool. For example, use the pkgrm command on the Solaris
platform.

321
Lab 3: Getting Started with VOM, page A-45
Lab 3: Getting Started with VOM, page B-73
Lesson 4
Creating a Volume and File System

89

Preparing disks and disk groups for volume creation 4
What is enclosure-based naming?
An enclosure, or disk enclosure, is an intelligent disk array, which permits
hotswapping of disks. With Storage Foundation, disk devices can be named for
enclosures rather than for the controllers through which they are accessed as with
standard disk device naming (for example, c0t0d0 or hdisk2).
Enclosure-based naming allows Storage Foundation to access enclosures as
separate physical entities. By configuring redundant copies of your data on
separate enclosures, you can safeguard against failure of one or more enclosures.
This is especially useful in a storage area network (SAN) that uses Fibre Channel
hubs or fabric switches and when managing the dynamic multipathing (DMP)
feature of Storage Foundation. For example, if two paths (c1t99d0 and
c2t99d0) exist to a single disk in an enclosure, VxVM can use a single DMP
metanode, such as enc0_0, to access the disk.
Here are some examples of naming schemes:
Naming Scheme Example

OS-based Solaris: /dev/[r]dsk/c1t9d0s2
HP-UX: /dev/[r]dsk/c3t2d0 (no slice)
HP-UX: /dev/[r]disk/disk32 (11iv3)
AIX: /dev/hdisk2
Linux: /dev/sda, /dev/hda
Enclosure-based sena0_1, sena0_2, sena0_3, ...
Enclosure-based customized englab2, hr1, boston3
91 Lesson 4 Creating a Volume and File System
43
Note: With SF 5.1 and later, the enclosure-based naming scheme is the default
naming scheme for all fresh SF installations. Upgrades to a new version of
SF preserve the naming scheme set by the user in previous versions of SF.
Benefits of enclosure-based naming include:

Easier fault isolation: Storage Foundation can more effectively place data and
metadata to ensure data availability.
Device-name independence: Storage Foundation is independent of arbitrary
device names used by third-party drivers.
Improved SAN management: Storage Foundation can create better location
identification information about disks in large disk farms and SANs.
Improved cluster management: In a cluster environment, disk array names
on all hosts in a cluster can be the same. Storage Foundation 5.0 MP3 and later
provide consistent enclosure-based device names across systems in a cluster;
that is each LUN in a disk array is indexed using the same number on different
systems sharing storage in the same cluster.
Improved dynamic multipathing (DMP) management: With multipathed
disks, the name of a disk is independent of the physical communication paths,
avoiding confusion and conflict.
You can use the vxddladm command to determine the current naming scheme as
follows:
vxddladm get namingscheme
NAMING_SCHEME PERSISTENCE LOWERCASE USE_AVID
======================================================
OS Native No Yes Yes
You can change the naming scheme from the command line using the vxddladm
set command with the following options:
vxddladm set namingscheme=<osn|ebn> \
[persistent=<yes|no>] [lowercase=<yes|no>] \
[use_avid=<yes|no>]
If you set the use_avid option to yes, the LUNs are numbered based on the
array volume ID instead of the traditional indexing method.

You can also change the device naming scheme using the Change the disk
naming scheme option in the vxdiskadm menu.

Before configuring a disk for use by VxVM 4
In order to use the space of a physical disk to build VxVM volumes, you must
place the disk under Volume Manager control. Before a disk can be placed under
Volume Manager control, the disk media must be formatted outside of VxVM
using standard operating system formatting methods. SCSI disks are usually
preformatted. After a disk is formatted, the disk can be initialized for use by
Volume Manager. In other words, disks must be detected by the operating system,
before VxVM can detect the disks.
Stage one: Initialize a disk

A formatted physical disk is considered uninitialized until it is initialized for use
by VxVM. When a disk is initialized, the public and private regions are created,
and VM disk header information is written to the private region. Any partitions
(other than slice 2 on the Solaris platform) that may have existed on the disk are
removed.
These disks are under Volume Manager control but cannot be used by Volume
Manager until they are added to a disk group.
Note: Encapsulation is another method of placing a disk under VxVM control in
which existing data on the disk is preserved. This method is covered in the Veritas
Storage Foundation 6.0 for UNIX: Manage and Administer course.
Changing the disk layout

To display or change the default values that are used for initializing disks, select
the Change/display the default disk layouts option in vxdiskadm:
45
For disk initialization, you can change the default format and the default length
of the private region. If the attribute settings for initializing disks are stored in
the user-created file, /etc/default/vxdisk, they apply to all disks to be
initialized
On Solaris for disk encapsulation, you can additionally change the offset
values for both the private and public regions. To make encapsulation
parameters different from the default VxVM values, create the user-defined
/etc/default/vxencap file and place the parameters in this file.
On HP-UX when converting LVM disks, you can change the default format
and the default private region length. The attribute settings are stored in the
/etc/default/vxencap file.
Stage two: Assign a disk to a disk group

When you add a disk to a disk group, VxVM assigns a disk media name to the disk
and maps this name to the disk access name.
Disk media name: A disk media name is the logical disk name assigned to a
drive by VxVM. VxVM uses this name to identify the disk for volume
operations, such as volume creation and mirroring.
Disk access name: A disk access name represents all paths to the device. A
disk access record maps the physical location to the logical name and
represents the link between the disk media name and the disk access name.
Disk access records are dynamic and can be re-created when vxdctl enable
is run.
The disk media name and disk access name, in addition to the host name, are
written to the private region of the disk. The disk name field in the private region
is used to hold the disk media name and the devicetag field is used to hold the disk
access name. Space in the public region is made available for assignment to
volumes. Whenever the VxVM configuration daemon is started (or vxdctl
enable is run), the system reads the private region on every disk and establishes
the connections between disk access names and disk media names.
After disks are placed under Volume Manager control, storage is managed in terms
of the logical configuration. File systems mount to logical volumes, not to physical
partitions. Logical names, such as
/dev/vx/[r]dsk/diskgroup/volume_name, replace physical locations,
such as /dev/[r]dsk/device_name.
The free space in a disk group refers to the space on all disks within the disk group
that has not been allocated as subdisks. When you place a disk into a disk group,
its space becomes part of the free space pool of the disk group.
Stage three: Assign disk space to volumes

When you create volumes, space in the public region of a disk is assigned to the
volumes. Some operations, such as removal of a disk from a disk group, are
restricted if space on a disk is in use by a volume.

What is a disk group? 4
A disk group is a collection of physical disks, volumes, plexes, and subdisks that
are used for a common purpose. A disk group is created when you place at least
one disk in the disk group. When you add a disk to a disk group, a disk group entry
is added to the private region header of that disk. Because a disk can only have one
disk group entry in its private region header, one disk group does not know
about other disk groups, and therefore disk groups cannot share resources, such as
disk drives, plexes, and volumes.
A volume with a plex can belong to only one disk group, and subdisks and plexes
of a volume must be stored in the same disk group. You can never have an empty
disk group, because a disk group with no disks would have no private region
available in which to store the disk group definition. Therefore, you cannot remove
all disks from a disk group without destroying the disk group.
Why are disk groups needed?

Disk groups assist disk management in several ways:
Disk groups enable the grouping of disks into logical collections for a
particular set of users or applications.
Disk groups enable data, volumes, and disks to be easily moved from one host
machine to another.
Disk groups ease the administration of high availability environments. Disk
drives can be shared by two or more hosts, but they can be accessed by only
one host at a time. If one host crashes, the other host can take over its disk
groups and therefore its disks.
A disk group provides the configuration boundary for VxVM objects.
47
System-wide reserved disk groups
VxVM has reserved three disk group names that are used to provide boot disk
group and default disk group functionality. The names bootdg, defaultdg, and
nodg are system-wide reserved disk group names and cannot be used as names
for any of the disk groups that you set up.
If you choose to place your boot disk under VxVM control, VxVM assigns bootdg
as an alias for the name of the disk group that contains the volumes that are used to
boot the system.
The main benefit of creating a default disk group is that SF commands default to
that disk group if you do not specify a disk group on the command line.
defaultdg is an alias for the disk group name that should be assumed if the -g
option is not specified to a command. You can set defaultdg when you install
Veritas Volume Manager (pre-SF 5.1) or anytime after installation.
By default, both bootdg and defaultdg are set to nodg.
Notes
The definitions of bootdg and defaultdg are written to the volboot file. The
definition of bootdg results in a symbolic link from the named bootdg in
/dev/vx/dsk and /dev/vx/rdsk.
The rootdg disk group name is no longer a reserved name for VxVM versions
after 4.0. If you are upgrading from a version of Volume Manager earlier than
4.0 where the system disk is encapsulated in the rootdg disk group, the bootdg
is assigned the value of rootdg automatically.

Creating a disk group 4
A disk must be placed into a disk group before it can be used by VxVM. A disk
group cannot exist without having at least one associated disk. When you create a
new disk group, you specify a name for the disk group and at least one disk to add
to the disk group. The disk group name must be unique for the host machine.
Adding disks
To add a disk to a disk group, you select an uninitialized disk or a free disk. If the
disk is uninitialized, you must initialize the disk before you can add it to a disk
group.
Disk naming
When you add a disk to a disk group, the disk is assigned a disk media name. The
disk media name is a logical name used for VxVM administrative purposes.
Notes on disk naming

You can change disk media names after the disks have been added to disk groups.
However, if you must change a disk media name, it is recommended that you make
the change before using the disk for any volumes. Renaming a disk does not
rename the subdisks on the disk, which may be confusing.
Assign logical media names, rather than use the device names, to facilitate
transparent logical replacement of failed disks.

49
Creating a disk group: vxdiskadm
From the vxdiskadm main menu, select the Add or initialize one or more disks
option. Specify the disk group to which the disk should be added. To add the disk
to a new disk group, you type a name for the new disk group. You use this same
menu option to add additional disks to the disk group.
To verify that the disk group was created, you can use vxdg list.
When you add a disk to a disk group, the disk group configuration is copied onto
the disk, and the disk is stamped with the system host ID.

Creating a volume and adding a file system 4
Creating a volume
When you create a volume, you indicate the desired volume characteristics, and
VxVM creates the underlying plexes and subdisks automatically. The VxVM
interfaces require minimal input if you use default settings. For experienced users,
the interfaces also enable you to enter more detailed specifications regarding all
aspects of volume creation.
Before you create a volume
Before you create a volume, ensure that you have enough disks to support the
layout type.
A striped volume requires at least two disks.
A mirrored volume requires at least one disk for each plex. A mirror cannot be
on the same disk that other plexes of the same volume are using.
To create a volume from the command line, you use the vxassist command. In
the syntax:
Use the -g option to specify the disk group in which to create the volume.
make is the keyword for volume creation.
volume_name is a name you give to the volume. Specify a meaningful name
which is unique within the disk group.
length specifies the number of sectors in the volume. You can specify the
length by adding an m, k, g, or t to the length.

411
Adding a file system to a volume
A file system provides an organized structure to facilitate the storage and retrieval
of files. You can add a file system to a volume when you create a volume or any
time after you create the volume initially.
When a file system has been mounted on a volume, the data is accessed
through the mount point directory.
When data is written to files, it is actually written to the block device file:
/dev/vx/dsk/diskgroup/volume_name.
When fsck is run on the file system, the raw device file is checked:
/dev/vx/rdsk/diskgroup/volume_name.
To add a file system to a volume from the command line, you must create the file
system, create a mount point for the file system, and then mount the file system.
Solaris
To create and mount a VxFS file system:

mkfs -F vxfs /dev/vx/rdsk/datadg/datavol
mkdir /data
mount -F vxfs /dev/vx/dsk/datadg/datavol /data
To create and mount a UFS file system:
newfs /dev/vx/rdsk/datadg/datavol
mkdir /data
mount /dev/vx/dsk/datadg/datavol /data

HP-UX
To create and mount a VxFS file system:
mkfs -F vxfs /dev/vx/rdsk/datadg/datavol
mkdir /data
mount -F vxfs /dev/vx/dsk/datadg/datavol /data
To create and mount an HFS file system:
newfs -F hfs /dev/vx/rdsk/datadg/datavol
mkdir /data
mount -F hfs /dev/vx/dsk/datadg/datavol /data
AIX
To create and mount a VxFS file system using mkfs:
mkfs -V vxfs /dev/vx/rdsk/datadg/datavol
mkdir /data
mount -V vxfs /dev/vx/dsk/datadg/datavol /data
To create and mount a VxFS file system using crfs:
crfs -v vxfs -d /dev/vx/rdsk/datadg/datavol -m /data -A 4
yes
Notes:
An uppercase V is used with mkfs; a lowercase v is used with crfs (to avoid
conflict with another crfs option).
crfs creates the file system, creates the mount point, and updates the file
systems file (/etc/filesystems). The -A yes option requests mount at
boot.
If the file system already exists in /etc/filesystems, you can mount the
file system by simply using the syntax: mount mount_point.
Linux
To create and mount a VxFS file system using mkfs:
mkfs -t vxfs /dev/vx/rdsk/datadg/datavol

mkdir /data
mount -t vxfs /dev/vx/dsk/datadg/datavol /data

413
Mounting a file system at boot
Using CLI, if you want the file system to be mounted at every system boot, you
must edit the file system table file by adding an entry for the file system. If you
later decide to remove the volume, you must remove the entry in the file system
table file.
Platform File System Table File

Solaris /etc/vfstab
HP-UX /etc/fstab
AIX /etc/filesystems
Linux /etc/fstab
AIX
In AIX, you can use the following commands when working with the file system
table file, /etc/filesystems:
To view entries: lsfs mount_point
To change details of an entry, use chfs. For example, to turn off mount at
boot: chfs -A no mount_point

Displaying disk and disk group information 4
Displaying basic disk information

By viewing disk information, you can determine if a disk has been initialized and
added to a disk group, verify the changes that you make to disks, and keep track of
the status and configuration of your disks.
You use the vxdisk -o alldgs list command to display basic information
about all disks attached to the system. The vxdisk list command displays the:
Device names for all recognized disks
Type of disk, that is, how a disk is placed under VxVM control
Disk names
Disk group names associated with each disk
Status of each disk
In the output:
A status of online, in addition to entries in the Disk and Group columns
indicates that the disk has been initialized or encapsulated, assigned a disk
media name, and added to a disk group. The disk is under Volume Manager
control and is available for creating volumes.
A status of online without entries in the Disk and Group columns indicates that
the drive has been initialized or encapsulated but is not currently assigned to a
disk group. Note that if there is a disk group name in parentheses without any
disk media name, it indicates that the disk belongs to a deported disk group.

415
A status of online invalid indicates that the disk has neither been initialized
nor encapsulated by VxVM. The disk is not under VxVM control.
A status of error (not shown on the slide) indicates that Volume Manager can
no longer access the disk device, possibly due to a failure.
Notes:
On the HP-UX platform, LVM disks have a type of auto:LVM and a status of
LVM.
With SF 5.1 on the Solaris platform, ZFS/SVM disks have a type of auto:ZFS
or auto:SVM and a status of ZFS or SVM respectively.

Viewing detailed disk information 4
To display detailed information about a disk, you use the vxdisk list
command with the name of the disk. With this command, you can either use the
disk access name or the disk media name together with the disk group name as
shown in the following syntax:
vxdisk -g diskgroup list dm_name
vxdisk -g appdg list appdg01
Device: emc0_dd5
devicetag: emc0_dd5
type: auto
hostid: train12
disk: name=appdg01 id=1000753057.1114.train12

group: name=appdg id=1000753077.1117.train12
...
In the example output:
Device is the VxVM name for the device path.
devicetag is the name used by VxVM to refer to the physical disk.
type is how a disk was discovered by VxVM. auto is the default type.
hostid is the name of the system that currently manages the disk group to
which the disk belongs; if blank, no host is currently controlling this group.
disk is the VM disk media name and internal ID.
417
group is the disk group name and internal ID.
To view a summary of information for all disks, you use the -s option with the
vxdisk list command.
To display discovered properties of a disk, such as vendor ID, array port ID/WWN
and so on, you use the -p option with the vxdisk list command.
vxdisk -p list emc0_dd1
DISK : emc0_dd1
DISKID : 1320849045.92.sym1
VID : EMC
UDID : EMC%5FSYMMETRIX%5F313635323300%5FDD0DD1
SCSI_VERSION : 3
SCSI3_VPD_ID : 5123456000000000
REVISION : 5671
PORT_SERIAL_NO : 1a-a
PID : SYMMETRIX
PHYS_CTLR_NAME : c3
NR_DEVICE : Y
MEDIA_TYPE : hdd
LUN_TYPE : std
LUN_SNO_ORDER : 0
LUN_SERIAL_NO : DD0DD1
LIBNAME : libvxemc.so
HARDWARE_MIRROR: no
DMP_DEVICE : emc0_dd1
DDL_DEVICE_ATTR: lun
CAB_SERIAL_NO : 313635323300
ATYPE : A/A
ARRAY_VOLUME_ID: DD1
ARRAY_PORT_PWWN: 10.10.5.3:3260
ANAME : EMC
TRANSPORT : iSCSI
ENCLOSURE_NAME : emc0
NUM_PATHS : 2
Notes:
The disk name and the disk group name are changeable. The disk ID and disk
group ID are never changed as long as the disk group exists or the disk is
initialized.
The detailed information displayed by the vxdisk list command is
discussed in more detail in the Veritas Storage Foundation 6.0 for UNIX:
Manage and Administer course.

Displaying disk group information 4
To display disk group information:
Use vxdg list to display disk group names, states, and IDs for all imported
disk groups in the system.
Use vxdg free to display free space on each disk. This command displays
free space on all disks in all disk groups that the host can detect. Add -g
diskgroup to restrict the output to a specific disk group.
Note: This command does not show space on spare disks. Reserved disks are
displayed with an r in the FLAGS column.
Use vxdisk -o alldgs list to display all disk groups, including
deported disk groups. For example:
DEVICE TYPE DISK GROUP STATUS

Disk_1 auto:cdsdisk appdg01 appdg online
Disk_7 auto:cdsdisk - (oradg) online

419
Using vxlist to display disk and disk group information
The vxlist command is a new display command that provides a consolidated
view of the SF configuration.
To display the vxlist command output, the vxdclid daemon must be running.
If this daemon is not running, execute
/opt/VRTSsfmh/adm/dclisetup.sh as the root user.
For more information on using the vxlist command, refer to the manual pages.

Displaying volume configuration information 4
Displaying volume layout information
The vxprint command

You can use the vxprint command to display information about how a volume is
configured. This command displays records from the VxVM configuration
database.
vxprint -g diskgroup [options]
The vxprint command can display information about disk groups, disk media,
volumes, plexes, and subdisks. You can specify a variety of options with the
command to expand or restrict the information displayed. Only some of the
options are presented in this training. For more information about additional
options, see the vxprint(1m) manual page.

421
Displaying information for all volumes
To display the volume, plex, and subdisk record information for a disk group:
vxprint -g diskgroup -htr - u h
In the output, the top few lines indicate the headers that match each type of output
line that follows. Each volume is listed along with its associated plexes and
subdisks and other VxVM objects.
dg is a disk group.
st is a storage pool (used in Intelligent Storage Provisioning).
dm is a disk.
rv is a replicated volume group (used in Veritas Volume Replicator).
rl is an rlink (used in Veritas Volume Replicator).
co is a cache object.
vt is a volume template (used in Intelligent Storage Provisioning).

v is a volume.
pl is a plex.
sd is a subdisk.
sv is a subvolume.
sc is a storage cache.
dc is a data change object.
sp is a snap object.
For more information, see the vxprint(1m) manual page.

Using vxlist and vxinfo for volume information 4
The vxlist command is useful in summarizing the volume information on the
system. You can also use this command to display the disks and the plexes
associated with a specific volume, using the following command options:
vxlist s disk vol volume_name
vxlist -s disk vol appvol
disks
TY DEVICE DISK NPATH ENCLR_NAME ENCLR_SNO STATUS
disk emc0_dd1 appdg01 2 emc0 ... imported
vxlist s plexes vol volume_name
vxlist -s plexes vol appvol
plexes
TY NAME TYPE STATUS
plex appvol-01 simple attached
The vxinfo command prints the accessibility and the usability information on
VxVM volumes. The -p option with vxinfo also reports the name and status of
each plex within the volume.

423
Removing volumes, disks, and disk groups
Removing a volume
Only remove a volume if you are sure that you do not need the data in the volume,
or if the data is backed up elsewhere. A volume must be closed before it can be
removed. For example, if the volume contains a file system, the file system must
be unmounted. You must edit the OS-specific file system table file manually in
order to remove the entry for the file system and avoid errors at boot. If the volume
is used as a raw device, the application, such as a database, must close the device.

Evacuating a disk 4
Evacuating a disk moves the contents of the volumes on a disk to another disk. The
contents of a disk can be evacuated only to disks in the same disk group that have
sufficient free space.
To evacuate to any disk except for appdg03:
vxevac -g appdg appdg02 !appdg03

425
Removing a disk
You can verify the removal by using the vxdisk list command to display disk
information. A disk that has been taken out of a disk group no longer has a disk
media name or disk group assignment but still shows a status of online.
Before the disk is taken out of the disk group:
emc0_dd1 auto:cdsdisk appdg01 appdg online
...
After the disk is taken out of the disk group using the vxdg -g appdg
rmdisk appdg01 command:

emc0_dd1 auto:cdsdisk - - online
...

Uninitializing and shredding a disk 4
After the disk has been removed from its disk group, you can remove it from
Volume Manager control completely by using the vxdiskunsetup command.
This command reverses the configuration of a disk by removing the public and
private regions that were created by the vxdisksetup command. The
vxdiskunsetup command does not operate on disks that are active members of
an imported disk group. This command does not usually operate on disks that
appear to be imported by some other hostfor example, a host that shares access
to the disk. You can use the -C option to force deconfiguration of the disk,
removing host locks that may be detected.
Before the disk is uninitialized:
emc0_dd1 auto:cdsdisk - - online

...
After the disk is uninitialized using the vxdiskunsetup emc0_dd1
command:
emc0_dd1 auto:none - - online invalid
...

427
With SF 6.0, you can use the -o shred option with the vxdiskunsetup
command to shred a disk. Shredding a disk destroys the data stored on the disk by
overwriting the disk with a digital pattern in one of three ways:
One-pass: VxVM overwrites the disk with a randomly selected pattern. This
option takes the least amount of time. This is the default behavior if the user
does not specify a type.
Three-pass: The disk is overwritten a total of 3 times. In the first pass, it is
overwritten with a pre-selected digital pattern. The second time, it is
overwritten with the binary complement of the pattern. In the last pass, the disk
is overwritten with a randomly selected digital pattern. This algorithm is based
on the US DoD.5200.22-M standard for the sanitization of sensitive data.
Seven-pass: Disk is overwritten a total of 7 times. Each pass consists of
overwriting the disk with a randomly selected digital pattern or with the binary
complement of the previous pattern. This algorithm is based on the US
DoD.5200.28-STD standard.
Note: Use the -f option to force a shred operation on a Solid State Drive (SSD)
disk.

Destroying a disk group 4
Destroying a disk group permanently removes a disk group from Volume Manager
control, and the disk group ceases to exist. When you destroy a disk group, all of
the disks in the disk group are made available as empty disks. Volumes and
configuration information including the automatic configuration backups of the
disk group are removed. Disk group configuration backups are discussed later in
this course. Because you cannot remove the last disk in a disk group, destroying a
disk group is the only method to free the last disk in a disk group for reuse. A disk
group cannot be destroyed if any volumes in that disk group are in use or contain
mounted file systems. The bootdg disk group cannot be destroyed.
Caution: Destroying a disk group can result in data loss. Only destroy a disk
group if you are sure that the volumes and data in the disk group are not needed.
To destroy a disk group from the command line, use the vxdg destroy
command.
Note: You can bring back a destroyed disk group by importing it with its dgid if
its disks had not been re-used for other purposes.

429
Lab 4: Creating a Volume and File System, page A-53
Lab 4: Creating a Volume and File System, page B-87
Lesson 5
Working with Volumes with Different Layouts

119

Volume layouts
Each volume layout has different advantages and disadvantages. For example, a
volume can be extended across multiple disks to increase capacity, mirrored on
another disk to provide data redundancy, or striped across multiple disks to
improve I/O performance. The layouts that you choose depend on the levels of
performance and availability required by your system.
5
Concatenated layout
A concatenated volume layout maps data in a linear manner onto one or more
subdisks in a plex. Subdisks do not have to be physically contiguous and can
belong to more than one VM disk. Storage is allocated completely from one
subdisk before using the next subdisk in the span. Data is accessed in the
remaining subdisks sequentially until the end of the last subdisk.
For example, if you have 12 GB of data then a concatenated volume can logically
map the volume address space across subdisks on different disks. The addresses
0 GB to 8 GB of volume address space map to the first 8-gigabyte subdisk, and
addresses 9 GB to 12 GB map to the second 4-gigabyte subdisk. An address offset
of 10 GB, therefore, maps to an address offset of 2 GB in the second subdisk.

121 Lesson 5 Working with Volumes with Different Layouts
53
Striped layout
A striped volume layout maps data so that the data is interleaved, or allocated in
stripes, among two or more subdisks on two or more physical disks. Data is
allocated alternately and evenly to the subdisks of a striped plex.
The subdisks are grouped into columns. Each column contains one or more
subdisks and can be derived from one or more physical disks. To obtain the
maximum performance benefits of striping, you should not use a single disk to
provide space for more than one column.
All columns must be the same size. The size of a column is equal to the size of the
volume divided by the number of columns. The default number of columns in a
striped volume is based on the number of disks in the disk group.
Data is allocated in equal-sized units, called stripe units, that are interleaved
between the columns. Each stripe unit is a set of contiguous blocks on a disk. The
stripe unit size can be in units of sectors, kilobytes, megabytes, or gigabytes. The
default stripe unit size is 64K, which provides adequate performance for most
general purpose volumes. Performance of an individual volume may be improved
by matching the stripe unit size to the I/O characteristics of the application using
the volume.

Mirrored layout
By adding a mirror to a concatenated or striped volume, you create a mirrored
layout. A mirrored volume layout consists of more than one plex that duplicate the
information contained in a volume. Each plex in a mirrored layout contains an
identical copy of the volume data. In the event of a physical disk failure and when
the plex on the failed disk becomes unavailable, the system can continue to operate 5
using the unaffected mirrors.
Although a volume can have a single plex, at least two plexes are required to
provide redundancy of data. Each of these plexes must contain disk space from
different disks to achieve redundancy.
Volume Manager uses true mirrors, which means that all copies of the data are the
same at all times. When a write occurs to a volume, all plexes must receive the
write before the write is considered complete.
Distribute mirrors across controllers to eliminate the controller as a single point of

failure.

55
RAID-5 layout
A RAID-5 volume layout has the same attributes as a striped plex, but one column
in each stripe is used for parity. Parity provides redundancy.
Parity is a calculated value used to reconstruct data after a failure. While data is
being written to a RAID-5 volume, parity is calculated by performing an exclusive
OR (XOR) procedure on the data. The resulting parity is then written to the
volume. If a portion of a RAID-5 volume fails, the data that was on that portion of
the failed volume can be re-created from the remaining data and parity
information.
RAID-5 volumes keep a copy of the data and calculated parity in a plex that is
striped across multiple disks. Parity is spread equally across columns. Given a
five-column RAID-5 where each column is 1 GB in size, the RAID-5 volume size
is 4 GB. An amount of space equivalent to one column is devoted to parity; the
remaining space is used for data.

The default stripe unit size for a RAID-5 volume is 16K. Each column must be the
same length but may be made from multiple subdisks of variable length. Subdisks
used in different columns must not be located on the same physical disk.
RAID-5 requires a minimum of three disks for data and parity. When implemented
as recommended, an additional disk is required for the log.
RAID-5 cannot be mirrored.

Comparing volume layouts
Concatenation: Advantages
Better utilization of free space: Concatenation removes the restriction on size
of storage devices imposed by physical disk size. It also enables better
utilization of free space on disks by providing for the ordering of available
discrete disk space on multiple disks into a single addressable volume. 5
Simplified administration: System administration complexity is reduced

because making snapshots and mirrors uses any size space, and volumes can be
increased in size by any available amount.
Concatenation: Disadvantages
No protection against disk failure: Concatenation does not protect against disk
failure. A single disk failure results in the failure of the entire volume.
Striping: Advantages
Improved performance through parallel data transfer: Improved
performance is obtained by increasing the effective bandwidth of the I/O path
to the data. This may be achieved by a single volume I/O operation spanning
across a number of disks or by multiple concurrent volume I/O operations to
more than one disk at the same time.
Load-balancing: Striping is also helpful in balancing the I/O load from
multiuser applications across multiple disks.

57
Striping: Disadvantages
No redundancy: Striping alone offers no redundancy or recovery features.
Disk failure: Striping a volume increases the chance that a disk failure results
in failure of that volume. For example, if you have three volumes striped
across two disks, and one of the disks is used by two of the volumes, then if
that one disk goes down, both volumes go down.
Mirroring: Advantages
Improved availability: With concatenation or striping, failure of any one disk
makes the entire plex unusable. With mirroring, data is protected against the
failure of any one disk. Mirroring improves the availability of a striped or
concatenated volume.
Improved read performance: Reads benefit from having multiple places
from which to read the data.
Mirroring: Disadvantages
Requires more disk space: Mirroring requires twice as much disk space,
which can be costly for large configurations. Each mirrored plex requires
enough space for a complete copy of the volumes data.
Slightly slower write performance: Writing to volumes is slightly slower,
because multiple copies have to be written in parallel. The overall time the
write operation takes is determined by the time needed to write to the slowest
disk involved in the operation.
The slower write performance of a mirrored volume is not generally significant
enough to decide against its use. The benefit of the resilience that mirrored
volumes provide outweighs the performance reduction.
RAID-5: Advantages
Redundancy through parity: With a RAID-5 volume layout, data can be re-
created from remaining data and parity in case of the failure of one disk.
Requires less space than mirroring: RAID-5 stores parity information, rather
than a complete copy of the data.
Improved read performance: RAID-5 provides similar improvements in read
performance as in a normal striped layout.
Fast recovery through logging: RAID-5 logging minimizes recovery time in

case of disk failure.
RAID-5: Disadvantages
Slow write performance: The performance overhead for writes can be
substantial, because a write can involve much more than simply writing to a
data block. A write can involve reading the old data and parity, computing the
new parity, and writing the new data and parity. If you have more than twenty
percent writes, do not use RAID-5.
Very poor performance after a disk failure: After one column fails, all I/O
performance goes down. This is not the case with mirroring, where a disk
failure does not have any significant effect on performance.
Creating volumes with various layouts
Using CLI to create volumes with various layouts
To specify different volume layouts while creating a volume from the command
line using the vxassist make command, you use the layout attribute. If you do
not specify the layout attribute, by default, vxassist creates a concatenated
volume that uses one or more sections of disk space. The layout=striped attribute 5
designates a striped layout and the layout=mirror-concat or the
layout=mirror-stripe attributes designate a mirrored volume layout. Note that you
can also use the layout=mirror attribute to create a mirrored volume. However,
layout=mirror may result in the creation of layered volumes. Layered volumes are
covered in detail later in this lesson.
Note: To guarantee that a concatenated volume is created, include the

layout=nostripe attribute in the vxassist make command.

Without the layout attribute, the default layout is used that may have
been changed by the creation of the /etc/default/vxassist file.
The following additional attributes are used with the striped volume layout:
ncol=n designates the number of stripes, or columns, across which the volume
is created. This attribute has many aliases. For example, you can also use
nstripe=n or stripes=n.

59
The minimum number of stripes in a volume is 2 and the maximum is 8. You
can edit these minimum and maximum values in
/etc/default/vxassist using the min_columns and max_columns
attributes.
stripeunit=size specifies the size of the stripe unit to be used. The default is
64K.
The following additional attributes are used with the mirrored volume layout:
To specify more than two mirrors, you add the nmirror attribute.
When creating a mirrored volume, the volume initialization process requires
that the mirrors be synchronized. The vxassist command normally waits for
the mirrors to be synchronized before returning to the system prompt. To run
the process in the background, you add the -b option.
Estimating volume size

The vxassist maxsize command can determine the largest possible size for a
volume that can currently be created with a given set of attributes. This command
does not create the volume but returns an estimate of the maximum volume size.
The output value is displayed in sectors, by default.
vxassist -g appdg maxsize layout=stripe ncol=2
Maximum volume size: 14389248 (7026Mb)
If the volume with the specified attributes cannot be created, an error message is
returned:
VxVM vxassist ERROR V-5-1-752 No volume can be created
within the given constraints
Creating volumes with the maximum possible size

With SF 6.0, you can also create a volume of the maximum possible size using a
single command:
vxassist g diskgroup make volume_name maxsize[=length] \
attributes
You can also provide an upper limit for the maximum size by specifying
maxsize=length parameter. If the maximum possible size is higher than this upper
limit, the volume is created using the upper limit as the volume length. If the
maximum possible size is smaller than this limit, the volume is created with the
maximum possible size.

Volume creation examples using the CLI
While creating a concatenated volume, the vxassist command attempts to
locate sufficient contiguous space on one disk for the volume. However, if
necessary, the volume is spanned across multiple disks. VxVM selects the disks on
which to create the volume unless you designate the disks by adding the disk
media names to the end of the command.
5
To stripe the volume across specific disks, you can specify the disk media names at
the end of the command. The order in which disks are listed on the command line
does not imply any ordering of disks within the volume layout.
To exclude a disk or list of disks, add an exclamation point (!) before the disk
media names. For example, !appdg01 specifies that the disk appdg01 should
not be used to create the volume.
Creating a mirrored and logged volume
When you create a mirrored volume, you can add a dirty region log by adding the
logtype=drl attribute:
vxassist -g diskgroup [-b] make volume_name length \
layout=mirror-concat logtype=drl [nlog=n]
A log plex that consists of a single subdisk is created.
If you plan to mirror the log, you can add more than one log plex by specifying
a number of logs using the nlog=n attribute, where n is the number of logs.
vxassist -g appdg make appvol 5m layout=mirror-concat \
logtype=drl
Note: Dirty regions logs are covered in a later lesson.
511
Creating a layered volume
What is a layered volume?
VxVM provides two ways to mirror your data:
Original VxVM mirroring: With the original method of mirroring, data is
mirrored at the plex level. The loss of a disk results in the loss of a complete
plex. A second disk failure could result in the loss of a complete volume if the
volume has only two mirrors. To recover the volume, the complete volume
contents must be copied from backup.
Enhanced mirroring: VxVM 3.0 introduced support for an enhanced type of
mirrored volume called a layered volume. A layered volume is a virtual
Volume Manager object that mirrors data at a more granular level. To do this,
VxVM creates subvolumes from traditional bottom-layer objects, or subdisks.
These subvolumes function much like volumes and have their own associated
plexes and subdisks.

With this method of mirroring, data is mirrored at the column or subdisk level.
Loss of a disk results in the loss of a copy of a column or subdisk within a plex.
Further disk losses may occur without affecting the complete volume. Only the
data contents of the column or subdisk affected by the loss of the disk need to
be recovered. This recovery can be performed from an up-to-date mirror of the
failed disk.

How do layered volumes work?
In a regular mirrored volume, top-level plexes consist of subdisks. In a layered
volume, these subdisks are replaced by subvolumes. Each subvolume is associated
with a second-level volume. This second-level volume contains second-level
plexes, and each second-level plex contains one or more subdisks.
In a layered volume, only the top-level volume is accessible as a device for use by
applications.
Note: You can also build a layered volume from the bottom up by using the
vxmake command. For more information, see the vxmake(1m) manual
page.
Layered volumes: Advantages

Improved redundancy: Layered volumes tolerate disk failure better than
nonlayered volumes and provide improved data redundancy.
Faster recovery times: If a disk in a layered volume fails, a smaller portion of the
redundancy is lost, and recovery and resynchronization times are usually quicker
than for a nonlayered volume that spans multiple drives.
For a stripe-mirror volume, recovery of a single subdisk failure requires
resynchronization of only the lower plex, not the top-level plex. For a mirror-stripe
volume, recovery of a single subdisk failure requires resynchronization of the
entire plex (full volume contents) that contains the subdisk.
Layered volumes: Disadvantages

5
Requires more VxVM objects: Layered volumes consist of more VxVM objects
than nonlayered volumes. Therefore, layered volumes may fill up the disk group
configuration database sooner than nonlayered volumes. When the configuration
database is full, you cannot create more volumes in the disk group.
With SF 5.0 and later, the default size of the private region is 32 MB. Each VxVM
object requires about 256 bytes.
The private region can be made larger when a disk is initialized. The size cannot be
changed once disks have been initialized.

513
Comparing regular mirroring with enhanced mirroring
To understand the purpose and benefits of layered volume layouts, compare
regular mirroring with the enhanced mirroring of layered volumes in a disk failure
scenario.
Regular mirroring
The example illustrates a regular mirrored volume layout called a mirror-stripe
layout. Data is striped across two disks, disk01 and disk03, to create one plex,
and that plex is mirrored and striped across two other disks, disk02 and disk04.
If two drives fail, the volume survives 2 out of 6 (1/3) times. As more subdisks are
added to each plex, the odds of a traditional volume surviving a two-disk failure
approach (but never equal) 50 percent.
If a disk fails in a mirror-stripe layout, the entire plex is detached, and redundancy
is lost on the entire volume. When the disk is replaced, the entire plex must be
brought up-to-date, or resynchronized.

Layered volumes
The example illustrates a layered volume layout called a stripe-mirror layout. In
this layout, VxVM creates underlying volumes that mirror each subdisk. These
underlying volumes are used as subvolumes to create a top-level volume that
contains a striped plex of the data.
If two drives fail, the volume survives 4 out of 6 (2/3) times. In other words, the 5
use of layered volumes reduces the risk of failure rate by 50 percent without the
need for additional hardware. As more subvolumes are added, the odds of a
volume surviving a two-disk failure approach 100 percent. For volume failure to
occur, both subdisks that compose a subvolume must fail. If a disk fails, only the
failing subdisk must be detached, and only that portion of the volume loses
redundancy. When the disk is replaced, only a portion of the volume needs to be
recovered, which takes less time.
Failed Volume Status

Subdisks
Stripe-Mirror (Layered) Mirror-Stripe (Nonlayered)
1 and 2 Down Down
1 and 3 Up Up
1 and 4 Up Down
2 and 3 Up Down
2 and 4 Up Up
3 and 4 Down Down

515
Layered volume layouts
In general, use regular mirrored layouts for smaller volumes and layered layouts
for larger volumes. By default in VxVM, a volume larger than 1 GB is created as a
layered volume, unless you specify otherwise. Before you create layered volumes,
you need to understand the terminology that defines the different types of mirrored
layouts in VxVM.
mirror-concat: This layout mirrors data across concatenated plexes. The
concatenated plexes can consist of subdisks of different sizes. When you create
a simple mirrored volume using the layout=mirror attribute that is less than 1
GB in size, a nonlayered mirrored volume is created by default.
mirror-stripe: This layout mirrors data across striped plexes. The striped plexes
can consist of different numbers of subdisks.
concat-mirror: This volume layout contains a single plex consisting of one or
more concatenated subvolumes. Each subvolume consists of two concatenated

plexes (mirrors), which consist of one or more subdisks. If you have two
subdisks in the top-level plex, a second subvolume is created, which is used as
the second concatenated subdisk of the plex.
stripe-mirror: This volume layout stripes data across mirrored volumes. The
difference between stripe-mirror and concat-mirror is that the top-level plex is
striped rather than concatenated. Each mirrored subvolume must have the same
number of disks. The stripe-mirror volumes require at least four disks.

Creating a layered volume
In the vxassist make syntax, you can specify any of the following layout
types:
To create layered volumes:
layout=concat-mirror
layout=stripe-mirror 5
To create simple mirrored volumes:

layout=mirror-concat
layout=mirror-stripe
For striped volumes, you can specify other attributes, such as
ncol=number_of_columns and stripeunit=size.

517
Viewing a layered volume
To view the configuration of a layered volume from the command line, you use the
-r option of the vxprint command. The -r option ensures that subvolume
configuration information for a layered volume is displayed. The -L option is also
useful for displaying layered volume information when used with -r. -L displays
related records of a volume containing subvolumes, but grouping is performed
under any volume.
The following is an example output for a stripe-mirror layered volume striped
across three columns.
vxprint -g dg -htrL vol
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG

REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX
UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID
MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM
MODE

SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE
dm dg01 disk_0 auto 65536 10340608 -

dm dg02 disk_1 auto 65536 10340608 -
dm dg03 disk_2 auto 65536 10340608 -
dm dg04 disk_3 auto 65536 10340608 -
dm dg05 disk_4 auto 65536 10340608 -
dm dg06 disk_5 auto 65536 10340608 -
v vol - ENABLED ACTIVE 6291456 SELECT vol-03

fsgen
pl vol-03 vol ENABLED ACTIVE 6291456 STRIPE 3/128 RW
sv vol-S01 vol-03 vol-L01 1 2097152 0/0 3/3 ENA
v2 vol-L01 - ENABLED ACTIVE 2097152 SELECT - fsgen
p2 vol-P01 vol-L01 ENABLED ACTIVE 2097152 CONCAT - RW
s2 dg03-02 vol-P01 dg03 0 2097152 0 disk_2 ENA
sv vol-S02 vol-03 vol-L02 1 2097152 1/0 3/3 ENA

sv vol-S03 vol-03 vol-L03 1 2097152 2/0 3/3 ENA 5


519
Allocating storage for volumes
Specifying storage attributes for volumes
VxVM selects the disks on which each volume resides automatically, unless you
specify otherwise. To create a volume on specific disks, you can designate those
disks when creating a volume. By specifying storage attributes when you create a
volume, you can:
Include specific disks, controllers, enclosures, targets, or trays to be used for
the volume.
Exclude specific disks, controllers, enclosures, targets, or trays from being
used for the volume.
Mirror volumes across specific controllers, enclosures, targets, or trays. (By
default, VxVM does not permit mirroring on the same disk.)
By specifying storage attributes, you can ensure a high availability environment.

For example, you can only permit mirroring of a volume on disks connected to
different controllers and eliminate the controller as a single point of failure.
To exclude a disk, controller, enclosure, target, or tray, you add the exclusion
symbol (!) before the storage attribute. For example, to exclude appdg02 from
volume creation, you use the format: !appdg02.
Note: When creating a volume, all storage attributes that you specify for use must
belong to the same disk group. Otherwise, VxVM does not use these
storage attributes to create a volume.

Using the Storage Provisioning add-on in VOM
Veritas Operations Manager Storage Provisioning add-on enables the administrator
to allocate storage to hosts based on previously defined templates. The storage
template is an efficient way to quickly create storage based on the configurations
that are mentioned in the template. This mechanism lets you specify storage
attributes and conditions, and it ensures that the allocated storage adheres to the
conditions that are specified in the template. 5
When you install the add-on, new wizards are added to the Solutions page on the
VOM console as shown on the slide.
Using this add-on, you can create storage templates from existing virtual storage
devices, such as volumes and file systems. The add-on extracts all the properties of
the virtual storage device, and recreates the entire stack. The supported file
systems are Veritas File System (VxFS) and NTFS.
You can then use these templates to provision storage.

This add-on also provides functionality to move volumes from one enclosure to
another or to move volumes from thick to thin storage simplifying the migration
tasks.
Finally, it provides the capability to view the status of volume migration and
storage provisioning tasks.

521
Creating a storage template
To create a storage template, first navigate to the Solutions tab. Then, select the
Manage Storage Templates link under the Storage Provisioning section. This
takes you to the Storage Template overview pane. On this page, select the Create
Storage Template link in the Actions menu. The wizard allows you to create a
template either from scratch or based on an existing NTFS or VxFS file system or
an existing volume.
If you base the template on an existing volume or file system, you need to select
the host, the disk group, and the object on which to base the template. The wizard
extracts the properties of the existing volume or file system. You can then modify
the extracted parameters before you save the storage template.
If you place a check mark next to the Ask button for certain parameters, such as
the size of the file system or the mount point prefix, these parameters are presented
to the user as modifiable input fields when the template is used for provisioning
storage.
For details on the different methods used to create a storage template and all the
parameters that can be set, refer to the Veritas Storage Foundation Add-on for
Storage Provisioning User's Guide.

Provisioning storage using a storage template
To provision storage using templates, click Provision Storage from the Solutions
tab or in the Storage Template overview pane, select a template from the object
list then click Actions and select Provision Storage. You then have to select a host
and a disk group on which the storage should be provisioned. If the template
requires any user input, such as the size or the mount point prefix, you can modify 5
these fields. The wizard then provides a summary of the file systems and volumes
that will be created before you complete the wizard.

523
Lab 5: Working with Volumes with Different Layouts, page A-63
Lab 5: Working with Volumes with Different Layouts, page B-107
Lesson 6
Making Configuration Changes

143

Administering mirrored volumes
Adding a mirror to a volume
If a volume was not originally created as a mirrored volume, or if you want to add
additional mirrors, you can add a mirror to an existing volume.
By default, a mirror is created with the same plex layout as the plex already in the
volume. For example, assume that a volume is composed of a single striped plex.
If you add a mirror to the volume, VxVM makes that plex striped, as well.
However, you can specify a different layout.
A mirrored volume requires at least two disks. You cannot add a mirror to a disk
that is already being used by the volume. A volume can have multiple mirrors, as
long as each mirror resides on separate disks. 6
Only disks in the same disk group as the volume can be used to create the new
mirror. Unless you specify the disks to be used for the mirror, VxVM
automatically locates and uses available disk space to create the mirror.
A volume can contain up to 32 plexes (mirrors); however, the practical limit is 31.
One plex should be reserved for use by VxVM for background repair operations.
Removing a mirror
When a mirror (plex) is no longer needed, you can remove it. You can remove a
mirror to provide free space, to reduce the number of mirrors, to remove a
temporary mirror.
Caution: Removing a mirror results in loss of data redundancy. If a volume only
has two plexes, removing one of them leaves the volume unmirrored.
145 Lesson 6 Making Configuration Changes Copyright 2012 Symantec Corporation. All rights reserved.
63
Migrating data to a new array
Without Storage Foundation, moving data from one array to another requires
downtime. Using Storage Foundation, you can mirror to a new array, ensure it is
stable, and then remove the plexes from the old array. No downtime is necessary.
This is useful in many situations, for example, if a company purchases a new array.
The high level steps for migrating data using Storage Foundation are listed on the
slide. Note that if you have multiple volumes on the old array, you would need to
repeat steps 6 to 9 for each volume. The following steps illustrate the commands
you need to use to perform the migration using a simple example where the appvol
volume in the appdg disk group is moved from the emc0 enclosure to the emc1
enclosure. To keep the example simple, only one LUN is used to mirror the simple
volume.
1 Set up LUNs on the new array.
2 Get the OS to detect the LUNS. For example, type devfsadm on a Solaris
system.
3 vxdisk scandisks new (for VxVM to recognize LUNS from the new
emc1 enclosure)
4 vxdisksetup -i emc1_dd1 (Repeat for each new LUN to be used in the
volume.)
5 vxdg -g appdg adddisk appdg02=emc1_dd1
6 vxassist -g appdg mirror appvol appdg02
7 Wait for the synchronization to complete.

8 vxvol -g appdg rdpol prefer appvol appvol-02 (appvol-02
is the new plex in the volume that is configured on the emc1 enclosure. Note
that setting read policies for mirrored volumes is explained in more detail later
in this lesson.)
9 After the testing period: vxplex -g appdg -o rm dis appvol-01
(appvol-01 is the original plex in the volume that was configured on the emc0
enclosure.)
10 vxdg -g appdg rmdisk appdg01 (appdg01 is the disk media name of
the old LUN from the emc0 enclosure.)
Note that the steps after you get Storage Foundation to recognize the LUNs in the
new array can be automated using the Move Volumes functionality that is
available with the Veritas Operations Manager Storage Provisioning add-on. This
wizard moves all VxVM volumes from one enclosure to another in a single
operation.
6

65
Adding a mirror: CLI
To add a mirror onto a specific disk, you specify the disk name in the command:
vxassist -g appdg mirror appvol appdg03
Removing a mirror: CLI
To remove a mirror, use vxassist remove mirror as shown on the slide. If
you specify a disk media name with an exclamation mark in front, the plex that
contains a subdisk on that disk is removed. To remove a specific plex, you can also
use the following vxplex command specifying the name of the plex you want to
remove:
vxplex -g diskgroup -o rm dis plex_name

Logging in VxVM
By enabling logging, VxVM tracks changed regions of a volume. Log information
can then be used to reduce plex synchronization times and speed the recovery of
volumes after a system failure. Logging is an optional feature, but is highly
recommended, especially for large volumes.
Dirty region logging

Dirty region logging (DRL) is used with mirrored volume layouts. DRL keeps
track of the regions that have changed due to I/O writes to a mirrored volume.
Prior to every write, a bit is set in a log to record the area of the disk that is being
changed. In case of system failure, DRL uses this information to recover only the
portions of the volume that need to be recovered. 6
If DRL is not used and a system failure occurs, all mirrors of the volumes must be
restored to a consistent state by copying the full contents of the volume between its
mirrors. This process can be lengthy and I/O intensive.
When you enable logging on a mirrored volume, one log plex is created by default.
The log plex uses space from disks already used for that volume, or you can
specify which disk to use. To enhance performance, you should consider placing
the log plex on a disk that is not already in use by the volume.
How does DRL work?

In the dirty region log:
A small number of bytes of the DRL are reserved for internal use. The
remaining bytes are used for the DRL bitmap.
67
The bytes are divided into two bitmaps: an active bitmap and a recovery
bitmap.
Each bit in the active bitmap maps to a single region of the volume.
A maximum of 2048 dirty regions per system is allowed by default.
How the bitmaps are used in dirty region logging

Both bitmaps are zeroed when the volume is started initially, after a clean
shutdown. As regions transition to dirty, the corresponding bits in the active
bitmap are set before the writes to the volume occur.
If the system crashes, the active map is ORd with the recovery map.
Mirror resynchronization is now limited to the dirty bits in the recovery map.
The active map is simultaneously reset, and normal volume I/O is permitted.
Usage of two bitmaps in this way allows VxVM to handle multiple system crashes.

Adding a log to a volume
To create a volume that is mirrored and logged:
vxassist -g appdg make appvol 5m layout=mirror-concat \
logtype=drl
Dirty region log considerations:

Multiple logs can be added to mirror the DRL, up to a maximum of one log per
data plex in the volume.
The size of the DRL is determined by Volume Manager based on the length of
the volume.
DRL adds a small I/O overhead for most write access patterns. 6
DRL should not be used for:
Mirrored boot disks
Volumes that have a data change object (DCO)

Data change objects are used with the FastResync feature which is
explained in detail in the Veritas Storage Foundation 6.0 for UNIX:
Manage and Administer course.
Data volumes for databases that support the SmartSync feature of Volume
Manager
Redo log volumes and other volumes that are used primarily for sequential
writes may benefit from using a sequential DRL instead of a standard DRL
(logtype=drlseq).

151 Lesson 6 Making Configuration Changes
69
Volume read policies with mirroring
One of the benefits of mirrored volumes is that you have more than one copy of the
data from which to satisfy read requests. The read policy for a volume determines
the order in which plexes are accessed during read I/O operations.
Round robin: VxVM reads each plex in turn in round-robin manner for
each nonsequential I/O detected. Sequential access causes only one plex to be
accessed in order to take advantage of drive or controller read-ahead caching
policies. If a read is within 256K of the previous read, then the read is sent to
the same plex.
Preferred plex: VxVM reads first from a plex that has been named as the
preferred plex. Read requests are satisfied from one specific plex, presumably
the plex with the highest performance. If the preferred plex fails, another plex
is accessed. For example, if you are mirroring across disk arrays with
significantly different performance specifications, setting the plex on the faster
array as the preferred plex would increase performance.

Selected plex: This is the default read policy. Under the selected plex policy,
Volume Manager chooses an appropriate read policy based on the plex
configuration to achieve the greatest I/O throughput. If the mirrored volume
has exactly one enabled striped plex, the read policy defaults to that plex;
otherwise, it defaults to a round-robin read policy.
Siteread: VxVM reads preferentially from plexes at the locally defined site.
This is the default policy for volumes in disk groups where site consistency has
been enabled. Configuring site consistency and the siteread policy is covered
in detail in the Veritas Storage Foundation 6.0 for UNIX: Manage and
Administer course.
Changing the volume read policy: CLI
vxvol -g diskgroup rdpol round volume_name
vxvol -g diskgroup rdpol prefer volume_name preferred_plex
vxvol -g diskgroup rdpol select volume_name
Note: Before configuring the siteread policy, the Site Awareness feature must be
configured by assigning hosts and LUNs to different sites. The Site
Awareness feature is described in detail in the Veritas Storage Foundation
6.0 for UNIX: Manage and Administer course. Note that setting the
siteread policy on a volume has no impact if the site name has not been set
for the host. 6
You can also use the vxprint command to observe the read policy of a mirrored
volume as shown in the following output extracts. Note that the fields related to the
read policy are displayed in bold font for emphasis:
The vxprint output with the default read policy:
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX
UTYPE
v appvol - ENABLED ACTIVE 2097152 SELECT -
fsgen
The vxprint output after the read policy is changed to preferred plex:
v appvol - ENABLED ACTIVE 2097152 PREFER appvol-02
fsgen

611
Resizing a volume and a file system
Resizing a volume
If users require more space on a volume, you can increase the size of the volume.
If a volume contains unused space that you need to use elsewhere, you can shrink
the volume.
When the volume size is increased, sufficient disk space must be available in the
disk group to support extending the existing volume layout. A volume with
concatenated layout can be grown by any amount on any disk within the disk
group whereas a volume with striped layout can be grown only if subdisks remain
the same length and an equal number of disks as stripes are available. When
increasing the size of a volume, VxVM assigns the necessary new space from
available disks. By default, VxVM uses space from any disk in the disk group,
unless you define specific disks.
Resizing a volume with a file system

Volumes and file systems are separate virtual objects. When a volume is resized,
the size of the raw volume is changed. If a file system exists that uses the volume,
the file system must also be resized. When you resize a volume using VOM or the
vxresize command, the file system is also resized.
Resizing volumes with other types of data

For volumes containing data other than file systems, such as raw database data,
you must ensure that the data manager application can support the resizing of the
data device with which it has been configured.
Resizing a volume and file system: Methods
To resize a volume from the command line, you can use either the vxassist
command or the vxresize command. Both commands can expand or reduce a
volume to a specific size or by a specified amount of space, with one significant
difference:
vxresize automatically resizes a volumes file system.
vxassist does not resize a volumes file system.
When using vxassist, you must resize the file system separately by using the
fsadm command.
When you expand a volume, both commands automatically locate available disk
space unless you designate specific disks to use. When you shrink a volume, the 6
unused space becomes free space in the disk group.
When you resize a volume, you can specify the length of a new volume in sectors,
kilobytes, megabytes, or gigabytes. The unit of measure is added as a suffix to the
length (s, k, m, or g). If no unit is specified, the default unit is sectors.

613
Resizing a volume and file system: CLI
The new_length operand can begin with a plus sign (+) to indicate that the new
length is added to the current volume length. A minus sign (-) indicates that the
new length is subtracted. -b runs the process in the background. The -x switch
restricts the change to an expand operation and the -s switch restricts the change
to a shrink operation.
The vxassist maxgrow command can be used to get an estimate of how much
an existing volume can be expanded. The output indicates the amount by which the
volume can be increased and the total size to which the volume can grow. The
output is displayed in sectors, by default.
vxassist -g datadg maxgrow datavol
Volume datavol can be extended by 366592 to 1677312
(819Mb)
Note that this command does not change the size of the volume.
The ability to expand or shrink a file system depends on the file system type and
whether the file system is mounted or unmounted. The following table provides
some examples:
File System Type Mounted FS Unmounted FS

VxFS Expand and shrink Not allowed
UFS (Solaris) Expand only Expand only
HFS (HP-UX) Not allowed Expand only

Example: The size of the volume myvol is 1 GB. To extend myvol to 5 GB:
vxresize -g mydg myvol 5g
To extend myvol by an additional 1 GB:
vxresize -g mydg myvol +1g
To shrink myvol back to a length of 4 GB:
vxresize -g mydg myvol 4g
To shrink myvol by an additional 1 GB:
vxresize -g mydg myvol -1g
Resizing a volume only: vxassist

The vxassist command can be used to resize a volume only as follows:
vxassist -g diskgroup {growto|growby|shrinkto|shrinkby} \
volume_name size
growto Increases volume to specified length
growby Increases volume by specified amount
shrinkto Reduces volume to specified length
shrinkby Reduces volume by specified amount
You should use this command only if the volume does not include a file system or
if you are resizing the volume and the file system separately for a specific purpose.
Resizing a file system only: fsadm

You may need to resize a file system to accommodate a change in usefor
example, when there is an increased need for space in the file system. You may
also need to resize a file system as part of a general reorganization of disk
usagefor example, when a large file system is subdivided into several smaller
file systems. You can resize a VxFS file system while the file system remains
mounted by using the fsadm command:
fsadm [-b newsize] [-r rawdev] mount_point
6
Using fsadm to resize a file system does not automatically resize the underlying
volume. When you expand a file system, the underlying device must be large
enough to contain the new larger file system.

615
Resizing a Volume Manager disk to match a resized LUN
When you resize a LUN in the hardware, you should resize the VxVM disk
corresponding to that LUN. You can use vxdisk resize to update disk headers
and other VxVM structures to match a new LUN size. This command does not
resize the underlying LUN itself.

Moving data between systems
Example: Disk groups and high availability
The example in the diagram represents a high availability environment.
In the example, Computer sym1 and Computer sym2 each have their own bootdg
on their own private SCSI bus. The two hosts are also on a shared SCSI bus. On
the shared bus, each host has a disk group, and each disk group has a set of VxVM
disks and volumes. There are additional disks on the shared SCSI bus that have not
been added to a disk group.
If Computer sym1 fails, then Computer sym2, which is on the same SCSI bus as
the appdg disk group, can take ownership or control of the disk group and all of its
components. 6

617
Deporting a disk group
A deported disk group is a disk group over which management control has been
surrendered. The objects within the disk group cannot be accessed, its volumes are
unavailable, and the disk group configuration cannot be changed. (You cannot
access volumes in a deported disk group because the directory containing the
device nodes for the volumes are deleted upon deport.) To resume management of
the disk group, it must be imported.
A disk group cannot be deported if any volumes in that disk group are in use.
Before you deport a disk group, you must unmount file systems and stop any
application using the volumes in the disk group.
Deporting and specifying a new host

When you deport a disk group using VOM or CLI commands, you have the option
to specify a new host to which the disk group is imported at reboot. If you know
the name of the host to which the disk group will be imported, then you should
specify the new host during the operation. If you do not specify the new host, then
the disks could accidentally be added to another disk group, resulting in data loss.
You cannot specify a new host using the vxdiskadm utility.
Deporting and renaming

When you deport a disk group using VOM or CLI commands, you also have the
option to rename the disk group when you deport it. You cannot rename a disk
group when deporting using the vxdiskadm utility.

Importing a deported disk group
During a disk group import operation, the volume device files
(/dev/vx/[r]dsk/diskgroup/volume_name) are created and with SF
versions 5.1 SP1 and later, the volumes are automatically started.
Importing and renaming
A deported disk group cannot be imported if another disk group with the same
name has been created since the disk group was deported. You can import and
rename a disk group at the same time.
Importing and clearing host locks
When a disk group is created, the system writes a lock on all disks in the disk
6
group. The lock ensures that dual-ported disks (disks that can be accessed
simultaneously by two systems) are not used by both systems at the same time. If a
system crashes, the locks stored on the disks remain, and if you try to import a disk
group containing those disks, the import fails.

Importing as temporary
A temporary import does not persist across reboots. A temporary import can be
useful, for example, if you need to perform administrative operations on the
temporarily imported disk group.
Forcing an import
A disk group import fails if the VxVM configuration daemon cannot find all of the
disks in the disk group. If the import fails because a disk has failed, you can force
the import. Forcing an import should always be performed with caution.

619
How to deport a disk group
Before deporting a disk group, unmount all file systems used within the disk group
that is to be deported. You can also stop all volumes in the disk group to verify that
they are not being used:
umount mount_point
vxvol -g diskgroup stopall
After you deport a disk group, disks that were in the disk group have a state of
Deported. If the disk group was deported to another host, the disk state is Foreign.
How to import a disk group:

With SF 5.1 SP1 and later, all volumes in the disk group are started automatically
during a disk group import by default. However, with earlier versions of SF or if
the autostartvolumes parameter is modified to off, you must manually start all
volumes after you import a disk group from the command line.
A disk group must be deported from its previous system before it can be imported
to the new system. During the import operation, the system checks for host import
locks. If any locks are found, you are prompted to clear the locks.
To temporarily import a disk group, you use the -t option. This option does not
set the autoimport flag, which means that the import cannot survive a reboot.
To display all disk groups, including deported disk groups:
emc0_dd1 auto:cdsdisk appdg01 appdg online
emc0_dd2 auto:cdsdisk - (oradg) online
Renaming VxVM objects
Changing the disk media name
VxVM creates a unique disk media name for a disk when you add a disk to a disk
group. Sometimes you may need to change a disk name to reflect changes of
ownership or use of the disk. Renaming a disk does not change the physical disk
device name. The new disk name must be unique within the disk group.
Before you rename a VxVM object

Before you rename a VxVM object, you should carefully consider the change. For
example, VxVM names subdisks based on the disks on which they are located. A
disk named appdg01 contains subdisks that are named appdg01-01, 6
appdg01-02, and so on. Renaming a disk does not automatically rename its
subdisks. Similarly, renaming a volume does not automatically rename its plexes.
Volumes are not affected when subdisks are named differently from the disks.

621
Renaming a disk group
You cannot import or deport a disk group when the target system already has a disk
group of the same name. To avoid name collision or to provide a more appropriate
name for a disk group, you can rename a disk group.
To rename a disk group when moving it from one system to another, you
specify the new name during the deport or during the import operations.
To rename a disk group without moving the disk group, you must still deport
and reimport the disk group on the same system.
Note that renaming a disk group:
does not change the disk group ID (dgid).
may require modifying the filesystem table (For example, /etc/vfstab for
Solaris).
may require modifying applications, such as databases, using the volumes.
Using the CLI, for example, to rename the disk group appdg to oradg:
vxdg -n oradg deport appdg or vxdg deport appdg
vxdg import oradg vxdg -n oradg import appdg
From the command line, if you need to restart all volumes in the disk group:
vxvol -g new_dg_name startall
vxvol -g oradg startall

Managing disk group versions and formats
Upgrading a disk group
All disk groups have an associated version number. Each VxVM release supports a
specific set of disk group versions and can import and perform tasks on disk
groups with those versions. Some new features and tasks only work on disk groups
with the current disk group version, so you must upgrade existing disk groups in
order to perform those tasks.
Once you upgrade a disk group, the disk group becomes incompatible with earlier
releases of VxVM that do not support the new version. Upgrading the disk group
version is an online operation. You cannot downgrade a disk group version.
6
Displaying the disk group version:
From the command line, type:
vxdg list newdg

Group: newdg
dgid: 971216408.1133.cassius
...
version: 170

623
Requirements for CDS disk groups
The CDS attribute indicates that the disk group can be shared across platforms.
CDS disk groups have fields indicating which platform-type created the disk group
and which platform-type last imported the disk group, in addition to device quotas.

Converting a non-CDS disk group to a CDS disk group
Requirements for converting a non-CDS disk group to a CDS disk group
The disk group must be in good condition:
No dissociated or disabled objects
No sparse plexes
No volumes requiring recovery or having pending snapshot operations
No objects in an error state
Disk groups can be converted online or offline:
Performing the conversion online, while use of the disk group continues, may
greatly increase the amount of time required for conversion. 6
Performing the conversion offline requires minimal offline time.
What happens when a disk group is converted?

The following are some other factors to consider when converting a disk group:
A non-CDS disk group is upgraded (using the vxdg upgrade command).
If the non-CDS disk group has one or more disks that are not CDS disks, these
disks are converted to CDS disks.
If the non-CDS disk group does not have a CDS-compatible disk group
alignment, the objects go through relayout so that they are CDS-compatible.
Applications using disks that require format conversion are terminated for the
duration of the disk conversion process (unless novolstop is used).
Using novolstop may require objects to be evacuated and then unrelocated.
625
Lab 6: Making Configuration Changes, page A-73
Lab 6: Making Configuration Changes, page B-125
Lesson 7
Administering File Systems

169

Benefits of using Veritas File System
A file system is simply a method for storing and organizing computer files and the
data they contain to make it easy to find and access them.
Veritas File System includes the following features:
Intent log
Veritas File System (VxFS) was the first commercial journaling file
system. With journaling, metadata changes are first written to a log (or
journal) then to disk. Since changes do not need to be to be written in
multiple places, throughput is much faster as the metadata is written
asynchronously.
VxFS provides fast recovery of a file system from system failure because
the recovery usually involves only a log replay.
Extent-based allocation
Extents allow disk I/O to take place in units of multiple blocks if storage is
allocated in consecutive blocks. This topic is analyzed in more detail in the
following pages.
7
Extent attributes
Extent attributes are the extent allocation policies associated with a file.
Online administration
A lot of the file system administration tasks, such as backing the file system up
or resizing the file system, can be performed while the file system is still
mounted. Online file system defragmentation is discussed later in this lesson.

171 Lesson 7 Administering File Systems
73
Storage checkpoints
Backup and restore applications can leverage Storage Checkpoint, a disk- and
I/O-efficient copying technology for creating periodic frozen images of a file
system. Storage checkpoints are discussed in the Veritas Storage Foundation
6.0 for UNIX: Manage and Administer course.
Multi-volume file system support
The multi-volume support feature allows several volumes to be represented by
a single logical object. This feature is used with the SmartTier feature.
SmartTier (previously known as Dynamic Storage Tiering)
The SmartTier feature allows you to configure policies that automatically
allocate storage from specific volumes for certain files, or relocate files by
running file relocation commands, which can improve performance for
applications that access specific types of files.
Both multi-volume file systems and the SmartTier feature are covered in the
Veritas Storage Foundation 6.0 for UNIX: Manage and Administer course.
Improved database performance
Databases can be created on the character devices to achieve the same
performance as databases created on raw disks.
Performance tuning options
The VxFS file system supports extended mount options to specify
enhanced data integrity modes, enhanced performance modes, temporary
file system modes. For more information on these modes of operation,
refer to the Veritas Storage Foundation Administrators Guide.
VxFS provides superior performance for synchronous write applications.

VxFS supports files larger than two gigabytes and large file systems up to
256 terabytes.
Cross-platform data sharing
Cross-platform data sharing allows data to be serially shared among
heterogeneous systems where each system has direct access to the physical
devices that hold the data.
Access control lists (ACLs)
An access control list (ACL) stores a series of entries that identify specific
users or groups and their access privileges for a directory or file.
Quotas
VxFS supports quotas, which allocate per-user and per-group quotas and limit
the use of two principal resources: files and data blocks.
File change log
The VxFS file change log tracks changes to files and directories in a file
system.
The SmartMove feature
The information stored by Veritas File System about used and unused blocks is
used by Veritas Volume Manager to optimize mirror synchronization
operations.
Storage Foundation thin reclamation
The thin reclamation feature allows you to release free data blocks of a VxFS
file system to the free storage pool of a thin storage LUN. This feature is only
supported on file systems mounted on a VxVM volume.
Note: The Storage Foundation thin reclamation feature is not supported on the
Solaris x64 operating environment.
File system data compression
The file system data compression feature with SF 6.0 aims to reduce the space
used by files, while retaining the accessibility of the files and being transparent
to applications.
File system deduplication
The Veritas file system deduplication feature is another new feature with SF
6.0 that aims to maximize storage utilization. This feature scans the file
system, identifies the duplicate data and eliminates it without any continuous
cost.
File replication
7
Veritas File Replicator (VFR), which is available as an option to Storage
Foundation, included in the Veritas Replicator license, supports file-level
replication of application data. VFR tracks all updates to the file system and
periodically replicates these updates at the end of a configured time interval.
Cluster File System
Clustered file systems are an extension of VxFS that support concurrent direct
media access from multiple systems.

75
VxFS extent-based allocation
Similar to other file systems on UNIX platforms, VxFS uses index tables to store
information and location information about blocks used for files. VxFS allocation
is extent-based as opposed to block-based.
Block-based allocation: File systems that use block-based allocation assign
disk space to a file one block at a time.
Extent-based allocation: File systems that use extent-based allocation assign
disk space in groups of contiguous blocks, called extents.
Veritas File System selects a contiguous range of file system blocks, called an
extent, for inclusion in a file. The number of blocks in an extent varies and is based
on either the I/O pattern of the application, or explicit requests by the user or
programmer. Extent-based allocation enables larger I/O operations to be passed to
the underlying drivers.
VxFS attempts to allocate each file in one extent of blocks. If this is not possible,
VxFS attempts to allocate all extents for a file close to each other.
Each file is associated with an index block, called an inode. In an inode, an extent
is represented as an address-length pair, which identifies the starting block address
and the length of the extent in logical blocks. This enables the file system to
directly access any block of the file.
VxFS automatically selects an extent size by using a default allocation policy that
is based on the size of I/O write requests. The default allocation policy attempts to
balance two goals:
Optimum I/O performance through large allocations

Minimal file system fragmentation through allocation from space available in
the file system that best fits the data
The first extent allocated is large enough for the first write to the file. Typically, the
first extent is the smallest power of 2 that is larger than the size of the first write,
with a minimum extent allocation of 8K. Additional extents are progressively
larger, doubling the size of the file with each new extent. This method reduces the
total number of extents used by a single file.

77
Using Veritas File System commands
You can generally use Veritas File System (VxFS) as an alternative to other disk-
based, OS-specific file systems, except for the file systems used to boot the
system. File systems used to boot the system are mounted read-only in the boot
process, before the VxFS driver is loaded.
VxFS can be used in place of:
UNIX File System (UFS) on Solaris, except for root, /usr, /var, and /opt.
Hierarchical File System (HFS) on HP-UX, except for /stand.
Journaled File System (JFS) and Enhanced Journaled File System (JFS2) on
AIX, except for root and /usr.
Extended File System Version 2 (EXT2) and Version 3 (EXT3) on Linux,
except for root, /boot, /etc, /lib, /var, and /usr.
Location of VxFS commands

Most Veritas file system commands are located in /opt/VRTS/bin, which must
be included in the PATH environment variable. Other locations where Veritas file
system commands can be found are listed in the following table:
Platform Location of VxFS Commands

Solaris /opt/VRTSvxfs/sbin, /usr/lib/fs/vxfs, /etc/fs/vxfs
HP-UX /sbin/fs
AIX /opt/VRTSvxfs/sbin, /usr/lib/fs/vxfs, /etc/fs/vxfs
Linux /usr/lib/fs/vxfs
General file system command syntax
To access VxFS-specific versions, or wrappers, of standard commands, you use
the Virtual File System switchout mechanism followed by the file system type,
vxfs. The switchout mechanism directs the system to search the appropriate
directories for VxFS-specific versions of commands.
Platform File System Switchout

Solaris -F vxfs
HP-UX -F vxfs
AIX -V vxfs (or -v vxfs when used with crfs)
Linux -t vxfs
Note: The Linux platform includes a native fsadm command in the

/usr/sbin directory. If this path is listed before the /opt/VRTS/bin
directory in the PATH environment variable, provide the full pathname of
the fsadm command (/opt/VRTS/bin/fsadm) to use the VxFS-
specific version of this command.
Using VxFS commands by default

If you do not use the switchout mechanism, then the file system type is taken from
the default specified in the OS-specific default file system file. If you want Veritas
File System to be your default file system type, then you change the default file
system file to contain vxfs.
Platform Default File System File

Solaris /etc/default/fs
HP-UX /etc/default/fs
AIX /etc/vfs
Linux /etc/default/fs

79
Using mkfs command options
You can set a variety of file system properties when you create a Veritas file
system by adding VxFS-specific options to the mkfs command.
Here are some example outputs from a Linux platform before and after a Veritas
file system is created:
mkfs -t vxfs -o N /dev/vx/rdsk/appdg/appvol
version 9 layout
4194304 sectors, 2097152 blocks of size 1024, log size
16384 blocks
rcq size 1024 blocks
largefiles supported
mkfs -t vxfs /dev/vx/rdsk/appdg/appvol

mkfs -m /dev/vx/rdsk/appdg/appvol
mkfs -t vxfs -o
bsize=1024,version=9,inosize=256,logsize=16384,rcqsize=10
24,largefiles /dev/vx/rdsk/appdg/appvol 4194304

Identifying file system type
If you do not know the file system type of a particular file system, you can
determine the file system type by using the fstyp command. You can use the
fstyp command to describe either a mounted or unmounted file system.
Identifying free space

To report the number of free disk blocks and inodes for a VxFS File System, you
use the df command. The df command displays the number of free blocks and
free inodes in a file system or directory by examining the counts kept in the
superblocks. Extents smaller than 8K may not be usable for all types of allocation,
so the df command does not count free blocks in extents below 8K when reporting
the total number of free blocks.

711
Preventing accidental file system unmounts
The Mountlock feature disallows a user or script from unmounting a file system
unless a specific key (identifier) is given during the unmount operation. The ID
can be any string up to 31 characters. It is a good practice to use descriptive
identifiers.
The mount/vxumount commands can be used to mount lock and unlock the file
system with a specific identifier as shown in the slide. To lock/unlock when the file
system is already mounted, use the fsadm command:
fsadm o mntlock=ID mount_point
fsadm o mntunlock=ID mount_point
View the /etc/mnttab file on the Solaris platform or use the /sbin/mount
command to display the Mountlock feature among the file system attributes.
mount -F vxfs -o mntlock="tie" /dev/vx/dsk/appdg/appvol \

/app
cat /etc/mnttab
...
/dev/vx/dsk/appdg/appvol /app vxfs
rw,suid,delaylog,largefiles,qio,ioerror=mwdisable,mntlock
=tie,dev=50c4268 1221602352
If the file system is unmounted without specifying the correct identifier, an error
message is displayed and the file system remains mounted.

Upgrading the Veritas File System layout
The placement of file system structures and the organization of user data on disk is
referred to as the file system layout. The evolution of Veritas File System has
included nine different file system layout versions. Each version has become
increasingly complex to support greater scalability for large files and to minimize
file system fragmentation.
By default, any new file system that you create using VxFS 6.0 has file system
layout Version 9. You can upgrade an existing file system that has an earlier file
system layout to Version 9 by using the vxupgrade command. The upgrade does
not require an unmount and can be performed online.
Upgrading to disk layout Version 9 changes all inodes in the file system. After a
file system is upgraded to disk layout Version 9, it cannot be mounted with releases
prior to VxFS 6.0.
Performing online upgrades

Only a privileged user can upgrade the file system layout. Once you upgrade to a
later layout version, you cannot downgrade to an earlier layout version while the 7
file system is online.
You must perform the layout upgrade procedure in stages when using the
vxupgrade command. For example, you cannot upgrade Version 7 file systems
directly to Version 9. You must upgrade from Version 7 to Version 8, then from
Version 8 to Version 9.
Note: Use vxfsconvert to convert disk layout versions prior to Version 6. For
more information on this command, see the vxfsconvert(1m) manual page.
713
The vxupgrade command
To upgrade the VxFS file system layout, use the vxupgrade command. The
vxupgrade command only operates on file systems mounted for read/write
access.
vxupgrade [-n new_version] [-r rawdev] mount_point
The -n option specifies the new file system layout version number to which
you are upgrading. The new version can be 7, 8, or 9.
The -r rawdev option specifies the path of the raw device. You use this
option when vxupgrade cannot determine which raw device corresponds to
the mount pointfor example, when /etc/mnttab is corrupted.
Displaying the file system layout version

Use the vxupgrade command without the -n option to display the file system
layout version number of a file system. For example, to display the file system
layout version number of a Veritas file system mounted at /app, type:
vxupgrade /app
/app: vxfs file system version 7 layout
In the output, the current file system layout version is displayed.
Using the vxupgrade command

A VxFS file system with Version 7 file system layout is mounted at /app. To
upgrade this file system to Version 9 layout, you execute the following sequence of
commands:
vxupgrade -n 8 /app
vxupgrade -n 9 /app
If you attempt to upgrade directly from file system layout Version 7 to Version 9,
you receive an error.
How does vxupgrade work?

The upgrade process follows this sequence of events:
1 The vxupgrade command creates the lock file in
/lost+found/.fsadm. The lock file blocks any use of the fsadm utility
on this file system during the vxupgrade procedure.
2 The file system is frozen.
3 New file system structures are allocated and initialized.
4 The file system thaws, and the inodes are released.
5 The lock file in /lost+found/.fsadm is removed.
This process does not keep the file system frozen for more than a few seconds.

Logging in VxFS
Role of the intent log
A file system may be left in an inconsistent state after a system failure. Recovery
of structural consistency requires examination of file system metadata
structures.Veritas File System provides fast file system recovery after a system
failure by using a tracking feature called intent logging, or journaling. Intent
logging is the process by which intended changes to file system metadata are
written to a log before changes are made to the file system structure. Once the
intent log has been written, the other updates to the file system can be written in
any order. In the event of a system failure, the VxFS fsck utility replays the intent
log to nullify or complete file system operations that were active when the system
failed.
Traditionally, the length of time taken for recovery using fsck was proportional to
the size of the file system. For large disk configurations, running fsck is a time-
consuming process that checks, verifies, and corrects the entire file system.
The VxFS version of the fsck utility performs an intent log replay to recover a
7
file system without completing a full structural check of the entire file system. The
time required for log replay is proportional to the log size, not the file system size.
Therefore, the file system can be recovered and mounted seconds after a system
failure. Intent log recovery is not readily apparent to users or administrators, and
the intent log can be replayed multiple times with no adverse effects.
Note: Replaying the intent log may not completely recover the damaged file
system structure if the disk suffers a hardware failure. Such situations may require
a complete system check using the VxFS fsck utility.
715
Maintaining file system consistency
You use the VxFS-specific version of the fsck command to check the consistency
of and repair a VxFS file system. The fsck utility replays the intent log by
default, instead of performing a full structural file system check, which is usually
sufficient to set the file system state to CLEAN. You can also use the fsck utility to
perform a full structural recovery in the unlikely event that the log is unusable.
The syntax for the fsck command is:
fsck [fstype] [generic_options] [-y|-Y] [-n|-N] \
[-o full,nolog] special
For a complete list of generic options, see the fsck(1m) manual page. Some of
the generic options include:
Option Description
-m Checks, but does not repair, a file system before mounting

-n|N Assumes a response of no to all prompts by fsck (This option
does not replay the intent log and performs a full fsck.)
-V Echoes the expanded command line but does not execute the
command
-y|Y Assumes a response of yes to all prompts by fsck (If the file
system requires a full fsck after the log replay, then a full fsck is
performed.)
-o p can only be run with log fsck, not with full fsck.
File change log
The VxFS file change log (FCL) is another type of log that tracks changes to files
and directories in a file system. Applications that can make use of the FCL are
those that are typically required to scan an entire file system to discover changes
since the last scan.
Note: The FCL records only that data has changed, not the actual data. It is the
responsibility of the application to examine the files that have changed data to
determine which data has changed.
FCL stores changes in a file in the file system namespace. The FCL log file is
always located in mount_point/lost+found/changelog.
To print the FCL, use fcladm print 0|offset mount_point.
To translate the log entries in inodes to full paths, type:
vxlsino inode_number mount_point
To remove an FCL that has already been turned off, type:

fcladm rm mount_point
Comparing the intent log and the file change log 7
The intent log is used to speed recovery of the file system after a crash. The FCL
has no such role. Instead, the FCL is used to improve the performance of
applications. For example, your IT department mandates that all systems undergo a
virus scan once a week. The virus scan takes some time and your system takes a
performance hit during the scan. To improve this situation, an FCL could be used

717
with the virus scanner. The virus scanner, if using an FCL, could read the log, find
all files on your system that are either new or that have been modified, and scan
only those files.
FCL is used with NetBackup to greatly improve the speed of incremental backups.
FCL is also used with the SmartTier feature of Storage Foundation, with Veritas
file system deduplication, and with Veritas File Replicator to keep track of the
changes in the file system. The SmartTier feature, Veritas File System
deduplication, and Veritas File Replicator are described in detail in the Veritas
Storage Foundation 6.0 for UNIX: Manage and Administer course.

Controlling file system fragmentation
In a Veritas file system, when free resources are initially allocated to files, they are
aligned in the most efficient order possible to provide optimal performance. On an
active file system, the original order is lost over time as files are created, removed,
and resized. As space is allocated and deallocated from files, the available free
space becomes broken up into fragments. This means that space has to be assigned
to files in smaller and smaller extents. This process is known as fragmentation.
Fragmentation leads to degraded performance and availability.
VxFS provides online reporting and optimization utilities to enable you to monitor
and defragment a mounted file system. These utilities are accessible through the
file system administration command, fsadm.
Types of fragmentation
VxFS addresses two types of fragmentation:
Directory fragmentation: As files are created and removed, gaps are left in
directory inodes. This is known as directory fragmentation. Directory
fragmentation causes directory lookups to become slower. 7
Extent fragmentation: As files are created and removed, the free extent map
for an allocation unit changes from having one large free area to having many
smaller free areas. Extent fragmentation occurs when files cannot be allocated
in contiguous chunks and more extents must be referenced to access a file. In a
case of extreme fragmentation, a file system may have free space, none of
which can be allocated.

719
Running fragmentation reports
You can monitor fragmentation in a Veritas file system by running reports that
describe fragmentation levels. You use the fsadm command to run reports on
both directory and extent fragmentation. The df command, which reports on file
system free space, also provides information useful in monitoring fragmentation.
Interpreting fragmentation reports

In general, for optimum performance, the percentage of free space in a file system
should not fall below 10 percent. A file system with 10 percent or more free space
has less fragmentation and better extent allocation.
A badly fragmented file system will have one or more of the following
characteristics:
Greater than 5 percent of free space in extents of less than 8 blocks in length
More than 50 percent of free space in extents of less than 64 blocks in length
Less than 5 percent of the total file system size available as free extents in
lengths of 64 or more blocks
Fragmentation can also be determined based on the fragmentation index. The
fragmentation report displays fragmentation indices for both the free space and the
files in the file system. A value of 0 for the fragmentation index means that the file
system has no fragmentation, and a value of 100 means that the file system has the
highest level of fragmentation. The fragmentation index is new with SF 6.0 and
enables you to determine whether you should perform extent defragmentation or
free space defragmentation.

VxFS defragmentation
You can use the online administration utility fsadm to defragment, or reorganize,
file system directories and extents. The fsadm utility defragments a file system
mounted for read/write access by:
Removing unused space from directories
Making all small files contiguous
Consolidating free blocks for file system use
Sorting entries by the time of last access
Only a privileged user can reorganize a file system.
The fsadm defragmentation options
If you specify both -d and -e, directory reorganization is always completed
before extent reorganization.
If you use the -D and -E with the -d and -e options, fragmentation reports are
produced both before and after the reorganization.
You can use the -t and -p options to control the amount of work performed by 7
fsadm, either in a specified time or by a number of passes. By default, fsadm
runs five passes. If both -t and -p are specified, fsadm exits if either of the
terminating conditions is reached.
Note: On the Linux platform, the -T time option is used instead of the
-t time option because the -t switch is used for file system switchout
mechanism.

721
Free space defragmentation for a file system
The free space defragmentation option is new with SF 6.0. It attempts to get bigger
chunks of free space in the file system by:
Freeing as many fragmented allocation units as possible
Filling as many allocation units completely as possible
Never breaking any file extent during data movement to ensure that file extent
fragmentation does not get worse during the process
Note that you can observe the available free extents by size using the VxFS-
specific df -os command as shown on the slide.

Scheduling defragmentation
The best way to ensure that fragmentation does not become a problem is to
defragment the file system on a regular basis. The frequency of defragmentation
depends on file system usage, activity patterns, and the importance of file system
performance. In general, follow these guidelines:
Schedule defragmentation during a time when the file system is relatively idle.
For frequently used file systems, you should schedule defragmentation daily or
weekly.
For infrequently used file systems, you should schedule defragmentation at
least monthly.
Full file systems tend to fragment and are difficult to defragment. You should
consider expanding the file system.
To determine the defragmentation schedule that is best for your system, select
what you think is an appropriate interval for running extent reorganization and run
the fragmentation reports both before and after the reorganization. If the degree of
fragmentation is approaching the bad fragmentation figures, then the interval
7
between fsadm runs should be reduced. If the degree of fragmentation is low, then
the interval between fsadm runs can be increased.
You should schedule directory reorganization for file systems when the extent
reorganization is scheduled. The fsadm utility can run on demand and can be
scheduled regularly as a cron job.
The defragmentation process can take some time. You receive an alert when the
process is complete.

723
Benchmarking using vxbench
What is benchmarking?
Benchmarking is a testing technique that enables you to measure performance
based on a set of standards, or benchmarks. You can use benchmarking techniques
to try to predict the performance of a new file system configuration or to analyze
the performance of an existing file system.
What is vxbench?
Symantec engineering developed a benchmarking tool called vxbench that
enables you to create different combinations of I/O workloads.
The vxbench program is installed as part of the VRTSspt software installation
and exists under the /opt/VRTSspt/FS/VxBench directory.
Notes on testing performance

The vxbench program applies a workload to a file system and measures
performance based on how long file system operations take. If anything else is
using the file system at the same time, then the vxbench performance reports
are affected.
For sequential workloads: iosize x iocount = size of the file.
The iosize and maxfilesize parameters are defined in units of 1K; therefore,
iosize=8 defines a size of 8K.
The output of vxbench displays elapsed time in seconds, throughput in
KB/second, and CPU time for the system and the user in seconds.

The vxbench_platform command
In the syntax, you specify the command followed by a type of workload. Valid
workloads are:
read Performs a sequential read of the test files
write Performs a sequential write of the test files
rand_read Performs a random read of the test files
rand_write Performs a random write of the test files
rand_mixed Performs a mix of random reads and writes
mmap_read Uses mmap to read the test files
mmap_write Uses mmap to overwrite the test files
After specifying the type of workload, you can add specific options that
characterize the test that you want to perform.
Finally, you specify the name of the file on which to run the test. If you specify
multiple filenames, vxbench_platform runs tests in parallel to each file,
which simulates multiple simultaneous users. If you use the option that specifies
multiple threads, then each simulated user runs multiple threads. The total number
of I/O threads is the number of users multiplied by the number of threads.
Command options
By adding options to the vxbench_platform command, you can simulate a
wide variety of I/O environments. The following table describes some of these
options and their uses. You can display a complete list of vxbench_platform
command options by typing vxbench_platform -h.
Option Use
-h Prints a detailed help message
-P Uses processes for users and uses threads for multithreaded I/O
(This is the default option.)
-p Uses processes for users and for multithreaded I/O
-t Uses threads for users and for multithreaded I/O
Locks I/O buffers in memory
-m
-s For multiuser tests, only prints summary results
-v For multithreaded tests, prints per-thread results
7
-k Prints throughput in kilobytes/second (This is the default option.)
-M Prints throughput in megabytes/second
-i [suboptions] Specifies suboptions describing the test you want to perform
vxbench is included in the VRTSspt package.

725
Using thin provisioning disk arrays
What is a thin provisioning disk array?
Thin provisioning is a hardware-based storage solution that enables system
administrators to configure storage space for a server without pre allocating the
space on storage array. A thin provisioning disk array creates virtual disk drives
(LUNs) that appear to be one size, but whose actual physical storage only covers a
fraction of their claimed size. If a LUN needs more storage, the storage array
allocates more physical storage to it, without changing the presented size.
So for example, a project may require up to a 1TB of storage space over the life of
the project. The actual data that currently exists may be only 100GB. In the
standard method of provisioning, 1TB of space needs to be preallocated. A
majority of that space may never be used and is therefore wasted space.
When using a thin provisioning capable array, a virtual container (virtual volume)
is created for the 1TB. The array then creates/resizes LUNs as actual data is
written to the virtual container. The administrator is not involved after the initial
virtual container is created unless the amount of actual physical storage is used up.
To truly benefit from thin storage, you need the right stack on all hosts:
A multi-pathing driver that supports the thin hardware
A file system optimized not to waste storage on thin volumes
A stack to reclaim space as you migrate to thin storage
A stack to continually optimize utilization of thin storage
SF unlocks thin provisionings full potential with DMP and VxFS which is the
only cross-platform thin storage friendly file system.
Displaying information on thin disks
SF automatically controls the applicability of features such as SmartMove and thin
reclamation based on known device attributes. If SmartMove is enabled only for
thin LUNs and a device is known to be thin by Storage Foundation, then mirroring
operations are optimized to keep the device thin. If a device is known to be
thinrclm, then SF allows thin reclamation commands to be issued to it.
SF 5.0 MP3 and later automatically discover thin LUNs and their attributes. If a
thin LUN is not automatically discovered as thin, you can use the following
command to manually inform SF that the LUN is thin or thin reclaim:
vxdisk -g diskgroup set dm_name thin=[on|reclaim]
The vxdisk -e list command prints the extended device attributes
(EXT_ATTR) as the last column to indicate the type of the device.
To display properties of the devices that support thin provisioning, use the
vxdisk -o thin list command. This command also indicates whether the
LUN supports thin reclamation. Thin reclamation is the process of reclaiming
unused storage that is a result of deleted files and volumes back to the available 7
free pool of the thin provisioning capable array. Not all thin provisioning arrays
support thin reclamation. Use the vxdisk -o thin,fssize list command
to display and compare the physically allocated storage size to the storage size
used by the file system. If there is a big difference between the two sizes, it is time
to initiate a thin reclamation process on the corresponding device.
The vxdisk -p list command displays the discovered properties of the
disks including the attributes related to thin provisioning and thin reclamation.

727
Introducing the SmartMove feature
When you mirror a volume, the whole volume content is normally copied to the
newly added plex. This is because the volume has no knowledge of the data stored
in it and is not aware which blocks are in use. Therefore, if you mirror a
1-Terabyte volume where only 10 GB is in use, the copy operation still copies all
of that 1-Terabyte of volume content.
With the SmartMove feature, Volume Manager can use Veritas File System
information to identify the free blocks and skip copying them. So, in the previous
example, only 10 Gigabytes would be copied to complete the mirror
synchronization. Note that the SmartMove feature is only available when the
volume has a Veritas File System on it. If you are using raw volumes with other
applications, such as databases, you still need to copy the whole mirror content.
By default, the SmartMove feature is turned on all LUNs. To enable the
SmartMove feature only for volumes that contain thin LUNs, you need to specify
usefssmartmove=thinonly in the /etc/default/vxsf file. This

tunable is system-wide and persistent, so it only needs to be set once per server.
Setting this tunable parameter to none completely disables the SmartMove
feature. Note that with SF 5.1 and later, you can also use the vxdefault
command to change the value of this tunable parameter. The vxdefault
command is explained in more detail later in this topic.
Note: The Veritas file system must be mounted to get the benefits of the
SmartMove feature.
This feature can be used for faster plex creation and faster array migration.
Administering thin provisioning parameters
In SF 5.1 and later, the vxdefault command is used to modify and display the
tunable parameters that are stored in the /etc/vx/vxsf file as shown on the
slide.
The sharedminorstart tunable parameter is used with the dynamic disk group
reminoring feature. This feature is used to allocate minor numbers dynamically to
disk groups based on their private or shared status. Shared disk groups are used
with Cluster Volume Manager and are not covered in this course.
The fssmartmovethreshold defines a threshold value; only if the filesystem
%usage is less than this threshold, then the SmartMove feature is used. By default,
the fssmartmovethreshold is set to 100 which means that SmartMove is used with
all vxfs file systems with less than 100% usage.
The autostartvolumes tunable parameter turns on or off automatic volume
recovery. If this parameter is set to on, VxVM automatically recovers and starts
disabled volumes when you import, join, move or split a disk group.
7

729
Migrating to thin provisioning using SmartMove
The example steps provided on the slide for migrating from a traditional disk array
to a disk array that supports thin provisioning assume that the total space provided
by the thin provisioning array is larger in size than the traditional LUNs used to
build the volume and file system. Here is an example implementation:
1 Turn the SmartMove feature on if necessary.
vxdefault list
vxdefault set usefssmartmove all (if necessary)
2 Add the new, thin LUN, called thinarray0_01 in this example, to the
existing disk group. Note that you can use multiple LUNs although this
example is showing only one.
vxdisksetup -i thinarray0_01
vxdg -g appdg adddisk thinarray0_01
3 Add the new, thin LUN as a new plex to the volume.

vxassist -g appdg mirror appvol thinarray0_01
4 Test the performance of the new LUN.
You can optionally direct all read requests to the plex on the new LUN and
then use benchmarking tools or statistic commands to test performance.
vxvol -g appdg rdpol prefer appvol appvol-02
5 Remove the original mirror and the original LUN.
vxplex -g appdg -o rm dis appvol-01
6 Optionally, grow the file system and the volume to use all of the larger thin
LUN.
vxresize -g appdg -x appvol newsize thinarray0_01

Reclaiming storage with thin provisioning
Thin provisioning (TP) capable arrays allocate actual physical storage only when
the applications using the LUNs write data. However, when portions of this data is
deleted, storage is not normally reclaimed back to the available free pool of the
thin provisioning capable array.
Storage Foundation uses the VxFS knowledge of used and unused blocks at the file
system level to reclaim that unused space. This process must be manually started
by the system administrator.
Thin reclamation can only be performed on volumes with mounted VxFS file
systems. Volumes without a VxFS file system or volumes that are not currently
mounted are not reclaimed. If the volume consists of a mix of thin-provisioning
disks and regular disks, the reclamation is only performed on the thin-provisioning
disks.
Thin reclamation can be triggered on one or more disks, enclosures or disk groups,
or at the file system level on a mounted VxFS file system as displayed on the slide.
When you reclaim at the file system level, the command goes through all the free 7
extents in the file system and issues the storage level reclaim on the regions which
are free. Every time the command is run, the complete file system is scanned.
VxVM is optimized to issue the reclaim only to the TP LUNs in the file system.
When you reclaim at the VxVM level, the reclaim command goes through the list
of all TP LUN-backed mounted file systems associated to the specified object, and
issues the reclaim on all the file systems. The output displays the list of volumes
skipped and the list of volumes reclaimed.

731
Aggressive reclamation in SF 5.1 and later
Thin reclamation as implemented in SF 5.0 MP3 (and as described on the previous
page) is a best effort in the sense that it takes any existing contiguous free space in
the file system and reports it to Volume Manager for reclamation. If that
contiguous free space is large enough to be reclaimed in the array (based on chunk
size and chunk alignment on the LUN), the space is effectively reclaimed.
Otherwise, the free space is not reclaimed.
The core benefit of this approach is that it either returns storage to the array free
pool, or it does not; the operation never triggers additional storage usage.
The main drawback is that if the free space is fragmented into small contiguous
areas, it may not get reclaimed.
SF 5.1 and later have the capability to perform more aggressive reclamation by
moving data around in the file system to maximize the size of the contiguous free
space. This is an additional option for reclamation that can only be triggered at the
file system level using the fsadm -R -A mount_point command. Note that
you can use the -o analyze option first to determine if you should perform a
normal reclaim operation or an aggressive reclaim operation.
Notes:
Aggressive reclamation can only be performed on file systems that are known
to use thin reclaim capable storage.
Aggressive reclamation can increase the thin storage usage temporarily during
the data compaction process.

Automatic reclamation for volumes
In SF 5.1 and later, commands like vxassist remove volume, and vxedit
rf rm volume, and the volume shrink operation can trigger automatic
reclamation if the released storage is on thin provision reclaimable LUNs.
The reclaim operation is asynchronous, because the delete or shrink operations are
quicker.
The reclamation of the storage released due to volume delete or shrink is
performed by the vxrelocd daemon and can be controlled by the following
tunable parameters:
reclaim_on_delete_wait_period=[-1 366]
A value of -1 indicates immediate reclamation and a value of 366 indicates that
no reclamation will be performed by the vxrelocd daemon.
reclaim_on_delete_start_time=[00:00-23:59]
The vxdg destroy diskgroup command does not reclaim any storage
automatically. The thin provision reclaimable LUNs belonging to the destroyed
disk group must be reclaimed manually using the vxdisk reclaim disk 7
command.

733
Default VxVM behavior with thin LUNs and SF Enterprise license
The SF Enterprise license enables the FastResync feature of Veritas Volume
Manager. The FastResync feature is used for fast resynchronization of the plexes
of a mirrored volume. This feature is mostly used with instant volume snapshots
and is explained in more detail in the Veritas Storage Foundation 6.0 for UNIX:
Manage and Administer course. However, it is also used for resynchronization of
plexes that become stale with respect to the contents of the volume due to failures.
Without FastResync, when a plex of a mirrored volume becomes stale, the
resynchronization involves an entire atomic copy from the active plexes to the
stale plex. With FastResync, Volume Manager keeps track of the changed regions
of the volume and synchronizes only those regions. This behavior helps with
optimizing thin LUN usage. Therefore, FastResync is automatically enabled on
mirrored volumes if the disk group contains thin LUNs and the feature is licensed.
When FastResync is enabled on a mirrored volume, a data cache object (DCO) is

created with a DCO volume to hold the FastResync maps as well as the DRL
recovery maps and other special maps used with instant snapshot operations on
disk.
Note that you cannot remove a mirrored volume using the vxassist remove
volume command if it has an associated DCO log. To remove a mirrored volume
with a DCO log, use the following vxedit command:
vxedit -g diskgroup -rf rm volume_name

Lab 7: Administering File Systems, page A-85
Lab 7: Administering File Systems, page B-147
203 Lesson 7 Administering File Systems Copyright 2012 Symantec Corporation. All rights reserved.
735

205
Labs
Appendix A


206 A2 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
Lab environment overview
The labs for this course are performed within a virtual environment consisting of
five virtual machines. This virtual environment has been developed specifically for
this course and is detailed in the next sections.

207 Copyright 2012 Symantec Corporation. All rights reserved.
A3
Virtual machine configuration
These labs use the five virtual machines shown in the slide. The introductory page
of each lab shows which virtual machines are being used. The labs contain icons,
such as those shown in the slide, to indicate which steps are performed on which
virtual machines.
System name Description Fully qualified host name

mgt NFS Server mgt.example.com
DNS Server
iSCSI Array
3par iSCSI Array 3par.example.com
vom Veritas Operations vom.example.com
Manager MS
sym1 Storage Foundation sym1.example.com

Server
Server
Note: In the following exercises, the virtual machines are identified by the system
names in the preceding table.

Required parameters
The software and the scripts required during the labs throughout the course exist in
subdirectories under the /student directory on each user system as displayed on
the slide.
Virtual machine account information

Refer to the following table for the logon credentials to the various virtual
machines:
System Logon information

mgt The user does not log into this system unless instructed to
by the instructor
3par The user does not log into this system unless instructed to
by the instructor
vom User: root
Password: veritas
sym1 User: root
Password: veritas
sym2 User: root
Password: veritas
A

A5
Accessing virtual machines
Depending on how and where you attend this class, you access the virtual
machines in the lab environment in one of several ways. Your instructor will direct
you to the appropriate set of lab procedures for the environment you are using in
this class.
If you are working with VMware Workstation, continue to the VMware
Workstation Introduction section on the next page.
If you are working with Hatsize, skip to the Hatsize Introduction section that
starts after all the VMware Workstation exercises.

Lab 1: VMware Workstation Introduction
In this lab, you become familiar with the lab environment used with the Veritas
Storage Foundation 6.0 for UNIX: Install and Configure course, as well as the
method for accessing systems.
The hands-on portion of this lab enables you to perform basic operations on virtual
machines, as shown in the slide overview. Adopting the best practice guidelines
provided in this lab enables you to perform the remaining labs more efficiently.
Note: The exercises in this section apply to VMware Workstation lab

environments. Exercises for other environments, such as Hatsize, are
located elsewhere in this document.
Two parallel versions of the labs enable you to choose the level of detail that suits
your experience level:

Appendix A provides step-by-step lab instructions.

211 Lab 1: VMware Workstation Introduction
A7
VMware Workstation lab environment
In this lab environment, each of the virtual machines is connected to a virtual
network (10.10.2.0) residing on the host. This network can be used to access the
Web server on the vom virtual machine from a Web browser on the host machine
(if available). However, lab instructions use a Web browser on the vom virtual
machine itself.
Note that other virtual networks exist in the environment for accessing multiple
disk arrays and for the purpose of multi-pathing.

VMware Workstation interface
The screen shot in the slide shows the VMware Workstation interface used to
access the virtual machines. Virtual machines are referred to as guest systems,
which are running their own guest operating systems. The physical system running
the VMware Workstation application is referred to as the host system running the
host operating system. Virtual machines are accessed by clicking on the tab with
the appropriate system name.

A9
Exercise 1: Starting virtual machines (VMware Workstation)
In this exercise, you start the virtual machines and display the existing snapshots
for each virtual machine.
1 If VMware is not already open, start VMware Workstation.
2 Review the current settings for each virtual machine.
mgt
3 Start the mgt virtual machine.

3par
4 Start the 3par virtual machine.

CAUTION Do not proceed to the next step until the login screen is visible on
both mgt and 3par. The mgt server will show a typical RHEL
graphical logon screen, while the 3par server will stop at a CLI
login prompt.
Note: The first two virtual machines must be turned on at all times during all lab
testing. Failure to start the mgt and 3par virtual machines results in
missing files and missing shared LUNs.
vom
5 Start the vom virtual machine.
sym1
6 Start the sym1 virtual machine.
sym2


A11
Exercise 2: Logging on to virtual machines (VMware Workstation)
Log on to each virtual machine to become familiar with the logon procedures for
each system type.
Note: Do not log onto the mgt and 3par virtual machines unless the instructor
requests you to do so.
vom
1 Log on to VOM Server (vom) as the root user.
sym1
2 Log on to the first Storage Foundation Server (sym1) as the root user.
sym2
3 Log on to the second Storage Foundation Server (sym2) as the root user.
4 Press Ctrl+Alt to release keyboard and mouse controls from the virtual
machine.

Exercise 3: Adjusting the VMware view (VMware Workstation)
Adjust the VMware view controls to become familiar with navigating a virtual
machine.
vom
1 Select View > Quick Switch to enable the Quick Switch view.
How is the Quick Switch view different from the default view?
2 Press F11 to change back to the default view.
Note: When working through the lab exercises, use the F11 shortcut to toggle
between the default and Quick Switch views, as desired.

A13
Exercise 4: Running basic commands (VMware Workstation)
Determine whether the virtual machines can communicate by way of TCP/IP on

the virtual network.
vom
1 On the VOM Server, open a terminal window if none is already open.
2 Record the IP addresses assigned to this system.
VOM Server IP address - eth0: ___________________________________

3 From the terminal windows, ping default gateways.
Did you receive a reply, indicating that systems are communicating?
Note: If a ping command reports unknown host or timeout errors, verify

the command syntax, and then contact the instructor for assistance.
4 Use the nslookup command to view the fully qualified host name of the first
Storage Foundation Server (sym1).
What is the fully qualified host name of server?

sym1
5 On the first Storage Foundation Server (sym1), open a terminal window if

none is already open.

sym1 Server IP address - eth0: ___________________________________
7 From the terminal window, ping default gateways.

8 Use the nslookup command to view the fully qualified host name of the
second Storage Foundation Server (sym2).
What is the fully qualified host name of sym2?
9 Ensure that iSCSI LUNs are available using the fdisk -l command.
Note: The mgt and 3par virtual machines must be running to have access to the
iSCSI LUNs. If only the sda and sdb disks are visible, contact the
instructor to isolate the issue.
sym2
10 On the second Storage Foundation Server (sym2), open a terminal window if


sym2 Server IP address - eth3: ___________________________________ A

A15

VOM management server (vom).
What is the fully qualified host name of vom?
End of lab

Lab 1: Hatsize Introduction
way to access the systems in it.
Note: These exercises are to be used only if the class is using the hosted Hatsize
platform to access the lab environment. Exercises for other environments,
such as VMware Workstation, are located elsewhere in this document.


221 Lab 1: Hatsize Introduction
A17
Hatsize lab environment
The following table provides a translation of virtual machine system names
referred to in the lab guide to the corresponding system names in the Hatsize
interface. Each system name is prefixed with S#. (Student number) in Hatsize.
System Name Description Hatsize Name

mgt NFS Server S#.mgt
DNS Server
iSCSI Array
scst iSCSI Array S#.scst
vom Veritas Operations S#.vom
Manager Management
Server
sym1 Storage Foundation S#.sym1
Server
Server

Hatsize interface
The screen shot in the slide shows the Hatsize interface used to access the virtual
machines. Instead of using tabs, such as the tabs in VMware Workstation, you
access Hatsize virtual machines from the Operations and Window menus. Other
key interface elements include:
Title Bar: Indicates the currently connected machine and whether you have
control of the machine or are in view-only mode
Operations: Is used to connect to additional virtual machines
Window: Is used to switch between active virtual machines
System Control: Is used to start, stop and restart virtual machines
Time remaining: Indicates the time remaining in the session

223 Lab 1: Hatsize Introduction Copyright 2012 Symantec Corporation. All rights reserved.
A19
Exercise 1: Connecting to the lab environment (Hatsize)
Log on to Hatsize and connect to the first system. For each lab environment in
Hatsize, a particular virtual machine is marked as a primary machine. All other
machines are marked as secondary machines. When you connect to the Hatsize
interface, you are initially connected to the primary virtual machine.
1 Locate the Hatsize portal URL and login credentials from your registration
e-mail. Record your credentials here:
Hatsize username:
Hatsize password:
2 Your student number is the number at the end of your Hatsize username
recorded in the previous step.
Record your student number here:
Note: When you use the Hatsize environment, all of the virtual machines
assigned to you are prefixed with a letter and your student number. For
example, if your student number is 8, the virtual machine named vom is
named something like k8-vom or s8-vom. Because the prefix is
different for each student, the lab exercises refer only to the system
name without the prefix.
3 In Internet Explorer, open the Hatsize portal URL and log in with your
assigned user name and password recorded in a previous step.
4 After logging in, find your class in the Current Classes table and click Enter.
Note that the name of your class will be different than the sample shown here.

Sample:
5 In the Agenda for your class, find the Day 1 lab session and click OPEN.
6 Confirm that you see the primary machine connecting. Note that the machine
name you see will be different than the one shown in the following sample
7 Wait for the first console window to open.

A21
sym1
8 Click in the console window and log in to sym1 using the following
credentials:
Username root
Password veritas

Exercise 2: Connecting to additional virtual machines (Hatsize)
Connect to additional virtual machines to become familiar with switching between

systems.
sym1
1 Use the Operations menu to connect to sym2.
sym2
2 Click in the console window and log in to the sym2 system using the following
credentials:
Username root
Password veritas
3 Use the Window menu to switch back to sym1.
sym1
4 Use the Operations menu to connect to vom.

vom
5 Click in the console window and log in to vom using the following credentials:
A
Username root
Password veritas
A23
6 Use the Operations menu to disconnect the secondary machine.
sym1
7 Using the Window menu, verify that the console window for the vom system
is closed.
Note: In further labs, use the steps you practiced in this exercise to navigate
between different virtual lab systems in the Hatsize environment. The lab
solutions will no longer display the steps needed to navigate from one
virtual machine to another.

Exercise 3: Running basic commands (Hatsize)

the virtual networks.
sym1


3 From the terminal window, ping sym2 IP addresses corresponding to each of

these networks. Note that sym2 system IP addresses have .12 in the last octet
on each network; for example, 10.10.2.12 on the 10.10.2.0 network.


A25
Note: The mgt and scst virtual machines must be running to have access to the
sym2





vom

13 From the terminal windows, ping sym1 IP addresses corresponding to each of




A27
Exercise 4: Restarting virtual machines (Hatsize)
If the lab steps instruct you to restart a VMware machine, you must preserve the
system state during the process. Otherwise, the machine is restored to the initial
state and loses any changes you have made. Only discard the state of the machine
after consulting with your instructor. There are two methods, either within the
operating system on the virtual machine, or in the console System Control menu.
sym2

2 From a terminal window, use the shutdown -ry now command to restart
the virtual machine.
Note: Using this method preserves system state.
sym1
Note: In this portion of the lab, you do not actually restart the virtual machine;
you stop at the screen where you can restart.
3 Select the system to control from the System Control menu.
4 If enabled for your course, you can start, stop, and restart the virtual machine,
either keeping state or discarding state. As previously mentioned, you do not
discard state without first consulting with your instructor.
Note: Do not click Do Action here. Instead, click Close. If you restart, you
may have to wait longer to start the next lab while the machine restarts.

Note: If at any time, by timeout or other condition, you are disconnected from
the primary machine, you can reconnect by selecting Operations >
Connect To Primary from the menu, as shown in the following dialog
box.
5 At the end of the session, or when otherwise necessary, you can use the File
menu to quit out of the console.
Note: To reconnect, use the procedure shown in Exercise 1.
End of lab

A29

Lab 2: Installing SF and Accessing SF Interfaces
In this lab, you verify that your lab system is ready for SF 6.0 installation. You
then install Veritas Storage Foundation 6.0 on your lab systems.
This lab contains the following exercises:
Verifying that the system meets installation requirements
Installing Veritas Storage Foundation
Performing post-installation and version checks
Optional lab: Setting up Veritas Enterprise Administrator
Optional lab: Text-based VxVM menu interface
Optional lab: Accessing CLI commands

235 Lab 2: Installing SF and Accessing SF Interfaces Copyright 2012 Symantec Corporation. All rights reserved.
A31
Lab information
In preparation for this lab, you need the following information about your lab
environment.
Object Value
root password veritas
Host names of lab systems sym1
sym2
Domain name example.com
Fully qualified hostnames (FQHN) sym1.example.com
sym2.example.com
Boot disk on lab systems: sda
Location of Storage Foundation 6.0 /student/software/sf/sf60
software:
Location of SORT data collector: /student/software/sf/sort
Location of lab scripts: /student/labs/sf/sf60
The exercises for this lab start on the next page.


Exercise 1: Verifying that the system meets installation
requirements
sym1
1 Before installing Storage Foundation, save the following important system

files into backup files named with a .preVM extension. Also, save your boot
disk information to a file for later use (do not store the file in /tmp). You may
need the boot disk information when you bring the boot disk under VxVM
control in a later optional lab.
/etc/grub.conf
/etc/modprobe.conf
2 If you have access to the Internet, start a Web browser and navigate to the
Symantec Operations Readiness Tools (SORT) Web site at
https://sort.symantec.com. In the SORT section, click the link for
My SORT. Under the Custom Reports section, click the Data Collector tab.
Select the link for the Linux (x86-64) operating system. Save the SORT data
collector sharball to a local directory, such as /var/tmp, or to the Desktop.
If you do not have access to the Internet, copy the SORT data collector sharball
located in the /student/software/sf/sort directory to a local
directory, such as /var/tmp.
Note: The SORT data collector is updated for each release. You can download
the latest version from https://sort.symantec.com.
3 Decompress the SORT data collector sharball you copied to the local directory.
Note that you may need to change file permissions to execute the sharball or
run it using sh. When the Would you like to run the data
collector now? prompt is displayed, enter n.
4 Run SORT data collector and verify completion using displayed text output.
a Start the SORT utility. If you need to install Storage Foundation on more A
than one system, start the SORT utility to check all systems.

A33
b If your system has access to the Internet and a more recent version of the
SORT utility is available than the version you are running, you are
prompted that a newer version is available. Symantec recommends that you
always use the latest version of the SORT utility.When prompted to accept
the terms and conditions enter y.
c When prompted for which task to accomplish, select option 1)

Installation/Upgrade report and press Enter to continue.
d When prompted to choose a Symantec Enterprise product family, select

option 2) Storage Foundation and HA Solutions and press
Enter to continue.
e When prompted on which system to run the report, select option 2) One
or more remote systems and press Enter to continue.
f When prompted, type the names of the systems that you desire to test.
Note: SORT data collector uses the same code base as the CPI installer, so
you can specify multiple systems of the same OS and the utility
includes all specified systems in the test. A single XML file is
created that includes all systems.
g Provide the user name for accessing remote systems if you entered a
system other than the system that contains the SORT utility.
h After the SORT data collector checks for partial clusters and performs
some basic data collection, choose the Symantec enterprise product you
want to install or upgrade to. Select option 1) Veritas Storage
Foundation and press Enter to continue.
i Choose the product version to which you want to install or upgrade. Select
option 1) 6.0 and press Enter to continue.
j The SORT data collector collects data and generates XML and TXT report
files. If the system has access to the SORT Web site you are prompted to
upload the file. Otherwise, a message is displayed stating that the SORT
Web site cannot be accessed and describing how to manually upload the
file.
k When all tasks have been completed, you are prompted to exit the data
collector; select y.
l If desired, view the report .txt file.

5 If you have access to the Internet, upload the SORT .xml output file to the
SORT Web site. Otherwise, skip steps 5 and 6.
Note: Uploading the SORT .xml report to the SORT Web site requires that
there be access to the Internet from the classroom lab. If an external
connection is not available, the .xml file can be saved to a USB drive
and these steps can be performed at a later date.
6 Using the displayed output, determine if the system is ready for installation.

A35
Exercise 2: Installing Veritas Storage Foundation
sym1
1 Open a terminal window and navigate to the directory that contains the Storage
Foundation 6.0 installer script.
2 Perform a CPI installation of Storage Foundation 6.0.
a Start the installer script.
Note: The SF installer script is designed to check for SSH

communications first and then RSH communications if SSH is not
available.
b Select I for Install a Product option.
c Select 3 for Storage Foundation (SF) option.
d Type y to agree to the terms of the End User License Agreement (EULA).
e Select 3 for Install all rpms.
f Type the names of your two systems when prompted. The server where the
installer script was executed on is the default value.
g Observe that the following checks complete successfully;

System communications
Release compatibility
Installed product
Prerequisite patches and rpms
Platform version
Product licensing
Product prechecks
If you discover any issues, report them at this time.

h Press Enter to scroll through the list of packages and start the package
installation.
i Select 2 for the Enable keyless licensing and complete system licensing
later option.
j Select 2 for SF Enterprise product mode to license.
k Type n to not enable replication.
l Observe that the Storage Foundation startup completes successfully.
m View the summary file, if desired.
3 Check to ensure that the Storage Foundation path (/opt/VRTS/bin) is

present in the profile.
Notes:
Your lab systems are already configured with the PATH and MANPATH
environment variable settings. However, in a real-life environment, you
must modify /usr/.bash_profile or /etc/profile yourself.
The VxVM commands in the /opt/VRTS/bin directory are linked to
the same commands in /usr/lib/vxvm/bin.
4 Verify that Storage Foundation 6.0 packages have been properly installed.
5 View the log files from the installation using the location specified at the end
of the installation. The log file directory is located in
/opt/VRTS/install/logs.
6 Use the vxlicrep command to view the keys that were installed during the
installation.

A37
Exercise 3: Performing post-installation and version checks
sym1
2 Perform a CPI post-installation check of the Storage Foundation 6.0 systems.

available.
b Select O for the Perform a Post-Installation Check option.
c Select 3 for the Storage Foundation (SF) option.
d Type the names of your two systems when prompted. The server where the
installer script was executed is the default value.
e Observe that the following checks complete successfully;
Installed product
Platform version
Product prechecks
If you discover any issues report them at this time.
f Observe that the Storage Foundation postcheck completes successfully.
g View the summary file, if desired.
3 Perform a version check of the installed Storage Foundation 6.0 systems. Start
the installer script with the -version option. Specify the sym1 and
sym2 system names.
available.
Note: The installer script attempts to contact the SORT Web site to
check for product updates.

A39
Exercise 4: Optional lab: Setting up Veritas Enterprise
Administrator
sym1
Note: Check with your instructor to see if you have more time to complete the
optional lab exercises. You do not need to perform the optional lab
exercises unless you have extra time. The optional exercises do not have
any impact on further labs.
The VEA GUI client package has been removed from the Storage Foundation
installed packages, although the object bus (VRTSob) is still present. This section
covers how to enable the server and install the VEA GUI client if desired.
1 From a terminal window, use the vxsvcctrl command to activate vxsvc.
2 Verify that the service is online (enabled).
3 Use the ps -ef command to determine if the vxsvc daemon is running. If it

is not, use vxsvcctrl start to start the daemon.
4 Attempt to start the VEA GUI using the vea command. Observe the message
displayed.
5 Navigate to the directory that contains the VEA GUI package.
6 Install the VEA GUI package using the appropriate OS commands.
7 Re-create the symbolic link from /opt/VRTS/bin/vea to

/opt/VRTSob/bin/vea. By default, vea is symbolically linked to
/opt/VRTS/bin/vea.sh.
8 Verify that you can start the VEA GUI and connect to the local host.

244A40 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
9 In the Select Profile window, click the Manage Profiles button and configure
VEA to always start with the Default profile.
10 Click the Connect to a Host or Domain link and connect to your system as
root.
11 On the left pane (object tree) view, navigate the system and observe the various
categories of VxVM objects.
12 Select the Assistant perspective, on the quick access bar and view tasks for
systemname.
13 Using the System perspective, determine which disks are available to the OS.
14 Execute the Disk Scan command and check if any messages are displayed on
the Console view.
15 Which commands were executed by the Disk Scan task?
16 Exit the VEA graphical interface.
17 Create a root equivalent administrative account named admin1 for use of VEA.
18 Test the new account. After you have tested the new account, exit VEA.

A41
Exercise 5: Optional lab: Text-based VxVM menu interface
sym1
1 From the command line, invoke the text-based VxVM menu interface using
the vxdiskadm command.
2 Display information about the menu or about specific commands.
3 Which disks are available to the OS?
4 Exit the vxdiskadm interface.


Exercise 6: Optional lab: Accessing CLI commands
sym1
This exercise introduces several commonly used VxVM commands. These

commands and associated concepts are explained in detail throughout this course.
If you have used Volume Manager before, you may already be familiar with these
commands. If you are new to Volume Manager, this exercise aims to show you the
amount of information you can get from the manual pages. Note that you do not
need to read all of the manual pages for this exercise.
1 From the command line, invoke the VxVM manual pages as follows and then
read about the vxassist command.
2 Which vxassist command parameter creates a VxVM volume?
3 From the command line, invoke the VxVM manual pages to read about the
vxdisk command.
4 Which disks are available to VxVM?

vxdg command.
6 How do you list locally imported disk groups?
vxprint command.
A

A43
8 Determine which Storage Foundation daemons are running on the system
using the ps -ef command.
End of lab

Lab 3: Getting Started with VOM
The purpose of this lab is to provide an introduction to the Veritas Operations
Manager 4.1.
Installing the VOM management server (MS)
Adding managed hosts to the MS
Adding the active management add-on
Prerequisite setup
To perform this lab, you use the vom virtual machine, which is a Linux server that
is used to install and configure the VOM management server (MS). The other lab
systems (sym1 and sym2) already have SF 6.0 installed. Before starting this lab,
ensure that the VOM virtual machine is turned on.

249 Lab 3: Getting Started with VOM Copyright 2012 Symantec Corporation. All rights reserved.
A45
Lab information
environment.
Object Value
VOM management server root veritas
password
Host name - Management server vom
Host name - Managed hosts sym1
sym2
Shared data disks: emc0_dd7 - emc0_dd12
3pardata0_49 - 3pardata0_60
Location of VOM 4.1 software: /student/software/vom/vom41


Exercise 1: Installing the VOM management server (MS)
vom
1 On your system, navigate to the directory that contains the binary for the VOM
central management server
(Veritas_Operations_Manager_CMS_4.1_Linux.bin binary).
2 Copy the CMS binary to the /tmp directory. Then, navigate to the /tmp
directory. If necessary, change the permissions of the file so that the file is
executable. Execute the binary.
Note: You cannot execute this binary from an NFS share. If you do, the
extraction of the packages fails.
3 Verify that the xprtld process is started.
4 Open a Web browser and type the URL shown at the completion of the
installation. If the browser is unable to resolve the system name, replace the
system name with the IP address or use the fully qualified host name.
Notes:
This URL is only used for configuration. Do not use it after the VOM
management server is configured.
You may be prompted to choose a digital certificate. If a certificate is
displayed, choose the most appropriate certificate.
5 You are prompted for a password. Type the root user and password for the
system that the VOM server was installed on.
6 A configuration screen displays showing the Server Name and Server

Address. These values are, typically, correct; if they are not, change them to
the appropriate values. Click Next to continue. A

251 Lab 3: Getting Started with VOM
A47
7 Next, you are prompted for a database location. Symantec recommends that
you use the default values. Click Next to continue.
8 Next, you are asked whether to Enable Analytics Gathering. This allows
Symantec to track the usage of the product so as to optimize the user interface
for future versions of this product. For the purpose of the labs, remove the tick.
Click Finish to complete the configuration.
9 After you complete all of the configuration steps, click the Launch Web
Console button. Log into the Web console as the root user.

Exercise 2: Adding managed hosts to the MS
This section requires an additional system that has SF 6.0 pre-installed but is not
already configured in the VOM MS. For this lab section, use the sym1 and sym2
virtual machines.
sym1
1 Open a terminal window and use the ps -ef command to determine if the
vxsvc daemon is running. If it is not, use vxsvcctrl activate followed
by vxsvcctrl start to start the daemon.
Note: You are enabling the vxsvc service now for ease of use later in the lab.
2 Verify that the service (isisd) is online (enabled) on the system to be added
as a managed host on the MS server.
sym2

A49
vom
5 If the Web console is already open, skip this step. Otherwise, open a Web
browser and type the URL for the VOM MS Web console on the address line.
You may receive an error about the Web sites certificate; click the buttons
necessary to continue to this Web site. Log on using the root username and
password for your server.
6 Select the Settings tab, and then from the submenu, select Host Management.
7 From the Actions pull-down menu, select Add Hosts(s). A new Add Host(s)
window opens.
8 Type the fully qualified host name of the first system to be added as a managed
host (sym1.example.com). Type root for the username and the root
password.
9 Click the Add Entries button and type the fully qualified hostname of the
second system to be added as a managed host (sym2.example.com). Type
root for the username and the root password.
10 Click Next to have the VOM server add the hosts.
Note: The VOM MS server and the managed host must be time synchronized.
Check the system times using the date command to ensure that the
time difference between the two systems is not greater than five
minutes.
11 Click the OK button to exit the Add Host(s) window.
12 Verify that your hosts have been added. If so, they are now visible when you
navigate to Manage > Servers > Hosts.

Exercise 3: Adding the active management add-on
vom
1 If the Web console is already open, skip this step; otherwise, open a Web
You may receive an error about the Web sites certificate. Click the link to
continue to this Web site. Log on using the root username and password for
your server.
2 Select the Settings tab and then, from the sub menu, select Deployment
Management.
3 From the Actions pull-down menu, select upload. A new Upload to

Repository window is displayed.
4 In the Upload to Repository window, click the Browse button and browse to
the folder that contains the Active Management add-on (VRTSsfmunixadm-
4.1.100.0.sfa). Typically, this is located in /student/software/
vom/vom41/add-ons. If it is not, ask the instructor for the correct location.
Select the VRTSsfmunixadm-4.1.100.0.sfa file and click Open. Click
the Upload button to begin the upload of the add-on to the VOM MS. When
the upload is complete, click the Close button to exit the Upload to
Repository window.
5 The Active Management add-on is now present in the Deployment

Management Repository. Verify that the Installed Status shows Not
Installed.
6 Select the Storage Foundation Administration for Unix add-on radio button
from the Deployment Management Repository. Then from the Actions pull-
down menu, select install. A new Install Solution window is displayed.
7 In the Install Solution window, click the Install button to start the deployment
A
of the add-on. After the deployment completed, the following message is
displayed:

A51
Install request sent successfully. If the solution is
being installed on central server then the Web Server
needs to be restarted after successful installation
using command ( /opt/VRTSsfmcs/bin/vomsc restart
sfmcswd )
Click the OK button to close the wizard.
8 The browser now displays the Deployment Summary. Note that the Result
shows Enabled.
9 On a terminal session on the VOM MS server, restart the Web server.
10 Refresh the browser and return to the Deployment Management page by

selecting the Settings tab, and then, from the sub menu, select Deployment
Management. Verify that the Installed Status shows Enabled.
Note: After the Web server is restarted, you may be asked to log back into the
Web console.
End of lab

Lab 4: Creating a Volume and File System
In this lab, you create new disk groups, simple volumes, and file systems, mount
and unmount the file systems, and observe the volume and disk properties. The
first exercises use the command line interface. The optional exercises use the
VOM interface.
Creating disk groups, volumes and file systems: CLI
Removing volumes and disks: CLI
Destroying disk data using disk shredding: CLI
Optional lab: Creating disk groups, volumes, and file systems: VOM
Optional lab: Removing volumes, disks, and disk groups: VOM
If you use object names other than the ones provided, substitute the names
accordingly in the commands.
CAUTION In this lab, do not include the boot disk in any of the tasks.
Prerequisite setup
To perform this lab, you need a lab system with Storage Foundation pre-installed,
configured and licensed. In addition to this, you also need four empty and unused
external disks to be used during the labs. A

257 Lab 4: Creating a Volume and File System Copyright 2012 Symantec Corporation. All rights reserved.
A53
Although you should not have to perform disk labeling, here are some tips that
may help if your disks are not properly formatted:
On Linux, if you have problems initializing a disk, you may need to run this
command: fdisk /dev/disk.
Use options -o and -w to write a new DOS partition table.
If you are unsure of the device name, you can use the fdisk -l command to
list all devices that are visible to the Linux Operating System.
Note: If there are multiple paths to each disk, the fdisk -l output will show a
higher number of devices than actually present.
Lab information
environment.
Object Value
Host names of lab systems vom
sym1

Exercise 1: Creating a volume and file system: VOM

Exercise 1: Creating disk groups, volumes and file systems: CLI
sym1
1 View all the disk devices on the system. What is the status of the disks assigned
to you for the labs?
2 Choose a disk (emc0_dd7) and initialize it, if necessary, using the CLI. Using
the vxdisk -o alldgs list command observe the change in the Status
column. What is the status of the disk now?
Do not initialize the sda device, this is the system boot disk.
3 Create a new disk group using the disks you initialized in the previous step
(emc0_dd7). Name the new disk group appdg. Observe the change in the disk
status.
4 Using the vxassist command, create a new volume of size 1g in appdg.

Name the new volume appvol.
5 Create a Veritas file system on the appvol volume, mount the file system to the
/app directory. Create the directory if it does not exist.
6 Make sure that the file system is mounted at boot time.
7 Unmount the /app file system, verify the unmount, and remount using the
mount -a command to mount all file systems in the file system table.
8 Identify the amount of free space in the appdg disk group. Try to create a
volume in this disk group named largevol with a size slightly larger than the
available free space, for example 2g on standard Symantec classroom systems.
What happens?
9 Choose a second disk (emc0_dd8), initialize it, if necessary, and add it to the A
appdg disk group. Observe the change in free space.

A55
10 Create the same volume, largevol, in the appdg disk group using the same size
as in step 8.
11 Display volume information for appdg disk group using the

vxprint -g appdg -htr command. Can you identify which disks are
used for which volumes?
12 List the disk groups on your system using the vxdg list command.
13 Display disk property information for each disk in the appdg disk group using
the vxdisk -p list command. From the output record the following
information:
DISK _______________ _______________

SCSI_VERSION _______________ _______________
LUN_SERIAL_NO _______________ _______________
DDL_THIN_DISK _______________ _______________
ATYPE _______________ _______________
14 Display the OS native names for all the disks using the vxdisk -e list
command.

Exercise 2: Removing volumes and disks: CLI
sym1
1 Unmount the /app file system and remove it from the file system table.
2 Remove the largevol volume in the appdg disk group. Observe the disk group
configuration information using the vxprint -g appdg -htr command.
3 Remove the second disk (appdg02) from the appdg disk group. Observe the
change in its status.

261 Lab 4: Creating a Volume and File System
A57
Exercise 3: Destroying disk data using disk shredding: CLI
sym1
1 Mount the appvol volume to the /app directory. Do not add the entry to the
file system table.
2 Copy some data files into the /app file system. For this test, use the files
located in the /etc/default directory. List the contents of the /app
directory after the copy has completed.
3 Unmount the /app file system, verify the unmount.
4 Destroy the appdg disk group.
5 Observe the status of the disk devices on the system.
6 To prove that the data files have not been destroyed, recreate the appdg disk
group and the appvol volume using the exact same steps as used in Exercise 1 -
steps 3-4. DO NOT create a new file system on the appvol volume.
7 Mount the appvol volume to the /app directory and list the contents of the
directory. The data files should still exist.

10 Use the vxdiskunsetup command with the -o shred option to shred the
disk that was used in the appdg disk group for the appvol volume. This
command may take a while to compete.
11 Re-initialize the disk using the vxdisksetup command.

12 Recreate the appdg disk group and the appvol volume using the exact same
steps as used in Exercise 1 - steps 3-4. DO NOT create a new file system on the
appvol volume.
13 Attempt to mount the appvol volume to the /app directory. What happened?


A59
systems: VOM
vom
1 Start the VOM GUI and log on as the root user.
3 Select an uninitialized disk (emc0_dd7) and initialize it, if necessary, using

VOM. Observe the change in the Status column. What is the status of the disk
now?
4 Create a new disk group using the disk you initialized in the previous step.
Name the new disk group appdg. Observe the change in the disk status.
5 Using VOM, create a new 1g volume in the appdg disk group. Name the new
volume appvol. Create a file system on it and make sure that the file system is
mounted at boot time to /app directory.
6 Check if the file system is mounted and verify that there is an entry for this file
system in the file system table.
7 View the properties of the disk in the appdg disk group and note the Size and
the Unallocated fields.
Size ___________________________
Unallocated ___________________
8 Try to create a second volume, largevol, in the appdg disk group and specify a
size slightly larger than the unallocated space on the existing disk in the disk
group, for example 2g in the standard Symantec classroom systems. Do not
create a file system on the volume. What happens?
9 Add a second disk (emc0_dd8) to the appdg disk group.
as in step 8. Do not create a file system.
11 Observe the volumes displayed in the Volumes in Disk Group table. Can you
tell which volume has a mounted file system?
12 Create a VxFS file system on largevol and mount it to /large directory.

Ensure that the file system is not mounted at boot time. Check if the /large
file system is currently mounted and verify that it has not been added to the file
system table.

A61
groups: VOM
vom
1 Unmount both /app and /large file systems using VOM. Accept to remove
the file systems from the file system table if prompted. Check if the file
systems are unmounted and verify that any corresponding entries have been
removed from the file system table.
2 Remove the largevol volume in the appdg disk group.
3 Select the Administer button, All Disk Groups, and then select the appdg disk
group. View the Disks tab. Observe the disks in the appdg disk group. Can you
identify which disk is empty?
4 Remove the disk you identified as empty from the appdg disk group.
5 Observe all the disks on the system. What is the status of the disk you removed
from the disk group?

7 Observe all the disks on the system. What is the status of the disks?
End of lab

Lab 5: Working with Volumes with Different Layouts
In this lab, you create simple concatenated volumes, striped volumes, and mirrored
volumes. Optionally, you practice creating a a layered volume and using the
Storage Provisioning add-on with VOM.
Creating volumes with different layouts: CLI
Optional lab: Setting up Storage Provisioning: VOM
Optional lab: Creating layered volumes
Optional lab: Creating volumes with user defaults: CLI
Prerequisite setup
external disks to be used during the labs. Optional labs require the VOM
management server to be pre-installed and the SF servers to be managed hosts.

267 Lab 5: Working with Volumes with Different Layouts Copyright 2012 Symantec Corporation. All rights reserved.
A63
Lab information
environment.
Object Value
sym1
sym2


Exercise 1: Creating volumes with different layouts: CLI
sym1
1 Add four initialized disks (emc0_dd7 - emc0_d10) to a disk group called

appdg. Verify your action using vxdisk -o alldgs list.
a If you have completed the Creating a Volume and File System lab
(lab 4), you should already have some initialized disks. You will need four
disks for this lab. If four disks are not initialized, then initialize the needed
disks from the same enclosure for use in Volume Manager (all disks on the
EMC array).
b Create a new disk group and add disks:
2 Create a 50-MB concatenated volume in appdg disk group called appvol with
one drive.
3 Display the volume layout. What names have been assigned to the plex and
subdisks?
4 Remove the volume.
5 Create a 50-MB striped volume on two disks in appdg and specify which two
disks to use in creating the volume. Name the volume stripevol.
What names have been assigned to the plex and subdisks?
6 Create a 20-MB, two-column striped volume with a mirror in appdg. Set the
stripe unit size to 256K. Name the volume strmirvol.
What do you notice about the plexes?
7 Create a 20-MB, two-column striped volume with a mirror. Set the stripe unit
size to 128K. Select at least one disk that you should not use. Name the volume
2colstrvol.
A
Was the volume created?

A65
8 Create a 20-MB 3-column striped volume with a mirror. Specify three disks to
be used during volume creation. Name the volume 3colstrvol.
9 Create the same volume specified in the previous step using the same three
disks, but without the mirror. However, this time first determine what the
maximum size that the volume can be based on the remaining free space.
Create the volume with the maximum possible size for this layout.
a Determine the maximum size that the volume could be.
b Create a new volume with the maximum possible volume size for the
layout specified in the previous step.
Note: Only perform the remaining steps if you do not intend to complete the
optional exercises towards the end of this lab. Otherwise, skip the next two
steps.
10 Remove the volumes created in this exercise.
11 Remove the disk group that was used in this exercise.


Exercise 2: Optional lab: Setting up Storage Provisioning: VOM
Note: Storage Provisioning requires that the Veritas Storage Foundation Add-on
for Storage Provisioning is installed. This lab section covers the steps to
install the add-on and to set up storage provisioning.
vom
1 If the Web console is already open, skip this step, otherwise, open a Web
browser and enter the URL for the VOM MS Web console on the address line.
You may receive an error about the Web sites certificate, click the link to
your server.
2 Select the Settings tab, then from the sub menu select Deployment
Management.

Repository window will open.
the folder that contains the Storage Provisioning add-on
(VRTSsfmvtp-4.1.119.0.sfa). This software is in
/student/software/vom/vom41/add-ons. Select the
VRTSsfmvtp-4.1.119.0.sfa file and click Open. Click the Upload
button to begin the upload of the add-on to the VOM MS. When the upload is
complete, click the Close button to exit the Upload to Repository window.

271 Lab 5: Working with Volumes with Different Layouts
A67
5 The Storage Provisioning add-on should now be present in the Deployment
Installed.
6 Select the Storage Provisioning add-on radio button from the Deployment
Management Repository. Then from the Actions pull-down menu, select
Install. A new Install Solution window will open.
7 In the Install Solution window, Click the Install button to start the
deployment of the add-on. After the deployment completes you will receive
the following message. Click the Ok button to close the wizard.

sfmcswd )
8 The browser will now display the Deployment Summary. Note that the
Result shows Enabled.
9 On a terminal session on the VOM management server, restart the Web server.

selecting the Settings tab, then from the sub menu select Deployment
11 Create a VxFS file system on the strmirvol volume on the

sym1.example.com system.
12 Using the VxFS file system created in the previous step, create a storage
template.
13 Create a new webdg disk group on sym2.example.com using 4 disks

(3pardata0_49 - 3pardata0_52) on a different array than the one used by the
appdg disk group on sym1.example.com.
14 Using the storage template created in step 12, provision storage in the webdg
disk group on sym2.example.com.

15 Verify that the storage has been provisioned in the webdg disk group on
sym2.example.com.
16 Delete the newly created volume on sym2.example.com and destroy the

webdg disk group.

A69
Exercise 3: Optional lab: Creating layered volumes
Note: In order to perform the tasks in this exercise, you should have at least four
disks in the disk group that you are using.
sym1
1 First, ensure that any volumes created in the previous labs are removed from
the appdg disk group. You may need to first unmount any volumes that have
mounted file systems.
2 Create a 100-MB Striped Mirrored volume with no logging. Name the volume
strmirvol.
3 Create a Concatenated Mirrored volume with no logging called concatmirvol.

The size of the volume should be greater than the size of the largest disk in the
disk group; for example, if your largest disk is 2 GB, then create a 3-GB
volume.
4 View the volumes and compare the layouts.

5 Remove all of the volumes in the appdg disk group.

Exercise 4: Optional lab: Creating volumes with user defaults: CLI
This optional guided practice illustrates how to use the files:

/etc/default/vxassist
/etc/default/alt_vxassist
to create volumes with defaults specified by the user.
sym1
1 Navigate to the /etc/default directory.
2 Create two files in /etc/default:
a Using the vi editor, create a file called vxassist that includes the
following:
nmirror=3
b Using the vi editor, create a file called alt_vxassist that includes the
following:
stripeunit=256k
3 Use these files when creating the following volumes:
a Create a 100-MB volume called mirrorvol using layout=mirror.
b Create a 100-MB, two-column stripe volume called 2colstrvol using

-d /etc/default/alt_vxassist so that Volume Manager uses
the specified default file.
A

A71
Note: The -d option of the vxassist command specifies the file
containing custom values for specific attributes related to volume
creation and space allocation. If -d option is not specified, the
command defaults to /etc/default/vxassist.
4 View the layout of these volumes using vxprint -g appdg -htr. What
do you notice?
5 Remove any vxassist default files that you created in this optional lab
section. The presence of these files can impact subsequent labs where default
behavior is assumed.
End of lab

Lab 6: Making Configuration Changes
This lab provides practice in making configuration changes. In this lab, you add
mirrors and logs to existing volumes. You also change the volume read policy,
resize volumes, rename disk groups, and move data between systems.
Resizing a volume and file system
Optional lab: Resizing a file system only:
Optional lab: Converting a non-cds disk group
Prerequisite setup
To perform this lab, you need two lab systems with Storage Foundation pre-
installed, configured and licensed. In addition to this, you also need four external
shared disks to be used during the labs.
At the beginning of this lab, you should have a disk group called appdg that has
four external disks and no volumes in it.

277 Lab 6: Making Configuration Changes Copyright 2012 Symantec Corporation. All rights reserved.
A73
Lab information
In preparation for this lab, you will need the following information about your lab
environment.
Object Value
Host name of the main lab system sym1
Host name of the system sharing disks sym2


Exercise 1: Administering mirrored volumes
sym1
1 Ensure that you have a disk group called appdg with four disks in it. If not,
create the disk group using four disks.
Note: If you have completed the previous lab steps you should already have
the appdg disk group with four disks and no volumes.
2 Create a 50-MB, two-column striped volume called appvol in appdg.
3 Display the volume layout. How are the disks allocated in the volume? Note
the disk devices used for the volume.
Notice which two disks are allocated to the first plex and record your
observation.
4 Add a mirror to appvol, and display the volume layout. What is the layout of
the second plex? Which disks are used for the second plex?
5 Add a dirty region log to appvol and specify the disk to use for the DRL.
Display the volume layout.
6 Add a second dirty region log to appvol and specify another disk to use for the
DRL. Display the volume layout.
7 Remove the first dirty region log that you added to the volume. Display the
volume layout. Can you control which log was removed?
A

A75
8 Find out what the current volume read policy for appvol is. Change the volume
read policy to round robin, and display the volume layout.
9 Remove the original mirror (appvol-01) from appvol, and display the volume
layout.
10 Remove appvol.

Exercise 2: Resizing a volume and file system
sym1
1 Create a 20-MB concatenated mirrored volume called appvol in appdg. Create

a Veritas file system on the volume and mount it to /app. Make sure that the
file system is not added to the file system table.
2 View the layout of the volume and display the size of the file system.
3 Add data to the volume by creating a file in the file system and verify that the
file has been added.
4 Expand the file system and volume to 100 MB. Observe the volume layout to
see the change in size. Display file system size.

281 Lab 6: Making Configuration Changes
A77
Exercise 3: Renaming a disk group
sym1
1 Create a 100-MB concatenated volume called webvol in appdg. Create a

Veritas file system on the volume and mount it to /web. Make sure that the file
system is not added to the file system table.
2 Add data to the webvol volume by copying the /etc/group file to the
/web file system. Verify that the file has been added.
3 Try to deport and rename the appdg disk group to webdg while the /app and
/web file systems are still mounted. Can you do it?
4 Observe the contents of the /dev/vx/rdsk and /dev/vx/dsk directories

and their subdirectories. What do you see?
5 Unmount all the mounted file systems in the appdg disk group.
6 Deport and rename the appdg disk group to webdg. Then import the newly
renamed webdg disk group.

and their subdirectories. What has changed?
8 Observe the disk media names. Is there any change?
9 Mount the /app and /web file systems, and observe their contents.

Exercise 4: Moving data between systems
sym1
1 Copy new data to the /app and /web file systems. For example, copy the file
/etc/group to /app and the file /etc/hosts to /web.
2 View all the disk devices on the system.
3 Unmount all file systems in the webdg disk group and deport the disk group.
Do not assign it to a new host. View all the disk devices on the system.
sym2
4 Import the webdg disk group on the other system (sym2), ensure that the
volumes in the imported disk group are all started, and view all the disk
devices on the system.
5 Mount the /app and /web file systems. Note that you will need to create the
mount directories on the other system before mounting the file systems.
Observe the data in the file systems.
6 Unmount the file systems.

7 Deport webdg and assign the original machine name (sym1) as the new host.
sym1
A
8 Import the disk group and change its name back to appdg. View all the disk

A79
Note: Because the hostname of the sym1 system is assigned to the disk group
during the deport operation, the disk group can be automatically
imported if you execute the vxdctl enable command on your
system.
9 Deport the disk group appdg by assigning the ownership to a system called
anotherhost. View all the disk devices on the system. Why would you do this?
10 Display detailed information about one of the disks in the disk group
(emc0_dd7) using the vxdisk list command. Note the hostid field in
the output.
11 Import appdg. Were you successful?
12 Now import appdg and overwrite the disk group lock. What did you have to do
to import it and why?
13 Display detailed information about the same disk in the disk group as you did
in step 10. Note the change in the hostid field in the output.
14 Remove the appvol and webvol volumes.


Exercise 5: Optional lab: Resizing a file system only
sym1
1 Create a 50-MB concatenated volume named appvol in the appdg disk group.
2 Create a Veritas file system on the volume by using the mkfs command.
Specify the file system size as 40 MB.
3 Create a mount point /app on which to the mount the file system, if it does not
already exist.
4 Mount the newly created file system on the mount point /app.
5 Verify disk space using the df command. Observe that the total size of the file
system is smaller than the size of the volume.
6 Expand the file system to the full size of the underlying volume using the
fsadm -b newsize command.
Note: On Linux there is more than one fsadm command, you must use the
command located in /opt/VRTS/bin.
7 Verify disk space using the df command.
8 Make a file on the file system mounted at /app, so that the free space is less
A
than 50 percent of the total file system size.

A81
9 Shrink the file system to 50 percent of its current size. What happens?
10 Unmount the /app file system and remove the appvol volume in appdg.

Exercise 6: Optional lab: Converting a non-cds disk group
sym1
In this optional lab, you will destroy the existing appdg disk group, recreate it as a
non-cds disk group with non-cds disks and then convert the disk group to a cds
disk group.
1 Use the vxdisk -o alldgs list command to determine the disks that
are a part of the appdg disk group.
2 Destroy the existing appdg disk group using the vxdg destroy command.
3 Use the vxdisksetup command to re-initialize the first disk (emc0_dd7)

determined in step one as a sliced disk.
4 Use the vxdisk -o alldgs list command to verify that the disk now
shows as auto:sliced.
5 Recreate the 4 disk appdg disk group as a non-cds disk group using the vxdg
init command.
6 List the appdg disk group using the vxdg list command. Note that the cds
flag is not set.
7 Try to turn the cds flag on using the vxdg set command. Was the command
successful?
8 Use the vxcdsconvert command with the alldisks option to convert A

the appdg disk group to a cds disk group.

A83
9 Use the vxdisk list to verify that all disks in the appdg disk group have
been converted to cds disks.
flag is still not set.
11 Use the vxdg set command to turn the cds flag on.
flag is now set.
End of lab

Lab 7: Administering File Systems
In this lab, you defragment a fragmented file system and protect a file system from
being accidentally unmounted using the MountLock feature. You also observe the
time to creation improvement when using the SmartMove feature with mirroring
and try the thin reclamation feature.
Preparation for defragmenting a Veritas File System lab
Defragmenting a Veritas File System
SmartMove
Thin reclamation
Optional lab: Testing the MountLock feature
Optional lab: Reading the file change log (FCL)
Optional lab: Defragmenting a Veritas File System
Prerequisite setup
configured and licensed. In addition to this, you also need four external disks and
the second internal disk to be used during the labs. If you do not have a second
internal disk or if you cannot use the second internal disk, you need five external
disks to complete the labs.
At the beginning of this lab, you should have a disk group called appdg that has A
four external disks and no volumes in it. The second internal disk should be empty
and unused.

289 Lab 7: Administering File Systems Copyright 2012 Symantec Corporation. All rights reserved.
A85
Lab information
environment.
Object Value
Host name of the lab system sym1
2nd internal disk: sdb
Location of Lab Scripts (if any): /student/labs/sf/sf60


Exercise 1: Preparation for defragmenting a Veritas File System
lab
sym1
1 Identify the device name for the second internal disk on your lab system.
2 Initialize the sdb disk using a non-cds disk format.
3 Create a non-cds disk group called testdg using the internal disk you initialized
in step 2.
4 In the testdg disk group create a 1-GB concatenated volume called testvol
initializing the volume space with zeros using the init=zero option to
vxassist.
5 Create a VxFS file system on testvol.
6 Change into the /student/labs/sf/sf60 directory and run the

extentfrag_vxfs.pl script.
This script restores a fragmented file system onto the volume and performs a
file system check so that the volume can be mounted. Whatever files are in the
existing file system will be lost.
7 Mount the file system on /test. Note that you may need to perform a file
system check before mounting the file system.
8 Ensure that the directory where the vxbench command is located is included
in your PATH definition.

291 Lab 7: Administering File Systems
A87
Exercise 2: Defragmenting a Veritas File System
sym1
The purpose of this section is to examine the structure of a fragmented and an

unfragmented file system and compare the file systems throughput in each case.
The general steps in this exercise are:
Make and mount a file system.
Examine the structure of the new file system for extents allocated.
Then examine a fragmented file system and report the degree of fragmentation
in the file system.
Use a support utility called vxbench to measure throughput to specific files
within the fragmented file system.
De-fragment the file system, reporting the degree of fragmentation.
Repeat executing the vxbench utility using identical parameters to measure
throughput to the same files within a relatively unfragmented file system.
Compare the total throughput before and after the defragmentation process.
1 In the appdg disk group create a 1-GB concatenated volume called appvol.
2 Create a VxFS file system on appvol and mount it on /app.
3 Run a fragmentation report on /app to analyze directory and extent

fragmentation. Is a newly created, empty file system considered fragmented?
In the report, what percentages indicate a file systems fragmentation?
4 What is a fragmented file system?
5 If you were shown the following extent fragmentation report about a file
system, what would you conclude?
Directory Fragmentation Report

Dirs Total Immed Immeds Dirs to Blocks to
Searched Blocks Dirs to Add Reduce Reduce
total 199185 85482 115118 5407 5473 5655
6 Unmount /app and remove appvol in the appdg disk group.
7 Run a fragmentation report on /test to analyze directory and extent

fragmentation. Is /test fragmented? Why or why not? What should be done?
8 Use the getext command to display the extent attributes of the files in the
/test file system.
9 Measure the sequential read throughput to a particular file, for example, an

8MB file on an 8K extent (for example, /test/test48), in a fragmented
file system using the vxbench utility and record the results. Use an 8K
sequential I/O size.
Note: Remount the file system before running each I/O test
10 Repeat the same test for an 8Mb file on an 8Mb extent (for example, using the
/test/test58 file). Note that the file system must be remounted between
the tests. Can you explain why?
11 Defragment /test and gather summary statistics after each pass through the
file system. After the defragmentation completes, determine if /test is
fragmented? Why or why not?
Note: The defragmentation can take about 5 minutes to complete.

12 Measure the throughput of the unfragmented file system using the vxbench
utility on the same files as you did in steps 9 and 10. Is there any change in
throughput?
Notes:
The file system must be remounted before each test to clear the read
buffers. A
If you have used external shared disks on a disk array used by other
systems for this lab, the performance results may be impacted by the disk
A89
array cache and may not provide a valid comparison between a fragmented
and defragmented file system.
13 What is the difference between an unfragmented and a fragmented file system?
14 Is any one environment more prone to needing defragmentation than another?


Exercise 3: SmartMove
sym1
In this lab section, you make a larger volume so that you can see the time
difference when using the SmartMove feature.
1 Create a 1-GB, volume called appvol in appdg.
2 Create a VxFS File System on appvol and mount it to /app.
3 Copy /etc/hosts to /app.
4 Umount the /app file system.
5 Mirror the appvol volume. Record the time it takes to complete the mirror
operation.
Note: Although SmartMove is enabled by default in Storage Foundation 6.0,

it is not used when the file system is unmounted.
6 Delete the mirror that you added to appvol.
7 Mount the /app file system.
operation.
9 Unmount /app using the umount command.
10 Remove appvol in the appdg disk group.

A91
Exercise 4: Thin reclamation
sym1
1 View all the disk devices on the system. Then use the vxdisk -o thin
list command to list only the thin provisioning capable devices.
2 Locate the thin provisioning and thin reclamation capable devices from the
output in the previous step. The TYPE column in the output of the
vxdisk -o thin list command should display thinrclm. Choose
two thin reclamation capable devices (3pardata0_49 and 3pardata0_50), if they
are uninitialized use the vxdisksetup command to initialize them.
Note: If you do not see any thin provisioning and thin reclamation capable
devices in the vxdisk list output, contact your instructor. You
must have thin provisioning and thin reclamation capable devices to
complete this lab section.
3 Create a new disk group using the two disks (3pardata0_49 and 3pardata0_50)
you initialized in the previous step. Name the new disk group thindg. Observe
the change in the disk status.
4 Using the vxassist command, create a new volume of size 3g in thindg.

Name the new volume thinvol.
5 Create a Veritas file system on the volume and mount it to /thin. Do not add
the file system to the file system table.
6 Display the size of the file system using the df -k /thin command.
7 Use the vxdisk -o thin,fssize list command to view the size of

the disks compared to the physically allocated space.
8 Use the dd command to make some 400MB files on the file system mounted at
/thin, so that the free space is less than 10 percent of the total file system
size. Use the df -k /thin command to monitor the file system free space.

9 Use the vxdisk -o thin,fssize list command again to view the
increase to the physically allocated space.
10 Delete the files created in the step 8.
11 Use the df -k and vxdisk -o thin,fssize list commands again.

Note that the usage has decreased back to the starting point, but the physically
allocated space remains the same.
12 Use the vxdisk reclaim command on the thindg disk group to reclaim
the space on the LUNS.

decrease to the physically allocated space.
14 Unmount the /thin file system and destroy the thindg disk group.
15 If you are NOT planning to perform the optional exercises for this lab,
unmount /test file system and destroy the testdg disk group; otherwise, skip
this step.

A93
Exercise 5: Optional lab: Testing the Mountlock feature
sym1
1 In the appdg disk group create a new 10-MB volume called appvol. Create a
VxFS file system on appvol.
2 Mount the file system using the Mountlock feature and a tag of
locktest. Mount it to /app.
3 Use the mount command to view that the mount lock was set.
4 Attempt to unmount using the umount command. What is the error?
5 Use the fsadm command to remove the lock on the mount point.
6 Use the mount command to view that the mount lock was removed.
7 Attempt to unmount using the umount command. Did the operation

complete?
9 If you are NOT planning to perform the rest of the optional exercises for this
lab, unmount /test file system and destroy the testdg disk group; otherwise,
skip this step.

Exercise 6: Optional lab: Reading the file change log (FCL)
sym1
VxFS file system on appvol and mount it on /fcl_test.
2 Turn the FCL using the fcladm command for /fcl_test, and ensure that it
is on.
3 Navigate to the directory that contains the FCL and list the contents.
4 Display the superblock for /fcl_test using the fcladm print 0

/fcl_test command.
5 How do you know that there have been no changes in the file system yet?
6 Add some files to /fcl_test. Then remove one of the files you just added
and rename one of the others.

/fcl_test command.
8 How do you know that changes have been made to the file system?
9 Print the contents of the FCL using the fcladm print 1024
/fcl_test command.

A95
10 Use the vxlsino command to determine which files are identified by the
inode numbers that are listed in the Create type that do not have an Unlink
type as well?
11 Unmount the fcl_test file system and remove appvol.
12 The next lab section is an optional lab on analyzing and defragmenting a

fragmented file system. If you are not planning to carry out this optional
exercise, unmount /test file system and destroy the testdg disk group;
otherwise, skip this step.

Exercise 7: Optional lab: Defragmenting a Veritas File System
sym1
This section uses the /test file system to analyze the impact of fragmentation on
the performance of a variety of I/O types on files using small and large extent
sizes.
1 Recreate the fragmented /test file system using the following steps:
a Unmount the /test file system.
b Change into the /student/labs/sf/sf60 directory and run the

extentfrag_vxfs.pl script to restore a fragmented file system to the
volume.
c Mount the file system to /test. Note that you may need to perform a file
2 Run a series of performance tests for a variety of I/O types using the vxbench
utility to compare the performance of the files with the 8K extent size
(/test/test48) and the 8000K extent size (/test/test58) by
performing the following steps.

301 Lab 7: Administering File Systems
A97
Complete the table when doing the performance tests.
Test type Time (seconds) Throughput (KB/second)

Before defrag After defrag Before defrag After defrag
Sequential
reads, 8K
extent
Sequential
reads,
8000K
extent
Random
reads, 8K
extent
Random
reads,
8000K
extent
Note: Results can vary depending on the nature of the data and the model of
array used. No performance guarantees are implied by this lab.
You must unmount and remount the file system /test before each step to
clear and initialize the buffer cache.
a Ensure that the directory where the vxbench utility is located is included
b Perform a sequential read I/O test on the 8K extent size using the
vxbench command. Use an I/O size of 8k and a count of 1000 I/Os.
c Perform a sequential read I/O test on the 8000K extent size using the
d Perform a random read I/O test on the 8K extent size using the vxbench
command. Use an I/O size of 8k and a count of 1000 I/Os.
e Perform a random read I/O test on the 8000K extent size using the
3 Defragment the /test file system. The defragmentation process takes some
time.

4 Repeat the vxbench performance tests and complete the table with these
performance results.
5 Compare the results of the defragmented file system with the fragmented file
system.
6 When finished comparing the results in the previous step, unmount the
/test file system and destroy the testdg disk group.
End of lab

A99

Appendix B
Lab Solutions

305

306 B2 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
B
Lab environment overview

The labs for this course are performed within a virtual environment consisting of
five virtual machines. This virtual environment has been developed specifically for
this course and is detailed in the next sections.

B3
Virtual machine configuration
These labs use the five virtual machines shown in the slide. The introductory page
of each lab shows which virtual machines are being used. The labs contain icons,
such as those shown in the slide, to indicate which steps are performed on which
virtual machines.
System name Description Fully qualified host name

mgt NFS Server mgt.example.com
DNS Server
iSCSI Array
3par iSCSI Array 3par.example.com
vom Veritas Operations vom.example.com
Manager MS

Server
Server
Note: In the following exercises, the virtual machines are identified by the system
names in the preceding table.

B
Required parameters
The software and the scripts required during the labs throughout the course exist in
subdirectories under the /student directory on each user system as displayed on
the slide.
Virtual machine account information

Refer to the following table for the logon credentials to the various virtual
machines:
System Logon information

mgt The user does not log into this system unless instructed to
by the instructor
3par The user does not log into this system unless instructed to
by the instructor
vom User: root
Password: veritas
sym1 User: root
Password: veritas
sym2 User: root
Password: veritas

B5
Accessing virtual machines
Depending on how and where you attend this class, you access the virtual
machines in the lab environment in one of several ways. Your instructor will direct
you to the appropriate set of lab procedures for the environment you are using in
this class.
If you are working with VMware Workstation, continue to the VMware
Workstation Introduction section on the next page.
If you are working with Hatsize, skip to the Hatsize Introduction section that
starts after all the VMware Workstation exercises.

B
Lab 1: VMware Workstation Introduction

method for accessing systems.
Note: The exercises in this section apply to VMware Workstation lab

environments. Exercises for other environments, such as Hatsize, are
located elsewhere in this document.


B7
VMware Workstation lab environment
In this lab environment, each of the virtual machines is connected to a virtual
network (10.10.2.0) residing on the host. This network can be used to access the
Web server on the vom virtual machine from a Web browser on the host machine
(if available). However, lab instructions use a Web browser on the vom virtual
machine itself.
Note that other virtual networks exist in the environment for accessing multiple
disk arrays and for the purpose of multi-pathing.

B
VMware Workstation interface

The screen shot in the slide shows the VMware Workstation interface used to
access the virtual machines. Virtual machines are referred to as guest systems,
which are running their own guest operating systems. The physical system running
the VMware Workstation application is referred to as the host system running the
host operating system. Virtual machines are accessed by clicking on the tab with
the appropriate system name.

B9
Exercise 1: Starting virtual machines (VMware Workstation)
In this exercise, you start the virtual machines and display the existing snapshots
1 If VMware is not already open, start VMware Workstation.

Solution
a On the desktop of your host system, double-click the Load Environment

icon.
b Ensure that VMware Workstation opens and that the following tabs are
present - mgt, 3par, vom, sym1 and sym2. If these tabs are not present, do
not proceed until notifying the instructor.
End of Solution
2 Review the current settings for each virtual machine.
Solution
a To select a virtual machine, click a tab.
b Use the Summary view to locate the Devices tab and review the
information showing the virtual machine configuration.
c Click each of the remaining tabs and review the Devices pane information
End of Solution

B
mgt
3 Start the mgt virtual machine.
Solution
a In VMware, click the mgt tab.
b From the toolbar, click the green Power On button.
c While the virtual machine is starting, proceed to the next virtual machine.
End of Solution

B11
3par
4 Start the 3par virtual machine.
Solution
a In VMware, click the 3par tab.
c Wait until the login window is displayed.
End of Solution
CAUTION Do not proceed to the next step until the login screen is visible on
both mgt and 3par. The mgt server will show a typical RHEL
graphical logon screen, while the 3par server will stop at a CLI
login prompt.
Note: The first two virtual machines must be turned on at all times during all lab
testing. Failure to start the mgt and 3par virtual machines results in
missing files and missing shared LUNs.
vom
5 Start the vom virtual machine.
Solution
a In VMware, click the vom tab.

c While the virtual machine is starting, proceed to the next virtual machine. B
End of Solution
sym1
Solution
a In VMware, click the sym1 tab.
c While the virtual machine is starting, proceed to the next virtual machine.
End of Solution
sym2

Solution
a In VMware, click the sym2 tab.
End of Solution

B13
Exercise 2: Logging on to virtual machines (VMware Workstation)
Log on to each virtual machine to become familiar with the logon procedures for
each system type.
Note: Do not log onto the mgt and 3par virtual machines unless the instructor
requests you to do so.
vom
1 Log on to VOM Server (vom) as the root user.

Solution
a Click the vom tab.
b On the login screen of the vom server, type the username and click the
Enter key.
User name: root
c When prompted, type the password for this system and click the Enter key.
Password: veritas
d Wait until all startup scripts have completed.
End of Solution
sym1
2 Log on to the first Storage Foundation Server (sym1) as the root user.
Solution
a Click the sym1 tab.

b On the login screen of the sym1 server, type the username and click the
Enter key.
User name: root

B
Password: veritas
End of Solution
sym2
3 Log on to the second Storage Foundation Server (sym2) as the root user.
Solution
a Click the sym2 tab.
b On the login screen of the sym2 server, type the username and click the
Enter key.
User name: root
Password: veritas

End of Solution
4 Press Ctrl+Alt to release keyboard and mouse controls from the virtual
machine.

B15
Exercise 3: Adjusting the VMware view (VMware Workstation)
Adjust the VMware view controls to become familiar with navigating a virtual
machine.
vom
1 Select View > Quick Switch to enable the Quick Switch view.
How is the Quick Switch view different from the default view?
Solution
The workspace is enlarged to fit the screen, including the other virtual machine
tabs.
End of Solution
2 Press F11 to change back to the default view.
Solution
If the view does not change, press Ctrl+Alt on the keyboard to release controls
from the virtual machine and press F11 again.
End of Solution
Note: When working through the lab exercises, use the F11 shortcut to toggle
between the default and Quick Switch views, as desired.

Exercise 4: Running basic commands (VMware Workstation)
Determine whether the virtual machines can communicate by way of TCP/IP on B

the virtual network.
vom

Solution
On the desktop, right-click and select Konsole.
End of Solution
Solution
a From one of the open terminal windows, type ip addr.
b Locate the entries for the eth0 and eth1 interfaces.
c Record the IP addresses.
End of Solution

3 From the terminal windows, ping default gateways.
Solution
ping 10.10.2.1
ping 10.10.3.1
End of Solution

B17
Solution
Yes, the output shows a reply has been received from the gateway IP address.
End of Solution

Solution
nslookup sym1
End of Solution
What is the fully qualified host name of server?

Solution
sym1.example.com
End of Solution
sym1

Solution
End of Solution
Solution

b Locate the entries for the eth0, eth1, eth2 and eth3 interfaces.
c Record the IP address on the following line.
End of Solution B

Solution
ping 10.10.2.1
ping 10.10.3.1
ping 10.10.4.1
ping 10.10.5.1
End of Solution

Solution
End of Solution

Solution
nslookup sym2
End of Solution

323 Lab 1: VMware Workstation Introduction Copyright 2012 Symantec Corporation. All rights reserved.
B19
Solution
sym2.example.com
End of Solution
Solution
From one of the open terminal windows, type fdisk -l.
End of Solution
sym2

Solution
End of Solution
Solution
End of Solution

B
Solution
ping 10.10.2.1
ping 10.10.3.1
ping 10.10.4.1
ping 10.10.5.1
End of Solution

Solution
End of Solution

Solution
nslookup vom
End of Solution

Solution
vom.example.com
End of Solution

325 Lab 1: VMware Workstation Introduction Copyright 2012 Symantec Corporation. All rights reserved.
B21
Solution
End of Solution
End of lab

B
Lab 1: Hatsize Introduction

way to access the systems in it.
Note: These exercises are to be used only if the class is using the hosted Hatsize
platform to access the lab environment. Exercises for other environments,
such as VMware Workstation, are located elsewhere in this document.


B23
Hatsize lab environment
The following table provides a translation of virtual machine system names
referred to in the lab guide to the corresponding system names in the Hatsize
interface. Each system name is prefixed with S#. (Student number) in Hatsize.
System Name Description Hatsize Name

mgt NFS Server S#.mgt
DNS Server
iSCSI Array
scst iSCSI Array S#.scst
vom Veritas Operations S#.vom
Manager Management
Server
Server
Server

B
Hatsize interface
The screen shot in the slide shows the Hatsize interface used to access the virtual
machines. Instead of using tabs, such as the tabs in VMware Workstation, you
access Hatsize virtual machines from the Operations and Window menus. Other
key interface elements include:
Title Bar: Indicates the currently connected machine and whether you have
control of the machine or are in view-only mode
Operations: Is used to connect to additional virtual machines
Window: Is used to switch between active virtual machines
System Control: Is used to start, stop and restart virtual machines
Time remaining: Indicates the time remaining in the session

B25
Exercise 1: Connecting to the lab environment (Hatsize)
Log on to Hatsize and connect to the first system. For each lab environment in
Hatsize, a particular virtual machine is marked as a primary machine. All other
machines are marked as secondary machines. When you connect to the Hatsize
interface, you are initially connected to the primary virtual machine.
1 Locate the Hatsize portal URL and login credentials from your registration
e-mail. Record your credentials here:
Hatsize username:
Hatsize password:
2 Your student number is the number at the end of your Hatsize username
recorded in the previous step.
Record your student number here:
Note: When you use the Hatsize environment, all of the virtual machines
assigned to you are prefixed with a letter and your student number. For
example, if your student number is 8, the virtual machine named vom is
named something like k8-vom or s8-vom. Because the prefix is
different for each student, the lab exercises refer only to the system
name without the prefix.

3 In Internet Explorer, open the Hatsize portal URL and log in with your
assigned user name and password recorded in a previous step.
Solution
B
The logon screen in the browser is similar to this:
End of Solution
4 After logging in, find your class in the Current Classes table and click Enter.
Note that the name of your class will be different than the sample shown here.
Sample:

B27
5 In the Agenda for your class, find the Day 1 lab session and click OPEN.
6 Confirm that you see the primary machine connecting. Note that the machine
name you see will be different than the one shown in the following sample
7 Wait for the first console window to open.
sym1
8 Click in the console window and log in to sym1 using the following
credentials:
Username root
Password veritas

Exercise 2: Connecting to additional virtual machines (Hatsize)
Connect to additional virtual machines to become familiar with switching between B

systems.
sym1
1 Use the Operations menu to connect to sym2.

Solution
Select Operations > Connect To Secondary > S#.sym2.
Note: The sample screenshot displayed in this solution shows different

system names than what you will observe in your environment
End of Solution

B29
sym2
2 Click in the console window and log in to the sym2 system using the following
credentials:
Username root
Password veritas
3 Use the Window menu to switch back to sym1.
Solution
Select Window > S#.sym1.

system names than what you will observe in your environment.
End of Solution
sym1
4 Use the Operations menu to connect to vom.
Solution
Select Operations > Connect To Secondary > S#.vom.

End of Solution
vom
5 Click in the console window and log in to vom using the following credentials:
Username root
Password veritas
6 Use the Operations menu to disconnect the secondary machine.

Solution
Note: The sample screenshots displayed in this solution show different


B31
a Select Operations > Disconnect.
b When you see a Disconnect Confirmation dialog box, click Yes.
End of Solution
sym1
7 Using the Window menu, verify that the console window for the vom system
is closed.
Solution
Select Window and note that the vom system name is no longer displayed.

End of Solution
Note: In further labs, use the steps you practiced in this exercise to navigate
between different virtual lab systems in the Hatsize environment. The lab
solutions will no longer display the steps needed to navigate from one
virtual machine to another.

B33
Exercise 3: Running basic commands (Hatsize)

the virtual networks.
sym1

Solution
End of Solution
Solution
End of Solution



Solution
ping 10.10.2.12
ping 10.10.3.12
ping 10.10.4.12
ping 10.10.5.12
End of Solution
Did you receive a reply, indicating that systems are communicating? B
Solution
Yes, the output shows a reply has been received from the sym2 IP addresses.
End of Solution

Solution
nslookup sym2
End of Solution

Solution
sym2.example.com
End of Solution
Solution

End of Solution

B35
sym2

Solution
End of Solution
Solution
End of Solution



Solution
ping 10.10.2.11
ping 10.10.3.11
ping 10.10.4.11
ping 10.10.5.11
End of Solution
Did you receive a reply, indicating that systems are communicating? B
Solution
Yes, the output shows a reply has been received from the sym1 IP addresses.
End of Solution

Solution
nslookup vom
End of Solution

Solution
vom.example.com
End of Solution
Solution

End of Solution

B37
vom
Solution
End of Solution
Solution
b Locate the entries for the eth0 and eth1 interfaces.
c Record the IP addresses.
End of Solution

13 From the terminal windows, ping sym1 IP addresses corresponding to each of

Solution
ping 10.10.2.11
ping 10.10.3.11
End of Solution

Solution
Yes, the output shows a reply has been received from the sym1 IP address.
End of Solution B

Solution
nslookup sym1
End of Solution

Solution
sym1.example.com
End of Solution

B39
Exercise 4: Restarting virtual machines (Hatsize)
If the lab steps instruct you to restart a VMware machine, you must preserve the
system state during the process. Otherwise, the machine is restored to the initial
state and loses any changes you have made. Only discard the state of the machine
after consulting with your instructor. There are two methods, either within the
operating system on the virtual machine, or in the console System Control menu.
sym2

Solution
End of Solution
2 From a terminal window, use the shutdown -ry now command to restart
the virtual machine.
Solution
shutdown -ry now
End of Solution
Note: Using this method preserves system state.


344B40 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
sym1
B
Note: In this portion of the lab, you do not actually restart the virtual machine;
you stop at the screen where you can restart.
3 Select the system to control from the System Control menu.
Solution
Select System Control > user_name > S#.sym1.

End of Solution
4 If enabled for your course, you can start, stop, and restart the virtual machine,
either keeping state or discarding state. As previously mentioned, you do not
discard state without first consulting with your instructor.
Note: Do not click Do Action here. Instead, click Close. If you restart, you
may have to wait longer to start the next lab while the machine restarts.
Solution
You would select an action from the list, and click Do Action. Do not select an
action at this time. Click Close instead.

B41
Note: The sample screenshot displayed in this solution shows a different
system name than what you will observe in your environment.
End of Solution
Note: If at any time, by timeout or other condition, you are disconnected from
the primary machine, you can reconnect by selecting Operations >
Connect To Primary from the menu, as shown in the following dialog
box.
5 At the end of the session, or when otherwise necessary, you can use the File
menu to quit out of the console.
Solution
Select File > Quit.

Note: The sample screenshot displayed in this solution shows a different
system name than what you will observe in your environment.
End of Solution
Note: To reconnect, use the procedure shown in Exercise 1.
End of lab

B43

B
Lab 2: Installing SF and Accessing SF Interfaces

In this lab, you verify that your lab system is ready for SF 6.0 installation. You
then install Veritas Storage Foundation 6.0 on your lab systems.
Verifying that the system meets installation requirements
Installing Veritas Storage Foundation
Performing post-installation and version checks
Optional lab: Setting up Veritas Enterprise Administrator
Optional lab: Text-based VxVM menu interface
Optional lab: Accessing CLI commands

B45
Lab information
environment.
Object Value
Host names of lab systems sym1
sym2
Domain name example.com
Fully qualified hostnames (FQHN) sym1.example.com
sym2.example.com
Location of Storage Foundation 6.0 /student/software/sf/sf60
software:
Location of SORT data collector: /student/software/sf/sort
Location of lab scripts: /student/labs/sf/sf60


Exercise 1: Verifying that the system meets installation
requirements
sym1
1 Before installing Storage Foundation, save the following important system

files into backup files named with a .preVM extension. Also, save your boot
disk information to a file for later use (do not store the file in /tmp). You may
need the boot disk information when you bring the boot disk under VxVM
control in a later optional lab.
/etc/grub.conf
/etc/modprobe.conf
Solution
a cp /etc/grub.conf /etc/grub.conf.preVM
b cp /etc/modprobe.conf /etc/modprobe.conf.preVM
c fdisk -l /dev/sda
Note: This lab section shows the steps for one lab system. These steps should
be repeated for all systems that SF 6.0 will be installed on, for example
sym2.
End of Solution
2 If you have access to the Internet, start a Web browser and navigate to the
Symantec Operations Readiness Tools (SORT) Web site at
https://sort.symantec.com. In the SORT section, click the link for
My SORT. Under the Custom Reports section, click the Data Collector tab.
Select the link for the Linux (x86-64) operating system. Save the SORT data
collector sharball to a local directory, such as /var/tmp, or to the Desktop.
If you do not have access to the Internet, copy the SORT data collector sharball
located in the /student/software/sf/sort directory to a local
directory, such as /var/tmp.

351 Lab 2: Installing SF and Accessing SF Interfaces
B47
Note: The SORT data collector is updated for each release. You can download
the latest version from https://sort.symantec.com.
Solution
cp /student/software/sf/sort/sort_linux_x64.sh /var/tmp
cd /var/tmp
End of Solution
3 Decompress the SORT data collector sharball you copied to the local directory.
Note that you may need to change file permissions to execute the sharball or
run it using sh. When the Would you like to run the data
collector now? prompt is displayed, enter n.
Solution
sh ./sort_linux_x64.sh
Would you like to run the data collector now? [y,n] (y) n
End of Solution
4 Run SORT data collector and verify completion using displayed text output.
a Start the SORT utility. If you need to install Storage Foundation on more
than one system, start the SORT utility to check all systems.
Note: If your system has access to the Internet and a more recent version of the
SORT utility is available than the version you are running, you are
prompted that a newer version is available. Symantec recommends that you
always use the latest version of the SORT utility.
Solution
./sort/sortdc
End of Solution
b When prompted to accept the terms and conditions enter y.

c When prompted for which task to accomplish, select option 1)
Installation/Upgrade report and press Enter to continue.
Solution
B
What task do you want to accomplish?
1) Installation/Upgrade report (NetBackup,
Storage Foundation and HA Solutions)
2) Risk Assessment report (Storage Foundation
and HA Solutions)
3) License/Deployment report (Storage
Foundation and HA Solutions)
4) VxExplorer report
5) NetBackup Support Utility (NBSU) report
6) Other tasks
Choose your option (separate multiple selections

with commas): [1-6,q] (1)
End of Solution
d When prompted to choose a Symantec Enterprise product family, select

option 2) Storage Foundation and HA Solutions and press
Enter to continue.
Solution
Main Menu->Installation/Upgrade report:
Choose the Symantec enterprise product family:

1) NetBackup
2) Storage Foundation and HA Solutions
b) Back to previous menu
Choose your option: [1-2,b,q] (1) 2
End of Solution
e When prompted on which system to run the report, select option 2) One
or more remote systems and press Enter to continue.
Solution
Main Menu->Installation/Upgrade report-
B49
>SFProductFamily:
On which systems do you want to run and report?

1) This system only(<sym1>)
2) One or more remote systems
Choose your option: [1-2,b,q] (1) 2

End of Solution
f When prompted, type the names of the systems that you desire to test.
Note: SORT data collector uses the same code base as the CPI installer, so
you can specify multiple systems of the same OS and the utility
includes all specified systems in the test. A single XML file is
created that includes all systems.
Solution
Enter space-separated system names: [q,?] sym1
sym2
End of Solution
g Provide the user name for accessing remote systems if you entered a
system other than the system that contains the SORT utility.
Solution
Enter a user name to access the remote system(s):
[q,?] (root)
End of Solution
h After the SORT data collector checks for partial clusters and performs
some basic data collection, choose the Symantec enterprise product you
want to install or upgrade to. Select option 1) Veritas Storage
Foundation and press Enter to continue.
Solution
Choose the Symantec enterprise product you want to
install or upgrade to. If
you are installing or upgrading multiple products,
run the data collector
for each one.
1) Veritas Storage Foundation

2) Veritas Storage Foundation for Oracle
B
3) Veritas Cluster Server
4) Veritas Storage Foundation HA
5) Veritas Storage Foundation Cluster File
System
6) Veritas Storage Foundation for Oracle RAC
7) Veritas Storage Foundation for Sybase
8) Veritas Storage Foundation for DB2
9) Veritas Storage Foundation Cluster File
System for Oracle RAC
10) Veritas Storage Foundation Sybase ASE CE
Choose the product: [1-10,b,q] (1) 1

End of Solution
i Choose the product version to which you want to install or upgrade. Select
option 1) 6.0 and press Enter to continue.
Solution
Choose the product version you want to install or
upgrade to on the
system(s) in your environment.
Veritas Storage Foundation
1) 6.0 (AIX, HP-UX, Linux_x86_64,

SunOS_sparc, SunOS_x86_64)
2) 5.1SP1 (AIX, HP-UX, Linux_x86_64,
3) 5.1 (AIX, Linux_x86_64, SunOS_sparc,
SunOS_x86_64)
4) 5.0MP4 (Linux_ppc64, Linux_x86_64)
5) 5.0RU4 (Linux_ppc64, Linux_x86_64)
6) 5.0RU1 (Linux_x86_64)
7) 5.0MP3 (AIX, Linux_x86_64, SunOS_sparc,
SunOS_x86_64)

B51
8) 5.0MP2 (HP-UX, Linux_x86_64)
9) 5.0MP1 (AIX, HP-UX, Linux_x86_64,
SunOS_sparc)
10) 5.0 (AIX, HP-UX, Linux_x86_64,
Choose the product version: [1-10,b,q] (1)

End of Solution
j The SORT data collector collects data and generates XML and TXT report
files. If the system has access to the SORT Web site you are prompted to
upload the file. Otherwise, a message is displayed stating that the SORT
Web site cannot be accessed and describing how to manually upload the
file.
Solution
Analyzing systems: 100%
Estimated time remaining: 00:00:00

5 of 5
Detecting the server tier

......................................... Done
Detecting the processor tier
...................................... Done
Detecting installed Storage Foundation
products ................... Done
Running a pre-installation assessment
............................. Done
Detecting installed Storage Foundation patches
.................... Done
Generated XML and text files based on the systems

and the time you ran the
data collector.
Created /var/tmp/sort/reports/
sym1andothers_IAS_20111101_111659.xml
Created /var/tmp/sort/reports/
sym1andothers_IAS_20111101_111659.txt

The system cannot access the SORT Web site now,
you can manually upload the
XML file to the SORT Web site (https://
sort.symantec.com/) to view your
custom server report that contains documentation B
and links related to your
environment. The text file does not contain this
additional information.
End of Solution
k When all tasks have been completed, you are prompted to exit the data
collector; select y.
Solution
Your tasks are completed. Would you like to exit
the data collector? [y,n,q](y) y
End of Solution
l If desired, view the report .txt file.
Solution
more /var/tmp/sort/reports/
sym1andothers_IAS_20111101_111659.txt
End of Solution
5 If you have access to the Internet, upload the SORT .xml output file to the
SORT Web site. Otherwise, skip steps 5 and 6.
Note: Uploading the SORT .xml report to the SORT Web site requires that
there be access to the Internet from the classroom lab. If an external

connection is not available, the .xml file can be saved to a USB drive
and these steps can be performed at a later date.
Solution
a Open a Web browser and navigate to https://

sort.symantec.com.

B53
b Under the SORT section, click the My SORT link. Under the Custom
Reports section, select the Upload Report tab. Click the Choose File
button and then browse to the /var/tmp/sort/reports directory,
select the SORT .xml file, and click the Open button. Click the Upload
button to continue.
End of Solution
6 Using the displayed output, determine if the system is ready for installation.
Solution
Mark the checkbox next to Passed in the Filter View By section at the top of
the page. In the Summary for this server section, ensure that each section
displays a green icon. If any of the sections display an orange or red icon,
record the steps that need to be taken before the installation can be performed
on the following lines.
_______________________________________________________________
______________________________________________________________
End of Solution

Exercise 2: Installing Veritas Storage Foundation
sym1
Solution
cd /student/software/sf/sf60
End of Solution
2 Perform a CPI installation of Storage Foundation 6.0.

available.
Solution
./installer
End of Solution
b Select I for Install a Product option.
c Select 3 for Storage Foundation (SF) option.

d Type y to agree to the terms of the End User License Agreement (EULA).
e Select 3 for Install all rpms.
f Type the names of your two systems when prompted. The server where the
installer script was executed on is the default value.
Solution
sym1 sym2
End of Solution

B55
g Observe that the following checks complete successfully;
Installed product
Prerequisite patches and rpms
Platform version
Product licensing
Product prechecks
If you discover any issues, report them at this time.
h Press Enter to scroll through the list of packages and start the package
installation.
i Select 2 for the Enable keyless licensing and complete system licensing
later option.
j Select 2 for SF Enterprise product mode to license.
k Type n to not enable replication.
l Observe that the Storage Foundation startup completes successfully.
m View the summary file, if desired.
3 Check to ensure that the Storage Foundation path (/opt/VRTS/bin) is

present in the profile.
Notes:
Your lab systems are already configured with the PATH and MANPATH
environment variable settings. However, in a real-life environment, you
must modify /usr/.bash_profile or /etc/profile yourself.
The VxVM commands in the /opt/VRTS/bin directory are linked to

the same commands in /usr/lib/vxvm/bin.
Solution
echo $PATH
echo $MANPATH
End of Solution

4 Verify that Storage Foundation 6.0 packages have been properly installed.
Solution
rpm -qa | grep VRTS
B
VRTSvlic-3.02.60.007-0
VRTSfsadv-6.0.000.000-GA_RHEL5
VRTSob-3.4.526-0
VRTSsfmh-4.1.119.0-0
VRTSspt-6.0.000.000-GA
VRTSlvmconv-6.0.000.000-GA_RHEL5
VRTSdbed-6.0.000.000-GA_RHEL
VRTSvxvm-6.0.000.000-GA_RHEL5
VRTSvxfs-6.0.000.000-GA_RHEL5
VRTSodm-6.0.000.000-GA_RHEL5
VRTSaslapm-6.0.000.000-GA_RHEL5
VRTSsfcpi60-6.0.000.000-GA_GENERIC
VRTSperl-5.12.2.6-RHEL5.5
VRTSfssdk-6.0.000.000-GA_RHEL5
rpm -qi VRTSvxvm

End of Solution
5 View the log files from the installation using the location specified at the end
of the installation. The log file directory is located in
/opt/VRTS/install/logs.
Solution
cd /opt/VRTS/install/logs/
ls
cd installer-unique_string/
ls
installer-unique_string.summary
installer-unique_string.response
installer-unique_string.tunables
installer-unique_string.log#
install.package.system
start.SFprocess.system
End of Solution

B57
6 Use the vxlicrep command to view the keys that were installed during the
installation.
Solution
vxlicrep | more
Symantec License Manager vxlicrep utility version

3.02.60.006
Copyright (C) 1996-2011 Symantec Corporation. All
rights reserved.
Creating a report on all VERITAS products

installed on this system
-----------------***********************---------
--------
License Key = XXXX-XXXX-

XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-X
Product Name = VERITAS
Storage Foundation Enterprise
Serial Number = 16689
License Type = PERMANENT
OEM ID = 2006
Site License = YES
Editions Product = YES
Features :=
Reserved = 0
CPU Count = Not
Restricted
VxVM#VERITAS Volume Manager = Enabled

VXFS#VERITAS File System = Enabled
QLOG#VERITAS File System = Enabled
PGR#VERITAS Volume Manager = Enabled
VERITAS Storage Foundation Enterprise = Enabled
. . . (more
End of Solution

Exercise 3: Performing post-installation and version checks
sym1
Solution
cd /student/software/sf/sf60
End of Solution
2 Perform a CPI post-installation check of the Storage Foundation 6.0 systems.

available.
Solution
./installer
End of Solution
b Select O for the Perform a Post-Installation Check option.
c Select 3 for the Storage Foundation (SF) option.

d Type the names of your two systems when prompted. The server where the
installer script was executed is the default value.
Solution
sym1 sym2
End of Solution
e Observe that the following checks complete successfully;
B59
Installed product
Platform version
Product prechecks
If you discover any issues report them at this time.
f Observe that the Storage Foundation postcheck completes successfully.
g View the summary file, if desired.
3 Perform a version check of the installed Storage Foundation 6.0 systems. Start
the installer script with the -version option. Specify the sym1 and
sym2 system names.

available.
Solution
./installer -version sym1 sym2
Installed product(s) on sym1:
Veritas Storage Foundation - 6.0
Product:
Packages:
Installed Required packages for Veritas
Storage Foundation 6.0:
#PACKAGE #VERSION
VRTSaslapm 6.0.000.000
VRTSfsadv 6.0.000.000
VRTSperl 5.12.2.6
VRTSsfcpi60 6.0.000.000
VRTSvlic 3.02.60.007
VRTSvxfs 6.0.000.000
VRTSvxvm 6.0.000.000
Installed Optional packages for Veritas

#PACKAGE #VERSION
VRTSdbed 6.0.000.000
VRTSfssdk 6.0.000.000
VRTSlvmconv 6.0.000.000
B
VRTSob 3.4.522
VRTSodm 6.0.000.000
VRTSsfmh 4.1.99.0
VRTSspt 6.0.000.000
Summary:
Packages:
7 of 7 required Veritas Storage Foundation
6.0 packages installed
7 of 7 optional Veritas Storage Foundation
Attempted to connect to https://sort.symantec.com to

check for product updates,
but connection failed.
Please visit https://sort.symantec.com to check for
available product updates
and information.
Installed product(s) on sym2:

Product:
Packages:
Installed Required packages for Veritas
#PACKAGE #VERSION
VRTSaslapm 6.0.000.000
VRTSfsadv 6.0.000.000
VRTSperl 5.12.2.6
VRTSsfcpi60 6.0.000.000
VRTSvlic 3.02.60.007
VRTSvxfs 6.0.000.000
B61
VRTSvxvm 6.0.000.000
Installed Optional packages for Veritas

#PACKAGE #VERSION
VRTSdbed 6.0.000.000
VRTSfssdk 6.0.000.000
VRTSlvmconv 6.0.000.000
VRTSob 3.4.522
VRTSodm 6.0.000.000
VRTSsfmh 4.1.99.0
VRTSspt 6.0.000.000
Summary:
Packages:
7 of 7 required Veritas Storage Foundation
7 of 7 optional Veritas Storage Foundation
Attempted to connect to https://sort.symantec.com to

check for product updates,
but connection failed.
Please visit https://sort.symantec.com to check for
available product updates
and information.
End of Solution
Note: The installer script attempts to contact the SORT Web site to
check for product updates.

Exercise 4: Optional lab: Setting up Veritas Enterprise
Administrator
sym1
The VEA GUI client package has been removed from the Storage Foundation
installed packages, although the object bus (VRTSob) is still present. This section
covers how to enable the server and install the VEA GUI client if desired.
1 From a terminal window, use the vxsvcctrl command to activate vxsvc.

Solution
/opt/VRTS/bin/vxsvcctrl activate
End of Solution
2 Verify that the service is online (enabled).
Solution
chkconfig --list |grep isisd
isisd 0:off 1:off 2:off 3:on
4:off 5:on 6:off
Note: The chkconfig command is used to list and maintain the /etc/
rc[0-6].d directories
End of Solution

B63
3 Use the ps -ef command to determine if the vxsvc daemon is running. If it
is not, use vxsvcctrl start to start the daemon.
Solution
ps -ef | grep vxsvc
/opt/VRTS/bin/vxsvcctrl start
/opt/VRTS/bin/vxsvcctrl status
End of Solution
4 Attempt to start the VEA GUI using the vea command. Observe the message
displayed.
Solution
vea &
VEA GUI is no longer packaged. Symantec recommends that you use VOM to
manage, monitor, and report on multi-host environments. You can download
this utility at no charge from http://go.symantec.com/vom. If you
wish to continue using VEA GUI, you can downloaded it from the same Web
site.
End of Solution
5 Navigate to the directory that contains the VEA GUI package.
Solution
cd /student/software/sf/vea_gui
End of Solution
6 Install the VEA GUI package using the appropriate OS commands.

Solution
rpm -ivh VRTSobgui-3.4.15.0-0.i686.rpm
End of Solution

7 Re-create the symbolic link from /opt/VRTS/bin/vea to
/opt/VRTSob/bin/vea. By default, vea is symbolically linked to
/opt/VRTS/bin/vea.sh.
Solution B
rm /opt/VRTS/bin/vea
ln -s /opt/VRTSob/bin/vea /opt/VRTS/bin/vea
End of Solution
8 Verify that you can start the VEA GUI and connect to the local host.
Solution
/opt/VRTS/bin/vea &
End of Solution
9 In the Select Profile window, click the Manage Profiles button and configure
VEA to always start with the Default profile.
Solution
Set the Start VEA using profile option to Default, click Close, and then
click OK to continue.
End of Solution
10 Click the Connect to a Host or Domain link and connect to your system as
root.
Solution
Hostname: (For example, sym1)
Username: root
Password: veritas
End of Solution
11 On the left pane (object tree) view, navigate the system and observe the various
categories of VxVM objects.
12 Select the Assistant perspective, on the quick access bar and view tasks for
systemname.
B65
13 Using the System perspective, determine which disks are available to the OS.
Solution
In the System perspective object tree, expand your host and then select the
Disks node. Examine the Device column in the grid.
End of Solution
14 Execute the Disk Scan command and check if any messages are displayed on
the Console view.
Solution
In the VEA System perspective object tree, select your host. Select Actions >
Rescan.
End of Solution
15 Which commands were executed by the Disk Scan task?
Solution
Navigate to the Log perspective. Select the Task Log tab in the right pane and
double-click the Scan for new disks task.
End of Solution
16 Exit the VEA graphical interface.
Solution
In the VEA main window, select File > Exit. Confirm when prompted.
End of Solution
17 Create a root equivalent administrative account named admin1 for use of VEA.
Solution
a Create a new administrative account named admin1:
useradd admin1
passwd admin1

b Type a password for admin1.
c Modify the /etc/group file to add the vrtsadm group and specify the
root and admin1 users by using the vi editor, as follows:
B
vi /etc/group
d In the file, navigate to the location where you want to insert the vrtsadm
entry, change to insert mode by typing i, and then add the line:
vrtsadm::99:root,admin1
e When you are finished editing, press Esc to leave insert mode.
f Then, save the file and quit, as follows:
:wq
End of Solution
18 Test the new account. After you have tested the new account, exit VEA.
Solution
a Launch VEA, as follows:
vea &
b Select Connect, and specify the host name, as follows:
Hostname: sym1
c Select the Connect using a different user account option and click
Connect.
d Type the username and password for the new user, as follows:
User: admin1
Password: (Type the password that you created for admin1.)
e After confirming the account, select File > Exit.
End of Solution

B67
Exercise 5: Optional lab: Text-based VxVM menu interface
sym1
1 From the command line, invoke the text-based VxVM menu interface using
the vxdiskadm command.
Solution
vxdiskadm
End of Solution
2 Display information about the menu or about specific commands.
Solution
Type ? at any of the prompts within the interface.
End of Solution
3 Which disks are available to the OS?

Solution
Type list at the main menu and then type all.
End of Solution

4 Exit the vxdiskadm interface.
Solution
Type q at the prompts until you exit vxdiskadm.
B
End of Solution

B69
Exercise 6: Optional lab: Accessing CLI commands
sym1
This exercise introduces several commonly used VxVM commands. These

commands and associated concepts are explained in detail throughout this course.
If you have used Volume Manager before, you may already be familiar with these
commands. If you are new to Volume Manager, this exercise aims to show you the
amount of information you can get from the manual pages. Note that you do not
need to read all of the manual pages for this exercise.
1 From the command line, invoke the VxVM manual pages as follows and then
read about the vxassist command.
Solution
man vxassist
End of Solution
2 Which vxassist command parameter creates a VxVM volume?
Solution
The make parameter is used in creating a volume.
End of Solution
vxdisk command.
Solution
man vxdisk
End of Solution

4 Which disks are available to VxVM?
Solution
B
All the available disks are displayed in the list.
End of Solution
vxdg command.
Solution
man vxdg
End of Solution
6 How do you list locally imported disk groups?
Solution
vxdg list
Note: Because you have not created any disk groups yet, the command output
shows only the header statement at this stage in the labs.
End of Solution
vxprint command.
Solution
man vxprint
End of Solution
8 Determine which Storage Foundation daemons are running on the system

using the ps -ef command.
Solution
ps -ef | grep -i vx

B71
vxconfigd, vxrelocd, vxnotify, vxesd, vxdclid,
vxconfigbackupd, vxsvc, vxattachd, vxdbd.
End of Solution
End of lab

B
Lab 3: Getting Started with VOM

The purpose of this lab is to provide an introduction to the Veritas Operations
Manager 4.1.
Installing the VOM management server (MS)
Adding managed hosts to the MS
Adding the active management add-on
Prerequisite setup
To perform this lab, you use the vom virtual machine, which is a Linux server that
is used to install and configure the VOM management server (MS). The other lab
systems (sym1 and sym2) already have SF 6.0 installed. Before starting this lab,
ensure that the VOM virtual machine is turned on.

B73
Lab information
environment.
Object Value
VOM management server root veritas
password
Host name - Management server vom
Host name - Managed hosts sym1
sym2
Location of VOM 4.1 software: /student/software/vom/vom41


Exercise 1: Installing the VOM management server (MS)
vom
1 On your system, navigate to the directory that contains the binary for the VOM
central management server
(Veritas_Operations_Manager_CMS_4.1_Linux.bin binary).
Solution
cd /student/software/vom/vom41
End of Solution
2 Copy the CMS binary to the /tmp directory. Then, navigate to the /tmp
directory. If necessary, change the permissions of the file so that the file is
executable. Execute the binary.
Solution
a cp Veritas_Operations_Manager_CMS_4.1_Linux.bin
/tmp
b cd /tmp
c chmod 744
Veritas_Operations_Manager_CMS_4.1_Linux.bin
d ./Veritas_Operations_Manager_CMS_4.1_Linux.bin
e Type y to accept the End User license agreement (EULA).

The End User License Agreement (EULA) is available in

the EULA.pdf file,
which is located in the .zip file that you downloaded
to install Veritas Operations Manager Management
Server.
Do you agree with the terms of the EULA? [y,n] y
Initializing installation. Please wait.....[OK]

Verifying available disk space.............[OK]

B75
Extracting archive.........................[OK]
Verifying MD5 checksum of packages.........[OK]
Installing VRTSsfmh........................[OK]
Installing VRTSsfmcs.......................[OK]
Installation is complete. You will need to configure

Veritas Operations Manager Management Server.
Please open your browser and type the following URL

to configure:
https://vom:5634/
Please skip this step if you intend to use this host
as a standby node for Veritas Operations Manager
Management Server HA.
End of Solution
Note: You cannot execute this binary from an NFS share. If you do, the
extraction of the packages fails.
3 Verify that the xprtld process is started.
Solution
ps -ef | grep xprtld
End of Solution
4 Open a Web browser and type the URL shown at the completion of the
installation. If the browser is unable to resolve the system name, replace the
system name with the IP address or use the fully qualified host name.
Notes:
This URL is only used for configuration. Do not use it after the VOM
management server is configured.
You may be prompted to choose a digital certificate. If a certificate is
displayed, choose the most appropriate certificate.

5 You are prompted for a password. Type the root user and password for the
system that the VOM server was installed on.
Solution
B
End of Solution
6 A configuration screen displays showing the Server Name and Server

Address. These values are, typically, correct; if they are not, change them to
the appropriate values. Click Next to continue.
Solution
End of Solution

381 Lab 3: Getting Started with VOM
B77
7 Next, you are prompted for a database location. Symantec recommends that
you use the default values. Click Next to continue.
Solution
End of Solution
8 Next, you are asked whether to Enable Analytics Gathering. This allows
Symantec to track the usage of the product so as to optimize the user interface
for future versions of this product. For the purpose of the labs, remove the tick.
Click Finish to complete the configuration.
Solution
End of Solution

9 After you complete all of the configuration steps, click the Launch Web
Console button. Log into the Web console as the root user.
Solution
B
End of Solution

B79
Exercise 2: Adding managed hosts to the MS
This section requires an additional system that has SF 6.0 pre-installed but is not
already configured in the VOM MS. For this lab section, use the sym1 and sym2
virtual machines.
sym1
Solution
a ps -ef | grep vxsvc
b /opt/VRTS/bin/vxsvcctrl activate
c /opt/VRTS/bin/vxsvcctrl start
End of Solution
Solution
chkconfig --list | grep isisd

isisd 0:off 1:off 2:off 3:on 4:off
5:on 6:off
Note: The chkconfig command is used to list and maintain the

/etc/rc[0-6].d directories.
End of Solution

sym2
B
Solution
a ps -ef | grep vxsvc
b /opt/VRTS/bin/vxsvcctrl activate
c /opt/VRTS/bin/vxsvcctrl start
End of Solution
Solution
chkconfig --list | grep isisd
isisd 0:off 1:off 2:off 3:on 4:off
5:on 6:off
Note: The chkconfig command is used to list and maintain the

/etc/rc[0-6].d directories.
End of Solution

B81
vom
5 If the Web console is already open, skip this step. Otherwise, open a Web
You may receive an error about the Web sites certificate; click the buttons
necessary to continue to this Web site. Log on using the root username and
password for your server.
Solution
https://vom.example.com:14161/
End of Solution
6 Select the Settings tab, and then from the submenu, select Host Management.
7 From the Actions pull-down menu, select Add Hosts(s). A new Add Host(s)
window opens.
8 Type the fully qualified host name of the first system to be added as a managed
host (sym1.example.com). Type root for the username and the root
password.
9 Click the Add Entries button and type the fully qualified hostname of the
second system to be added as a managed host (sym2.example.com). Type
root for the username and the root password.
10 Click Next to have the VOM server add the hosts.
Note: The VOM MS server and the managed host must be time synchronized.
Check the system times using the date command to ensure that the
time difference between the two systems is not greater than five
minutes.
11 Click the OK button to exit the Add Host(s) window.
12 Verify that your hosts have been added. If so, they are now visible when you
navigate to Manage > Servers > Hosts.

Exercise 3: Adding the active management add-on
vom
1 If the Web console is already open, skip this step; otherwise, open a Web
You may receive an error about the Web sites certificate. Click the link to
your server.
Solution
https://vom.example.com:14161/sfm
End of Solution
2 Select the Settings tab and then, from the sub menu, select Deployment
Management.

Repository window is displayed.
the folder that contains the Active Management add-on (VRTSsfmunixadm-
4.1.100.0.sfa). Typically, this is located in /student/software/
vom/vom41/add-ons. If it is not, ask the instructor for the correct location.
Select the VRTSsfmunixadm-4.1.100.0.sfa file and click Open. Click
the Upload button to begin the upload of the add-on to the VOM MS. When
the upload is complete, click the Close button to exit the Upload to
Repository window.
5 The Active Management add-on is now present in the Deployment

Installed.
6 Select the Storage Foundation Administration for Unix add-on radio button
from the Deployment Management Repository. Then from the Actions pull-
down menu, select install. A new Install Solution window is displayed.

B83
7 In the Install Solution window, click the Install button to start the deployment
of the add-on. After the deployment completed, the following message is
displayed:

sfmcswd )
Click the OK button to close the wizard.
8 The browser now displays the Deployment Summary. Note that the Result
shows Enabled.
9 On a terminal session on the VOM MS server, restart the Web server.
Solution
(sfmcswd)................[STOPPED]
Veritas Operations Manager Security Service
(sfmsecd)...........[STOPPED]
Veritas Operations Manager Messaging Service
(xprtld)...........[STOPPED]
Veritas Operations Manager Database Service
(vxsfmcsdb).........[STOPPED]
Veritas Operations Manager Distributed Command Line
Daemon (vxdcli[STOPPED]
Veritas Operations Manager watchdog (sfmh-
discovery)............[OFFLINE]
Veritas Operations Manager watchdog (sfmh-
discovery)............[STARTED]
Veritas Operations Manager Distributed Command Line

Daemon (vxdcli[STARTED]
Veritas Operations Manager Database Service
(vxsfmcsdb).........[STARTED]
Veritas Operations Manager Messaging Service
(xprtld)...........[STARTED]
Veritas Operations Manager Security Service
(sfmsecd)...........[STARTED]

(sfmcswd)................[STARTED]
End of Solution
B
selecting the Settings tab, and then, from the sub menu, select Deployment
Note: After the Web server is restarted, you may be asked to log back into the
Web console.
End of lab

B85

B
Lab 4: Creating a Volume and File System

In this lab, you create new disk groups, simple volumes, and file systems, mount
and unmount the file systems, and observe the volume and disk properties. The
first exercises use the command line interface. The optional exercises use the
VOM interface.
Creating disk groups, volumes and file systems: CLI
Removing volumes and disks: CLI
Destroying disk data using disk shredding: CLI
Optional lab: Creating disk groups, volumes, and file systems: VOM
Optional lab: Removing volumes, disks, and disk groups: VOM
If you use object names other than the ones provided, substitute the names
accordingly in the commands.
CAUTION In this lab, do not include the boot disk in any of the tasks.
Prerequisite setup
external disks to be used during the labs.

391 Lab 4: Creating a Volume and File System
B87
Although you should not have to perform disk labeling, here are some tips that
may help if your disks are not properly formatted:
On Linux, if you have problems initializing a disk, you may need to run this
command: fdisk /dev/disk.
Use options -o and -w to write a new DOS partition table.
If you are unsure of the device name, you can use the fdisk -l command to
list all devices that are visible to the Linux Operating System.
Note: If there are multiple paths to each disk, the fdisk -l output will show a
higher number of devices than actually present.
Lab information
environment.
Object Value
sym1

Exercise 1: Creating a volume and file system: VOM

Exercise 1: Creating disk groups, volumes and file systems: CLI
sym1
Solution
End of Solution
2 Choose a disk (emc0_dd7) and initialize it, if necessary, using the CLI. Using
the vxdisk -o alldgs list command observe the change in the Status
column. What is the status of the disk now?
CAUTION Do not initialize the sda device, this is the system boot disk.
Solution
vxdisksetup -i emc0_dd7
The TYPE field should change to auto:cdsdisk and the STATUS of the
disk should change to online but the DISK and GROUP columns should still
be empty.
End of Solution
3 Create a new disk group using the disks you initialized in the previous step
(emc0_dd7). Name the new disk group appdg. Observe the change in the disk
status.
Solution
vxdg init appdg appdg01=emc0_dd7

B89
The TYPE and STATUS of the disk are the same but the DISK and GROUP
columns now show the new disk media name and the disk group name
respectively.
End of Solution
4 Using the vxassist command, create a new volume of size 1g in appdg.

Name the new volume appvol.
Solution
vxassist -g appdg make appvol 1g
End of Solution
5 Create a Veritas file system on the appvol volume, mount the file system to the
/app directory. Create the directory if it does not exist.
Solution
mkdir /app
mount -t vxfs /dev/vx/dsk/appdg/appvol /app
End of Solution
6 Make sure that the file system is mounted at boot time.
Solution
vi /etc/fstab
/dev/vx/dsk/appdg/appvol /app vxfs rw,\
largefiles,delaylog 0 2
End of Solution
7 Unmount the /app file system, verify the unmount, and remount using the
mount -a command to mount all file systems in the file system table.
Solution
umount /app
/bin/mount | grep app
/bin/mount -a

End of Solution
8 Identify the amount of free space in the appdg disk group. Try to create a B
volume in this disk group named largevol with a size slightly larger than the
available free space, for example 2g on standard Symantec classroom systems.
What happens?
Solution
vxdg -g appdg free
The free space is displayed in sectors in the LENGTH column.
vxassist -g appdg make largevol 2g

You should receive an error indicating that Volume Manager cannot allocate
the requested space for the volume, and the volume is not created.
End of Solution
9 Choose a second disk (emc0_dd8), initialize it, if necessary, and add it to the
appdg disk group. Observe the change in free space.
Solution
vxdg -g appdg adddisk appdg02=emc0_dd8
vxdg -g appdg free
End of Solution
as in step 8.
Solution
Note: The 2g volume size is used as an example here. You may need to use a
value more suitable to your lab environment if you are not working in a
standard Symantec classroom.
vxassist -g appdg make largevol 2g

This time the volume creation should complete successfully.
End of Solution

B91
11 Display volume information for appdg disk group using the
vxprint -g appdg -htr command. Can you identify which disks are
used for which volumes?
Solution
vxprint -g appdg -htr
End of Solution
12 List the disk groups on your system using the vxdg list command.
Solution
vxdg list
If you have followed the labs so far, you should have one disk group listed
appdg.
End of Solution
13 Display disk property information for each disk in the appdg disk group using
the vxdisk -p list command. From the output record the following
information:
DISK _______________ _______________

SCSI_VERSION _______________ _______________
LUN_SERIAL_NO _______________ _______________
DDL_THIN_DISK _______________ _______________
ATYPE _______________ _______________
Solution
vxdisk -p list -g appdg emc0_dd7
DISK _______________ _______________

SCSI_VERSION _______________ _______________

LUN_SERIAL_NO _______________ _______________
DDL_THIN_DISK _______________ _______________
ATYPE _______________ _______________
vxdisk -p list -g appdg emc0_dd8
DISK _______________ _______________

SCSI_VERSION _______________ _______________
LUN_SERIAL_NO _______________ _______________
DDL_THIN_DISK _______________ _______________
ATYPE _______________ _______________
End of Solution
14 Display the OS native names for all the disks using the vxdisk -e list
command.
Solution
vxdisk -e list
End of Solution

B93
Exercise 2: Removing volumes and disks: CLI
sym1
1 Unmount the /app file system and remove it from the file system table.
Solution
umount /app
vi /etc/fstab
Navigate to the line with the entry corresponding to the /app file system and
type dd to delete the line.
Type :wq to save and close the file.
End of Solution
2 Remove the largevol volume in the appdg disk group. Observe the disk group
configuration information using the vxprint -g appdg -htr command.
Solution
vxassist -g appdg remove volume largevol
There should be only appvol volume, and the second disk, appdg02, should be
unused.
End of Solution
3 Remove the second disk (appdg02) from the appdg disk group. Observe the
change in its status.
Solution
vxdg -g appdg rmdisk appdg02
Note that the disk is still in online state; it is initialized.
End of Solution

Exercise 3: Destroying disk data using disk shredding: CLI
sym1
1 Mount the appvol volume to the /app directory. Do not add the entry to the
file system table.
Solution
End of Solution
2 Copy some data files into the /app file system. For this test, use the files
located in the /etc/default directory. List the contents of the /app
directory after the copy has completed.
Solution
cp /etc/default/* /app
ls -al /app
End of Solution
Solution
umount /app
End of Solution
Solution
vxdg destroy appdg
End of Solution

B95
5 Observe the status of the disk devices on the system.
Solution
End of Solution
6 To prove that the data files have not been destroyed, recreate the appdg disk
group and the appvol volume using the exact same steps as used in Exercise 1 -
steps 3-4. DO NOT create a new file system on the appvol volume.
Solution
End of Solution
7 Mount the appvol volume to the /app directory and list the contents of the
directory. The data files should still exist.
Solution
ls -al /app
End of Solution
Solution
umount /app

End of Solution
Solution
vxdg destroy appdg
End of Solution

10 Use the vxdiskunsetup command with the -o shred option to shred the
disk that was used in the appdg disk group for the appvol volume. This
command may take a while to compete.
Solution B
vxdiskunsetup -o shred emc0_dd7

End of Solution
11 Re-initialize the disk using the vxdisksetup command.
Solution
End of Solution
12 Recreate the appdg disk group and the appvol volume using the exact same
steps as used in Exercise 1 - steps 3-4. DO NOT create a new file system on the
appvol volume.
Solution
End of Solution
13 Attempt to mount the appvol volume to the /app directory. What happened?
Solution
The volume will not mount because the file system information was shredded.
End of Solution
Solution
vxdg destroy appdg
End of Solution

B97
systems: VOM
vom
1 Start the VOM GUI and log on as the root user.

Solution
a https://vom:14161
b A warning message may appear to advise that this has an invalid security
certificate.
Choose or you can add an exception,

add exception,
get certificate,
confirm security exception.
c Log on using root, with a password of veritas.
End of Solution
Solution
a Manage > Servers > Hosts. Click the sym1.example.com link, and
choose the Disks tab.
b View the disks in the table.
Normally the disks should be in Free (Uninitialized) state unless they have
already been initialized for Volume Manager use and the state would be
Free (Initialized).
End of Solution
B
3 Select an uninitialized disk (emc0_dd7) and initialize it, if necessary, using
VOM. Observe the change in the Status column. What is the status of the disk
now?
Solution
a Select Administer > All Disks and mark the disk to initialize.
b Select Actions > Initialize.
c Verify the selected disk in the Initialize view and click Next, Finish, then
Ok.
The status of the disk should change to Free.

End of Solution
4 Create a new disk group using the disk you initialized in the previous step.
Name the new disk group appdg. Observe the change in the disk status.
Solution
a Select Create Disk Group from the Tasks list.
b In the Create Disk Group screen, type the name of the disk group. Ensure
that Enable Cross-platform Data Sharing (CDS) remains checked and
click Next.
c Select the newly initialized disk(emc0_dd7) and click Next, Finish and
Ok.
The status of the disk should change to Imported and the disk media name
(Internal name) and the disk group name should be visible in the disk table.
End of Solution

B99
5 Using VOM, create a new 1g volume in the appdg disk group. Name the new
volume appvol. Create a file system on it and make sure that the file system is
mounted at boot time to /app directory.
Solution
a Select Create Volume from the Tasks lists.
b Select the appdg disk group name and click Next.
c Let volume manager decide what disks to use for this volume, and click
Next to continue.
d Enter volume name and click Next to continue.
e Specify the volume size and leave the other options at their default values.
f Leave the Create as a Snapshot Cache Volume option unchecked,

select Show create file system options and click Next.
g On the File System options page, select to create a VxFS file system.
Select Show mount options and click Next.
h Enter the mount point called /app and verify that Add to file system table
is checked. Click Next.
i Verify the summary information, and click Finish and OK.
End of Solution
6 Check if the file system is mounted and verify that there is an entry for this file
system in the file system table.
Solution
a Select the appdg disk group link from the table. The disk group details are
displayed.
b View the details of the volumes in the disk group. The /app file system
should be listed here. Note the Mounted column.
c You can also use the command line to verify the changes as follows:
mount
cat /etc/fstab
The /app file system should show as mounted and there should be a line
in the file system table to ensure that it is mounted at boot time.
End of Solution
B
7 View the properties of the disk in the appdg disk group and note the Size and
the Unallocated fields.
Size ___________________________
Unallocated ___________________
Solution
Select Disks tab from the Disk Group Details display.
End of Solution
8 Try to create a second volume, largevol, in the appdg disk group and specify a
size slightly larger than the unallocated space on the existing disk in the disk
group, for example 2g in the standard Symantec classroom systems. Do not
create a file system on the volume. What happens?
Solution
a Select Create Volume from the Tasks list.
b Select the disk group name and click Next.
c Let volume manager decide what disks to use for this volume, click Next to
continue.
e Specify the volume size and leave the other options at their default values,
click Next.
f Leave the Create as a Snapshot Cache Volume option unchecked. and

click Next.
g Verify the summary information, and click Finish.
You should receive an error indicating that Volume Manager cannot allocate
the requested space for the volume, and the volume is not created.
End of Solution

B101
9 Add a second disk (emc0_dd8) to the appdg disk group.
Solution
a Select Add Disk from the Tasks list.
b Verify that the appdg disk group is selected, and click Next.
c Choose the emc0_dd8 disk and click Next.
d Verify the summary information and click Finish and Ok.
End of Solution
as in step 8. Do not create a file system.
Solution
a Select Create Volume from the Tasks list.
b Select the disk group name and click Next.
c Let volume manager decide what disks to use for this volume, click Next to
continue.
e Specify the volume size and leave the other options at their default values,
click Next.
f Leave the Create as a Snapshot Cache Volume option unchecked. and

click Next.
g Verify the summary information, and click Finish.
This time the volume creation should complete successfully.

End of Solution

11 Observe the volumes displayed in the Volumes in Disk Group table. Can you
tell which volume has a mounted file system?
Solution
B
View the details of the volumes in the disk group from the volumes tab. You
should notice that the mount point and mounted columns have file system
information for appvol and not for largevol.
End of Solution
12 Create a VxFS file system on largevol and mount it to /large directory.

Ensure that the file system is not mounted at boot time. Check if the /large
file system is currently mounted and verify that it has not been added to the file
system table.
Solution
a Select the largevol volume and select Actions > Create File System.
b Verify the disk group and volumes names and that the file system type is
vxfs. Select Show mount options and click Next.
c Enter the mount point, uncheck the Add to file system table option, and
click Next.
d View the summary and click Finish, and OK.
e View the details of the volumes in the disk group from the volumes tab.
You should notice that the mount point and mounted columns have file
system information now for largevol with a mount point of /large.
The /large file system should show as mounted but there should be no
change in the file system table.
f You can also use the command line to verify the changes as follows:
mount
cat /etc/fstab
End of Solution

B103
groups: VOM
vom
1 Unmount both /app and /large file systems using VOM. Accept to remove
the file systems from the file system table if prompted. Check if the file
systems are unmounted and verify that any corresponding entries have been
removed from the file system table.
Solution
a Select the checkbox for appvol volume.
b Select Actions > Unmount File System.
c Confirm the unmount and select Yes for Would you like to remove /app
from file system table?. Click Finish then OK.
d Check the largevol volume. Select Actions > Unmount File System.
Confirm the unmount.
The volumes should no longer have mounted file systems.

End of Solution
2 Remove the largevol volume in the appdg disk group.
Solution
a Select the Volumes tab and check the largevol volume.
b Select Actions > Delete. Click Next, Finish and then OK.
End of Solution

3 Select the Administer button, All Disk Groups, and then select the appdg disk
group. View the Disks tab. Observe the disks in the appdg disk group. Can you
identify which disk is empty?
Solution B
The Usage column should show 0% for the unused disk which is the second
disk in the disk group (appdg02).
End of Solution
4 Remove the disk you identified as empty from the appdg disk group.
Solution
Mark the empty disk and select Actions > Remove. Click Next, Finish, and
OK.
End of Solution
5 Observe all the disks on the system. What is the status of the disk you removed
from the disk group?
Solution
Select sym1.example.com Summary >All Disks and observe the disks.
The disk removed in step 4 should be in Free state.
End of Solution
Solution
a Select sym1.example.com Summary >All Disk Groups.
b Mark the appdg disk group in the right pane view.
c Select Actions > Destroy. Click Next, Finish and Ok.
End of Solution

B105
7 Observe all the disks on the system. What is the status of the disks?
Solution
Select hostname Summary >All Disks and observe the disks listed.
If you have followed all the lab steps, you should have 4 disks in Free state;
they are already initialized but not in a disk group.
End of Solution
End of lab

B
Lab 5: Working with Volumes with Different Layouts

In this lab, you create simple concatenated volumes, striped volumes, and mirrored
volumes. Optionally, you practice creating a a layered volume and using the
Storage Provisioning add-on with VOM.
Creating volumes with different layouts: CLI
Optional lab: Setting up Storage Provisioning: VOM
Optional lab: Creating layered volumes
Optional lab: Creating volumes with user defaults: CLI
Prerequisite setup
external disks to be used during the labs. Optional labs require the VOM
management server to be pre-installed and the SF servers to be managed hosts.

411 Lab 5: Working with Volumes with Different Layouts
B107
Lab information
environment.
Object Value
sym1
sym2


Exercise 1: Creating volumes with different layouts: CLI
sym1 B
1 Add four initialized disks (emc0_dd7 - emc0_d10) to a disk group called

appdg. Verify your action using vxdisk -o alldgs list.
a If you have completed the Creating a Volume and File System lab
(lab 4), you should already have some initialized disks. You will need four
disks for this lab. If four disks are not initialized, then initialize the needed
disks from the same enclosure for use in Volume Manager (all disks on the
EMC array).
Solution
vxdisksetup -i emc0_d10
Perform the above command for any disks that have not been initialized for
Volume Manager use and that will be used in this lab.
End of Solution
b Create a new disk group and add disks:
Solution
vxdg init appdg appdg01=emc0_dd7 \
appdg02=emc0_dd8 appdg03=emc0_dd9 \
appdg04=emc0_d10
Alternatively, you can also create the disk group using a single disk device
and then add each additional disk as follows:
vxdg g appdg adddisk appdg##=accessname

where accessname is the enclosure-based name for the disk as displayed
in the DEVICE column of the output of the vxdisk list command in
SF 6.0.
End of Solution

B109
2 Create a 50-MB concatenated volume in appdg disk group called appvol with
one drive.
Solution
vxassist -g appdg make appvol 50m
End of Solution
3 Display the volume layout. What names have been assigned to the plex and
subdisks?
Solution
To view the assigned names, view the volume using:
vxprint -g appdg -htr | more
End of Solution
4 Remove the volume.
Solution
vxassist -g appdg remove volume appvol
End of Solution
5 Create a 50-MB striped volume on two disks in appdg and specify which two
disks to use in creating the volume. Name the volume stripevol.
Solution
vxassist -g appdg make stripevol 50m layout=stripe \
appdg01 appdg02
End of Solution

Solution
End of Solution

6 Create a 20-MB, two-column striped volume with a mirror in appdg. Set the
stripe unit size to 256K. Name the volume strmirvol.
Solution
B
vxassist -g appdg make strmirvol 20m \
layout=mirror-stripe ncol=2 stripeunit=256k
End of Solution
What do you notice about the plexes?

Solution
View the volume using vxprint -g appdg -htr | more.
Notice that you now have a second plex.
End of Solution
7 Create a 20-MB, two-column striped volume with a mirror. Set the stripe unit
size to 128K. Select at least one disk that you should not use. Name the volume
2colstrvol.
Solution
vxassist -g appdg make 2colstrvol 20m \
layout=mirror-stripe ncol=2 stripeunit=128k \
\!appdg03
Note: As you are using bash as your shell environment, you must use the
escape character before the exclamation mark; for example
\!appdg03.
End of Solution

Solution
This operation should fail because there are not enough disks available in the
disk group. A two-column striped mirror requires at least four disks.
VxVM vxassist ERROR V-5-1-15315 Cannot allocate space
for 40960 block volume: Not enough HDD devices
available for allocation.
End of Solution

B111
8 Create a 20-MB 3-column striped volume with a mirror. Specify three disks to
be used during volume creation. Name the volume 3colstrvol.
Solution
vxassist -g appdg make 3colstrvol 20m \
layout=mirror-stripe ncol=3 appdg01 appdg02 \
appdg03
End of Solution

Solution
Again, this operation should fail because there are not enough disks allocated
on the command line. At least six disks are required for this type of volume
configuration.
VxVM vxassist ERROR V-5-1-15315 Cannot allocate space
for 40960 block volume: Not enough HDD devices
available for allocation.
End of Solution
9 Create the same volume specified in the previous step using the same three
disks, but without the mirror. However, this time first determine what the
maximum size that the volume can be based on the remaining free space.
Create the volume with the maximum possible size for this layout.
a Determine the maximum size that the volume could be.
Solution
vxassist -g appdg maxsize layout=stripe ncol=3 \
appdg01 appdg02 appdg03
Maximum volume size: 12128256 (5922Mb)
Note: The example solution provided here shows a maximum volume

size that will be different than what will be seen on your system. It
is for example purposes only.
End of Solution

b Create a new volume with the maximum possible volume size for the
layout specified in the previous step.
Solution
B
vxassist -g appdg make 3colstrvol maxsize \
layout=stripe ncol=3 appdg01 appdg02 appdg03
End of Solution

Solution
End of Solution
Note: Only perform the remaining steps if you do not intend to complete the
optional exercises towards the end of this lab. Otherwise, skip the next two
steps.
10 Remove the volumes created in this exercise.
Solution
vxassist -g appdg remove volume stripevol
vxassist -g appdg remove volume strmirvol
vxassist -g appdg remove volume 3colstrvol
End of Solution
11 Remove the disk group that was used in this exercise.

Solution
vxdg destroy appdg
End of Solution

B113
Exercise 2: Optional lab: Setting up Storage Provisioning: VOM
Note: Storage Provisioning requires that the Veritas Storage Foundation Add-on
for Storage Provisioning is installed. This lab section covers the steps to
install the add-on and to set up storage provisioning.
vom
1 If the Web console is already open, skip this step, otherwise, open a Web
browser and enter the URL for the VOM MS Web console on the address line.
You may receive an error about the Web sites certificate, click the link to
your server.
Solution
https://vom.example.com:14161/sfm
End of Solution
2 Select the Settings tab, then from the sub menu select Deployment
Management.

Repository window will open.
the folder that contains the Storage Provisioning add-on
(VRTSsfmvtp-4.1.119.0.sfa). This software is in
/student/software/vom/vom41/add-ons. Select the
VRTSsfmvtp-4.1.119.0.sfa file and click Open. Click the Upload
button to begin the upload of the add-on to the VOM MS. When the upload is
complete, click the Close button to exit the Upload to Repository window.
5 The Storage Provisioning add-on should now be present in the Deployment
Installed.
B
6 Select the Storage Provisioning add-on radio button from the Deployment
Management Repository. Then from the Actions pull-down menu, select
Install. A new Install Solution window will open.
7 In the Install Solution window, Click the Install button to start the
deployment of the add-on. After the deployment completes you will receive
the following message. Click the Ok button to close the wizard.

sfmcswd )
8 The browser will now display the Deployment Summary. Note that the
Result shows Enabled.
9 On a terminal session on the VOM management server, restart the Web server.
Solution
End of Solution

selecting the Settings tab, then from the sub menu select Deployment
11 Create a VxFS file system on the strmirvol volume on the

sym1.example.com system.
Solution
choose Administer > All Volumes.
b Select the strmirvol volume and select Actions > Create File System.

B115
c Verify the disk group and volumes names and that the file system type is
vxfs. Select Show mount options and click Next.
d Enter the mount point /app, uncheck the Add to file system table
option, and click Next.
e View the summary and click Finish, and Ok.
End of Solution
12 Using the VxFS file system created in the previous step, create a storage
template.
Solution
a From the VOM console menu, select Solutions.
b Under Storage Provisioning, select the Manage Storage Templates link.
c In the Storage Template overview pane, select Actions > Create Storage
Template.
d In the Create Storage Template window, choose Using NTFS or VxFS

file systems, and click Next. This should already be selected.
e Select the sym1.example.com host, then the appdg disk group and then
the /app file system, and click Next.
f In the Summary options panel, enter app-template as the storage

template name. Enter a description if desired.
g Select the file system object from the left navigation tree. Click the
Parameters tab and remove any Rules for select LUNs on Mirror1 and
Mirror2. This is done by selecting the rule, then clicking the minus sign
icon. Click Save, then OK.
End of Solution

13 Create a new webdg disk group on sym2.example.com using 4 disks
(3pardata0_49 - 3pardata0_52) on a different array than the one used by the
appdg disk group on sym1.example.com.
Solution B
a Manage > Servers > Hosts. Click the sym2.example.com link.
b Select Administer > All Disks and mark four disks to initialize
(3pardata0_49 - 3pardata0_52). Select Actions > Initialize.
c Select Create Disk Group from the Tasks list.
d In the Create Disk Group screen, type the name of the disk group
(webdg). Ensure that Enable Cross-platform Data Sharing (CDS)
remains checked and click Next.
e Select the newly initialized disks and click Next, Finish and Ok.
End of Solution
14 Using the storage template created in step 12, provision storage in the webdg
disk group on sym2.example.com.
Solution
a From the VOM console menu, select Solutions.
b Under Storage Provisioning, select the Provision Storage link.
c Select the sym2.example.com host, then the webdg disk group, and click
Next.
d Under Select a template, select the app-template template. click Next,

Submit and Ok.
e Ensure that the status of the storage provisioning shows the State as
Completed.
End of Solution

B117
15 Verify that the storage has been provisioned in the webdg disk group on
sym2.example.com.
Solution
choose the Volumes tab.
b View the newly created strmirvol_0 volume in the table.
c Note that the volume contains a file system and is mounted on /app_0.
End of Solution
16 Delete the newly created volume on sym2.example.com and destroy the

webdg disk group.
Solution
a Select Administer > All Volumes and mark the strmirvol_0 volume.
b Select Actions > Unmount file system. In the Unmount File System
window, answer Yes, click Next, Finish and Ok.
c Mark the strmirvol_0 volume again. Select Actions > Delete. In the
Delete window, answer Yes, click Next, Finish and Ok.
d Click the sym2.example.com Summary link > All Disk Groups.
e Mark the webdg disk group. Select Actions > Destroy. In the Destroy
window, click Next, Finish and Ok.
End of Solution

Exercise 3: Optional lab: Creating layered volumes
B
sym1
1 First, ensure that any volumes created in the previous labs are removed from
the appdg disk group. You may need to first unmount any volumes that have
mounted file systems.
Solution
df -k
umount /app
For each volume in the appdg disk group:

vxassist -g appdg remove volume volume_name
End of Solution
2 Create a 100-MB Striped Mirrored volume with no logging. Name the volume
strmirvol.
Solution
vxassist -g appdg make strmirvol 100m \
layout=stripe-mirror nmirror=2 ncol=2
End of Solution

B119
3 Create a Concatenated Mirrored volume with no logging called concatmirvol.
The size of the volume should be greater than the size of the largest disk in the
disk group; for example, if your largest disk is 2 GB, then create a 3-GB
volume.
Solution
vxassist -g appdg make concatmirvol 3g \
layout=concat-mirror nmirror=2
End of Solution
4 View the volumes and compare the layouts.
Solution
End of Solution
Solution
vxassist -g appdg remove volume strmirvol
vxassist -g appdg remove volume concatmirvol
End of Solution

Exercise 4: Optional lab: Creating volumes with user defaults: CLI
B
This optional guided practice illustrates how to use the files:

/etc/default/vxassist
/etc/default/alt_vxassist
to create volumes with defaults specified by the user.
sym1
1 Navigate to the /etc/default directory.

Solution
cd /etc/default
End of Solution
2 Create two files in /etc/default:
a Using the vi editor, create a file called vxassist that includes the
following:
nmirror=3
Solution
vi vxassist
# When mirroring create three mirrors
nmirror=3
End of Solution
b Using the vi editor, create a file called alt_vxassist that includes the
following:

B121
stripeunit=256k
Solution
vi alt_vxassist
# use 256K as the default stripe unit size for
# regular volumes
stripeunit=256k
End of Solution
3 Use these files when creating the following volumes:
a Create a 100-MB volume called mirrorvol using layout=mirror.
Solution
vxassist -g appdg make mirrorvol 100m \
layout=mirror
End of Solution
b Create a 100-MB, two-column stripe volume called 2colstrvol using

-d /etc/default/alt_vxassist so that Volume Manager uses
the specified default file.
Note: The -d option of the vxassist command specifies the file

containing custom values for specific attributes related to volume
creation and space allocation. If -d option is not specified, the
command defaults to /etc/default/vxassist.
Solution
vxassist -g appdg -d /etc/default/alt_vxassist \
make 2colstrvol 100m layout=stripe
End of Solution
4 View the layout of these volumes using vxprint -g appdg -htr. What
do you notice?
Solution
The first volume should show three plexes rather than the standard two.

The second volume should show a stripe size of 256K instead of the
standard 64K. Note that 256K is displayed as 512 sectors on the Linux
platform.
End of Solution
B
5 Remove any vxassist default files that you created in this optional lab
section. The presence of these files can impact subsequent labs where default
behavior is assumed.
Solution
rm -f /etc/default/vxassist
rm -f /etc/default/alt_vxassist
End of Solution
Solution
vxassist -g appdg remove volume mirrorvol
vxassist -g appdg remove volume 2colstrvol
End of Solution
End of lab

B123

B
Lab 6: Making Configuration Changes

This lab provides practice in making configuration changes. In this lab, you add
mirrors and logs to existing volumes. You also change the volume read policy,
resize volumes, rename disk groups, and move data between systems.
Resizing a volume and file system
Optional lab: Resizing a file system only:
Optional lab: Converting a non-cds disk group
Prerequisite setup
To perform this lab, you need two lab systems with Storage Foundation pre-
installed, configured and licensed. In addition to this, you also need four external
shared disks to be used during the labs.
four external disks and no volumes in it.

B125
Lab information
In preparation for this lab, you will need the following information about your lab
environment.
Object Value
Host name of the main lab system sym1
Host name of the system sharing disks sym2


Exercise 1: Administering mirrored volumes
sym1
1 Ensure that you have a disk group called appdg with four disks in it. If not,
create the disk group using four disks.
Note: If you have completed the previous lab steps you should already have
the appdg disk group with four disks and no volumes.
Solution
End of Solution
2 Create a 50-MB, two-column striped volume called appvol in appdg.
Solution
vxassist -g appdg make appvol 50m layout=stripe \
ncol=2
End of Solution
3 Display the volume layout. How are the disks allocated in the volume? Note
the disk devices used for the volume.
Solution
End of Solution
Notice which two disks are allocated to the first plex and record your
observation.

B127
4 Add a mirror to appvol, and display the volume layout. What is the layout of
the second plex? Which disks are used for the second plex?
Solution
vxassist -g appdg mirror appvol
Note the disk devices used for the second plex. Note that the default layout
used for the second plex is the same as the first plex.
End of Solution
5 Add a dirty region log to appvol and specify the disk to use for the DRL.
Display the volume layout.
Solution
vxassist -g appdg addlog appvol logtype=drl \
appdg01
End of Solution
6 Add a second dirty region log to appvol and specify another disk to use for the
DRL. Display the volume layout.
Solution
vxassist -g appdg addlog appvol logtype=drl \
appdg02
End of Solution
7 Remove the first dirty region log that you added to the volume. Display the
volume layout. Can you control which log was removed?
Solution
vxassist -g appdg remove log appvol \!appdg01
\!appdg01.

End of Solution
8 Find out what the current volume read policy for appvol is. Change the volume B
read policy to round robin, and display the volume layout.
Solution
You should observe that the read policy shows as SELECT which is the value
used for selected based on layouts.
vxvol -g appdg rdpol round appvol

The value of the attribute will change to ROUND.

End of Solution
9 Remove the original mirror (appvol-01) from appvol, and display the volume
layout.
Solution
vxassist -g appdg remove mirror appvol \
\!disk_used_by_original_mirror
\!appdg01. The appdg01 disk was used by the original plex.
Note that the DRL log will also be removed automatically with this command
because the volume is no longer mirrored.
End of Solution
10 Remove appvol.
Solution
End of Solution

B129
Exercise 2: Resizing a volume and file system
sym1
1 Create a 20-MB concatenated mirrored volume called appvol in appdg. Create

a Veritas file system on the volume and mount it to /app. Make sure that the
file system is not added to the file system table.
Solution
vxassist -g appdg make appvol 20m layout=mirror
mkdir /app (if necessary)
End of Solution
2 View the layout of the volume and display the size of the file system.
Solution
df -k /app
End of Solution
3 Add data to the volume by creating a file in the file system and verify that the
file has been added.
Solution
echo "hello app" > /app/hello

cat /app/hello
End of Solution

4 Expand the file system and volume to 100 MB. Observe the volume layout to
see the change in size. Display file system size.
Solution
B
vxresize -g appdg appvol 100m
df -k /app
End of Solution

B131
Exercise 3: Renaming a disk group
sym1
1 Create a 100-MB concatenated volume called webvol in appdg. Create a

Veritas file system on the volume and mount it to /web. Make sure that the file
system is not added to the file system table.
Solution
vxassist -g appdg make webvol 100m layout=concat
mkfs -t vxfs /dev/vx/rdsk/appdg/webvol
mkdir /web (if necessary)
mount -t vxfs /dev/vx/dsk/appdg/webvol /web
End of Solution
2 Add data to the webvol volume by copying the /etc/group file to the
/web file system. Verify that the file has been added.
Solution
cp /etc/group /web
ls -l /web
End of Solution
3 Try to deport and rename the appdg disk group to webdg while the /app and
/web file systems are still mounted. Can you do it?
Solution
vxdg -n webdg deport appdg
You receive an error message indicating that the volumes in the disk group are
in use.
End of Solution

and their subdirectories. What do you see?
Solution
B
ls -lR /dev/vx/rdsk
This directory contains a subdirectory for each imported disk group, which
contains the character devices for the volumes in that disk group.
ls -lR /dev/vx/dsk
This directory contains a subdirectory for each imported disk group, which
contains the block devices for the volumes in that disk group.
End of Solution
5 Unmount all the mounted file systems in the appdg disk group.
Solution
umount /app
umount /web
End of Solution
6 Deport and rename the appdg disk group to webdg. Then import the newly
renamed webdg disk group.
Solution
vxdg -n webdg deport appdg
vxdg import webdg
End of Solution

and their subdirectories. What has changed?
Solution
ls -lR /dev/vx/rdsk
ls -lR /dev/vx/dsk

B133
The device subdirectories are rebuilt with the new name of the disk group.
End of Solution
8 Observe the disk media names. Is there any change?
Solution
vxprint -g webdg -htr
There should be no change in disk media names.

End of Solution
9 Mount the /app and /web file systems, and observe their contents.
Solution
mount -t vxfs /dev/vx/dsk/webdg/appvol /app
mount -t vxfs /dev/vx/dsk/webdg/webvol /web
ls -l /app
ls -l /web
End of Solution

Exercise 4: Moving data between systems
sym1
1 Copy new data to the /app and /web file systems. For example, copy the file
/etc/group to /app and the file /etc/hosts to /web.
Solution
cp /etc/group /app
cp /etc/hosts /web
End of Solution
2 View all the disk devices on the system.
Solution
End of Solution
3 Unmount all file systems in the webdg disk group and deport the disk group.
Do not assign it to a new host. View all the disk devices on the system.
Solution
umount /app
umount /web
vxdg deport webdg
End of Solution

B135
sym2
4 Import the webdg disk group on the other system (sym2), ensure that the
volumes in the imported disk group are all started, and view all the disk
Solution
vxdg import webdg
vxprint -g webdg -htr
End of Solution
5 Mount the /app and /web file systems. Note that you will need to create the
mount directories on the other system before mounting the file systems.
Observe the data in the file systems.
Solution
mkdir /app
mkdir /web
mount -t vxfs /dev/vx/dsk/webdg/appvol /app
mount -t vxfs /dev/vx/dsk/webdg/webvol /web
ls -l /app
ls -l /web
The data should be the same as it was on the first system.

End of Solution
6 Unmount the file systems.
Solution
umount /app
umount /web
End of Solution

7 Deport webdg and assign the original machine name (sym1) as the new host.
Solution
vxdg -h sym1 deport webdg
B
End of Solution
sym1
8 Import the disk group and change its name back to appdg. View all the disk
Note: Because the hostname of the sym1 system is assigned to the disk group
during the deport operation, the disk group can be automatically
imported if you execute the vxdctl enable command on your
system.
Solution
vxdg -n appdg import webdg
End of Solution
9 Deport the disk group appdg by assigning the ownership to a system called
anotherhost. View all the disk devices on the system. Why would you do this?
Solution
vxdg -h anotherhost deport appdg
You would do this to ensure that the disks are not imported accidentally by any
system other than the one whose name you assigned to the disks.
End of Solution

B137
10 Display detailed information about one of the disks in the disk group
(emc0_dd7) using the vxdisk list command. Note the hostid field in
the output.
Solution
vxdisk list emc0_dd7
End of Solution
11 Import appdg. Were you successful?
Solution
vxdg import appdg
This operation should fail, because appdg belongs to another host.

End of Solution
12 Now import appdg and overwrite the disk group lock. What did you have to do
to import it and why?
Solution
vxdg -C import appdg
You had to forcefully clear the host lock using the -C option because the disks
in the disk group were locked to anotherhost.
End of Solution
13 Display detailed information about the same disk in the disk group as you did
in step 10. Note the change in the hostid field in the output.
Solution
vxdisk list emc0_dd7
End of Solution

14 Remove the appvol and webvol volumes.
Solution
B
vxassist -g appdg remove volume webvol
End of Solution

B139
Exercise 5: Optional lab: Resizing a file system only
sym1
1 Create a 50-MB concatenated volume named appvol in the appdg disk group.
Solution
End of Solution
2 Create a Veritas file system on the volume by using the mkfs command.
Specify the file system size as 40 MB.
Solution
mkfs -t vxfs /dev/vx/rdsk/appdg/appvol 40m
0
End of Solution
3 Create a mount point /app on which to the mount the file system, if it does not
already exist.
Solution
End of Solution

4 Mount the newly created file system on the mount point /app.
Solution
B
End of Solution
5 Verify disk space using the df command. Observe that the total size of the file
system is smaller than the size of the volume.
Solution
df -k
End of Solution
6 Expand the file system to the full size of the underlying volume using the
fsadm -b newsize command.
Solution
/opt/VRTS/bin/fsadm -b 50m -r \
/dev/vx/rdsk/appdg/appvol /app
End of Solution
7 Verify disk space using the df command.
Solution
df -k
End of Solution

B141
8 Make a file on the file system mounted at /app, so that the free space is less
than 50 percent of the total file system size.
Solution
dd if=/dev/zero of=/app/25_mb bs=1024k count=25
End of Solution
9 Shrink the file system to 50 percent of its current size. What happens?
Solution
/opt/VRTS/bin/fsadm -b 25m -r \
/dev/vx/rdsk/appdg/appvol /app
The command fails. You cannot shrink the file system because blocks are
currently in use.
End of Solution
10 Unmount the /app file system and remove the appvol volume in appdg.
Solution
umount /app
End of Solution

Exercise 6: Optional lab: Converting a non-cds disk group
sym1
In this optional lab, you will destroy the existing appdg disk group, recreate it as a
non-cds disk group with non-cds disks and then convert the disk group to a cds
disk group.
1 Use the vxdisk -o alldgs list command to determine the disks that
are a part of the appdg disk group.
Solution
End of Solution
2 Destroy the existing appdg disk group using the vxdg destroy command.
Solution
vxdg destroy appdg
End of Solution
3 Use the vxdisksetup command to re-initialize the first disk (emc0_dd7)

determined in step one as a sliced disk.
Solution
vxdisksetup -i emc0_dd7 format=sliced
End of Solution

B143
4 Use the vxdisk -o alldgs list command to verify that the disk now
shows as auto:sliced.
Solution
End of Solution
5 Recreate the 4 disk appdg disk group as a non-cds disk group using the vxdg
init command.
Solution
vxdg init appdg appdg01=emc0_dd7 appdg02=emc0_dd8 \
appdg03=emc0_dd9 appdg04=emc0_d10 cds=off
End of Solution
flag is not set.
Solution
vxdg list appdg
End of Solution
7 Try to turn the cds flag on using the vxdg set command. Was the command
successful?
Solution
vxdg -g appdg set cds=on
The command fails because one of the disks in the disk group is not a CDS
disk.
End of Solution

8 Use the vxcdsconvert command with the alldisks option to convert
the appdg disk group to a cds disk group.
Solution
B
vxcdsconvert -g appdg alldisks
End of Solution
9 Use the vxdisk list to verify that all disks in the appdg disk group have
been converted to cds disks.
Solution
End of Solution
flag is still not set.
Solution
vxdg list appdg
End of Solution
11 Use the vxdg set command to turn the cds flag on.
Solution
vxdg -g appdg set cds=on
End of Solution

B145
flag is now set.
Solution
vxdg list appdg
End of Solution
End of lab

B
Lab 7: Administering File Systems

In this lab, you defragment a fragmented file system and protect a file system from
being accidentally unmounted using the MountLock feature. You also observe the
time to creation improvement when using the SmartMove feature with mirroring
and try the thin reclamation feature.
Preparation for defragmenting a Veritas File System lab
Defragmenting a Veritas File System
SmartMove
Thin reclamation
Optional lab: Testing the MountLock feature
Optional lab: Reading the file change log (FCL)
Optional lab: Defragmenting a Veritas File System
Prerequisite setup
configured and licensed. In addition to this, you also need four external disks and
the second internal disk to be used during the labs. If you do not have a second
internal disk or if you cannot use the second internal disk, you need five external
disks to complete the labs.
four external disks and no volumes in it. The second internal disk should be empty
and unused.

B147
Lab information
environment.
Object Value
Host name of the lab system sym1
2nd internal disk: sdb
Location of Lab Scripts (if any): /student/labs/sf/sf60


Exercise 1: Preparation for defragmenting a Veritas File System
lab
sym1
1 Identify the device name for the second internal disk on your lab system.
Solution
df -k
The second internal disk should be sdb.

End of Solution
2 Initialize the sdb disk using a non-cds disk format.
Solution
vxdisksetup -i sdb format=sliced
End of Solution
3 Create a non-cds disk group called testdg using the internal disk you initialized
in step 2.
Solution
vxdg init testdg testdg01=sdb cds=off
End of Solution
4 In the testdg disk group create a 1-GB concatenated volume called testvol
initializing the volume space with zeros using the init=zero option to
vxassist.
Solution
vxassist -g testdg make testvol 1g init=zero
End of Solution

B149
5 Create a VxFS file system on testvol.
Solution
mkfs -t vxfs /dev/vx/rdsk/testdg/testvol
End of Solution
6 Change into the /student/labs/sf/sf60 directory and run the

extentfrag_vxfs.pl script.
This script restores a fragmented file system onto the volume and performs a
file system check so that the volume can be mounted. Whatever files are in the
existing file system will be lost.
Solution
cd /student/labs/sf/sf60
./extentfrag_vxfs.pl
End of Solution
7 Mount the file system on /test. Note that you may need to perform a file
Solution
fsck -t vxfs /dev/vx/rdsk/testdg/testvol (if necessary)
mkdir /test
mount -t vxfs /dev/vx/dsk/testdg/testvol /test
End of Solution
8 Ensure that the directory where the vxbench command is located is included
Solution
echo $PATH | grep -i vxbench
If necessary:
PATH=$PATH:/opt/VRTSspt/FS/VxBench
export PATH
End of Solution

Exercise 2: Defragmenting a Veritas File System
sym1
The purpose of this section is to examine the structure of a fragmented and an

unfragmented file system and compare the file systems throughput in each case.
The general steps in this exercise are:
Make and mount a file system.
Examine the structure of the new file system for extents allocated.
Then examine a fragmented file system and report the degree of fragmentation
in the file system.
Use a support utility called vxbench to measure throughput to specific files
within the fragmented file system.
De-fragment the file system, reporting the degree of fragmentation.
Repeat executing the vxbench utility using identical parameters to measure
throughput to the same files within a relatively unfragmented file system.
Compare the total throughput before and after the defragmentation process.
1 In the appdg disk group create a 1-GB concatenated volume called appvol.
Solution
End of Solution
2 Create a VxFS file system on appvol and mount it on /app.

Solution
End of Solution
3 Run a fragmentation report on /app to analyze directory and extent

fragmentation. Is a newly created, empty file system considered fragmented?
In the report, what percentages indicate a file systems fragmentation?

B151
Solution
/opt/VRTS/bin/fsadm -D -E /app

total 2 0 2 0 0 0
File System Extent Fragmentation Report
Free Space Fragmentation Index : 5

File Fragmentation Index : 0
# Files Fragmented by Fragmentation Index

0 1-25 26-50 51-75 76-100
2 0 0 0 0
Total Average Average Total

Files File Blks # Extents Free Blks
0 0 0 1030827
blocks used for indirects: 0
% Free blocks in extents smaller than 64 blks: 0.01
% blks allocated to extents 64 blks or larger: 0.00
Free Extents By Size
1: 1 2: 1 4: 2
8: 2 16: 1 32: 2
64: 1 128: 2 256: 1
512: 2 1024: 1 2048: 0

4096: 1 8192: 1 16384: 0
32768: 1 65536: 1 131072: 1
262144: 1 524288: 1 1048576: 0
2097152: 0 4194304: 0 8388608: 0
16777216: 0 33554432: 0 67108864: 0
134217728: 0 268435456: 0 536870912: 0
1073741824: 0 2147483648: 0
A newly created file system with no files or directories cannot be fragmented.

The following table displays the percentages you should be observing in the
output of the fragmentation report to determine if a file system with files and
directories is fragmented.
Percentage Unfragmented Badly

B
fragmented
% of Free blocks in extents smaller than < 5% > 50%
64 blocks
% of Free blocks in extents smaller than 8 < 1% > 5%
blocks
% blks allocated to extents 64 blks or > 5% < 5%
larger
End of Solution
4 What is a fragmented file system?
Solution
A fragmented file system is a file system where the free space and/or file data
is in relatively small extents scattered throughout different allocation units
within the file system.
End of Solution
5 If you were shown the following extent fragmentation report about a file
system, what would you conclude?

total 199185 85482 115118 5407 5473 5655
Solution
A high total in the Dirs to Reduce column indicates that the directories are not
optimized. This file system's directories should be optimized by directory
defragmentation.
End of Solution

B153
6 Unmount /app and remove appvol in the appdg disk group.
Solution
umount /app
End of Solution
7 Run a fragmentation report on /test to analyze directory and extent

fragmentation. Is /test fragmented? Why or why not? What should be done?
Solution
/opt/VRTS/bin/fsadm -D -E /test

total 2 2 1 0 0 0
File System Extent Fragmentation Report
Free Space Fragmentation Index : 38

File Fragmentation Index : 48
# Files Fragmented by Fragmentation Index

0 1-25 26-50 51-75 76-100
21 0 0 35 0
Total Average Average Total

Files File Blks # Extents Free Blks
56 4457 778 830117
blocks used for indirects: 560

% blks allocated to extents 64 blks or larger: 19.94
Free Extents By Size
1: 16949 2: 11484 4: 25466
8: 10812 16: 1405 32: 3
64: 1 128: 1 256: 0
512: 1 1024: 1 2048: 0
4096: 1 8192: 0 16384: 1

32768: 1 65536: 0 131072: 0
262144: 0 524288: 1 1048576: 0
2097152: 0 4194304: 0 8388608: 0
16777216: 0 33554432: 0 67108864: 0
134217728: 0 268435456: 0 536870912: 0 B
1073741824: 0 2147483648: 0
Dirs to Reduce column is 0. Therefore, the directories do not need to be

optimized. But the extents need to be optimized. Because:
% Free blocks in extents smaller than 64 blks: 30.22 (<50%) - OK
% Free blocks in extents smaller than 8 blks: 17.08 (>5%) - Not OK
% blks allocated to extents 64 blks or larger: 19.94 (>5%) - OK
Therefore, the file system's extents should be defragmented.
End of Solution
8 Use the getext command to display the extent attributes of the files in the
/test file system.
Solution
/opt/VRTS/bin/getext /test/*
...
/test/test42: Bsize 1024 Reserve 0 Extent
Size 2
Size 4
Size 6
Size 8
Size 0

Size 2
Size 4
Size 6
Size 8000
Size 0
...

B155
Two files that will be used in performance tests have been highlighted in the
sample output provided here.
End of Solution
9 Measure the sequential read throughput to a particular file, for example, an

8MB file on an 8K extent (for example, /test/test48), in a fragmented
file system using the vxbench utility and record the results. Use an 8K
sequential I/O size.
Note: Remount the file system before running each I/O test
Solution
mount -t vxfs -o remount \
/dev/vx/dsk/testdg/testvol /test
/opt/VRTSspt/FS/VxBench/vxbench_rhel5_x86_64 \
-w read -i iosize=8k,iocount=1000 /test/test48
A sample output is provided here as an example:
total: 7.147 sec 1119.40 KB/s cpu: 0.12 sys 0.00 user
End of Solution
10 Repeat the same test for an 8Mb file on an 8Mb extent (for example, using the
/test/test58 file). Note that the file system must be remounted between
the tests. Can you explain why?
Solution
The file system must be remounted to clear the read buffers.

End of Solution

11 Defragment /test and gather summary statistics after each pass through the
file system. After the defragmentation completes, determine if /test is
fragmented? Why or why not?
B
Note: The defragmentation can take about 5 minutes to complete.
Solution
/opt/VRTS/bin/fsadm -e -E -s /test
The file system no longer needs to be defragmented, because:

% Free blocks in extents smaller than 64 blks: (<50%) - OK
% Free blocks in extents smaller than 8 blks: (<1%) - OK
% blks allocated to extents 64 blks or larger: (>5%) - OK
End of Solution
12 Measure the throughput of the unfragmented file system using the vxbench
utility on the same files as you did in steps 9 and 10. Is there any change in
throughput?
Notes:
The file system must be remounted before each test to clear the read
buffers.
If you have used external shared disks on a disk array used by other
systems for this lab, the performance results may be impacted by the disk
array cache and may not provide a valid comparison between a fragmented
and defragmented file system.
Solution


B157

There is an improvement in throughput for both cases but the improvement is

highest for the file using small extent sizes (that is for /test/test48).
End of Solution
13 What is the difference between an unfragmented and a fragmented file system?
Solution
A fragmented file system has free space scattered throughout the file system in
relatively small extents whereas an unfragmented file system has free space in
just a few relatively large extents.
End of Solution
14 Is any one environment more prone to needing defragmentation than another?
Solution
Yes, volatile environments wherein files are grown, shrunk, erased, moved,
and so on, especially where the file systems do not have much free space, are
prone to fragmentation.
Stable environments, such as Oracle databases and logs, have very little impact
on the supporting file system so require infrequent defragmentation.
End of Solution

Exercise 3: SmartMove
sym1 B
In this lab section, you make a larger volume so that you can see the time
difference when using the SmartMove feature.
1 Create a 1-GB, volume called appvol in appdg.

Solution
End of Solution
2 Create a VxFS File System on appvol and mount it to /app.
Solution
End of Solution
3 Copy /etc/hosts to /app.
Solution
cp /etc/hosts /app
End of Solution
4 Umount the /app file system.
Solution
umount /app
End of Solution
operation.

B159
Note: Although SmartMove is enabled by default in Storage Foundation 6.0,
it is not used when the file system is unmounted.
Solution
time -p vxassist -g appdg mirror appvol
Time to create mirror _____________________________________
End of Solution
6 Delete the mirror that you added to appvol.
Solution
vxassist -g appdg remove mirror appvol
End of Solution
7 Mount the /app file system.
Solution
End of Solution
operation.
Solution
time -p vxassist -g appdg mirror appvol
Time to create mirror _____________________________________

Note: The mirroring operation should not take as long as it did the first time
the mirror was created. This is because it is only mirroring the used
data in the file system and not the whole volume by using SmartMove,
as the file system is now mounted.
End of Solution

9 Unmount /app using the umount command.
Solution
umount /app
B
End of Solution
Solution
End of Solution

B161
Exercise 4: Thin reclamation
sym1
1 View all the disk devices on the system. Then use the vxdisk -o thin
list command to list only the thin provisioning capable devices.
Solution
vxdisk -o thin list
End of Solution
2 Locate the thin provisioning and thin reclamation capable devices from the
output in the previous step. The TYPE column in the output of the
vxdisk -o thin list command should display thinrclm. Choose
two thin reclamation capable devices (3pardata0_49 and 3pardata0_50), if they
are uninitialized use the vxdisksetup command to initialize them.
Note: If you do not see any thin provisioning and thin reclamation capable
devices in the vxdisk list output, contact your instructor. You
must have thin provisioning and thin reclamation capable devices to
complete this lab section.
Solution
vxdisksetup -i 3pardata0_49
vxdisksetup -i 3pardata0_50
vxdisk -o thin list
The TYPE field in the output of the vxdisk -o alldgs list command
should change to auto:cdsdisk and the STATUS of the disk should change
to online thinrclm but the DISK and GROUP columns should still be
empty.
End of Solution

3 Create a new disk group using the two disks (3pardata0_49 and 3pardata0_50)
you initialized in the previous step. Name the new disk group thindg. Observe
the change in the disk status.
Solution B
vxdg init thindg thindg01=3pardata0_49 \

thindg02=3pardata0_50
The TYPE and STATUS of the disks are the same but the DISK and GROUP
columns now show the new disk media name and the disk group name
respectively.
End of Solution
4 Using the vxassist command, create a new volume of size 3g in thindg.

Name the new volume thinvol.
Solution
vxassist -g thindg make thinvol 3g
End of Solution
5 Create a Veritas file system on the volume and mount it to /thin. Do not add
the file system to the file system table.
Solution
mkfs -t vxfs /dev/vx/rdsk/thindg/thinvol
mkdir /thin (if necessary)
mount -t vxfs /dev/vx/dsk/thindg/thinvol /thin
End of Solution
6 Display the size of the file system using the df -k /thin command.
Solution
df -k /thin
End of Solution

B163
7 Use the vxdisk -o thin,fssize list command to view the size of
the disks compared to the physically allocated space.
Solution
vxdisk -o thin,fssize list
End of Solution
8 Use the dd command to make some 400MB files on the file system mounted at
/thin, so that the free space is less than 10 percent of the total file system
size. Use the df -k /thin command to monitor the file system free space.
Solution
dd if=/dev/zero of=/thin/file1 bs=1024k count=400
df -k /thin
End of Solution

increase to the physically allocated space.
Solution
End of Solution
10 Delete the files created in the step 8.
Solution
rm -f /thin/file*
End of Solution

11 Use the df -k and vxdisk -o thin,fssize list commands again.
Note that the usage has decreased back to the starting point, but the physically
allocated space remains the same.
Solution B
df -k /thin
End of Solution
12 Use the vxdisk reclaim command on the thindg disk group to reclaim
the space on the LUNS.
Solution
vxdisk reclaim thindg
End of Solution

decrease to the physically allocated space.
Solution
End of Solution
14 Unmount the /thin file system and destroy the thindg disk group.
Solution
umount /thin
vxdg destroy thindg
End of Solution

B165
15 If you are NOT planning to perform the optional exercises for this lab,
unmount /test file system and destroy the testdg disk group; otherwise, skip
this step.
Solution
umount /test
vxdg destroy testdg
End of Solution

Exercise 5: Optional lab: Testing the Mountlock feature
sym1 B
VxFS file system on appvol.
Solution
End of Solution
2 Mount the file system using the Mountlock feature and a tag of
locktest. Mount it to /app.
Solution
mount -t vxfs -o mntlock="locktest" \
/dev/vx/dsk/appdg/appvol /app
End of Solution
3 Use the mount command to view that the mount lock was set.
Solution
/bin/mount | grep locktest
End of Solution
4 Attempt to unmount using the umount command. What is the error?
Solution
umount /app
B167
umount: /app: device is busy
End of Solution
5 Use the fsadm command to remove the lock on the mount point.
Solution
/opt/VRTS/bin/fsadm -o mntunlock="locktest" /app
End of Solution
6 Use the mount command to view that the mount lock was removed.
Solution
/bin/mount | grep locktest
End of Solution
7 Attempt to unmount using the umount command. Did the operation

complete?
Solution
umount /app
Yes, the umount completed.

End of Solution
Solution

End of Solution

9 If you are NOT planning to perform the rest of the optional exercises for this
lab, unmount /test file system and destroy the testdg disk group; otherwise,
skip this step.
Solution B
umount /test
vxdg destroy testdg
End of Solution

B169
Exercise 6: Optional lab: Reading the file change log (FCL)
sym1
VxFS file system on appvol and mount it on /fcl_test.
Solution
mkdir /fcl_test
mount -t vxfs /dev/vx/dsk/appdg/appvol /fcl_test
End of Solution
2 Turn the FCL using the fcladm command for /fcl_test, and ensure that it
is on.
Solution
fcladm on /fcl_test
fcladm state /fcl_test
ON
End of Solution
3 Navigate to the directory that contains the FCL and list the contents.
Solution
cd /fcl_test/lost+found
ls
changelog
End of Solution

/fcl_test command.
Solution
B
fcladm print 0 /fcl_test
magic a506fcf5 version 4
time 1255029926 866253 (October 8, 2009 12:25:26 PM
PDT PDT)
state ON sync 1
foff 1024 loff 1024
eventmask 0x217effc event change time October 8, 2009
12:25:26 PM PDT PDT (nsecs 864434000)
End of Solution
5 How do you know that there have been no changes in the file system yet?
Solution
The superblock (foff) and the end of the FCL file (loff) are the same
number.
End of Solution
6 Add some files to /fcl_test. Then remove one of the files you just added
and rename one of the others.
Solution
cd /fcl_test
touch a b c
rm -f b
mv a d
End of Solution

/fcl_test command.
Solution
magic a506fcf5 version 4
time 1255029926 866253 (October 8, 2009 12:25:26 PM
PDT PDT)
B171
state ON sync 1
foff 1024 loff 1312
eventmask 0x217effc event change time October 8, 2009
12:25:26 PM PDT PDT (nsecs 864434000)
End of Solution
8 How do you know that changes have been made to the file system?
Solution
The superblock (foff) and the end of the FCL file (loff) are different
numbers.
End of Solution
9 Print the contents of the FCL using the fcladm print 1024
/fcl_test command.
Solution
The fields displayed in the output are Change Type, Inode Number,
Inode Generation, and Timestamp.
The Unlink and Rename types list the name of the file on the following line,
preceded by the parents inode number.
End of Solution
10 Use the vxlsino command to determine which files are identified by the
inode numbers that are listed in the Create type that do not have an Unlink
type as well?
Solution
vxlsino inode_number /fcl_test
End of Solution
11 Unmount the fcl_test file system and remove appvol.
Solution
cd /

umount /fcl_test
End of Solution
12 The next lab section is an optional lab on analyzing and defragmenting a

fragmented file system. If you are not planning to carry out this optional
exercise, unmount /test file system and destroy the testdg disk group;
otherwise, skip this step.
Solution
umount /test
vxdg destroy testdg
End of Solution

B173
Exercise 7: Optional lab: Defragmenting a Veritas File System
sym1
This section uses the /test file system to analyze the impact of fragmentation on
the performance of a variety of I/O types on files using small and large extent
sizes.
1 Recreate the fragmented /test file system using the following steps:
a Unmount the /test file system.
Solution
umount /test
End of Solution
b Change into the /student/labs/sf/sf60 directory and run the

extentfrag_vxfs.pl script to restore a fragmented file system to the
volume.
Solution
cd /student/labs/sf/sf60
./extentfrag_vxfs.pl
End of Solution
c Mount the file system to /test. Note that you may need to perform a file
Solution
fsck -t vxfs /dev/vx/rdsk/testdg/testvol
mount -t vxfs /dev/vx/dsk/testdg/testvol /test
End of Solution

2 Run a series of performance tests for a variety of I/O types using the vxbench
utility to compare the performance of the files with the 8K extent size
(/test/test48) and the 8000K extent size (/test/test58) by
performing the following steps.
B
Complete the table when doing the performance tests.
Test type Time (seconds) Throughput (KB/second)

Before defrag After defrag Before defrag After defrag
Sequential 2.709 .526 2953.22 15202.10
reads, 8K
extent
Sequential .547 .549 14634.57 14576.20
reads,
8000K
extent
Random 8.268 6.267 967.54 1276.53
reads, 8K
extent
Random 6.541 6.468 1223.02 1236.91
reads,
8000K
extent
Note: Results can vary depending on the nature of the data and the model of
array used. No performance guarantees are implied by this lab.
You must unmount and remount the file system /test before each step to
clear and initialize the buffer cache.
a Ensure that the directory where the vxbench utility is located is included
Solution
echo $PATH
PATH=$PATH:/opt/VRTSspt/FS/VxBench (if necessary)
export PATH
End of Solution

B175
b Perform a sequential read I/O test on the 8K extent size using the
Solution
To test the 8K extent size:
vxbench_rhel5_x86_64 -w read -i \
iosize=8k,iocount=1000 /test/test48
End of Solution
c Perform a sequential read I/O test on the 8000K extent size using the
Solution
vxbench_rhel5_x86_64 -w read -i \
iosize=8k,iocount=1000 /test/test58
End of Solution
d Perform a random read I/O test on the 8K extent size using the vxbench
command. Use an I/O size of 8k and a count of 1000 I/Os.
Solution
vxbench_rhel5_x86_64 -w rand_read -i \
iosize=8k,iocount=1000,maxfilesize=8000 \
/test/test48
End of Solution

e Perform a random read I/O test on the 8000K extent size using the
Solution
B
vxbench_rhel5_x86_64 -w rand_read -i \
iosize=8k,iocount=1000,maxfilesize=8000 \
/test/test58
End of Solution
3 Defragment the /test file system. The defragmentation process takes some
time.
Solution
/opt/VRTS/bin/fsadm -e -E -d -D -s /test
End of Solution
4 Repeat the vxbench performance tests and complete the table with these
performance results.
5 Compare the results of the defragmented file system with the fragmented file
system.
6 When finished comparing the results in the previous step, unmount the
/test file system and destroy the testdg disk group.
Solution
umount /test
vxdg destroy testdg
End of Solution
End of lab

B177

Appendix C
Using the VEA

483

484C2 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
Creating a disk group and a volume and adding a file system
C

485 Appendix C Using the VEA Copyright 2012 Symantec Corporation. All rights reserved.
C3

486 C4 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
C

C5
Displaying disk, disk group and volume information

C

C7

C

C9
Removing volumes, disks, and disk groups

Performing basic administration tasks on volumes and file
systems
C

C11

494C12 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
C

C13

C

C15

Index
Files and Directories CDS disk groups
converting disk groups 6-25
/dev/vx/dsk 4-8 CDS disk layout 1-9
/dev/vx/rdsk 4-8 chfs 4-14
/etc/default/fs 7-9 CLI 2-24
/etc/default/vxassist 5-9 cluster management 4-4
/etc/default/vxsf 7-28 column 5-4
/etc/filesystems 4-13, 4-14 command line interface 2-24, 2-25
/etc/fs/vxfs 7-8 CommandCentral Storage 3-5
/etc/fstab 4-14 concatenated volume 1-14, 5-3
/etc/system 2-16 creating 5-9
/etc/vfs 7-9 concatenation 1-14
/etc/vfstab 4-14 advantages 5-7
/etc/vx/elm 2-7 disadvantages 5-7
/opt/VRTS/bin 7-8 controller 1-4
/opt/VRTS/install/logs 2-14 creating a layered volume 5-12
/opt/VRTS/man 2-25 creating a volume 4-11
/opt/VRTSvxfs/sbin 7-8 crfs 4-13
/sbin 7-8 cron 7-23
/sbin/fs 7-8 cross-platform data sharing 1-9
converting disk groups 6-25
/usr/lib/fs/vxfs 7-8
requirements for CDS disk groups 6-24
A D
address-length pair 7-6
data change object 4-22, 7-34
aixdisk 1-10
data redundancy 1-14
array 1-6
DataInsight for Storage 3-5
authentication broker 3-7
defaultdg 4-8
defragmentation
B scheduling 7-23
defragmenting a file system 7-21
block device file 4-12
deporting a disk group
block-based allocation 7-6 and renaming 6-18
bootdg 4-8, 4-29 to new host 6-18
destroying a disk group 4-29
C device path 4-17
devicetag 4-17
CDS 1-9 directory fragmentation 7-19
CDS disk 1-10 dirty region logging 6-7

Index-1
disaster recovery Intro-8 Solaris 1-4
Disaster Recovery Advisor 3-5 disk spanning 1-13
disk disk status
configuring for VxVM 4-5 online 4-15
displaying summary information 4-18 online invalid 4-16
naming 1-4 disks
removing 4-26 adding to a disk group 4-9
removing from a disk group 4-26 displaying detailed information 4-17
shredding 4-27, 4-28 evacuating data 4-25
uninitializing 4-27 renaming 6-21
viewing in CLI 4-15 uninitialized 4-5
viewing information about 4-15
dynamic LUN
disk access name 4-6 resizing 6-16
disk access record 1-12, 4-6 dynamic multipathing 4-4
disk array 1-6
disk group
clearing host locks 6-19 E
creating 4-9 encapsulation 4-5
creating in vxdiskadm 4-10
definition 1-11 enclosure-based naming
deporting 6-18, 6-20 benefits 4-4
destroying 4-29 error status 4-16
destroying in CLI 4-29 evacuating a disk 4-25
displaying deported 4-19 exclusive OR 5-6
displaying free space in 4-19
EXT2 7-8
displaying properties for 4-19
forcing an import 6-19 EXT3 7-8
high availability 4-7 Extended File System 7-8
importing 6-20 extent 7-6
importing and renaming 6-19
extent fragmentation 7-19
importing as temporary in CLI 6-20
purpose 1-11, 4-7 extent-based allocation 7-6
reserved names 4-8
disk group configuration 1-11 F
disk group ID 4-18
disk group versions 6-23 FCL 7-17
disk ID 4-18 file change log 7-17

compared to intent log 7-17
disk initialization 4-5
file system
disk layout 1-9 adding to a volume 4-12
changing 4-5 adding to a volume in CLI 4-12
disk media name 1-11, 4-6, 4-9 consistency checking 7-16
default 1-11 defragmenting 7-21
disk name 4-17 file change log 7-17
disk naming 4-9 fragmentation 7-19
AIX 1-5 fragmentation reports 7-20
HP-UX 1-4 fragmentation types 7-19
Linux 1-5 intent log 7-15

500 Index-2 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
mounting at boot 4-14 verifying on HP-UX 2-15
resizing 6-15 verifying on Linux 2-15
resizing methods 6-13 verifying on Solaris 2-14
file system free space verifying package installation 2-14
identifying 7-11 installp 2-12
file system type 7-11 installsf 2-12
fragmentation 7-19 installvm 2-12
directory 7-19 Intelligent Storage Provisioning 4-22
extent 7-19
intent logging 7-15
free space 7-22
interfaces 2-24
fragmentation index 7-20
command line interface 2-24
free space pool 4-6 vxdiskadm 2-24
fsadm 6-15, 7-19, 7-20 iosize 7-24
fsck 7-15, 7-16
J
G
JFS 7-8
group name 4-18 JFS2 7-8
Journaled File System 7-8
H journaling 7-15
HFS 7-8
Hierarchical File System 7-8 K
high availability 6-17 kernel issues
host locks and VxFS 2-16
clearing 6-19 keyless licensing 2-6, 2-18
hostid 4-17
hpdisk 1-10
L
layered volume 1-14, 5-12
I advantages 5-13
importing a disk group creating 5-12
and renaming 6-19 creating in CLI 5-17
forcing 6-19 disadvantages 5-13
viewing in CLI 5-18

inode 7-6
layered volume layouts 5-16
installation menu 2-11
licensing 2-6
installer 2-11, 2-12
generating a license key 2-7
installfs 2-12 Web site 2-7
Installing SF listing installed packages 2-15
Web installer 2-17
load balancing 5-7
installing SF 2-11
location code 1-5
assessment service 2-8
installation logs 2-14 logging 6-7
verifying on AIX 2-15 for mirrored volumes 6-7

501 Veritas Storage Foundation 6.0 for UNIX: Install and Configure
Index-3
logical unit number 1-4 nostripe 5-9
logtype 5-11
lsfs 4-14
O
lslpp 2-15
LUN 1-4 Object Data Manager 1-5
and resizing VxVM structures 6-16 online invalid status 4-16
online status 4-15
operating system versions 2-3
M
man 2-25
P
manual pages 2-25
maxfilesize 7-24 packages
mirror listing 2-15
adding in CLI 6-6 parity 1-14, 5-6
removing 6-3 partition 1-4
mirror-concat 5-16 physical disk
mirrored volume 1-14, 5-5 naming 1-4
creating 5-11 pkgadd 2-12
mirroring 1-14 pkginfo 2-15
advantages 5-8 plex 1-12, 5-5
disadvantages 5-8 definition 1-12
enhanced 5-12 naming 1-12
mirrors plex name
adding 5-10 default 1-12
mirror-stripe layout 5-14 private region 1-9, 4-5
mkdir 4-12 private region size 1-9
mkfs 4-12 AIX 1-9
mkfs options 7-10 HP-UX 1-9
mmap 7-25 Linux 1-9
Solaris 1-9
mount 4-12
public region 1-9, 1-11
moving a disk
vxdiskadm 6-13, 6-16
multipathed disk array 1-6 R
RAID 1-13
N RAID array
benefits with VxVM Intro-8
naming disks
defaults 4-9 RAID levels 1-13
ncol 5-9 RAID-5 column 5-6
newfs 4-12 RAID-5 volume 1-14, 5-6
nlog 5-11 random read 7-25
nmirror 5-10 random write 7-25
nodg 4-8 raw device file 4-12
read policy 6-10

changing in CLI 6-11 striping 1-14
preferred plex 6-10 advantages 5-7
round robin 6-10 disadvantages 5-8
selected plex 6-10 subdisk 1-12
siteread 6-10 definition 1-12
redundancy 1-14 subdisk name
removing a disk 4-26 default 1-12
removing a volume 4-24 subvolume 5-12
renaming a disk 6-21 support for SF 2-19
renaming a disk group 6-22 swinstall 2-12
replicated volume group 4-22 swlist 2-15
resilience 1-14 Symantec Operations Readiness Tools 2-8
resilient volume 1-14 Patch Services 2-22
resizing a dynamic LUN 6-16
resizing a file system 6-15 T
resizing a volume 6-12
with vxassist 6-15 target 1-4
with vxresize 6-14 technical support for SF 2-19
resizing a volume and file system 6-13 thin provisioning 7-26
resizing a volume with a file system 6-12 displaying thin LUN information 7-27
fssmartmovethreshold 7-29
rlink 4-22
migration to 7-30
rpm 2-12, 2-15 overview 7-26
parameters 7-29
SmartMove 7-28
S thin reclamation 7-31, 7-32, 7-33
SAN management 4-4 usefssmartmove 7-28
selected plex read policy 6-10 true mirror 5-5
sequential read 7-25 true mirroring 1-14
sequential write 7-25 type 4-17
slice 1-4
sliced disk 1-10 U
SmartMove 7-28
UFS 7-8
snap object 4-22
uninitialized disks 4-5

storage
UNIX File System 7-8
allocating for volumes 5-20
upgrading a disk group version 6-23
storage attributes
specifying for volumes 5-20 user interfaces 2-24
storage cache 4-22
stripe unit 5-4, 5-6 V
striped volume 1-14, 5-4
VEA 2-24
stripe-mirror 5-16
installing the server and client 2-28
stripe-mirror layout 5-15 multiple views of objects 2-27
stripeunit 5-10 Preferences window 2-27

503 Veritas Storage Foundation 6.0 for UNIX: Install and Configure Copyright 2012 Symantec Corporation. All rights reserved.
Index-5
remote administration 2-27 volume read policy 6-10
security 2-27 changing in CLI 6-11
setting preferences 2-27 volumes
starting 2-28 allocating storage for 5-20
Veritas Operations Manager 2-23 VOM 3-5
Veritas Volume Replicator 4-22 add-ons 3-16, 3-17
versioning architecture 3-7, 3-8
and disk groups 6-23 benefits 3-6
browser requirements 3-12
virtual storage objects 1-8
connecting to MS 3-15
vol_subdisk_num 1-12 installing management server 3-13, 3-14
volboot 4-8 managed host 3-19, 3-20
volume 1-8, 4-6 platform support 3-11
accessing 1-8 Storage Provisioning add-on 5-21
adding a file system in CLI 4-12 storage templates 5-22, 5-23
adding a mirror 6-3 support for virtual environments 3-9
creating 4-11 VOM Advanced 3-5, 3-10
creating a layered volume 5-12 vrtsadm 2-28
creating in CLI 4-11
VRTSvxfs 2-16
creating layered in CLI 5-17
creating mirrored and logged 5-11 vxassist 4-11, 6-13, 6-15
definition 1-8, 1-12 vxassist growby 6-15
disk requirements 4-11 vxassist growto 6-15
estimating size 5-10
vxassist shrinkby 6-15
expanding the size 6-12
layered layouts 5-16 vxassist shrinkto 6-15
reducing the size 6-12 vxbench
removing 4-24 options 7-25
removing a mirror 6-3 vxdclid 3-13
resizing 6-12 vxdctl enable 4-6
resizing methods 6-13
resizing with vxassist 6-15 vxdefault 7-29
resizing with vxresize 6-14 vxdg destroy 4-29
starting manually 6-20 vxdisk list 4-10, 4-15, 4-17, 4-18
viewing layered in CLI 5-18 vxdisk resize 6-16
volume layout 1-13 vxdiskadm 2-24, 2-26, 4-5
concatenated 1-14 creating a disk group 4-10
displaying in CLI 4-21
vxdiskunsetup 4-27
layered 1-14
mirrored 1-14 VxFS 7-8
RAID-5 1-14 allocation 7-6
selecting 5-3 command locations 7-8
striped 1-14 command syntax 7-9
defragmenting 7-21
Volume Manager control 1-9
features 7-3, 7-4
Volume Manager disk 1-11 file change log 7-17
naming 1-11 file system switchout mechanisms 7-9
Volume Manager Support Operations 2-24, 2- file system type 7-11
26 fragmentation types 7-19
identifying free space 7-11

intent log 7-15
maintaining consistency 7-16
resizing 6-15
using by default 7-9
vxinfo 4-23
vxinstall 2-12
vxlist 4-23
vxmake 5-13
vxprint 4-21, 5-18
vxresize 6-13
VxVM
user interfaces 2-24
VxVM and RAID arrays Intro-8
VxVM configuration daemon 4-6
vxvol rdpol prefer 6-11
vxvol rdpol round 6-11
vxvol rdpol select 6-11
vxvol stopall 6-20
X
XOR 1-14, 5-6
xprtld 3-13
xprtlwid 2-17

505 Veritas Storage Foundation 6.0 for UNIX: Install and Configure Copyright 2012 Symantec Corporation. All rights reserved.
Index-7


100 002687 A

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

100 002687 A

Încărcat de

Drepturi de autor:

Formate disponibile

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Lesson 1: Virtual Objects

Lesson 2: Installing Storage Foundation and Accessing SF Interfaces

Lesson 3: Getting Started with Veritas Operations Manager (VOM)

Lesson 4: Creating a Volume and File System

Lesson 5: Working with Volumes with Different Layouts

Allocating storage for volumes ................................................................... 5-20

Lesson 6: Making Configuration Changes

CONFIDENTIAL - NOT FOR DISTRIBUTION

Exercise 5: Optional lab: Removing volumes, disks, and disk

CONFIDENTIAL - NOT FOR DISTRIBUTION

Appendix B: Lab Solutions

CONFIDENTIAL - NOT FOR DISTRIBUTION

Appendix C: Using the VEA

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

administration of heterogeneous environments

CONFIDENTIAL - NOT FOR DISTRIBUTION

Need for applications to access data contained in multiple storage devices

CONFIDENTIAL - NOT FOR DISTRIBUTION

Host-based storage virtualization

Network-based storage virtualization

Network-based storage virtualization refers to disks from multiple arrays and

CONFIDENTIAL - NOT FOR DISTRIBUTION

What is Veritas Volume Manager?

uninterrupted, consistent access to mission-critical data. VxVM enables you to

CONFIDENTIAL - NOT FOR DISTRIBUTION

What is Veritas Dynamic Multi-Pathing?

CONFIDENTIAL - NOT FOR DISTRIBUTION

intuitive, easy-to-use Web console that is implemented using Veritas

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Configure and manage disks and disk groups.

CONFIDENTIAL - NOT FOR DISTRIBUTION

System to optimize storage utilization.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Appendix A: Lab Exercises

Appendix B: Lab Solutions

Appendix C: Using the VEA

Typographic conventions used in this course

CONFIDENTIAL - NOT FOR DISTRIBUTION

Convention Element Examples

Typographic conventions in graphical user interface descriptions

Convention Element Examples

Remove the checkmark

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Operating system storage devices and virtual data storage

Use the following OS-specific commands to list storage devices on individual

Operating system Command to use

CONFIDENTIAL - NOT FOR DISTRIBUTION

system, with a target ID of 0, physical disk number 0, and partition number 1 on

CONFIDENTIAL - NOT FOR DISTRIBUTION

Example array structure

CONFIDENTIAL - NOT FOR DISTRIBUTION

How do you access a volume?

CONFIDENTIAL - NOT FOR DISTRIBUTION

Volume Manager-controlled disks

Operating System Default Block/Sector Size Default Private Region Size