Using Dynamic Root Disk Activate and Deactivate Commands

Transcription

1 Using Dynamic Root Disk Activate and Deactivate Commands Introduction... 2 Using a preview of drd activate to check boot settings... 2 Using a drd clone as an alternate boot disk... 3 On an Integrity System... 3 On a PA-RISC system... 4 Using SoftReboot Feature in DRD Activate... 5 Activating a mirrored clone... 5 Restoring the Primary Bootpath After Activate on a Running System... 5 Preparing For Recovery Without Altering Boot Order... 6 On an Integrity System... 7 On a PA-RISC system For More Information... 11

2 Introduction Dynamic Root Disk (DRD) provides a robust and reliable mechanism for creating, updating, and booting a clone of a running system. The commands drd activate and drd deactivate enable an administrator to choose an image to be booted the next time the system is re-started: An image is said to be activated if it will be booted. A drd activate command activates the inactive image. A drd deactivate command activates the booted image. This functionality overlaps with that supplied by the setboot command, but eliminates the need for an administrator to associate a hardware address specified on a setboot command with a block device special file specified on a drd clone command. (The 11iv3 setboot command accepts a persistent device special file as an argument for the -p option, but the 11iv2 setboot command requires a hardware address.) In the terminology of the setboot command, drd activate sets the boot disk of the inactive image to be the primary boot disk; drd deactivate sets the boot disk of the booted image to be the primary boot disk. The drd activate and drd deactivate commands also provide the extended options -x alternate-bootdisk and -x HA_alternate_bootdisk which correspond to the options -a and -h, respectively, of the setboot command. The argument of each of these drd extended options is a block device special file. The -x HA_alternate_bootdisk is supported on those systems for which the -h option of setboot is supported, that is, on Integrity systems and PA-RISC systems that support hardware partitions. The following examples show how an administrator can use drd activate and drd deactivate to implement various maintenance and recovery strategies. Using a preview of drd activate to check boot settings An administrator may want to check the current settings of the boot disks and see if they would be changed by a drd activate command. The preview ( -p ) option of drd activate displays the current and prospective settings, as shown in the 11iv3 example in Figure 1. Figure 1 drd activate p Command Output == 08/20/07 16:58:16 MDT BEGIN Activate Inactive System Image Preview * Checking for Valid Inactive System Image * Reading Current System Information * Locating Inactive System Image * Determining Bootpath Status * Primary bootpath : 0/4/1/0.0x5000c50000c9842d.0x0 (/dev/rdisk/disk9) before activate. * Primary bootpath : 0/4/1/0.0x5000c50000c9578d.0x0 after activate. * Alternate bootpath : 0/4/1/0.0x5000c50000c9842d.0x0 (/dev/rdisk/disk9) before activate. * Alternate bootpath : 0/4/1/0.0x5000c50000c9842d.0x0 (/dev/rdisk/disk9) after activate. * HA Alternate bootpath : 0/4/1/0.0x5000c50000c9578d.0x0 (/dev/rdisk/disk7) before activate.

3 * HA Alternate bootpath : 0/4/1/0.0x5000c50000c9578d.0x0 (/dev/rdisk/disk7) after activate. == 08/20/07 16:58:32 MDT END Activate Inactive System Image Preview succeeded. Using a drd clone as an alternate boot disk After a drd clone is created, an administrator may not want to activate it until after it has been updated with patches or new software. However, it is convenient to be able to easily boot the clone in the event of a problem with the booted system. To keep the booted system as the primary boot disk but use the clone as the alternate boot disk, the administrator issues the command drd deactivate x alternate_bootdisk=clone_target_block_device_special_file Figure 2 shows the output of the command above on an 11iv2 system, where the clone_target_block_device_special_file is /dev/dsk/c17t2d0. Figure 2 drd deactivate -x alternate_bootdisk=/dev/dsk/c17t2d0 Command Output ======= 08/21/07 01:43:26 MDT BEGIN Deactivate Inactive System Image * Checking for Valid Inactive System Image * Reading Current System Information * Locating Inactive System Image * Determining Bootpath Status * Primary bootpath : 0/4/1/ before deactivate. * Primary bootpath : 0/4/1/ after deactivate. * Alternate bootpath : 0/4/1/ before deactivate. * Alternate bootpath : 0/4/1/ after deactivate. * HA Alternate bootpath : 0/4/1/ before deactivate. * HA Alternate bootpath : 0/4/1/ after deactivate. * Deactivating Inactive System Image ======= 08/21/07 01:43:41 MDT END Deactivate Inactive System Image succeeded. On an Integrity System If the administrator has issued the command in Figure 2, and wants to boot the clone, the alternate boot path may be booted on an Integrity system by interrupting the boot when the message Press Any Key to interrupt Autoboot is issued and choosing HP-UX Alternate Boot in the Boot Menu displayed in Figure 3.

