Enterprise Volume Manager (Multi-OS) Version 2.0D Network Administration Guide

Enterprise Volume Manager (Multi-OS) Network Administration Guide 8–3
EVM Support for Volume Groups and HP Tru64 UNIX AdvFS Domains
• Any volume group or domain comprised of physical volumes that are:
— Not exclusively using HSG-based or HSV-based storage systems
— On HSG-based or HSV-based storage systems that the EVM server cannot
access through the Management Appliance
— On another vendor’s storage system
• On IBM AIX, duplicate volume group names may cause problems. A BCV of a
source volume group cannot be mounted back to the same host; a second copy of
the same source cannot be mounted to the same destination.
NOTE: Duplicates are allowed on HP Tru64 UNIX.
Domain Best Practices for HP Tru64 UNIX
For HP Tru64 UNIX best practices, refer to the Update Release Notes - Enterprise
Volume Manager (Multi-OS) Host Agent for HP Tru64 UNIX.
Volume Group Best Practices for IBM AIX
HP strongly recommends creating a basic volume group configuration. A basic
configuration consists of only one logical volume that is connected to a single volume
group made up of one physical volume.
Some important considerations for using volume groups in EVM:
• For multiple hosts in the EVM network, use the basic configuration for each host.
• Each volume group name on source hosts must be unique.
NOTE: HP recommends using a volume group name that identifies the host on which the
group resides, for example Host1VG1.
• Before running an EVM job, make sure that sufficient resources exist on each
HSG-based or HSV-based storage system to simultaneously replicate all of the
physical volumes that comprise a volume group.
• Unlike Windows environments, IBM AIX cannot replicate a unit and then mount
that unit on the same host.
Volume Group Best Practices for HP-UX
HP strongly recommends creating a basic volume group configuration. A basic
configuration consists of only one logical volume that is connected to a single volume
group made up of one physical volume.