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

12–2 Enterprise Volume Manager (Multi-OS) Network Administration Guide
Migration Planning
Preliminary Migration Steps
Before migrating any previous EVM network to EVM V2.0D, perform the following
on the old EVM network:
• Verify that no affected EVM jobs are running.
• Verify that no affected EVM jobs are scheduled to run.
• Run all pending EVM undo jobs, as desired.
• Coordinate migration activities with other operations and EVM users.
NOTE: HP recommends notifying users of the planned migration and instructing them not
to use the old or new EVM network until notified.
To prepare for the migration:
• Stop the EVM service or daemon on all host computers.
• Print the EVM jobs information so that these jobs can be re-created in the
EVM V2.0D network; EVM V1.x job files cannot be used in an EVM V2.0D
network.
Running Affected EVM Undo Jobs
If EVM undo jobs are affected, execute the following procedure to clear them:
1. Browse to the EVM Job Status page for the old EVM network.
2. Check for any pending undo jobs.
These pending undo jobs must be run before this EVM network is migrated.
3. Confirm with other operations and users that the undo jobs can be run.
CAUTION: Running an undo job unmounts the BCV units for the job and deletes the
BCV data. Always coordinate this activity with other operations and users that may be
affected.
4. In cases where the contents of a BCV must be retained after an instance of EVM is
removed, copy the data to other non-BCV storage resources before running the
undo job.