Migrating an Integrity HP-UX 11iv3 Instance to New Hardware

ManualsBrandsHP ManualsSoftwareHP-UX 11i v3 Foundation OE

Migrating an Integrity HP-UX 11iv3

Instance to New Hardware

August 2011

Technical white paper

Contents

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

Overview of the DRD method ................................................................................................................ 3

Assumptions for the DRD method ........................................................................................................... 3

Related Information .............................................................................................................................. 3

Summary of Steps for the DRD method ................................................................................................... 3

Use the DRD clone to migrate to new hardware....................................................................................... 4

Step 1: Create a DRD clone of the source system ................................................................................. 4

Step 2: Modify file system sizes on the clone if needed......................................................................... 4

Step 3: Identify and install additional target software on the clone ......................................................... 4

Step 4: Determine additional kernel content that is needed on the target ................................................ 5

Step 5: Build a kernel on the clone suitable for the target ...................................................................... 5

Step 6 (Optional): Adjust target kernel tunables if needed ..................................................................... 6

Step 7: Set the system identity on the clone for boot on the target .......................................................... 7

Step 8: Mark the clone LUN for identification from the target EFI ........................................................... 7

Step 9: Move scenario: Disable the source system ............................................................................... 7

Step 10: Move storage ..................................................................................................................... 8

Step 11: Boot the clone on the target system ....................................................................................... 8

Step 12: Test the target system ........................................................................................................... 8

Step 13: If not successful, revise and repeat. ....................................................................................... 9

Overview of the Ignite-UX Recovery Method ............................................................................................ 9

Assumptions for the Ignite-UX Recovery Method ....................................................................................... 9

Related Information ............................................................................................................................ 10

Detailed Migration Steps for the Ignite-UX Recovery Method ................................................................... 10

Step 1: Install the latest IGNITE bundle on the Ignite-UX server ............................................................. 10

Step 2: Make a recovery archive of the source system ........................................................................ 10

Step3: Copy source client config to the target config .......................................................................... 11

Step4: Clone scenario: Give the target read access to source recovery archive ..................................... 12

See the manpages dfstab(4) and share_nfs(1M) for more information. ....................................... 12

Step 5: Remove or modify the network information for the target ......................................................... 12

Step 6: Change a recovery-related variable in control_cfg ............................................................ 13

Step 7: Create depots with additional software for the target .............................................................. 14

Step 8: Ensure iux_postload scripts from the recovery archive run correctly ........................................... 14

Step 9: Create config files for the new depots ................................................................................... 16

Step 10: Add the new config files to the target CINDEX ..................................................................... 17

Step 11: Modify file system sizes if needed ....................................................................................... 18

Step 12: Check configuration syntax ................................................................................................ 18

Step 13: Move scenario- Disable the source system ............................................................................ 18

Step 14: Deploy the configuration to the target system ....................................................................... 18

Step 15: Boot and test the target system. .......................................................................................... 19

Step 16: Return to the source, if the target is not as desired ................................................................. 19

Call to action .................................................................................................................................... 20

Summary of content (20 pages)

