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

Enterprise Volume Manager (Multi-OS) Network Administration Guide 12–5
Migration Planning
Re-creating EVM V1.x Jobs as EVM V2.0D Jobs
After the EVM V1.x network has been migrated to an EVM V2.0D network, all of the
EVM jobs used in the old EVM network must be re-created and run immediately, to
make sure the new EVM jobs perform properly.
CAUTION: Running an old EVM V1.x job on an EVM V2.0D network can lead to
unpredictable results, including loss of data on BCVs. Avoid this by not running old
EVM jobs on the EVM V2.0D network. Instead, make sure all old jobs are re-created
as EVM V2.0D jobs.
Convert each EVM V1.x job to an EVM V2.0D job, as desired, using instructions for
creating a new job in the online Help/User Guide.
IMPORTANT: Also, review “HSG Container Name Limitations” on page 5–24 to make sure that
all container names meet EVM V2.0D requirements.
NOTE: Previous versions of EVM added a prefix (such as stor1_) to each EVM job name.
EVM V2.0D does not add such a prefix nor does it modify the name given by the user.