make_tape_recovery.1m (2012 03)

m
make_tape_recovery(1M) make_tape_recovery(1M)
Data Recovery from Raw Logical Volumes
Only file system data is included in recovery archives created by
make_tape_recovery
. Data
included in raw logical volumes (like those that contain database data) is not included in recovery
archives, and must be backed up as part of the overall backup stategy of a system.
LVM Volume Group Version 2.x or higher
Ignite-UX does not support the system recovery archive creation using the
make_tape_recovery
com-
mand for Volume Groups having Volume Group Version 2.0 or 2.1. If any LVM Volume Group having
unsupported Volume Group Versions is provided as arguments to
make_tape_recovery
command, the
command fails and reports the unsupported volume groups. In such situations, either omit the unsup-
ported volume groups as input to
make_tape_recovery
command or migrate all those unsupported
volume group version to 2.2 or higher (using LVM’s Volume Group Version migration tool, vgversion) and
rerun the command.
For LVM Volume Groups having Volume Group Version 2.2 or higher, if the
LVMP_CONF_PATH_NON_BOOT
configuration variable in
/etc/lvmrc file is modified to store LVM
configuration backups in a directory that is not backed up by default, user may need to consider including
that directory for recovery.
Non-default Device Files May Not Be Recovered Correctly
Any custom agile device files may not be correct after a recovery. Ignite-UX does not inventory or re-
create custom agile DSFs. They may be present post-recovery and may refer to the wrong device. It is up
to the person or application that created the custom agile DSFs to verify that they point to the correct
device and recreate them as required or not use them. This includes custom agile pass-through device
files created by HP Integrity VM on 11.31 systems (on the host system only). After recovery
hpvmdevmgmt must be run on the host system to recreate pass-through DSFs before starting a VM
guest. Failure to do so may cause HPVM host issues. Refer to hpvmdevmgmt (1M) for more details.
In the event of instance changes during recovery, custom legacy DSFs may point to the wrong legacy dev-
ice. Post-recovery in the event of instance changes in legacy devices it should be verified that any required
custom legacy DSF points to the correct device. It is the responsibility of the person or application who
created the custom legacy DSF to ensure that they point to the correct device in these circumstances
before attempting to use them.
Existence of Cluster-wide Device Special Files (cDSF) on the System
Ignite-UX does not support the creation of the recovery archive using the
make_tape_recovery
com-
mand for Volume Groups configured using Cluster-wide Device Special Files (cDSF). When volume groups
configured using cDSF are provided as arguments to the command, it fails and reports the same as
unsupported. To proceed, omit the unsupported volume groups as input and rerun the command. When
volume groups configured using cDSF are present on the system and are not provided as arguments,
there will be a warning about their existence, however the recovery archive will be created.
DEPENDENCIES
The Ignite-UX GUI must be run from the Ignite-UX Server, see ignite (5).
make_tape_recovery
depends on several other Ignite-UX tools. When running the Ignite-UX server GUI, Ignite-UX checks
whether the client system that make_tape_recovery runs on has the same versions of Ignite-UX
tools.
If running
make_tape_recovery from the command line without ever interacting with the Ignite-UX
GUI, commands will need to be installed using swinstall (1M) from the Ignite-UX server to the client sys-
tem on which make_tape_recovery will be run.
make_tape_recovery requires the following filesets of the Ignite-UX product be installed on the
system:
Ignite-UX.RECOVERY
Ignite-UX.BOOT-KERNEL
Ignite-UX.FILE-SRV-release
Ignite-UX.MGMT-TOOLS
AUTHOR
Ignite-UX and make_tape_recovery were developed by the Hewlett-Packard Company.
12 Hewlett-Packard Company − 12 − HP-UX 11i Version 3: March 2012