PAGE 1
Migrating an Integrity HP-UX 11iv3 Instance to New Hardware August 2011 Technical white paper Contents Introduction ......................................................................................................................................... 2 Overview of the DRD method ................................................................................................................ 3 Assumptions for the DRD method ..................................................................................
PAGE 2
Introduction Customers often find that they want to move an existing instance of an HP-UX installation to new hardware. The change may be to a new computer model or to a system of the same model with additional I/O or networking capacity. The move may provide greater compute capacity, more expansion for the future, lower power and cooling costs, and better use of data center real estate.
PAGE 3
If this is your situation Consider using this method: If you are moving from PA to IPF Install the new system from depots. Overview of the DRD method The overall approach used here is to create a DRD clone on an older “source” system, modify it to support the new “target” system model, and move it to the new target system.
PAGE 4
1. Create a DRD clone of the source system on storage that can be moved to the target. 2. Modify the file system sizes on the clone, if needed. 3. Identify and install additional target software on the clone. 4. Determine additional kernel content that is needed on the target. 5. Build a kernel on the clone suitable for the target. 6. Optional: Adjust target kernel tunables, if needed. 7. Set the system identify on the clone for boot on the target. 8.
PAGE 5
swcopy command from the system containing the serial depot. See swcopy (1M) for more information. Once the target software has been included in accessible depots, install it to the clone.
PAGE 6
#!/usr/bin/sh # # merge_system_files - Merges system file from new hardware # into system file on source clone # $1 - system file from new hardware to be merged into # system file on DRD clone. # typeset -i module_found system_new_hw=$1 system_merged=/var/opt/drd/mnts/sysimage_001/stand/system cp -p ${system_merged} ${system_merged}.
PAGE 7
Step 7: Set the system identity on the clone for boot on the target This step is ordinarily needed for both the “move” and “clone” scenarios, since the MAC address(es) on the target will differ from those on the source. (The exception to this is the case where your MAC addresses have been virtualized through Virtual Connect, and you are moving the VC profile to the new system.) To set the identity of the target (hostname, mapping of IP addresses to network interfaces, language, time zone, etc.
PAGE 8
Step 10: Move storage Use the interface to the SAN storage management (or move a hot-pluggable disk) to move the clone from the source system to the target. Depending on your system setup and whether you are executing a “move” or “clone” scenario, you may also want to move additional non-boot storage to the clone. Step 11: Boot the clone on the target system By default, the EFI screens do not usually display SAN LUNs unless they are already known to be boot disks.
PAGE 9
You may also want to run /usr/sbin/setboot to set the primary bootpath to the current boot disk as determined by vgdisplay. On the next reboot, you can speed up subsequent boots by using the steps above to reset EFIFCScanLevel back to 0. Step 13: If not successful, revise and repeat. If the target system does not work as expected, the target can be shutdown or removed from the network and the source system rebooted. Additional software or kernel content can be installed and the procedure repeated.
PAGE 10
For example, if the source is running 11iv3, the target must support 11iv3 as well. The target may need a newer revision of 11iv3, such as the March 2010 release, but not a new major release of HPUX. Related Information Additional information regarding Ignite-UX can be obtained from the Ignite-UX documentation web site, http://www.hp.com/go/ignite-ux-docs.
PAGE 11
For example, if the Ignite-UX server hostname is ignsvr, the command would be: /opt/ignite/bin/make_net_recovery -s ignsvr -A For more information about creating recovery archives, see the “Recovery” chapter of the Ignite-UX Administration Guide for HP-UX 11i, available at http://www.hp.com/go/Ignite-ux-docs. Step3: Copy source client config to the target config To make the following changes, log-in to the Ignite-UX server as root.
PAGE 12
Step4: Clone scenario: Give the target read access to source recovery archive In the move scenario, the source and target systems have the same hostname, so the target system already has network access to the recovery archive. If the Ignite-UX server is running 11i v3 or later, edit the /etc/dfs/dfstab file to allow access to both the source and target clients as follows: 1. Open the dfstab file: #vi /etc/dfs/dfstab 2.
PAGE 13
when the target system is deployed, either by specifying it directly on Ignite-UX menus, or by choosing on the menus to supply the information when the system is first booted. To remove the pre-existing network information, edit /var/opt/ignite/clients//recovery/latest/system_cfg to remove the _hp_custom_sys stanza. Alternatively, the stanza may be commented out by inserting “#” in column 1 of the lines it contains.
PAGE 14
else { init _HP_CLONING = "TRUE" } To: init _HP_CLONING = "TRUE" Step 7: Create depots with additional software for the target The target system may need additional software, particularly if the system differs greatly from the source. To ensure that all needed kernel modules, as well as any other required software, are available, consult the Errata document for the target system. The Errata document can be found by searching the web for the model and the string “Errata”.
PAGE 15
#!/bin/sh IPD_DIR=/var/adm/sw/products IUX_SCRIPT_NAME=iux_postload /usr/bin/find ${IPD_DIR} -name ${IUX_SCRIPT_NAME} | while read script_path do echo " Running ${script_path} .... " ${script_path} # Need to leave a harmless script named iux_postload # for IUX to run later. /usr/bin/mv ${script_path} ${script_path}.
PAGE 16
Create a config file, /var/opt/ignite/clients//run_iux_postloads_cfg, as shown in Figure 4 that runs the scripts listed in Figures 2 and 3.
PAGE 17
The specification of “%match” installs software and patches in the OE that match software that was included in the recovery archive. The specification of “load_order=2” ensures that the depot is processed after the recovery archive and the execution of the iux_postload scripts. You can use any value for category_tag other than “HPUXEnvironments”, which has special meaning and is already used for the recovery archive.
PAGE 18
Step 11: Modify file system sizes if needed Ordinarily, the update using the errata depot will not substantially increase the required file system sizes. Rather than try to predict exactly the file system sizes needed, it is more convenient to ensure that all file systems have some “growing space”. Use /usr/bin/bdf on the source system to check for file systems are close to full and need additional space.
PAGE 19
From the Ignite-UX installation screens, choose the configuration that was created in the previous steps. If the system is being cloned, specify the correct configuration (hostname, IP address, etc.) that is used for the target system. Step 15: Boot and test the target system. Determine whether additional data volumes need to be made available to the target. For example, additional SAN LUNs may need to be presented to the target and vgimported on the target system.
PAGE 20
Call to action HP welcomes your input. Please give us comments about this white paper, or suggestions for related documentation, through our technical documentation feedback website: http://www.hp.com/bizsupport/feedback/ww/webfeedback.html © 2011 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.