 |
» |
|
|
|
For information on Ignite-UX, see the manual Ignite-UX
Administration Guide. Making
an Archive of a Virtual Partition | |
make_tape_recovery is not supported for vPars hard partition. You need to
use make_net_recovery. make_net_recovery works the same for making archives of both non-vPars
and vPars hard partitions. Recovering
a Virtual Partition | |
Ignite-UX modifies the LIF area during a recovery, yet vPars
does not use the LIF area for booting a virtual partition; therefore,
on a vPars hard partition you need to perform some additional steps. To recover a virtual partition, perform the following from
a running virtual partition. (In these examples, the partition winona1 is
running and the partition winona2 is the
partition being recovered.) Record whether the autoboot attribute
is set. You may need to set it back to this state in Step 7. winona1# vparstatus -p winona2
[Virtual Partition]
Virtual Partition Name State Attributes
========================== ===== ==========
winona2 Down Dyn,Auto |
Set the autoboot attribute to manual for
the target virtual partition (the virtual partition you wish to
recover): winona1# vparmodify -p winona2 -B manual Set the kernel path of the
target partition to use the boot kernel /stand/WINSTALL: winona1# vparmodify -p winona2 -b /stand/WINSTALL Ignite-UX modifies the LIF area to boot the WINSTALL kernel
as part of its recovery process. However, because vPars uses the
vPars database instead of the LIF area to boot a virtual partition,
this change needs to be done to the vPars database. Set the TERM environment
variable to hpterm. For POSIX shell, the command
is winona1# export TERM=hpterm Boot the target partition and point the boot kernel
to use your Ignite-UX server (assume the Ignite server's
IP is 15.xx.yy.zz): winona1# vparboot -p winona2 -I 15.xx.yy.zz,/opt/ignite/boot/WINSTALL Run the Ignite-UX recovery as you would on a non-vPars
hard partition, entering the data (boot disk and LAN) of the target partition. After the target partition has been recovered, if
the autoboot attribute was set to AUTO in
Step 1, reset the autoboot attribute of the target partition back
to AUTO: winona1# vparmodify -p winona2 -B auto Reset the kernel path of the target partition back
to the normal kernel: winona1# vparmodify -p winona2 -b /stand/vmunix This changes the vPars database back to its original contents.
(See Step 3 above for the manual change that was done).
Recovering
all the Virtual Partitions of a Hard Partition | |
To recover all the virtual partitions within a hard partition,
first recover the virtual partition whose boot disk is the disk
set as the primary path within system-wide stable storage. Once
the virtual partition is recovered, recover the other virtual partitions
one by one. (There is no way to recover all partitions simultaneously.): From the BCH prompt, boot the
hard partition using the Ignite-UX server (assume the Ignite server's
IP is 15.xx.yy.zz): BCH> bo lan.15.xx.yy.zz install
interact with IPL? N From the Ignite-UX window,
select "Install HP-UX". Enter the network data using
the data for the virtual partition that owns the boot disk that
is set as the primary path within system-wide stable storage. Select Recovery
Archive Configuration -> Go After this virtual partition
is recovered, recover the remaining partitions using the instructions
in “Recovering
a Virtual Partition”.
|
Printable version
