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

5–24 Enterprise Volume Manager (Multi-OS) Network Administration Guide
Configuring the EVM Network
Using EVM in a DRM Configuration
EVM is compatible with Data Replication Manager (DRM) configurations. However,
management of a DRM environment may sometimes require that the Management
Appliance be excluded from the configuration (zoned out). Whenever the
Management Appliance is not part of the DRM configuration, the EVM server cannot
access storage systems within the DRM configuration.
HSG Container Name Limitations
The EVM network software places some limitations on changing the name of a
container. Keep these points in mind:
• Any HSG container name beginning with C! (capital “C” and an exclamation
point) and ending with !C (such as C!12345!C) is reserved for EVM program use.
The same restriction applies to any container name using this format with the
letter “S” (such as S!12345!S).
CAUTION: Do not use “C!” or “S!” at the beginning of a container name, and do not
use “!C” or “!S” at the end of one. Do not change the name of any container created by
the EVM network that begins or ends with these sequences.
Changing the name of a container created by EVM may affect the ability of EVM to
track that container. If a container name that uses the “C!...!C” or “S!...!S” format is
changed, EVM will not properly recognize that container. Since EVM safety rules
prohibit the EVM program from deleting anything that EVM storage did not create, the
container will not function properly.
• Do not include the words Warning, Critical, or Error, in any form, in any
container name. They are keywords used by EVM software for processing specific
functions.
Fault Tolerance and Disaster Recovery
This section contains procedures for protecting the EVM network configuration in the
event of a failure.
Using the Save Configuration Feature
EVM stores job files and critical configuration data on the Management Appliance.
HP recommends saving this information to a host computer on a regular basis. Being
able to reload the EVM configuration after a Management Appliance or EVM server
failure can prevent re-creating EVM jobs and reinstalling the EVM host agents.