Veritas Volume Manager 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)

How VxVM Handles Storage Management
8 VERITAS Volume Manager Administrator’s Guide
same name to VxVM for all of the paths over which it can be accessed. For example, the
disk device enc0_0 represents a single disk for which two different paths are known to
the operating system, such as c1t99d0 and c2t99d0.
To take account of fault domains when configuring data redundancy, you can control how
mirrored volumes are laid out across enclosures as described in “Mirroring across Targets,
Controllers or Enclosures” on page 216.
Example HA Configuration Using Multiple Hubs/Switches to Provide Redundant-Loop Access
See “Disk Device Naming in VxVM” on page 60 and “Changing the Disk-Naming
Scheme” on page 72 for details of the standard and the enclosure-based naming schemes,
and how to switch between them.
Virtual Objects
Virtual objects in VxVM include the following:
◆ Disk Groups
◆ VM Disks
◆ Subdisks
◆ Plexes
◆ Vol um es
The connection between physical objects and VxVM objects is made when you place a
physical disk under VxVM control.
c2c1
Host
Fibre Channel
Hubs/Switches
Disk Enclosures
enc0 enc1 enc2