Realize new workload migration and consolidation possibilities

15
Validating that the old disks can be updated and reused
• Integrity server disks only, not PA-RISC servers
• Supported storage
• 11i v3 to start with
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. The recommended steps will detail the upgrades and
changes that must be accomplished on the source system, as well as those that must be defined for automatic
consumption during boot of the target system.
Note:
A system administrator may choose to move the actual boot disk from the source system to the target. To do this, the following
changes should be applied to the boot disk rather than to the DRD clone. However, this makes it somewhat more difficult to revert to
the original hardware if issues are encountered. For this reason, the following procedure is described for a DRD clone.
Assumptions for the DRD method
• DynRootDisk is installed on the source system and on the DRD clone of the source system at release B.1131.A.3.6 or
above. This release, supplied with the September 2010 media, includes support for kernel management on the clone
using “
drd runcmd mk_kernel
”, “
drd runcmd kcmodule
” and “
drd runcmd kconfig
” (as well as the previously
supported “
drd runcmd kctune
”).
• The release of HP-UX on the source system is 11i v3.
• The root volume group is managed by LVM.
Summary of steps for the DRD method
In some cases, the goal is to move a pre-existing HP-UX instance to new hardware; in other cases, the goal is to deploy a
very similar (same HP-UX release, same patches, etc.) system with a different network identity (hostname, MAC, and IP
addresses, etc.). The difference between the steps needed for these two scenarios is small, so both scenarios are
covered by these steps. The following steps will be used in both scenarios:
1. Create a DRD clone of the source system on storage that can be moved to the target.
2. Modify file system sizes on the clone if needed.
3. Identify and install additional target software on the clone (see the system Errata document for the new vPar
machine. Errata documentation may be found by a Web search on the system model and the string “Errata”
1
).
4. Determine additional kernel content that is needed on the target (see Step 4 of the “Use the DRD clone to migrate
to new hardware” section of the white paper Migrating an Integrity HP-UX 11i v3 instance to new hardware).
5. Build a kernel on the clone suitable for the target (see step 5 of the “Use the DRD clone to migrate to new
hardware” section of the white paper Migrating an Integrity HP-UX 11i v3 instance to new hardware).
6. Optional: Adjust target kernel tunable parameters.
7. Set the system identity on the clone for boot on the target.
8. Mark the clone LUN for identification from the target EFI.
9. Move scenario: Disable the source system.
10. Move storage.
11. Boot the clone on the target system.
12. Test the target system.
13. If the target does not satisfy expectations, repeat the process, making any necessary adjustments.
1
Note: any software downloaded from the Web must be converted from a depot file to a “standard” depot by using the swcopy command. DRD does not
support running swinstall on a depot file to a clone disk.