HP UX System Management Software manual Tape recovery for Itanium-based systems

Page 203

Tape recovery for Itanium-based systems

To boot from tape on an Itanium-based system you must first create a tape boot option on the EFI Boot Manager menu. Verify that your Itanium-based system has firmware support for tape boot. If there is firmware that supports tape boot available for your system, you may first need to upgrade your firmware to make this functionality available. A set of tables showing minimum firmware revisions and SCSI HBAs that support tape boot is available in the Ignite-UX Installation Booting white paper available at

http://www.hp.com/go/ignite-ux-docs.

The first version of Ignite-UX to support native tape boot for Itanium-based systems is C.6.8. Recovery tapes created before that version of Ignite-UX can only be used with two-step recovery. See “Tape recovery with no tape boot support — two-step media recovery” (page 217) for more information on two-step recovery.

The screens shown in this example are from an HP Integrity rx1620 system. Other systems may vary in method and screen format. For information on how to configure boot devices for your system, consult your system’s hardware documentation.

IMPORTANT: Configuring an EFI menu option for tape boot requires downtime since it can only be done from the EFI Boot Manager. If you are going to use tape recovery on your Itanium-based system, consider adding the tape boot option at your next planned maintenance window.

TIP: An ideal time to test tape recovery on your unique combination of system, tape drive, and HBA, is after you have configured an EFI Boot Manager menu option for tape boot. You do not need to recover the system. If you create a recovery tape with the -Ioption, you will enter an interactive recovery. When you get to the interactive screens, reset the system instead of performing a recovery.

Determining the tape drive’s EFI path

When adding a tape boot option to the firmware, you must identify the tape drive you will use for booting. The EFI menus will display device paths to choose from. Before beginning the tape boot configuration process at the EFI level, you must determine the device path to your tape drive so you can select the correct one to use for booting.

The ioscan -ecommand does not report EFI device paths for tape drives. Alternative methods must be used to determine the correct path.

The EFI device path for our example is Acpi(HWP0002,100)/Pci(11)/Scsi(Pun4,Lun0)

One way to identify the tape drive’s path is to use the reconnect -rEFI command to get its SCSI Physical and Logical unit numbers (Pun and Lun). The Pun and Lun numbers can be mapped to the last part of the EFI device path. Below is the output of reconnect -rfor our example.

Figure 100 Output from reconnect -r

Finding the Ultrium tape drive’s Pun and Lun numbers in this example is simple because not many devices are listed.

If your system is partitionable, EFI will not automatically enumerate all connected devices. (This allows for a speedier boot.) For this reason the tape drive you want to use may not be listed. If

System recovery 203

