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

Enterprise Volume Manager (Multi-OS) Network Administration Guide 9–7
EVM Jobs and Job Management
In the Windows Snapshot Unit Example on page 9–5, the two BCVs are mounted on a
host named “backupserver” as drives x: and y:.
Mount Volume Operation
After creating the BCVs and restoring the application on the EVM host agent
computer to the normal mode of operation, the next step is to mount the BCVs on an
EVM host agent computer.
In the UNIX Snapshot Volume Example on page 9–5, the BCVs are mounted on a host
named “backupserver” as drives as logical volume /mnt/lv00-bcv.
Launch Operation
Most jobs end with a launch operation that executes a user-specified command on the
desired EVM host agent. Typically, this is the same EVM host agent on which the
mount operations were performed. The most common use for this operation is to
invoke a backup application to copy the data from the mounted BCVs to tape.
In the Windows Snapshot Unit Example on page 9–5, a batch file named
run-backup.bat executes on the backupserver host using the
WAIT parameter.
In the UNIX Snapshot Volume Example on page 9–5, a script named backup.sh
executes on the backupserver host using the
WAIT parameter.
UNIX Volume Group Example—No Specific Mount Point or Fileset
As an option, you can create a job that is built on a volume group or Tru64 UNIX
domain without a specific fileset or mount point. Choices appear in the snap or clone
step to specify a volume group or domain.
For example, if the source host contains a domain named “oracle_domain,” in addition
to all the filesets in this domain, the domain itself is presented in the format
“VG(oracle_domain).”
This type of job presents the new units to the destination and re-creates the domain,
but does not mount any filesets. If you build a job based on the oracle_domain, the
mount point must be specified as “N/A” because no specific fileset was chosen to
mount.