Enterprise Volume Manager (Multi-OS) Host Agent Version 2.0D for HP-UX Release Notes

Limitations and Known Issues
Release Notes – Enterprise Volume Manager (Multi-OS) Host Agent Version 2.0D
for HP-UX
8
Volume Group Is the Minimum Unit of Replication
The data for a given logical volume can be located on any or all of the physical disks
in a volume group. As a result, a hardware level replication of the logical volume (like
that performed by EVM) must copy all of the physical volumes in the volume group in
order to capture all of the data. This limitation also applies to logical volumes that
have been extended to specific disks.
Current Mapfile Requirement
EVM uses a mapfile to import a replicated HP-UX volume group. The mapfile defines
the logical volume name to number association for all of the logical volumes in a
volume group. Without this information, the system assigns default names to all of the
logical volumes in the replicated volume group and the original names are lost.
Without the original name, associating a source volume with a replicated copy is
difficult.
EVM includes a script named Generate_Mapfiles.ksh, which generates a mapfile for
each volume group. This script closes all the logical volumes (unmounts the
filesystems) and then deactivates the volume group before creating the mapfile. After
creating the mapfile, the script reactivates the volume group and reopens the logical
volumes. This process completes within two minutes for most volume groups. During
this time period, the volume group and all logical volumes contained within the group
are unavailable. This mapping process should be scheduled, as needed, to minimize
any impact to normal operations.
A mapfile must be created for each volume group that will be replicated using EVM.
If the logical volume configuration for a given volume group changes through the
addition or deletion of a logical volume, an updated mapfile must be generated using
this same process. Volume groups with invalid mapfiles are not displayed on the EVM
Resource page and cannot be used in EVM jobs.
EVM does not automatically display HP-UX volume groups on the EVM Resources
page. To display a volume group on this page, the mapfile for this volume group must
be created or updated. Refer to the EVM Network Administration Guide for the
procedure that makes selected HP-UX volume groups display on this page.
StorageWorks Storage System Requirement
All physical volumes that comprise a volume group must be located exclusively on
either HSG80 or HSV110 storage volumes. EVM cannot replicate a volume group that
does not reside entirely on one of these two types of storage systems.