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

9–2 Enterprise Volume Manager (Multi-OS) Network Administration Guide
EVM Jobs and Job Management
• Snapshot mount
• Snapshot suspend mount
Volume and Unit Commands
Source volumes (volumes that are to be replicated) can be specified by volume name
rather than by the unit they are based on. To implement this command style, the
CLONE, NORMALIZE, SPLIT, SNAP, and MOUNT commands have been divided into two
versions: VOLUME and UNIT.
Volume-style commands allow the source volume to be specified as a volume (drive
letter or mount point) on a specific host:
CLONE VOLUME aix_server_name /mnt/lv00 2
CLONE VOLUME windows_server_name F: 2
Note also that UFSs created on Logical Storage Manager (LSM) volumes are not supported.
Unit-style commands are the same as they were in EVM V2.0. Source volumes are
specified in terms of their storage system and unit number, as in the following
example:
CLONE UNIT SUBSYS1 D2 2
NOTE: For IBM AIX hosts, HP recommends using only the VOLUME syntax for snap and clone
operations. For Tru64 UFSs (UNIX file systems), unit- or volume-based job steps are valid; but,
for domain-based file systems, only volume-style job steps are valid.
Windows Clone Example
The following example illustrates operational sequences for a typical Windows clone
job:
CLONE UNIT SUBSYS1 D1 2
CLONE UNIT SUBSYS1 D2 2
CLONE UNIT SUBSYS1 D3 2
NORMALIZE UNIT SUBSYS1 D1
NORMALIZE UNIT SUBSYS1 D2
NORMALIZE UNIT SUBSYS1 D3
SUSPEND WAIT dbserver “freeze_database.bat”
SPLIT UNIT SUBSYS1 D1 $copy_db1
SPLIT UNIT SUBSYS1 D2 $copy_db2
SPLIT UNIT SUBSYS1 D3 $copy_db3
RESUME NOWAIT dbserver “thaw_database.bat”
MOUNT UNIT SUBSYS1 $copy_db1 backupserver 1 t:
MOUNT UNIT SUBSYS1 $copy_db2 backupserver 1 u:
MOUNT UNIT SUBSYS1 $copy_db3 backupserver 1 v:
LAUNCH WAIT backupserver “backup_db.bat”
Each operation is explained in the operation sections that follow.