InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Administrator's Guide - AIX
- Section I. Introducing Storage Foundation Cluster File System High Availability
- Overview of Storage Foundation Cluster File System High Availability
- About Veritas File System
- How Dynamic Multi-Pathing works
- How Volume Manager works
- How Volume Manager works with the operating system
- How Volume Manager handles storage management
- Volume layouts in Veritas Volume Manager
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- How VxVM handles hardware clones or snapshots
- How Veritas File System works
- How Storage Foundation Cluster File System High Availability works
- About Storage Foundation Cluster File System High Availability architecture
- About Veritas File System features supported in cluster file systems
- About single network link and reliability
- About I/O fencing
- About preventing data corruption with I/O fencing
- About I/O fencing components
- About server-based I/O fencing
- About secure communication between the SFCFSHA cluster and CP server
- How Cluster Volume Manager works
- Overview of clustering
- Cluster Volume Manager (CVM) tolerance to storage connectivity failures
- Storage disconnectivity and CVM disk detach policies
- CVM initialization and configuration
- Dirty region logging in cluster environments
- Multiple host failover configurations
- About Flexible Storage Sharing
- Overview of Storage Foundation Cluster File System High Availability
- Section II. Provisioning storage
- Provisioning new storage
- Advanced allocation methods for configuring storage
- Customizing allocation behavior
- 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
- Creating volumes of a specific layout
- Customizing allocation behavior
- Creating and mounting VxFS file systems
- Creating a VxFS file system
- Mounting a VxFS file system
- tmplog mount option
- ioerror mount option
- largefiles and nolargefiles mount options
- Resizing a file system
- Monitoring free space
- Extent attributes
- Section III. Administering multi-pathing with DMP
- Administering Dynamic Multi-Pathing
- Discovering and configuring newly added disk devices
- About discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Administering DMP using the vxdmpadm utility
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Discovering and configuring newly added disk devices
- Dynamic Reconfiguration of devices
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Managing devices
- Displaying disk information
- Changing the disk device naming scheme
- Adding and removing disks
- Event monitoring
- Administering Dynamic Multi-Pathing
- Section IV. Administering Storage Foundation Cluster File System High Availability
- Administering Storage Foundation Cluster File System High Availability and its components
- Administering CFS
- About the mount, fsclustadm, and fsadm commands
- When the CFS primary node fails
- About Snapshots on SFCFSHA
- Administering VCS
- Administering CVM
- About setting cluster node preferences for master failover
- About changing the CVM master manually
- Importing disk groups as shared
- Administering Flexible Storage Sharing
- Administering ODM
- About administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- About the vxfentsthdw utility
- Administering SFCFSHA global clusters
- Using Clustered NFS
- Understanding how Clustered NFS works
- Configure and unconfigure Clustered NFS
- Reconciling major and minor numbers for NFS shared disks
- Administering Clustered NFS
- Samples for configuring a Clustered NFS
- Using Common Internet File System
- Administering sites and remote mirrors
- About sites and remote mirrors
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Failure and recovery scenarios
- Administering Storage Foundation Cluster File System High Availability and its components
- Section V. Optimizing I/O performance
- Section VI. Veritas Extension for Oracle Disk Manager
- Using Veritas Extension for Oracle Disk Manager
- About Oracle Disk Manager
- About Oracle Disk Manager and Oracle Managed Files
- Using Cached ODM
- Using Veritas Extension for Oracle Disk Manager
- Section VII. Using Point-in-time copies
- Understanding point-in-time copy methods
- 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
- Traditional third-mirror break-off snapshots
- Full-sized instant snapshots
- Creating instant snapshots
- Adding an instant snap DCO and DCO volume
- Controlling instant snapshot synchronization
- Creating instant snapshots
- Cascaded snapshots
- Adding a version 0 DCO and DCO volume
- Administering Storage Checkpoints
- Storage Checkpoint administration
- Administering FileSnaps
- Administering snapshot file systems
- Understanding point-in-time copy methods
- Section VIII. Optimizing storage with Storage Foundation Cluster File System High Availability
- Understanding storage optimization solutions in Storage Foundation Cluster File System High Availability
- 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
- InfoScale 4K sector device support solution
- Section IX. Maximizing storage utilization
- Understanding storage tiering with SmartTier
- Creating and administering volume sets
- Multi-volume file systems
- Features implemented using multi-volume file system (MVFS) support
- Adding a volume to and removing a volume from a multi-volume file system
- Volume encapsulation
- Load balancing
- Administering SmartTier
- About SmartTier
- Placement classes
- Administering placement policies
- File placement policy rules
- Multiple criteria in file placement policy rule statements
- Using SmartTier with solid state disks
- Sub-file relocation
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Compressing files
- About compressing files
- Use cases for compressing files
- Section X. 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
- Performing online relayout
- Adding a mirror to a volume
- Managing disk groups
- Disk group versions
- Displaying disk group information
- Importing a disk group
- Moving disk groups between systems
- Importing a disk group containing hardware cloned disks
- Handling conflicting configuration copies
- Destroying a disk group
- Backing up and restoring disk group configuration data
- 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
- Extending an LVM rootvg that is enabled for DMP
- Quotas
- Using Veritas File System quotas
- File Change Log
- Section XI. Reference
- Appendix A. Reverse path name lookup
- Appendix B. Tunable parameters
- Tuning the VxFS file system
- Methods to change Dynamic Multi-Pathing tunable parameters
- Tunable parameters for VxVM
- Methods to change Veritas Volume Manager tunable parameters
- About LLT tunable parameters
- About GAB tunable parameters
- About VXFEN tunable parameters
- Appendix C. Command reference
- Appendix D. Creating a starter database
- Appendix E. Executive Order logging
Migrating an internal root disk to a SAN root disk under DMP control
If the system has been booted from an internal disk (such as hdisk0), you can configure an alternate root disk on the attached SAN storage before you put it under DMP control.
In this example, a SAN boot disk with multiple paths is created by cloning the existing root disk, and then enabling multi-pathing support by DMP.
To migrate an internal root disk to a SAN root disk under DMP control
- Choose a disk to use for the SAN root disk. If the disk is under VM control, then remove the disk from VM control before proceeding:.
# vxdiskunsetup ams_wms0_1
# vxdisk rm ams_wms0_1
- Clear the PVIDs of all the paths to the SAN boot disk. If the SAN disk is under VM control, then you can get multi-pathing information using the vxdmpadm command:
# vxdmpadm getsubpaths dmpnodename=ams_wms0_1
NAME STATE[A] PATH-TYPE[M] CTLR-NAME ENCLR-TYPE ENCLR-NAME ATTRS ===================================================================== hdisk542 ENABLED(A) PRIMARY fscsi0 AMS_WMS ams_wms0 - hdisk557 ENABLED SECONDARY fscsi0 AMS_WMS ams_wms0 - hdisk558 ENABLED(A) PRIMARY fscsi1 AMS_WMS ams_wms0 - hdisk559 ENABLED SECONDARY fscsi1 AMS_WMS ams_wms0 -
Clear the PVIDs of all these paths.
# chdev -l hdisk542 -a pv=clear hdisk542 changed # chdev -l hdisk557 -a pv=clear hdisk557 changed # chdev -l hdisk558 -a pv=clear hdisk558 changed # chdev -l hdisk559 -a pv=clear hdisk559 changed
Note that unless the disk is under VM control, the clear command may not work for secondary paths.
- If any path to the target disk has SCSI reserve ODM attribute set, then change the attributes to release the SCSI reservation from the paths, on a restart.
If a path has the reserve_policy attribute set, change the reserve_policy attribute to no_reserve for all the paths.
# lsattr -E1 hdisk557 | grep res reserve_policy single_path Reserve Policy True
# chdev -l hdisk557 -a reserve_policy=no_reserve -P hdisk557 changed
If a path has the reserve_lock attribute set, change the reserve_lock attribute to no.
# lsattr -E1 hdisk558 | grep reserve_lock reserve_lock yes Reserve Device on open True
# chdev -l hdisk558 -a reserve_lock=no -P hdisk558 changed
- Use the alt_disk_install command to clone the
rootvg
to the SAN boot disk. You can use any of the paths, but preferably use the primary path.# alt_disk_install -C -P all hdisk542 +-------------------------------------------------------------+ ATTENTION: calling new module /usr/sbin/alt_disk_copy. Please see the alt_disk_copy man page and documentation for more details. Executing command: /usr/sbin/alt_disk_copy -P "all" -d "hdisk542" +-------------------------------------------------------------+ Calling mkszfile to create new /image.data file. Checking disk sizes. Creating cloned rootvg volume group and associated logical volumes. Creating logical volume alt_hd5. Creating logical volume alt_hd6. Creating logical volume alt_hd8. Creating logical volume alt_hd4. Creating logical volume alt_hd2. Creating logical volume alt_hd9var. Creating logical volume alt_hd3. Creating logical volume alt_hd1. Creating logical volume alt_hd10opt. Creating logical volume alt_lg_dumplv. Creating /alt_inst/ file system. Creating /alt_inst/home file system. Creating /alt_inst/opt file system. Creating /alt_inst/tmp file system. Creating /alt_inst/usr file system. Creating /alt_inst/var file system. Generating a list of files for backup and restore into the alternate file system... Backing-up the rootvg files and restoring them to the alternate file system... Modifying ODM on cloned disk. Building boot image on cloned disk. forced unmount of /alt_inst/var forced unmount of /alt_inst/usr forced unmount of /alt_inst/tmp forced unmount of /alt_inst/opt forced unmount of /alt_inst/home forced unmount of /alt_inst forced unmount of /alt_inst Changing logical volume names in volume group descriptor area. Fixing LV control blocks... Fixing file system superblocks... Bootlist is set to the boot disk: hdisk542
- Use the lspv command to confirm that the
altinst_rootvg
has been created for one of the paths to the SAN disk:# lspv | grep rootvg hdisk125 00cdee4fd0e3b3da rootvg active hdisk542 00cdee4f5b103e98 altinst_rootvg
- Update the remaining paths to the SAN disk to include the correct
altinst_rootvg
information:# chdev -l hdisk557 -a pv=yes hdisk557 changed # chdev -l hdisk558 -a pv=yes hdisk558 changed # chdev -l hdisk559 -a pv=yes hdisk559 changed # lspv | grep rootvg hdisk125 00cdee4fd0e3b3da rootvg active hdisk542 00cdee4f5b103e98 altinst_rootvg hdisk557 00cdee4f5b103e98 altinst_rootvg hdisk558 00cdee4f5b103e98 altinst_rootvg hdisk559 00cdee4f5b103e98 altinst_rootvg
- The bootlist command verifies that the boot device has been updated for only one of the paths to the SAN disk:
# bootlist -m normal -o hdisk542 blv=hd5
- Use the bootlist command to include the other paths to the new boot device:
# bootlist -m normal hdisk542 hdisk557 hdisk558 hdisk559 blv=hd5 # bootlist -m normal -o hdisk542 blv=hd5 hdisk557 blv=hd5 hdisk558 blv=hd5 hdisk559 blv=hd5
- Reboot the system from the SAN disk.
- Enable DMP on the root disk, using one of the following commands.
The recommended method is to turn on DMP support for LVM volumes, including the root volume.
# vxdmpadm settune dmp_native_support=on
The following command enables DMP support for LVM volumes only for the root disk. This method will be deprecated in a future release.
# vxdmpadm native enable vgname=rootvg
- Reboot the system to enable DMP rootability.
- Confirm that the system is booted from the new multi-pathed SAN disk. Use the following commands:
# bootinfo -b hdisk542 # bootlist -m normal -o hdisk542 blv=hd5 hdisk557 blv=hd5 hdisk558 blv=hd5 hdisk559 blv=hd5 # lspv | grep rootvg hdisk125 00cdee4fd0e3b3da old_rootvg ams_wms0_1 00cdee4f5b103e98 rootvg active
- Verify whether DMP controls the root disk..
# vxdmpadm native list vgname=rootvg PATH DMPNODENAME ======================== hdisk542 ams_wms0_1 hdisk557 ams_wms0_1 hdisk558 ams_wms0_1 hdisk559 ams_wms0_1