Please enter search query.
Search <book_title>...
Storage Foundation 8.0.2 Administrator's Guide - AIX
Last Published:
2023-06-05
Product(s):
InfoScale & Storage Foundation (8.0.2)
Platform: AIX
- Section I. Introducing Storage Foundation
- Overview of Storage Foundation
- How Dynamic Multi-Pathing works
- How Veritas Volume Manager works
- How Veritas Volume Manager works with the operating system
- How Veritas Volume Manager handles storage management
- Volume layouts in Veritas Volume Manager
- Online relayout
- Volume resynchronization
- Hot-relocation
- Dirty region logging
- Volume snapshots
- FastResync
- Volume sets
- How VxVM handles hardware clones or snapshots
- How Veritas File System works
- Section II. Provisioning storage
- Provisioning new storage
- Advanced allocation methods for configuring storage
- Customizing allocation behavior
- Setting default values for vxassist
- Using rules to make volume allocation more efficient
- Understanding persistent attributes
- Customizing disk classes for allocation
- Specifying allocation constraints for vxassist operations with the use clause and the require clause
- Management of the use and require type of persistent attributes
- Creating volumes of a specific layout
- Creating a volume on specific disks
- Creating volumes on specific media types
- Specifying ordered allocation of storage to volumes
- Site-based allocation
- Changing the read policy for mirrored volumes
- Customizing allocation behavior
- Creating and mounting VxFS file systems
- Creating a VxFS file system
- Converting a file system to VxFS
- Mounting a VxFS file system
- log mount option
- delaylog mount option
- tmplog mount option
- logiosize mount option
- nodatainlog mount option
- blkclear mount option
- mincache mount option
- convosync mount option
- ioerror mount option
- largefiles and nolargefiles mount options
- cio mount option
- mntlock mount option
- ckptautomnt mount option
- Combining mount command options
- Unmounting a file system
- Resizing a file system
- Displaying information on mounted file systems
- Monitoring free space
- Extent attributes
- Section III. Administering multi-pathing with DMP
- Administering Dynamic Multi-Pathing
- Discovering and configuring newly added disk devices
- Partial device discovery
- About discovering disks and dynamically adding disk arrays
- About third-party driver coexistence
- How to administer the Device Discovery Layer
- Listing all the devices including iSCSI
- Listing all the Host Bus Adapters including iSCSI
- Listing the ports configured on a Host Bus Adapter
- Listing the targets configured from a Host Bus Adapter or a port
- Listing the devices configured from a Host Bus Adapter and target
- Getting or setting the iSCSI operational parameters
- Listing all supported disk arrays
- Displaying details about an Array Support Library
- Excluding support for a disk array library
- Re-including support for an excluded disk array library
- Listing excluded disk arrays
- Listing disks claimed in the DISKS category
- Adding unsupported disk arrays to the DISKS category
- Removing disks from the DISKS category
- Foreign devices
- Making devices invisible to VxVM
- Making devices visible to VxVM
- About enabling and disabling I/O for controllers and storage processors
- About displaying DMP database information
- Displaying the paths to a disk
- Administering DMP using the vxdmpadm utility
- Retrieving information about a DMP node
- Displaying consolidated information about the DMP nodes
- Displaying the members of a LUN group
- Displaying paths controlled by a DMP node, controller, enclosure, or array port
- Displaying information about controllers
- Displaying information about enclosures
- Displaying information about array ports
- Displaying information about devices controlled by third-party drivers
- Displaying extended device attributes
- Suppressing or including devices from VxVM control
- Gathering and displaying I/O statistics
- Setting the attributes of the paths to an enclosure
- Displaying the redundancy level of a device or enclosure
- Specifying the minimum number of active paths
- Displaying the I/O policy
- Specifying the I/O policy
- Disabling I/O for paths, controllers, array ports, or DMP nodes
- Enabling I/O for paths, controllers, array ports, or DMP nodes
- Renaming an enclosure
- Configuring the response to I/O failures
- Configuring the I/O throttling mechanism
- Configuring Low Impact Path Probing (LIPP)
- Configuring Subpaths Failover Groups (SFG)
- Displaying recovery option values
- Configuring DMP path restoration policies
- Stopping the DMP path restoration thread
- Displaying the status of the DMP path restoration thread
- Configuring Array Policy Modules
- Discovering and configuring newly added disk devices
- Dynamic Reconfiguration of devices
- About online dynamic reconfiguration
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Overview of manually reconfiguring a LUN
- Manually removing LUNs dynamically from an existing target ID
- Manually adding new LUNs dynamically to a new target ID
- About detecting target ID reuse if the operating system device tree is not cleaned up
- Scanning an operating system device tree after adding or removing LUNs
- Manually cleaning up the operating system device tree after removing LUNs
- Manually replacing a host bus adapter online
- Changing the characteristics of a LUN from the array side
- Upgrading the array controller firmware online
- Managing devices
- Displaying disk information
- Changing the disk device naming scheme
- About disk installation and formatting
- Adding and removing disks
- Renaming a disk
- Event monitoring
- Administering Dynamic Multi-Pathing
- Section IV. Administering Storage Foundation
- Administering sites and remote mirrors
- About sites and remote mirrors
- Making an existing disk group site consistent
- Configuring a new disk group as a Remote Mirror configuration
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Examples of storage allocation by specifying sites
- Displaying site information
- Failure and recovery scenarios
- Administering sites and remote mirrors
- Section V. Optimizing I/O performance
- Section VI. Using Point-in-time copies
- Understanding point-in-time copy methods
- About point-in-time copies
- When to use point-in-time copies
- About Storage Foundation point-in-time copy technologies
- Volume-level snapshots
- Storage Checkpoints
- About FileSnaps
- About snapshot file systems
- Administering volume snapshots
- About volume snapshots
- Traditional third-mirror break-off snapshots
- Full-sized instant snapshots
- Creating instant snapshots
- Adding an instant snap DCO and DCO volume
- Creating and managing space-optimized instant snapshots
- Creating and managing full-sized instant snapshots
- Creating and managing third-mirror break-off snapshots
- Creating and managing linked break-off snapshot volumes
- Creating multiple instant snapshots
- Creating instant snapshots of volume sets
- Adding snapshot mirrors to a volume
- Removing a snapshot mirror
- Removing a linked break-off snapshot volume
- Adding a snapshot to a cascaded snapshot hierarchy
- Refreshing an instant space-optimized snapshot
- Reattaching an instant full-sized or plex break-off snapshot
- Reattaching a linked break-off snapshot volume
- Restoring a volume from an instant space-optimized snapshot
- Dissociating an instant snapshot
- Removing an instant snapshot
- Splitting an instant snapshot hierarchy
- Displaying instant snapshot information
- Controlling instant snapshot synchronization
- Listing the snapshots created on a cache
- Tuning the autogrow attributes of a cache
- Monitoring and displaying cache usage
- Growing and shrinking a cache
- Removing a cache
- Creating instant snapshots
- Linked break-off snapshots
- Cascaded snapshots
- Creating multiple snapshots
- Restoring the original volume from a snapshot
- Adding a version 0 DCO and DCO volume
- Administering Storage Checkpoints
- About Storage Checkpoints
- Storage Checkpoint administration
- Storage Checkpoint space management considerations
- Restoring from a Storage Checkpoint
- Storage Checkpoint quotas
- Administering FileSnaps
- Administering snapshot file systems
- Understanding point-in-time copy methods
- Section VII. Optimizing storage with Storage Foundation
- Understanding storage optimization solutions in Storage Foundation
- Migrating data from thick storage to thin storage
- Maintaining Thin Storage with Thin Reclamation
- Reclamation of storage on thin reclamation arrays
- Identifying thin and thin reclamation LUNs
- Displaying VxFS file system usage on thin reclamation LUNs
- Reclaiming space on a file system
- Reclaiming space on a disk, disk group, or enclosure
- About the reclamation log file
- Monitoring Thin Reclamation using the vxtask command
- Configuring automatic reclamation
- Veritas InfoScale 4k sector device support solution
- Section VIII. Maximizing storage utilization
- Understanding storage tiering with SmartTier
- Creating and administering volume sets
- Multi-volume file systems
- About multi-volume file systems
- About volume types
- Features implemented using multi-volume file system (MVFS) support
- Creating multi-volume file systems
- Converting a single volume file system to a multi-volume file system
- Adding a volume to and removing a volume from a multi-volume file system
- Volume encapsulation
- Reporting file extents
- Load balancing
- Converting a multi-volume file system to a single volume file system
- Administering SmartTier
- About SmartTier
- Supported SmartTier document type definitions
- Placement classes
- Administering placement policies
- File placement policy grammar
- File placement policy rules
- Calculating I/O temperature and access temperature
- Multiple criteria in file placement policy rule statements
- Multiple file selection criteria in SELECT statement clauses
- Multiple placement classes in <ON> clauses of CREATE statements and in <TO> clauses of RELOCATE statements
- Multiple placement classes in <FROM> clauses of RELOCATE and DELETE statements
- Multiple conditions in <WHEN> clauses of RELOCATE and DELETE statements
- File placement policy rule and statement ordering
- File placement policies and extending files
- Using SmartTier with solid state disks
- Sub-file relocation
- Administering hot-relocation
- About hot-relocation
- How hot-relocation works
- Configuring a system for hot-relocation
- Displaying spare disk information
- Marking a disk as a hot-relocation spare
- Removing a disk from use as a hot-relocation spare
- Excluding a disk from hot-relocation use
- Making a disk available for hot-relocation use
- Configuring hot-relocation to use only spare disks
- Moving relocated subdisks
- Modifying the behavior of hot-relocation
- Deduplicating data
- Compressing files
- About compressing files
- Compressing files with the vxcompress command
- Interaction of compressed files and other commands
- Interaction of compressed files and other features
- Interaction of compressed files and applications
- Use cases for compressing files
- Section IX. Administering and protecting storage
- Administering VxVM volumes as paging devices
- Managing volumes and disk groups
- Rules for determining the default disk group
- Moving volumes or disks
- Monitoring and controlling tasks
- Using vxnotify to monitor configuration changes
- Performing online relayout
- Adding a mirror to a volume
- Configuring SmartMove
- Removing a mirror
- Setting tags on volumes
- Managing disk groups
- Disk group versions
- Displaying disk group information
- Creating a disk group
- Removing a disk from a disk group
- Deporting a disk group
- Importing a disk group
- Handling of minor number conflicts
- Moving disk groups between systems
- Importing a disk group containing hardware cloned disks
- Setting up configuration database copies (metadata) for a disk group
- Renaming a disk group
- Handling conflicting configuration copies
- Disabling a disk group
- Destroying a disk group
- Backing up and restoring disk group configuration data
- Working with existing ISP disk groups
- Managing plexes and subdisks
- Decommissioning storage
- Using DMP with a SAN boot disk
- Configuring DMP for SAN booting
- Administering the root volume group (rootvg) under DMP control
- Running the bosboot command when LVM rootvg is enabled for DMP
- Extending an LVM rootvg that is enabled for DMP
- Reducing the native rootvg that is enabled for DMP
- Mirroring the root volume group
- Removing the mirror for the root volume group (rootvg)
- Cloning a LVM rootvg that is enabled for DMP
- Cleaning up the alternate disk volume group when LVM rootvg is enabled for DMP
- Using mksysb when the root volume group is under DMP control
- Upgrading Storage Foundation and AIX on a DMP-enabled rootvg
- Quotas
- About Veritas File System quota limits
- About quota files on Veritas File System
- About Veritas File System quota commands
- About quota checking with Veritas File System
- Using Veritas File System quotas
- Turning on Veritas File System quotas
- Turning on Veritas File System quotas at mount time
- Editing Veritas File System quotas
- Modifying Veritas File System quota time limits
- Viewing Veritas File System disk quotas and usage
- Displaying blocks owned by users or groups
- Turning off Veritas File System quotas
- Support for 64-bit Quotas
- File Change Log
- Section X. Reference
- Appendix A. Reverse path name lookup
- Appendix B. Tunable parameters
- About tuning Storage Foundation
- Tuning the VxFS file system
- DMP tunable parameters
- Methods to change Dynamic Multi-Pathing tunable parameters
- DMP driver tunables
- Tunable parameters for VxVM
- Methods to change Veritas Volume Manager tunable parameters
- Appendix C. Command reference
- Appendix D. Executive Order logging
Examples of use and require constraints
The following examples show use and require constraints for storage allocation.
Example 1 - require constraint
This example shows the require constraint in a disk group that has disks from two arrays: emc_clariion0 and ams_wms0. Both arrays are connected through the same HBA hostportid (06-08-02), but the arrays have different arraytype (A/A and A/A-A respectively).
The following output shows the disk group information:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - -
To allocate both the data and the log on the disks that are attached to the particular HBA and that have the array type A/A:
# vxassist -g testdg make v1 1G logtype=dco dcoversion=20 \ require=hostportid:06-08-02,arraytype:A/A
The following output shows the results of the above command. The command allocated disk space for the data and the log on emc_clariion0 array disks, which satisfy all the storage specifications in the require constraint:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - - v v1 fsgen ENABLED 2097152 - ACTIVE - - pl v1-01 v1 ENABLED 2097152 - ACTIVE - - sd emc_clariion0_0-01 v1-01 ENABLED 2097152 0 - - - dc v1_dco v1 - - - - - - v v1_dcl gen ENABLED 67840 - ACTIVE - - pl v1_dcl-01 v1_dcl ENABLED 67840 - ACTIVE - - sd emc_clariion0_0-02 v1_dcl-01 ENABLED 67840 0 - - -
Example 2 - use constraint
This example shows the use constraint in a disk group that has disks from three arrays: ams_wms0, emc_clariion0, and hitachi_vsp0.
The following output shows the disk group information:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - -
To allocate both the data and the log on the disks that belong to the array ams_wms0 or the array emc_clariion0:
# vxassist -g testdg make v1 3G logtype=dco dcoversion=20 \ use=array:ams_wms0,array:emc_clariion0
The following output shows the results of the above command. The command allocated disk space for the data and the log on disks that satisfy the arrays specified in the use constraint.
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - - v v1 fsgen ENABLED 6291456 - ACTIVE - - pl v1-01 v1 ENABLED 6291456 - ACTIVE - - sd ams_wms0_359-01 v1-01 ENABLED 2027264 0 - - - sd ams_wms0_360-01 v1-01 ENABLED 143872 2027264 - - - sd emc_clariion0_0-01 v1-01 ENABLED 4120320 2171136 - - - dc v1_dco v1 - - - - - - v v1_dcl gen ENABLED 67840 - ACTIVE - - pl v1_dcl-01 v1_dcl ENABLED 67840 - ACTIVE - - sd ams_wms0_360-02 v1_dcl-01 ENABLED 67840 0 - - -
Example 3: datause and logrequire combination
This example shows the combination of a datause constraint and a logrequire constraint. The disk group has disks from three arrays: ams_wms0, emc_clariion0, and hitachi_vsp0, which have different array types.
The following output shows the disk group information:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - -
To allocate data on disks from ams_wms0 or emc_clariion0 array, and to allocate log on disks from arraytype A/A-A:
# vxassist -g testdg make v1 1G logtype=dco dcoversion=20 \ datause=array:ams_wms0,array:emc_clariion0 logrequire=arraytype:A/A-A
The following output shows the results of the above command. The command allocated disk space for the data and the log independently. The data space is allocated on emc_clariion0 disks that satisfy the datause constraint. The log space is allocated on ams_wms0 disks that are A/A-A arraytype and that satisfy the logrequire constraint:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - - v v1 fsgen ENABLED 2097152 - ACTIVE - - pl v1-01 v1 ENABLED 2097152 - ACTIVE - - sd emc_clariion0_0-01 v1-01 ENABLED 2097152 0 - - - dc v1_dco v1 - - - - - - v v1_dcl gen ENABLED 67840 - ACTIVE - - pl v1_dcl-01 v1_dcl ENABLED 67840 - ACTIVE - - sd ams_wms0_359-01 v1_dcl-01 ENABLED 67840 0 - - -
Example 4 - use and require combination
This example shows the combination of a use constraint and a require constraint. The disk group has disks from three arrays: ams_wms0, emc_clariion0, and hitachi_vsp0. Only the disks from ams_wms0 array are multi-pathed.
The following output shows the disk group information:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - -
To allocate data and log space on disks from emc_clariion0 or ams_wms0 array, and disks that are multi-pathed:
# vxassist -g testdg make v1 1G logtype=dco dcoversion=20 \ use=array:emc_clariion0,array:ams_wms0 require=multipathed:yes
The following output shows the results of the allocation. The data and log space is on ams_wms0 disks, which satisfy the use as well as the require constraints:
# vxprint -g testdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg testdg testdg - - - - - - dm ams_wms0_359 ams_wms0_359 - 2027264 - - - - dm ams_wms0_360 ams_wms0_360 - 2027264 - - - - dm ams_wms0_361 ams_wms0_361 - 2027264 - - - - dm ams_wms0_362 ams_wms0_362 - 2027264 - - - - dm emc_clariion0_0 emc_clariion0_0 - 4120320 - - - - dm emc_clariion0_1 emc_clariion0_1 - 4120320 - - - - dm emc_clariion0_2 emc_clariion0_2 - 4120320 - - - - dm emc_clariion0_3 emc_clariion0_3 - 4120320 - - - - dm hitachi_vsp0_3 hitachi_vsp0_3 - 4120320 - - - - v v1 fsgen ENABLED 2097152 - ACTIVE - - pl v1-01 v1 ENABLED 2097152 - ACTIVE - - sd ams_wms0_359-01 v1-01 ENABLED 2027264 0 - - - sd ams_wms0_360-01 v1-01 ENABLED 69888 2027264 - - - dc v1_dco v1 - - - - - - v v1_dcl gen ENABLED 67840 - ACTIVE - - pl v1_dcl-01 v1_dcl ENABLED 67840 - ACTIVE - - sd ams_wms0_360-02 v1_dcl-01 ENABLED 67840 0 - - -