AdvancedCopy Manager can back up or replicate volumes under the control of VxVM (referred to as VxVM volumes in this document) in the following units:
Physical slices in a logical volume
Physical disk that constitutes a volume group
For details on backup of a subordinate volume of VxVM, refer to the section titled "3.9 VxVM Volume Operation". For details on replication of a subordinate volume of VxVM, refer to the section titled "6.9 VxVM Volume Operation."
AdvancedCopy Manager copies a logical volume by copying the entire public region of the VM disk (physical disk) having the sliced attribute (the private region is separate from the public region) instead of copying in units of sub-disks.
Specify a device name as the VxVM logical volume name.
Figure 1.5 VM disk (physical disk) having the sliced attribute (the private region is separate from the public region)
The above means that AdvancedCopy Manager copies the VxVM logical volume in units of physical slices (/dev/dsk/cXtXdXsX) instead of units of logical volumes.
A VxVM volume that can be operated in units of logical volumes must satisfy the following conditions:
All sub-disks making up the logical volume are in one VM disk, and the VM disk does not have any sub-disk of another logical volume.
The VM disk has the sliced attribute (the private region and public region are located in different slices).
It is not a non-layered volume.
The logical volume is not encapsulated.
Figure 1.6 Relationships between volumes, VM disks and physical disks (1)
A configuration with more than one logical volume in a single VM disk (the logical volumes and VM disk are defined as N:1 (N>1)), such as shown below, is also supported but note the following points:
For logical volumes with a constructed file system, the unmount/mount operation must be performed before and after backup or replication.
For backup of an Oracle database, all logical volumes of the VM disk must be table areas.
Figure 1.7 Relationships between volumes, VM disks and physical disks (2)
Figure 1.8 Relationship between volumes and subdisks
AdvancedCopy Manager does not support logical volumes whose configuration is:
Concatenation with spanning (Concatenation without spanning is supported.)
Striping (RAID0)
Mirroring (RAID1)
RAID5
Mirroring plus Striping (RAID1 + RAID0)
Striping plus Mirroring (RAID0 + RAID1)
Note
A disk group is created as a CDS disk group by default for VxVM 4.0. To obtain a disk group supported by AdvancedCopy Manager, create a non-CDS disk group, and specify "sliced" as the disk type.
The VM disks (physical disks) on which a sub-disk used by a logical volume exists are used as the management units.
Figure 1.9 Example of VxVM configuration
Since AdvancedCopy Manager copies an entire VM disk, not only the shared area that is a sub-disk but also the public region containing VxVM-internal configuration information is copied.
When backup or replication is performed, therefore, the integrity of VxVM configuration information must be maintained during copying.
Specify a device name as follows:
/dev/vx/dmp/c#t#d#s#
/dev/vx/dmp/c#t#d#
/dev/vx/dmp/enclosure name (only for use under a SunCluster environment)
Note
Except when used under a SunCluster environment, operations are not supported under naming convention operations based on enclosures in VxVM.
Note
For operation in a cluster configuration, the device name of the physical disks that comprise the volume group must be the same at all servers that comprise the cluster, and the ETERNUS Disk storage system's disk indicated by the device name must be the same.
For operation in a SunCluster environment, the VxVM enclosure name must be the same at all servers that comprise the cluster, and the ETERNUS disk indicated by the enclosure name must be the same.
Note
It is only VM disk of the <nopriv> type that a physical slice becomes the unit of management.
