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
Activation modes of shared disk groups
A shared disk group must be activated on a node in order for the volumes in the disk group to become accessible for application I/O from that node. The ability of applications to read from or to write to volumes is dictated by the activation mode of a shared disk group. Valid activation modes for a shared disk group are exclusivewrite, readonly, sharedread, sharedwrite, and off (inactive).
The default activation mode for shared disk groups is off (inactive).
Special uses of clusters, such as high availability (HA) applications and off-host backup, can use disk group activation to explicitly control volume access from different nodes in the cluster
Table: Activation modes for shared disk groups describes the activation modes.
Table: Activation modes for shared disk groups
Activation mode | Description |
---|---|
exclusivewrite (ew) | The node has exclusive write access to the disk group. No other node can activate the disk group for write access. |
readonly (ro) | The node has read access to the disk group and denies write access for all other nodes in the cluster. The node has no write access to the disk group. Attempts to activate a disk group for either of the write modes on other nodes fail. |
sharedread (sr) | The node has read access to the disk group. The node has no write access to the disk group, however other nodes can obtain write access. |
sharedwrite (sw) | The node has write access to the disk group. Attempts to activate the disk group for shared read and shared write access succeed. Attempts to activate the disk group for exclusive write and read-only access fail. |
off | The node has neither read nor write access to the disk group. Query operations on the disk group are permitted. |
Table: Allowed and conflicting activation modes summarizes the allowed and conflicting activation modes for shared disk groups.
Table: Allowed and conflicting activation modes
Disk group activated in cluster as... | Attempt to activate disk group on another node as... | |||
---|---|---|---|---|
exclusive- write | readonly | sharedread | sharedwrite | |
exclusivewrite | Fails | Fails | Succeeds | Fails |
readonly | Fails | Succeeds | Succeeds | Fails |
sharedread | Succeeds | Succeeds | Succeeds | Succeeds |
sharedwrite | Fails | Fails | Succeeds | Succeeds |
Shared disk groups can be automatically activated in a specified mode when the disk group is created or imported. To control automatic activation of shared disk groups, create a defaults file /etc/default/vxdg
containing the following lines:
enable_activation=true default_activation_mode=activation-mode
The activation-mode is one of exclusivewrite, readonly, sharedread, sharedwrite, or off.
When a shared disk group is created or imported, it is activated in the specified mode. When a node joins the cluster, all shared disk groups accessible from the node are activated in the specified mode.
The activation mode of a disk group controls volume I/O from different nodes in the cluster. It is not possible to activate a disk group on a given node if it is activated in a conflicting mode on another node in the cluster. When enabling activation using the defaults file, it is recommended that the file be consistent on all nodes in the cluster as in Table: Allowed and conflicting activation modes. Otherwise, the results of activation are unpredictable.
If the defaults file is edited while the vxconfigd daemon is already running, run the /sbin/vxconfigd -k -x syslog command on all nodes to restart the process.
If the default activation mode is anything other than off, an activation following a cluster join, or a disk group creation or import can fail if another node in the cluster has activated the disk group in a conflicting mode.
To display the activation mode for a shared disk group, use the vxdg list diskgroup command.
You can also use the vxdg command to change the activation mode on a shared disk group.
It is also possible to configure a volume so that it can only be opened by a single node in a cluster.