Air Cleaner User Manual

recreated from this backup. Unless the logical volume was originally created
using a physical partition map, it is generally recommended that it not be
recreated using the same partitions, as this would preserve fragmentation that
develops over time as logical volumes and filesystems are expanded. You can
specify whether or not partition mapping will be used before recreating the
logical volume.
Examples
1. To perform a local backup of the lv02 logical volume to the directory
/usr/lpp/sysback/bf/root, indicating that only this user and host can read the
file and displaying a progress indicator, type:
mklvback -f /usr/lpp/sysback/bf/root -I lv02 -x -r host=h -r user=u lv02
The filename created will be /usr/lpp/sysback/bf/root/LV.hostname.lv02.
2. To perform a remote push backup to the virtual device vdev2 of the host jupiter
and to make this a compressed backup of the logical volumes datalv and
datalv2, type:
mklvback -nph jupiter -f vdev2 datalv datalv2
Note that the -n flag is specified. This prevents the tape drive from being
rewound before the backup begins, enabling this backup to be “stacked” on the
end of the previous backup image.
3. To initiate a pull backup of the /home filesystem on host lasher, from host
sysback1, and send the data to rmt1 of the host sysback1, type the following from
sysback1:
mklvback -U lasher -f /dev/rmt1 /home
4. To initiate a pull backup of the /home filesystem on host lasher, from host
sysback1, and send the data to rmt1 of the host shappy, type the following
command from sysback1:
mklvback -U lasher -h shappy -f /dev/rmt1 /home
Related Information
The sysrestore, cfgremsvs, cfgremaccess, mkvginfo, cfgremrootaccess, and
editlvminfo commands.
A-40 IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide