Ignite-UX and MirrorDisk/UX

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

Table of Contents

Abstract.............................................................................................................................................. 2

Introduction......................................................................................................................................... 2

Deployment..................................................................................................................................... 2

System Recovery .............................................................................................................................. 2

How to Deploy Mirrored Disk Systems with Ignite-UX ............................................................................... 3

How to mirror the root disk on an HP 9000 system .............................................................................. 3

How to mirror the root disk on an HP Integrity Server ........................................................................... 5

How to Recover Mirrored Disk Systems with Ignite-UX using make_tape_recovery.................................... 8

How to Recover Mirrored Disk Systems with Ignite-UX via make_net_recovery ......................................... 9

An Example config.local File ........................................................................................................... 10

Glossary........................................................................................................................................... 15

For More Information ......................................................................................................................... 15

Summary of content (16 pages)

PAGE 1
Ignite-UX and MirrorDisk/UX Table of Contents Abstract.............................................................................................................................................. 2 Introduction......................................................................................................................................... 2 Deployment .....................................................................................................................................
PAGE 2
Abstract It is a common misconception that Ignite-UX cannot be used with systems containing mirrored disks. While it is true that Ignite-UX does not have any built-in support for mirrored disks, it is not true that Ignite-UX cannot be used on systems with mirrored disks. Ignite-UX is still a very valuable tool for use on systems configured with LVM mirroring. This white paper has two primary goals: 1. Explain benefits and limitations of using Ignite-UX with LVM mirroring. 2.
PAGE 3
• The primary disk has a hardware failure and the mirror also fails before the primary can be replaced. • You are about to update your system to a new operating system release or add new patches to the system. Creating a recovery archive allows you to get back to a working system if the update does not succeed. During such a recovery, Ignite-UX will not automatically re-create the LVM mirrors. The mirrors need to be created via LVM commands or SAM/SMH after the recovery is complete.
PAGE 4
3. The mkboot command must be run on the alternate boot disk so that a copy of the primary and secondary loader (and other things) are placed into the LIF 1 space that was reserved by using the –B option to pvcreate in Step 1. # mkboot /dev/dsk/ 4. Update the boot string in the AUTO file in the LIF on the alternate boot disk. The –lq should be placed in the AUTO file to ensure that the system will attempt to boot without quorum.
PAGE 5
the block disk device of the alternate boot disk. This is to ensure that when software is installed the contents of the boot LIF both disks are updated. # cat /stand/bootconf l /dev/dsk/ After creating an alternate boot disk using LVM, HP recommends you test that it can boot and operates as expected. How to mirror the root disk on an HP Integrity Server 1. Determine the how the current boot disk is currently partitioned.
PAGE 6
answer all of the idisk queries. You may choose not to include this part of the command and answer the question when performing this task interactively. Remove the partition file created previously as follows: # echo yes | idisk -wf /tmp/partitionfile /dev/rdsk/ # rm /tmp/partitionfile 4. After creating the partitions on the disk you will need to create the device files associated with the partitions: # insf –e –H 5. Create the disk as a bootable LVM disk.
PAGE 7
# lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/s2 # lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/s2 # lvextend -m 1 /dev/vg00/lvol4 /dev/dsk/s2 # lvextend -m 1 /dev/vg00/lvol5 /dev/dsk/s2 . . . 10.
PAGE 8
# mkdir /var/HPSP # dd if=/dev/dsk/s3 bs=1024k | gzip > \ > /var/HPSP/.save.gz # dd if=/dev/dsk/s3 bs=1024k | gzip > \ > /var/HPSP/.save.gz Run make_tape_recovery or make_net_recovery ensuring that /var/HPSP (or where you have placed the copies of the HPSP partitions) is included into the recovery archives. After recovery you can then restore the diagnostics as in the following example: # gzcat < /var/HPSP/.save.
PAGE 9
To integrate the configuration of disk mirrors into the recovery process we will be using a feature of the make_tape_recovery command. The make_tape_recovery command automatically includes the /var/opt/ignite/recovery/config.local file, if it exists, into any make_tape_recovery configuration. Caution: If you perform a preview when using these instructions (using the –p option) there is a defect in make_tape_recovery that prevents the config.
PAGE 10
If you already have recovery configurations for this client and would like them to use the config.local file, edit the /var/opt/ignite/clients/0x{LLA}/CINDEX file to include a reference to “recovery/config.local” in all of the configuration clauses. The commands required to configure mirrored disks can be included as a post_config_cmd script, which executes automatically after the system has been restored. After creating or modifying the config.local file, it is recommended you run instl_adm -T -f config.
PAGE 11
cpu=$(/usr/bin/getconf CPU_VERSION) if [ $cpu = 532 ] then CPU=PA else CPU=IA fi # # # # Recreate a mirror of the boot disk. This assumes that the root volume group was mirrored when this configuration was added if this is an initial mirroring the disk does not have to be reduced from the volume group. # CHECK how many Disks in root vg NO_OF_00_DSKS=$(vgdisplay -v vg00 |grep \"PV Name\" |wc -l) if [ $NO_OF_00_DSKS != 2 ] then echo \" This script is designed to work with ignite.
PAGE 12
# Make sure the disk is removed from the group by using vgreduce. echo \" \n\nReducing $DISK2 from vg00.\" vgreduce /dev/vg00 $DISK2 # # # # # Once reduced we need to section the disk with the idisk command the sizes of the EFI and HPSP sections need to match the mirror. This assumes that there is a HP Service Partition (HPSP). If the size of any partition is different the sizes below need to be changed.
PAGE 13
print \"3\nEFI ${EFISIZE}MB\nHPUX 100%\nHPSP ${HPSPSIZE}MB\" >\ /tmp/partitionfile echo \"\n\n Partition file has been create .... Displaying \n\n\" cat /tmp/partitionfile echo \"\n\n Partitioning /dev/rdsk/$PART2 \" idisk -qwf /tmp/partitionfile /dev/rdsk/$PART2 rm /tmp/partitionfile # # # # # After partitioning the disk it needs to have its new device files created for it, we can’t just use insf because Ignite-UX has renamed the device as it probably had another name.
PAGE 14
# Copy the boot area to the disk. Note that mkboot is done to # the whole disk for bot IA and PA but the command is not # the same so ....... if [ $CPU = IA ] then echo \"\n\n Copy the boot area on ${PART2} with mkboot.\" mkboot -e -l /dev/rdsk/${PART2} # Turn off the quorum requirement echo \"\n\n adding hpux -lq to auto_file_string\" echo \"boot vmunix -lq\" > /tmp/AUTO.lq efi_cp -d /dev/rdsk/${PART2}s1 /tmp/AUTO.lq /EFI/HPUX/AUTO echo \"\n\n repeating for the primary boot disk.
PAGE 15
Glossary EFI Extensible Firmware Interface is the firmware interface for HP Integrity systems. It is the name of the first partition on a HP-UX boot disk. HPSP HP Service Partition, which contains the Offline Diagnostics on HP Integrity systems. LIF Logical Interchange Format. For More Information The following relevant documents are available online at the HP Technical Documentation Web site at http://www.docs.hp.
PAGE 16
© Copyright 2006, 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.