4 Figure 3 Integrity System Boot Menu, Showing HP-UX Alternate Boot Choice / \ / \ System Overview Boot Menu hp server rx3600 HP-UX Primary Boot: 0/4/1/0.. Serial #: USE47059YD HP-UX HA Alternate Boot: 0/4. HP-UX Alternate Boot: 0/4/1/. System Firmware: 2.03 [4648] Core LAN Gb A BMC Version: 5.13 EFI Shell [Built-in] MP Version: F Installed Memory: 4096 MB Boot Configuration System Configuration CPU Logical Security Configuration Module CPUs Speed Status GHz Active \ / GHz Active \ / On a PA-RISC system Similarly, if the administrator has issued the command in Figure 2 on a PA-RISC system and wants to boot the clone, the boot can be interrupted when the following messages are issued: Processor is booting from first available device. To discontinue, press any key within 10 seconds. The administrator can then enter BO ALT when the menu in Figure 4 is displayed. Figure 4 Boot Menu for PA-RISC, Showing Alternate Boot Choice Main Menu Command Description BOot [PRI ALT <path>] Boot from specified path PAth [PRI ALT] [<path>] Display or modify a path SEArch [DIsplay IPL] [<path>] Search for boot devices COnfiguration menu INformation menu SERvice menu Displays or sets boot values Displays hardware information Displays service commands DIsplay Redisplay the current menu HElp [<menu> <command>] Display help for menu or command RESET Restart the system ---- Main Menu: Enter command or menu >

5 Using SoftReboot Feature in DRD Activate SoftReboot feature reduces the operating system reboot time experienced during routine system maintenance. SoftReboot achieves this downtime reduction by skipping the platform hardware reset and booting the next kernel directly from the current operating system instance. The time saved due to SoftReboot solution varies across platforms and different hardware configurations of the same platform. Hence, the down time savings due to SoftReboot are not quantifiable. If a machine is installed with SoftReboot product on supported platform then time can be saved in booting to clone disk. Run swlist to verify if SoftReboot is installed in a machine. swlist grep SoftRebootEnh SoftReboot feature can be used with the following command only. drd activate -x softreboot=true If SoftReboot is not installed on the system, this option is invalid. SoftReboot feature for DRD is supported from HP-UX B fusion release onwards i.e. HP-UX 11iv3 operating system environment. Please check SoftReboot Release note for updated list of supported platforms. Activating a mirrored clone An administrator can use the drd activate command to activate a drd clone and use the clone s mirror as the alternate boot path. Sample commands for creating and activating the clone are shown below: drd clone vv t /dev/dsk/c10t10d0 x mirror_disk=/dev/dsk/c5/t10/d0 \ x overwrite=true drd activate x alternate_bootdisk=/dev/dsk/c5t10d0 Restoring the Primary Bootpath After Activate on a Running System If an inactive system image has been activated, but the administrator no longer wants it to be booted at the next system restart, the drd deactivate command can be used to set the primary bootpath to the current boot disk. The output from the drd activate command includes the before and after bootpaths, as shown in Figure 5.

6 Figure 5 drd activate Command Output ======= 08/21/07 00:58:03 MDT BEGIN Activate Inactive System Image * Checking for Valid Inactive System Image * Reading Current System Information * Locating Inactive System Image * Determining Bootpath Status * Primary bootpath : 0/4/1/ before activate. * Primary bootpath : 0/4/1/ after activate. * Alternate bootpath : 0/4/1/ before activate. * Alternate bootpath : 0/4/1/ after activate. * HA Alternate bootpath : 0/4/1/ before activate. * HA Alternate bootpath : 0/4/1/ after activate. * Activating Inactive System Image ======= 08/21/07 00:58:17 MDT END Activate Inactive System Image succeeded. When drd deactivate is run, the before and after bootpaths are also displayed, as shown in Figure 6. Figure 6 drd deactivate Command Output ======= 08/21/07 01:02:40 MDT BEGIN Deactivate Inactive System Image * Checking for Valid Inactive System Image * Reading Current System Information * Locating Inactive System Image * Determining Bootpath Status * Primary bootpath : 0/4/1/ before deactivate. * Primary bootpath : 0/4/1/ after deactivate. * Alternate bootpath : 0/4/1/ before deactivate. * Alternate bootpath : 0/4/1/ after deactivate. * HA Alternate bootpath : 0/4/1/ before deactivate. * HA Alternate bootpath : 0/4/1/ after deactivate. * Deactivating Inactive System Image ======= 08/21/07 01:02:55 MDT END Deactivate Inactive System Image succeeded. Note that in both examples above the alternate bootpaths are unchanged, and that drd deactivate sets the primary bootpath back to its state before drd activate was run. Preparing For Recovery Without Altering Boot Order A system administrator may wish to keep the primary bootpath for a system set to the current boot disk, the high-availability alternate set to another path to the current boot disk, and the alternate bootpath set to the mirror of the booted system. In such a situation, the administrator does not use the drd activate command. However, it may still be desirable to be prepared to boot the drd clone. In this case, the administrator needs to make a note of the clone s address in the format in which it will appear in the system boot menus.

