Exploring DRD Rehosting in HP-UX 11i v2 and 11i v3 (July 2010)

19
The /etc/fstab file can be edited to remove entries not available on the new blade.
14. The contents of /stand/bootconf must be checked to ensure that the current device for the
boot disk is recorded. The format of a line representing an LVM-managed disk is an “l” (ell) in
column one, followed by a space, followed by the block device file of the HP-UX (second)
partition of the boot disk. The boot disk can be determined from vgdisplay of the root group
(usually vg00.)
15. You might need to contact your network administrator to arrange for additional configuration of
the new blade on your DNS, NIS, or DHCP servers.
16. If additional applications use configuration or licensing information specific to a particular host
(such as hostname or IP address), they might need to be updated.
Using drd rehost to provision Integrity VMs
In this scenario, a new virtual machine (VM) is needed.
Assumptions
• There is an existing VM on the VM host where the new VM will be created. The existing VM has
an LVM root volume group and the desired software and patches. The root group of the pre-
existing VM will be cloned to provide a boot disk for the new VM, so the pre-existing VM will be
known as the source.
• On the VM host, a virtual switch is already defined, sufficient memory is available to boot a new
VM, and sufficient disk space is available to provision the boot disk for the new VM. The disk
space may be a raw disk, or may be an LVM logical volume.
• The required version of DRD, as described in
Installing required software, are installed on the
source VM. Ideal Configuration: Source VM is running HP-UX 11i v3 Update 3 (September 2008)
or later.
Enhancements to LVM in HP-UX 11i v3 allow a system to boot from a disk or SAN LUN, whose
device special file does not match the device special file listed first in /etc/lvmtab on the disk.
Further enhancements were made to this feature in the September 2008 release of LVM to remove
the need to run any LVM “cleanup” commands after the boot completed.
More information on this feature is available in the section on Boot Resiliency in
HP-UX 11i v3
Version 3 Release Notes: HP 9000 and HP Integrity Servers (in the Getting Started documents)
and the Summary of Changes for Logical Volume Manager in
LVM New Features in HP-UX 11i
v3 (in the White Papers documents) for more information on this LVM feature.
Special considerations for HP-UX 11i v3 prior to Update 3 (March 2008
or earlier)
Additional cleanup commands to be run after the target VM boots are noted below.