Image 203
Contents Abstract Ignite-UX Administration GuideAcknowledgements Revision HistoryB2355-90849 HP-UX 11.00, 11i v1, 11i v1.6, 11i Contents Complex networks multi-capable servers Complex networks challenges and solutionsManaging I/O for installation and recovery Simple network creating a server for anonymous clientsSecurity Booting and installing HP-UX on clients using the server 110Golden images 151 Customizing your installation 161Automating installations 174 Creating your own boot and installation media 180Support and other resources 224 Recovery 191Terminal keyboard shortcuts 255 Documentation feedback 227 Troubleshooting 228Configuring Dhcp services 236 LIF volume contents 239HP secure development lifecycle Ignite-UX overview Ignite-UX featuresCreate custom installation media One-step installationCustom installations Automated installationsIgnite-UX bundles available in the Ignite-UX product Getting the Ignite-UX softwareIgnite-UX command manpages Ignite-UX commands and manpagesIgnite-UX GUI Introduction to the Ignite-UX GUIView menu File menuActions menu Options menuClient status dialog box How Ignite worksNetwork booting and IP addresses Ignite-UX install environmentBoot sources Installation versus recoveryStartup Phases of operationPA-RISC Systems Itanium-Based SystemsPhase Hardware requirements Ignite-UX server requirementsOther considerations Disk arrays Supported peripheralsDisks and other I/O FirmwareSimple network solutions Making configuration decisions for Ignite serversBoot and install client from media Instlboottab Alternate boot with network server installation For a detailed discussion, see Diagnosing network boot issuesUse DVD media to boot a system for network installation Complex networksSimple network debugging Investigate instlbootd errors in /var/adm/syslog/syslog.logInstlboots allow HP-UX diagnosing and debuggingRDP diagnosing and debugging Ignite Configuring the Ignite-UX server for PA-RISC clientsSimple network creating a server for registered clients Launch Ignite-UXIgnite-UX GUI welcome dialog box Launch the server setup wizardServer setup wizard Register the PA-RISC clients with the server Configure booting IP addressesRegister the Itanium-based clients with the server Configuring the Ignite-UX server for Itanium-based clientsSkip Dhcp setup Go to the software setup sectionSetting up software from OE depots Configuring server options More server setup optionsIgnite-UX server configuration tabs Add Dhcp addresses dialog box Configuring session optionsSession options tab Non-SD software Setting up additional software on the serverExample Create a configuration for compiler software SD softwareSimple network creating a server for registered clients Simple network creating a server for anonymous clients Using the server setup wizardEditing the instlboottab file Itanium-based clients use Dhcp to boot anonymouslyWorking with Dhcp Understanding PXE booting of Itanium-based systemsIgnite-UX server and boot helper setup for Dhcp Page Class-id=PXEClientArch00002IgniteDHCPDeviceGroup Since the install kernel and install file system must beIsolating Ignite-UX from noncontrollable Dhcp servers Dhcpclassid=IgniteDHCPDeviceGroupPage Complex network challenges Complex networks challenges and solutionsHow to use this chapter Remote systems Multiple subnetsMultiple boot servers Avoiding complex network issuesExtend the local subnet Using virtual LANs properly for Ignite-UXAn Ignite-UX server for each subnet Multi-capable server for each subnetAutomating HP-UX OS version selection Complex network solutionsServer selection Directed bootLimit network boot response by network interface address Limit network response by system classInstall remote clients through a network router Control network boot via response timingHaving the client contact the correct server Multiple NICs attach the Ignite server to multiple subnetsGetting the client the correct networking information Ignite-UX bootp boot helper Configuring a Next server boot helper for Integrity systems HP-UX Dhcp PXE Next server boot helper for integrity systemsForwarding boot requests via bootp relay Ha=000000000000\ Hm=000000000000\ Bp=10.2.1.11 Non-HP-UX bootp boot helper Multi-capable subnet boot serverNon-HP-UX Next server boot helper Complex networks multi-capable servers Configuring an RDP server for specific MAC addressesConfiguring an RDP server to delay PXE response Setting up RDP MenuOptions via Windows commands Configuring an RDP server to initiate HP-UX installationSetting up RDP MenuOptions via interactive UI Complex networks multi-capable servers Configuring an RDP server to initiate HP-UX installation Client MAC Addr 00 30 6E 4C AA A5 Using an RDP MenuOption for HP-UXPage SuSE FTP Http RedHat installation from an HP-UX serverThen you must specify the location of Linux install content Configuring an HP-UX server to support Windows installationSuSE installation from an HP-UX server Agile view I/O addressing logic looks like Figure Managing I/O for installation and recoveryIntroducing multipathing Agile view conceptsAgile multiple path I/O stack addressing model Practical considerations System installation configurationIgnite-UX client installation configuration tabs Disk Selection Root Disk Dialog Box With Physical Locations More Info dialog box Disk selection add/remove disks dialog box Support for 2 TB boot diskIdentifying devices for other tasks Important characteristics of the agile viewUNpath Per YH/W evi Persistent DSFs and device matching Recovery and the agile viewLegacy DSFs and device matching Persistent DSF-to-device matching methods by protocol Controlling the I/O configuration processO Configuration variables O Configuration value types Agile view questions and answersAgile view questions and answers Ignite-UX server ports SecurityPort usage initiate LAN boot for Itanium-based clients Winstallfs Kernel BootSequence Makenetrecovery Initiated from Client Port usage makenetrecovery initiated from the clientMakesysimage Initiated from Client Port usage makenetrecovery initiated from the serverRemove or comment-out the following line Enabling Ignite-UX server requirementsRun Bastille Enabling Ignite-UX client requirementsIgnite Product Files Moved in Version C.7.9 and Later Configuring Ignite to replace Tftp with NFSProcedure OverviewWould need to be modified to be Now use instladm to update the install file systemSet up NFS exports and check custom configuration files Use vi to add hploadfileusenfs=true to the fileDisable Tftp on the Ignite-UX server optional For Itanium-based clients the files on the server are Preparing the client for installationWhere release is the release identifier For 64-bit PA-RISC clients the files on the server areBoot using the network Making boot decisions when using the client consoleBoot using media Support? Using bootsys on the client consoleBoot ADMINhelp boot Booting PA-RISC clients from the consoleBooting Itanium-based clients using the network Press Y to save the new boot option Select Add a Boot OptionEnter a brief description for this boot option Enter the data type of this boot optionLAN1 Direct boot profiles for Itanium-based systemsOptions and operands Dbprofile commandSyntax Shell dbprofile or Lanboot commandLanboot select -od optionaldata -dn name ExamplesShell lanboot or Installing HP-UX from the client consoleUser interface and media options Network Configuration with no Dhcp Examples Edit the file Setting 100 Full DuplexSetting Mixed interface types Add this configuration clause to WviinstallfsInstallation using bootsys Booting and installing HP-UX on clients using the serverMethods of installing client systems Touch /.bootsysblock Adding clients Installation using the Ignite-UX GUIPrepare the client for installation Starting Ignite-UXSelect boot release Booting a clientBoot process terminal window Boot confirmation dialog boxNew client displayed in GUI New installation Configuring the installationClient installation configuration interface Initializing the installationBasic tab Functions available from all tabsNo environments note Booting and installing HP-UX on clients using the server All Legacy HW Paths Dialog Box File system default choicesRoot Swap MB... button Languages dialog box Additional Configuration Controls Dialog Box Additional Configuration Controls Dialog Box Software tab Software tab for HP-UX 11i v1 and 11i Marked ? column status can be Software cannot be unselectedChange Depot Location note Interactive swinstall notes System tab Job? x/s/c#nslookup test Set Time Zone dialog box 255.255.248.0 or 0xfffff800 255.255.255.0 or 0xffffff00Set Root Password dialog box Network Services tabs Set DNS Search Domains Dialog Box NIS tab Select an Interface card from the selection list Network Interfaces Dialog BoxAdding or changing a file system configuration Configuring the installation To change, add, or remove a disk from the client Volume requirements for LVM and VxVMHighlight a disk in the selection list to select it Advanced Disk Parameters dialog boxAdvanced File System Parameters dialog box Root volume /, the boot volume /stand, dump volumes Has these characteristicsNo gap is enabled between physical extents within a mirror VolumeFor more information, see manageindex1M Advanced tabRepeat an installation Repeat Install dialog box Executing the installationInstallation Confirmation dialog box Client Status... dialog box Viewing and printing a manifest Installation log filePrintmanifest Creating a golden image Golden imagesAdvantages of golden images Installing critical patches onto the operating system Installing the HP-UX operating systemCreating the golden archive Installing optional softwareInstall the patch non-interactively Customizing the systemOn the golden system, run Localedescription Here are the HP-UX 11i v1 swsource and swsel examples Creating golden image using GUI Creating and using golden images using GUI and CLIOpt/ignite/bin/ignite Xhost +Ignite-UXserverhostnameEnabling the client Creation of a golden image using CLIExamples on using makegoldenimage script Installing the golden image on the client Classes of configuration files Customizing your installationUsing configuration files These install kernels and install file systems are located Configuration File Use and LocationsVar/opt/ignite/data/Relrelease Opt/ignite/data/Relrelease/configVar/opt/ignite/config.local Var/opt/ignite/clients/client/config Combining configuration files using Index entriesConfiguration choices dialog box Defining Disks Example configuration filesDefining Networking Parameters Combining Disks to Form a Single Volume GroupCustomizations based on the client hardware Defining an Installation Depot# 9000/785 Customizations based on user selection# ia64 # ia64 hp workstation zx2000Xpatchsavefiles=falsetrue Avoid archiving patch filesFor more information, see instldbg1M Debugging configuration filesUsing post-installation scripts Example How the installation functionsAdding a post-installation script Where t is for postconfigscript selection settings Using a saved configuration Automating installationsStarting a non-interactive installation with bootsys Using the per-client configuration file Specifying defaults in the config.local fileSetting defaults with instladm Final systemname=system11 Final ipaddrlan0=10.2.75.193 Press Ctrl-D Scheduling installationsSetting installation parameters dynamically Example Instladm -T -f file Checking modified files for errorsPossible tape contents Creating your own boot and installation mediaWhy use custom boot and installation media? Building PA-RISC boot and installation tapeLogical interchange format Possible PA-RISC installation tape layouts#nfssource= Archives and depotsChange the sourcetype attribute from NET to MT PA-RISC installation tape creation exampleAssumptions Sdserver = IPaddress Sddepotdir = /var/tmp/depotInstladm -d -f /var/tmp/lifvol Example PA-RISC installation tape creationInstladm -d -F /var/tmp/lifvol /var/tmp/cfg Verify your changesFile and ISO image size considerations Creating a boot CD/DVD or an installation DVDBoot and archive-based CD/DVDs Assumptions# makeopticaldiscrecovery -? Boot CD/DVD examplesInstallation archive-based DVD examples # makemediainstall -?No DVD available Error messagesCreate a recovery DVD Put a PA-RISC HP-UX 11i v2 golden archive on a DVDMissing -cargument on HP-UX 11i v2 USB DVD drive HP-UX 11i v2 Depot-based installation DVDsDepot-based DVDs No DVD special filesRun mkisofs to create the first DVD image pathtodvd1image For more information, see instladm1M and instladm4Create the first DVD Copy the EFI partition into the first DVD pseudo-rootBurn the DVD images and test them HP-UX 11i v3 Depot-based installation DVDsCreate the second DVD Run mkisofs to create the second DVD image pathtodvd2imageOverview RecoverySystem recovery Use makenetrecovery to System recovery toolsRecovery tool comparison Use maketaperecovery toRecovery image contents Recovery image configuration policies Var/opt/ignite/recovery/archives/client directory Recovery image creation processCreate files and directories for the recovery image Var/opt/ignite/clients/client/recovery/2005-03-17,1119Prepare the configuration file Run the recovery interfaceVar/opt/ignite/clients/client/recovery/defaults Var/opt/ignite/clients/client/recovery directoryExamining recovery image contents Recovery image creation statusOpt/ignite/lbin/listexpander -f archivecontent Init hpignoreswimpact=1 Verifying recovery image resultsRecovery Opt/ignite/recovery/mnressentials Creating and using recovery tapesRecovery tape creation examples Maketaperecovery -A -s myserver -a /dev/rmt/0m Tape recovery for PA-RISC systemsRecovering a minimal operating system Maketaperecovery -x incentire=vg00Determining the tape drive’s EFI path Tape recovery for Itanium-based systemsSelect Boot Configuration from the Boot Menu EFI menu with timerAdd boot entry Boot configurationList of selectable boot devices Enter load options Boot Manager menu with the new option Tape recovery for Integrity Blade systemsShell tapeboot select Fibre-Channel Creating and using network recovery imagesDetermine tape drive EFI path using Command Line Interface Var/opt/ignite/recovery/datetime/recovery.log Network recovery server dependencyNetworking features Adding clients for recoveryXhost +Ignite-UXserverhostname Makenetrecovery -s myserver -x incentire=vg00 Examples of network recovery image creationRecovering using the network for PA-RISC clients Makenetrecovery -s myserverRecovering using the network for Itanium-based clients Hpux Retaining recovery images# rm latest # ln -s RecoveryArchive.sav latest Var/opt/ignite/recovery/config.local Making recovery configuration file additionsUsing the recovery config.local file Var/opt/ignite/clients/client/recovery/config.localOpt/ignite/data/RelB.11.11/config Selecting file systems during recoveryCD/DVD Using the makesysimage method Run # shareall -F nfs Cloning a system using makenetrecoveryQuestion System recovery questions and answersCheck /etc/inetd.conf # rm oldhostname Related information Support and other resourcesContacting HP Websites Typographic Conventions Typographic conventionsFollowing conventions are used in this document Documentation feedback Installing systems with Ignite-UX TroubleshootingErrors and warnings Ignite-UX server problemsIgnite-UX requests more file system space than expected Problem installing clients on multiple subnetsDebugging SD during cold-installation Too much file space neededCorrupted /opt/ignite/boot/bootlif file Booting errors on PA-RISC systemsTftp quit Problems pointing to client over networkApplications hang after igniting Received n bytes in s secondsServer not listed Bootsys Command Seems to Work in ReverseInstalling from golden images Installing from mediaFile size miscalculated Common network booting errorsInsufficient Response to PXE Boot Request File Size miscalculated on HP Integrity virtual machines Creation of archiveOverview of Dhcp services Configuring Dhcp servicesDhcp usage examples Background information on Dhcp design Using bootptab as an alternative to DhcpLIF volume contents For more information, see Classes of configuration files For more information, see Using configuration filesDescription of the files in the LIF volume Using Integrated Lights Out Virtual Media with Ignite-UX 243 Using Integrated Lights Out Virtual Media with Ignite-UX 245 Using Integrated Lights Out Virtual Media with Ignite-UX 247 Using vMedia with DVD installation media and ISO images Expert recovery procedure Expert recoveryExpert recovery preparation Expert recovery Expert recovery procedure Expert recovery Expert recovery procedure # mknod /ROOT/dev/console c 0 HP terminals Terminal keyboard shortcutsBasic keyboard shortcuts Advanced keyboard navigationFunction keys Vt100 terminalsAdvanced keyboard actions See Link Level Address LLA GlossaryChecknetrecovery1M Maketaperecovery. See copyboottape1M Iinstall See instlcombine1M Makebundles1M Maketapenetrecovery See Software Distributor Vinstall Index Setting hplanadminargs, 108 boot sourceIndex DVD Index LVM PXE Port usage on makenetrecovery, 89 port usage with bootsys Page Server display Xntp configuring, 136 screen Xntpd daemon
Related manuals
Manual 40 pages 50.5 Kb Manual 41 pages 43.08 Kb