7 On an Integrity System This EFI (Extensible Firmware Interface) address of the clone can be obtained on an Integrity system by using the -e option on the ioscan command. The address can then be printed or stored on another system. In the event that a boot from the clone is needed, the stored address can be compared to those in the boot menus. Figure 7 below shows the output of an ioscan command on an Integrity system. The administrator needs to note which disk is the drd clone. In the display, the right-most field, Description has been deleted to make Figure 7 easier to read. Figure 7 ioscan -fnekc disk Command Output on an Integrity system (with Description field deleted) Class I H/W Path Driver S/W State H/W Type ========================================================================= disk 0 0/0/2/ sdisk CLAIMED DEVICE /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 5 0/4/1/ sdisk CLAIMED DEVICE /dev/dsk/c17t0d0 /dev/dsk/c17t0d0s3 /dev/rdsk/c17t0d0s2 /dev/dsk/c17t0d0s1 /dev/rdsk/c17t0d0 /dev/rdsk/c17t0d0s3 /dev/dsk/c17t0d0s2 /dev/rdsk/c17t0d0s1 Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002EC9C8D, Lun0)/HD(Part1,Sig409E3CF0-4E18-11DC D6217B60E588)/\EFI\HPUX\HPUX.EFI disk 6 0/4/1/ sdisk CLAIMED DEVICE /dev/dsk/c17t1d0 /dev/dsk/c17t1d0s3 /dev/rdsk/c17t1d0s2 /dev/dsk/c17t1d0s1 /dev/rdsk/c17t1d0 /dev/rdsk/c17t1d0s3 /dev/dsk/c17t1d0s2 /dev/rdsk/c17t1d0s1 Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002EC7671, Lun0)/HD(Part1,SigA76D A-11DC D6217B60E588)/\EFI\HPUX\HPUX.EFI disk 7 0/4/1/ sdisk CLAIMED DEVICE /dev/dsk/c17t2d0 /dev/dsk/c17t2d0s3 /dev/rdsk/c17t2d0s2 /dev/dsk/c17t2d0s1 /dev/rdsk/c17t2d0 /dev/rdsk/c17t2d0s3 /dev/dsk/c17t2d0s2 /dev/rdsk/c17t2d0s1 Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002ECB625, Lun0)/HD(Part1,SigE6A564E4-44BC-11DC D6217B60E588)/\EFI\HPUX\HPUX.EFI disk 8 0/4/1/ sdisk CLAIMED DEVICE /dev/dsk/c17t3d0 /dev/dsk/c17t3d0s3 /dev/rdsk/c17t3d0s2 /dev/dsk/c17t3d0s1 /dev/rdsk/c17t3d0 /dev/rdsk/c17t3d0s3 /dev/dsk/c17t3d0s2 /dev/rdsk/c17t3d0s1 Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002ECB781, Lun0)/HD(Part1,Sig5E644E4E-4E24-11DC D6217B60E588)/\EFI\HPUX\HPUX.EFI #

8 In the event that the administrator needs to boot the drd clone, the system boot can be interrupted when the message Press Any Key to interrupt Autoboot is issued, producing the screen in Figure 8. Figure 8 Boot Menu Obtained by Interrupting the Boot on an Integrity System / \ / \ System Overview Boot Menu hp server rx3600 HP-UX Primary Boot: 0/4/1/0.. Serial #: USE47059YD HP-UX HA Alternate Boot: 0/4. HP-UX Alternate Boot: 0/4/1/. System Firmware: 2.03 [4648] Core LAN Gb A BMC Version: 5.13 EFI Shell [Built-in] MP Version: F Installed Memory: 4096 MB Boot Configuration System Configuration CPU Logical Security Configuration Module CPUs Speed Status GHz Active \ / GHz Active \ / Choosing Boot Configuration displays the screen shown in Figure 9: Figure 9 Boot Configuration Menu for an Integrity System / \ Boot Configuration Boot From File Add Boot Entry Edit Boot Entry Remove Boot Entry Edit OS Boot Order AutoBoot Configuration BootNext Configuration Driver Configuration Console Configuration V \ / Choosing Boot From File initiates a hardware discovery process that displays the screen in Figure 10, containing the Extensible Firmware Interface addresses.

