| Ignite-UX is a product bundled with HP-UX 11i that provides a process to create a bootable system recovery tape. The tape contains a boot area and an operating system archive. Should your root disk fail or corruption of the root disk take place, you can recover using the bootable system recovery tape. make_recovery is the Ignite-UX tool that is used to create the bootable system recovery tape. make_recovery is being replaced by make_net_recovery at the time of this writing but make_recovery will be used throughout this section because the check_recovery function covered in this section was not yet implemented with make_net_recovery. You could boot and restore from the system recovery tape and then use your system backup to fully restore the system. If your root disk were to fail, in a non-mirrored environment, you would perform the following steps to recover from the failure: Replace the defective root disk. Boot from the recovery tape by selecting the tape device. Monitor the restoration of the operating system archive from the recovery tape. Restore the balance of data on the system with backup information.
The bootable system recovery tape consists of both a Logical Interchange Format (LIF) volume as well as the operating system archive. The LIF volume contains all the components necessary to boot from the tape. The operating system archive contains only the core operating system by default. You can include additional files in the operating system archive, if you wish, using two different techniques. The first is to edit the file /var/opt/ ignite/recovery/makrec.append and add to it the file name, directory name, or software distributor product name you wish to include in the operating system archive. The second technique is to run make_recovery in preview mode with the -p option, manually add files to include and/or exclude from the archive, and resume make_recovery with the -r option. The manual pages for /opt/ignite/bin/make_recovery and /opt/ignite/bin/ignite are online on your HP-UX system. You can also determine whether your recovery tape is up-to-date by using the check_recovery command. Running make_recovery with the -C option produces a system recovery status file. check_recovery compares the system recovery status file to the current state of the system and produces a list of discrepancies. From this list you can determine whether or not you should produce another system recovery tape. The manual page for /opt/ ignite/bin/check_recovery is online on your HP-UX system. The recovery feature is only one component of the Ignite-UX product. Ignite-UX provides a means to install systems over the network by either pushing the installation to a client from an Ignite server or pulling the installation from the Ignite server to the client. With Ignite-UX, "golden images" of your standard installation setup can be created and systems can be set up in a matter of minutes by "igniting" them from this image over the network. More information about Ignite-UX can be viewed on the Internet at http://www.software.hp.com/products/IUX and read about in the "Configuring an Ignite-UX Server" and "Installing from the Ignite-UX Server" chapters as well as Appendix C: "Ignite-UX System Administration" of the Installing HP-UX 11.0 and Upgrading 10.x to 11.0 manual from Hewlett-Packard. The "HP-UX System Recovery" chapter of the same manual gives additional information about the make_recovery feature of Ignite-UX. An Example of Creating a Bootable System Recovery Tape Now that we have covered the basic components and capabilities of the Ignite-UX recovery process, let's look at an example of creating a bootable system recovery tape. Let's first run make_recovery with the -p option so that we can see the way Ignite-UX reports the information it is including on the tape. I'll also use the -A option, which specifies that the entire root volume group is to be included. I sometimes use make_recovery to clone identical systems by producing a recovery tape with the -A option and then loading the tape on systems that I want to be identical to the original system. You would not use the -A option if you have a large root volume group or if you perform normal backups and don't need to include all root volume group information on the recovery tape. In addition to -p for preview and -A for all, I'll also use the -v for the verbose option and -C to create the system status file in the following preview command example: # make_recovery -p -v -A -C *** Previewing only *** Option -A specified. Entire Core Volume Group/disk will be backed up. *************************************** HP-UX System Recovery Validating append file Done File Systems on Core OS Disks/Volume Groups: vg name = vg00 pv_name = /dev/dsk/c0t5d0 vg00 /dev/vg00/lvol3 / vg00 /dev/vg00/lvol4 /home vg00 /dev/vg00/lvol5 /opt vg00 /dev/vg00/lvol1 /stand vg00 /dev/vg00/lvol6 /tmp vg00 /dev/vg00/lvol7 /usr vg00 /dev/vg00/lvol8 /var Create mount points /apps /work /spill /spill2 /rbdisk01 /rbdisk02 /rbdisk03 /rbdisk04 /rbdisk05 /rbdisk06 /rbdisk07 /rbdisk09 /rbdisk10 /rbdisk11 /rbdisk12 /rbdisk13 /rbdisk14 /rbdisk15 /rbdisk16 /rbdisk17 /rbdisk18 /nfs /opt is a mounted directory It is in the Core Volume Group Mounted at /dev/vg00/lvol5 /var is a mounted directory It is in the Core Volume Group Mounted at /dev/vg00/lvol8 Destination = /dev/rmt/0m Boot LIF location = /var/tmp/uxinstlf.recovery *************************************** Preview only. Tape not created The /var/opt/ignite/recovery/arch.include file has been created. This can be modified to exclude known files. Only delete files or directories that are strictly user created. The creation of the System Recovery tape can then be resumed using the -r option. No further checks will be performed by the commands. Cleanup The arch.include file has been produced at this point. This file lists the files that will be part of the archive that you can modify. The following is an abbreviated listing of arch.include, showing just the very beginning and very end of the file: / /lost+found /etc /etc/vue /etc/vue/config /etc/vue/config/types /etc/vue/config/types/tools /etc/vue/config/types/tools/System_Admin /etc/vue/config/types/tools/System_Admin/FontClientSrvr /etc/vue/config/types/tools/System_Admin/SetNetworking /etc/vue/config/types/tools/System_Admin/ShutdownSystem /etc/vue/config/types/tools/System_Admin/VerifyPEX /etc/vue/config/types/tools/System_Admin/VerifyPEX /etc/vue/config/types/tools/Media . . . /spp/scripts/tc_standalone /spp/scripts/sppconsole.old /spp/unsupported /spp/unsupported/cbus /spp/unsupported/clear_pid /spp/unsupported/ex_shm /spp/unsupported/rdr_dumper.fw /spp/unsupported/rdr_formatter /spp/unsupported/reset_jtag /spp/unsupported/scan_sram /users /users/sppuser /users/sppuser/.Xdefaults /users/sppuser/.cshrc /users/sppuser/.kshrc /users/sppuser/.login /users/sppuser/.mwmrc /users/sppuser/.profile /users/sppuser/.x11start /users/sppuser/.x11startlog /users/sppuser/.sh_history /users/sppuser/.sw /users/sppuser/.sw/sessions /users/sppuser/.sw/sessions/swlist.last /users/sppuser/.history /.sh_history /.profile /lib /lib /bin /bin /core /ignite_10.20.tar /var/tmp/makrec.lasttmp /var/opt/ignite/recovery/chkrec.include /var/opt/ignite/recovery/config.recover On the system on which this make_recovery was performed, the arch.include file had over 44,000 lines in it, as shown below: # cat /var/opt/ignite/recovery/arch.include | wc 44142 44146 1730818 Now let's resume make_recovery, which was running in preview mode with the -r option for resume, the -v option for verbose, and the -C option to create the system status file. The -d option will not be specified because the default tape device will be used. The -A option, which was specified earlier in preview mode, specifies that the entire root volume group is to be included. # make_recovery -r -C -v make_recovery(306): In Resume mode. Do you wish to continue?y *************************************** HP-UX System Recovery File Systems on Core OS Disks/Volume Groups: vg name = vg00 pv_name = /dev/dsk/c0t5d0 vg00 /dev/vg00/lvol3 / vg00 /dev/vg00/lvol4 /home vg00 /dev/vg00/lvol5 /opt vg00 /dev/vg00/lvol1 /stand vg00 /dev/vg00/lvol6 /tmp vg00 /dev/vg00/lvol7 /usr vg00 /dev/vg00/lvol8 /var Create mount points /apps /work /spill /spill2 /rbdisk01 /rbdisk02 /rbdisk03 /rbdisk04 /rbdisk05 /rbdisk06 /rbdisk07 /rbdisk09 /rbdisk10 /rbdisk11 /rbdisk12 /rbdisk13 /rbdisk14 /rbdisk15 /rbdisk16 /rbdisk17 /rbdisk18 /nfs /opt is a mounted directory It is in the Core Volume Group Mounted at /dev/vg00/lvol5 /var is a mounted directory It is in the Core Volume Group Mounted at /dev/vg00/lvol8 Destination = /dev/rmt/0m Boot LIF location = /var/tmp/uxinstlf.recovery *************************************** Creating the configuration file. Done Modifying the configuration file. Done Backing up vg configurations Volume Group vg00 Volume Group vg01 Volume Group vg03 Volume Group vg02 Done Creating the /var/opt/ignite/recovery/makrec.last file Done Going to create the tape. Processing tape Invoking instl_adm -T Creating boot LIF Done Writing boot LIF to tape /dev/rmt/0mn Done Creating archive - this may take about 30 minutes. Done System Recovery Tape successfully created. # A system recovery tape has now been produced. You could now boot from the system recovery tape and restore the entire volume group vg00 on this system. Running the check_recovery Command You can run the check_recovery command any time to view the changes that have been made to the system since the last time the system recovery status file was created with the -C option. The following example shows running the check_recovery command: # check_recovery Since the last System Recovery Image was created, the following software product changes have been detected. (Added) Auxiliary-OptB.11.01.01 Auxiliary Optimizer for HP Languages. (Added) OBJCOBOLB.12.50 Object COBOL Developer Since the last System Recovery Image was created, the following system files (or links) have been added to the current system. /apps/informix7.3/lib/iosm07a.sl /apps/informix7.3/lib/ipldd07a.sl /apps/informix7.3/lib/liborb_r.sl /dev/vg13/lvol01 /dev/vg13/rlvol01 /etc/sam/custom/scjjs.cf /etc/sam/custom/scrar.cf /sbin/init.d/flex /sbin/rc2.d/S989flex /usr/lib/iosm07a.sl /usr/lib/iosm07a.sl.980709 /usr/lib/ipldd07a.sl.980709 /usr/lib/liborb_r.sl /usr/local/adm/bin/user_watch.pl /usr/local/adm/etc/rept /usr/local/flexlm/bin/lmcksum /usr/local/flexlm/bin/lmdiag /usr/local/flexlm/bin/lmdown /usr/local/flexlm/bin/lmgrd /usr/local/flexlm/bin/lmhostid /usr/local/flexlm/bin/lmremove /usr/local/flexlm/bin/lmreread /usr/local/flexlm/bin/lmstat /usr/local/flexlm/bin/lmswitchr /usr/local/flexlm/bin/lmutil /usr/local/flexlm/bin/lmver /usr/local/flexlm/daemons/HPCUPLANGS /usr/local/flexlm/licenses/license.dat /usr/local/flexlm/licenses/license.log /usr/share/man/cat1.Z/X.1 /usr/share/man/cat1.Z/Xserver.1 /usr/share/man/cat1.Z/grep.1 /usr/share/man/cat1.Z/mwm.1 /usr/share/man/cat1.Z/xhost.1 /usr/share/man/cat1.Z/xset.1 /usr/share/man/cat2.Z/exec.2 Since the last System Recovery Image was created, the following system files (or links) have been deleted from the current system. /dev/vg13/lvol1 /dev/vg13/rlvol1 /stand/build/conf.o Since the last System Recovery Image was created, the following system files (or links) have been modified on the current system. Current makrec.last ------- ----------- /dev/pty/ttyp2 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/pty/ttyp3 permissions crw--w---- crw-rw-rw- uid 102 0 gid 10 0 /dev/pty/ttyp4 permissions crw--w---- crw-rw-rw- gid 10 0 /dev/pty/ttyp5 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/pty/ttyp6 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/pty/ttyp8 uid 0 2 gid 0 10 /dev/ttyp2 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/ttyp3 permissions crw--w---- crw-rw-rw- uid 102 0 gid 10 0 /dev/ttyp4 permissions crw--w---- crw-rw-rw- gid 10 0 /dev/ttyp5 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/ttyp6 permissions crw-rw-rw- crw--w---- uid 0 102 gid 0 10 /dev/ttyp8 uid 0 2 gid 0 10 /etc/MANPATH checksum 1982379524 497249200 /etc/PATH checksum 562953260 2784298760 /etc/SHLIB_PATH checksum 2664385509 241316845 /etc/fstab checksum 3014086519 200239819 /etc/fstab.old checksum 682979636 2528618126 /etc/group checksum 368341889 127908837 /etc/lvmconf/vg13.conf checksum 1522028984 929609311 /etc/lvmconf/vg13.conf.old checksum 1830986219 3891043243 /etc/lvmtab checksum 4141778997 3277790772 /etc/passwd checksum 1661378396 2350540120 /etc/profile checksum 510591831 2645970599 /stand/build/conf.SAM.c checksum 3973853979 4022316306 /stand/build/conf.SAM.o checksum 4142700410 118504989 /stand/build/conf.o.old checksum 2526740160 1129366190 /stand/build/config.SAM.mk checksum 2849240259 1706527948 /stand/build/function_names.c checksum 2434797998 1240646943 permissions rw-rw-rw- rw-r--r-- /stand/build/function_names.o checksum 3857693076 1165263911 permissions rw-rw-rw- rw-r--r-- /stand/build/space.h permissions rw-rw-rw- rw-r--r-- /stand/build/tune.h checksum 2763942582 2084822502 /stand/dlkm.vmunix.prev/symtab checksum 2086890351 1785861028 permissions rw-r--r-- rw-rw-rw- /stand/dlkm.vmunix.prev/system checksum 3376707916 2873910478 /stand/dlkm/symtab checksum 2368412414 2086890351 permissions rw-rw-rw- rw-r--r-- /stand/dlkm/system checksum 2855591959 3376707916 /stand/system checksum 4141126356 1910321628 permissions rw-rw-rw- r--r--r-- /stand/system.prev checksum 1910321628 253499711 permissions r--r--r-- rw-rw-rw- /stand/vmunix checksum 2977157561 2742478025 /stand/vmunix.prev checksum 2742478025 3594881120 /usr/lib/ipldd07a.sl linkname /apps/informix7.3/lib/ipldd07a.sl /apps/informix/lib/ipldd07a.sl /usr/local/samba.1.9.18p3/var/locks/browse.dat checksum 2594069517 2221092461 /usr/local/samba.1.9.18p3/var/log.nmb checksum 4219117043 2190854115 /usr/local/samba.1.9.18p3/var/log.smb checksum 2251415300 1791314631 /var/spool/cron/crontabs/root checksum 2015828837 1660287231 # This output indicates that many changes have been made to the system, including software additions and system file additions, deletions, and modifications. If check_recovery produces any significant changes to the system, you should rerun the make_recovery command so that the system recovery tape reflects the current state of your system. As a result of completing the procedure covered in this section, many files were produced. Some that you may want to take a look at are in the /var/opt/ignite/recovery directory shown in the following listing: # cd /var/opt/ignite/recovery # ll total 5412 -rw-rw-rw- 1 root sys 1737051 Jul 13 16:17 arch.include -rw-rw-rw- 1 root sys 250 Jul 13 16:12 chkrec.include -rw-rw-rw- 1 root sys 4872 Jul 13 16:17 config.recover -rw-rw-rw- 1 root sys 4872 Jul 13 16:17 config.recover.prev -rw-rw-rw- 1 root sys 1682 Jul 13 16:12 fstab -rw-rw-rw- 1 root sys 390 Jul 13 16:29 group.makrec -r--r--r-- 1 root sys 1971 Jun 25 12:27 makrec.append -r--r--r-- 1 bin bin 1971 Apr 24 00:32 makrec.append.org -rw-rw-rw- 1 root sys 1010844 Jul 13 16:28 makrec.last -rw-rw-rw- 1 root sys 2573 Jul 13 16:29 passwd.makrec | 