UX System Management Software specifications

HP-UX System Management Software is a robust suite of tools designed to facilitate the administration and management of HP's Unix-based operating system, HP-UX. As organizations increasingly rely on mission-critical applications, the need for a reliable and efficient management solution becomes paramount. HP-UX provides a comprehensive understanding of system performance, resource utilization, and enterprise-wide configuration, all while maintaining high availability and security.

One of the key features of HP-UX System Management Software is its Advanced System Administrator Toolkit. This toolkit includes a wide array of utilities that streamline daily administrative tasks such as monitoring system performance, managing user accounts, and configuring system settings. Tools such as Glance provide real-time monitoring of system resources, enabling administrators to identify bottlenecks and optimize performance.

The software also boasts an advanced security framework, including features such as Role-Based Access Control (RBAC) and Secure Shell (SSH) for secure data transmission. Security patches and updates can be managed through HP’s Service Pack for HP-UX, which provides a streamlined method for maintaining system integrity and compliance with various regulatory standards.

Another notable aspect is the extensive support for virtualization technologies. HP-UX supports HP’s Integrity Virtual Machines (IVMs) and vPars, allowing administrators to create multiple isolated environments on a single physical server. This not only enhances resource utilization but also improves disaster recovery planning by enabling easier backup and restore processes.

For storage management, HP-UX offers tools that enable easy setup and management of Logical Volume Managers (LVM). This allows simplified disk space allocation and management, ensuring that critical applications have the necessary resources without manual intervention.

Furthermore, HP-UX is designed with compatibility in mind, supporting a wide range of third-party applications and frameworks. Integration with management platforms like HP System Insight Manager enhances the ability to monitor and manage systems from a centralized perspective, providing alerts and reports that help in proactive decision-making.

In summary, HP-UX System Management Software delivers a streamlined approach to system administration, focusing on performance, security, and ease of management. Its advanced features, combined with an emphasis on virtualization and storage management, make it a powerful tool for organizations seeking reliability and efficiency in their Unix-based environments. As businesses continue to evolve, tools like HP-UX will remain crucial for ensuring consistent performance and operational excellence.