Veritas™ Volume Manager Administrator's Guide
- Understanding Veritas Volume Manager
- VxVM and the operating system
- How VxVM handles storage management
- Volume layouts in VxVM
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- Provisioning new usable storage
- Administering disks
- Disk devices
- Discovering and configuring newly added disk devices
- Discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Changing the disk-naming scheme
- Adding a disk to VxVM
- Rootability
- Displaying disk information
- Removing disks
- Removing and replacing disks
- Administering Dynamic Multi-Pathing
- How DMP works
- Administering DMP using vxdmpadm
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Online dynamic reconfiguration
- Reconfiguring a LUN online that is under DMP control
- Creating and administering disk groups
- About disk groups
- Displaying disk group information
- Creating a disk group
- Importing a disk group
- Moving disk groups between systems
- Handling cloned disks with duplicated identifiers
- Handling conflicting configuration copies
- Reorganizing the contents of disk groups
- Destroying a disk group
- Creating and administering subdisks and plexes
- Displaying plex information
- Reattaching plexes
- Creating volumes
- Types of volume layouts
- Creating a volume
- Using vxassist
- Creating a volume on specific disks
- Creating a mirrored volume
- Creating a striped volume
- Creating a volume using vxmake
- Initializing and starting a volume
- Using rules and persistent attributes to make volume allocation more efficient
- Administering volumes
- Displaying volume information
- Monitoring and controlling tasks
- Reclamation of storage on thin reclamation arrays
- Stopping a volume
- Resizing a volume
- Adding a mirror to a volume
- Preparing a volume for DRL and instant snapshots
- Adding traditional DRL logging to a mirrored volume
- Enabling FastResync on a volume
- Performing online relayout
- Adding a RAID-5 log
- Creating and administering volume sets
- Configuring off-host processing
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Administering cluster functionality (CVM)
- Overview of clustering
- Multiple host failover configurations
- CVM initialization and configuration
- Dirty region logging in cluster environments
- Administering VxVM in cluster environments
- Changing the CVM master manually
- Importing disk groups as shared
- 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
- Performance monitoring and tuning
- Appendix A. Using Veritas Volume Manager commands
- Appendix B. Configuring Veritas Volume Manager
Replacing a host bus adapter
This section describes replacing an online host bus adapter (HBA) when DMP is managing multi-pathing in a Storage Foundation Cluster File System (SFCFS) cluster. The HBA World Wide Port Name (WWPN) changes when the HBA is replaced. Following are the prerequisites to replace an online host bus adapter:
A single node or two or more node CFS or RAC cluster.
I/O running on CFS file system.
Hotplug capable server.
To replace an online host bus adapter
- Identify the HBA and its WWPN(s), which you want to replace.
Determine the hardware path or paths to be disabled on one of the nodes, which has a hotplug capability.
# vxdmpadm getctlr all LNAME PNAME VENDOR CTLR-ID ============================================================ c3 0/1/1/1.0x2 - - c2 0/1/1/0.0x0 - - c16 0/3/1/0.0x50060e8004278356 - - c18 0/4/1/0.0x50060e8004278366 - - c15 0/2/1/0.0x50060e8004278346 - - c13 0/4/1/1.0x50060e8004278376 - -
A single HBA may show as multiple controllers (
c#
) in the vxdmpadm getctlr output. To replace the HBA, you must disable each of these controllers in step 3 and enable each of them in step 10. - Ensure that you have a compatible spare HBA for hot-swap.
- Stop the I/O operations on the HBA port(s) and disable the DMP subpath(s) for the HBA that you want to replace.
# vxdmpadm disable ctrl=ctrl#
For example:
# vxdmpadm disable ctlr=c16
- Prepare to replace the HBA:
# /usr/bin/olrad -r slot_ID
The above command performs a Critical Resource Analysis (CRA).
- Replace the HBA with a new compatible HBA of similar type in the same slot.
- Bring the replaced HBA back into the configuration. Enter the following:
# /usr/bin/olrad -q
- Enter the following command after you replace the HBA:
# /usr/bin/olrad -R slot_ID
- Verify the success of the operation. The slot power should be ON, driver is OLAR capable, and so on.
# /usr/bin/olrad -q slot_ID
- Perform an operating system device scan to re-discover the LUNs. Enter the following:
# ioscan -fn
- Enable the controller in VxVM
# vxdmpadm enable ctlr=ctrl#
For example:
# vxdmpadm enable ctlr=c16
- Verify if I/O operations are scheduled on that path. If I/O operations are running correctly on all paths, the dynamic HBA replacement operation is complete.