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
vxclustadm utility
The vxclustadm command provides an interface to the CVM functionality of VxVM when VCS is used as the cluster monitor. It is also called during cluster startup and shutdown. In the absence of a cluster monitor, vxclustadm can also be used to activate or deactivate the CVM functionality of VxVM on any node in a cluster.
The startnode keyword to vxclustadm starts CVM functionality on a cluster node by passing cluster configuration information to the VxVM kernel. In response to this command, the kernel and the VxVM configuration daemon, vxconfigd, perform initialization.
The stopnode keyword stops CVM functionality on a node. It waits for all outstanding I/O to complete and for all applications to close shared volumes.
The setmaster keyword migrates the CVM master to the specified node. The migration is an online operation. Symantec recommends that you switch the master when the cluster is not handling VxVM configuration changes or cluster reconfiguration operations.
The reinit keyword allows nodes to be added to or removed from a cluster without stopping the cluster. Before running this command, the cluster configuration file must have been updated with information about the supported nodes in the cluster.
The nidmap keyword prints a table showing the mapping between CVM node IDs in VxVM's cluster-support subsystem and node IDs in the cluster monitor. It also prints the state of the nodes in the cluster.
The nodestate keyword reports the state of a cluster node and also the reason for the last abort of the node as shown in this example:
# vxclustadm nodestate state: out of cluster reason: user initiated stop
Table: Node abort messages lists the various reasons that may be given for a node abort.
Table: Node abort messages
Reason | Description |
---|---|
cannot find disk on slave node | Missing disk or bad disk on the slave node. |
cannot obtain configuration data | The node cannot read the configuration data due to an error such as disk failure. |
cluster device open failed | Open of a cluster device failed. |
clustering license mismatch with master node | Clustering license does not match that on the master node. |
clustering license not available | Clustering license cannot be found. |
connection refused by master | The join operation of a node refused by the master node. |
disk in use by another cluster | A disk belongs to a cluster other than the one that a node is joining. |
join timed out during reconfiguration | The join operation of a node has timed out due to reconfiguration taking place in the cluster. |
klog update failed | Cannot update kernel log copies during the join operation of a node. |
master aborted during join | Master node aborted while another node was joining the cluster. |
protocol version out of range | Cluster protocol version mismatch or unsupported version. |
recovery in progress | Volumes that were opened by the node are still recovering. |
transition to role failed | Changing the role of a node to be the master failed. |
user initiated abort | Node is out of cluster due to an abort initiated by the user or by the cluster monitor. |
user initiated stop | Node is out of cluster due to a stop initiated by the user or by the cluster monitor. |
vxconfigd is not enabled | The VxVM configuration daemon is not enabled. |
See the vxclustadm(1M) manual page.