9 Figure 10 Extensible Firmware Addresses / \ File System Explore <IA64_EFI [Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002ECB7... <IA64_EFI [Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002ECB6... <IA64_EFI [Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002EC76... <IA64_EFI [Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002EC76... <IA64_EFI [Acpi(HWP0002,PNP0A03,400)/Pci(1 0)/Sas(Addr5000C50002EC9C... Removable Media Boot [Internal Bootable DVD] Load File [EFI Shell [Built-in]] Load File [Acpi(HWP0002,PNP0A03,300)/Pci(1 0)/Mac(001A4B061860)] Load File [Acpi(HWP0002,PNP0A03,300)/Pci(1 1)/Mac(001A4B061861)] Load File [Core LAN Gb A] Load File [Core LAN Gb B] \ / The administrator can then select the disk that has been noted in the saved ioscan output. The selections EFI, HPUX, and HPUX.EFI are used to complete the boot. The screens are shown in Figure 11. Figure 11 Subsequent Extensible Firmware Interface (EFI) Boot Menus for an Integrity System / \ File System Explore 08/07/07 04:09p <DIR> 4,096 EFI \ / / \ File System Explore 08/07/07 04:09p <DIR> 4, /07/07 04:09p <DIR> /07/07 04:09p <DIR> 4,096 HPUX 08/07/07 04:09p <DIR> 4,096 Intel_Firmware 08/07/07 04:09p <DIR> 4,096 DIAG 08/07/07 04:09p <DIR> 4,096 HP \ / / \ File System Explore 08/07/07 04:09p <DIR> 4, /07/07 04:09p <DIR> /07/07 04:09p 645,215 HPUX.EFI 08/07/07 04:09p 24,576 HPUX.NBP \ /

10 On a PA-RISC system On a PA-RISC system, the system administrator issues ioscan fnkc disk and notes the value in the H/W Path column for the drd clone. Figure 12 shows a sample of ioscan output on a PA- RISC system. The right-most field, Description has been deleted to make Figure 12 easier to read. Figure 12 ioscan -fnkc disk Command Output on a PA-RISC system (Description field deleted) Class I H/W Path Driver S/W State H/W Type ====================================================================== disk 1 0/0/1/ sdisk CLAIMED DEVICE HP /dev/dsk/c1t15d0 /dev/rdsk/c1t15d0 disk 0 0/0/2/ sdisk CLAIMED DEVICE HP /dev/dsk/c3t15d0 /dev/rdsk/c3t15d0 In the event that the administrator wants to boot the drd clone, the boot can be interrupted when the following messages are issued: Processor is booting from first available device. To discontinue, press any key within 10 seconds. The menu in Figure 13 is then displayed. Figure 13 PA-RISC Boot Menu ---- Main Menu Command Description BOot [PRI ALT <path>] Boot from specified path PAth [PRI ALT] [<path>] Display or modify a path SEArch [DIsplay IPL] [<path>] Search for boot devices COnfiguration menu INformation menu SERvice menu DIsplay HElp [<menu> <command>] RESET ---- Main Menu: Enter command or menu > Displays or sets boot values Displays hardware information Displays service commands Redisplay the current menu Display help for menu or command Restart the system The administrator enters SEA to initiate the search for boot devices. When the search is complete, a menu similar to that in Figure 14 is displayed.

11 Figure 14 Boot Menu with Hardware Addresses of Possible Boot Devices Main Menu: Enter command or menu > search Searching for potential boot device(s) This may take several minutes. To discontinue search, press any key (termination may not be immediate). Path# Device Path (dec) Device Path (mnem) Device Type P0 0/0/0/0 lan LAN Module P1 0/0/1/1.15 intscsia.15 Random access media P2 0/0/2/1.15 intscsib.15 Random access media P3 0/6/2/0.8 Random access media Main Menu: Enter command or menu > The administrator compares the boot devices to the saved ioscan output and selects the clone. The command entered is BO Pn where Pn is the clone disk. The administrator then replies N to the prompt Interact with IPL (Y, N, or Cancel)?> and the boot completes. For More Information See the DRD Web site at: Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein , September 2007