Realize new workload migration and consolidation possibilities

16
Overview of the Ignite-UX recovery method
The overall approach used here is to deploy an Ignite-UX recovery archive of the HP-UX instance running on older
hardware, called the source system, to the new system, called the target. The recommended steps detail the upgrades
and changes that must be accomplished on the source system prior to creating the recovery archive, on the Ignite-UX
server after the recovery archive is created, and during boot of the target system.
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 system—same HP-UX release, same patches, etc.—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 here. To distinguish these similar scenarios, the first is called the move scenario, and the second is called the
clone scenario.
Assumptions for the Ignite-UX recovery method
It is assumed that the HP-UX major release installed on the source system is 11i v3. The use of the “match” specification
when installing an Operating Environment requires 11i v3.
Summary of steps for the Ignite-UX recovery method
1. Install the latest IGNITE bundle on the Ignite-UX server.
2. Make a recovery archive of the source system.
3. Copy the source client configuration to the target configuration.
4. Clone scenario: Give the target read access to the source recovery archive.
5. Remove or modify the network information for the target (see Step 5 of the “Detailed Migration Steps for the
Ignite-UX Recovery Method” chapter of the white paper Migrating an Integrity HP-UX 11i v3 instance to new
hardware).
6. Change a recovery-related variable(s) in control_cfg (see Step 6 of the “Detailed Migration Steps for the Ignite-UX
Recovery Method” chapter of the white paper Migrating an Integrity HP-UX 11i v3 instance to new hardware).
7. Create depots with additional software for the target (see the HP-UX Errata for your target server).
8. Ensure iux_postload scripts from the recovery archive run correctly.
9. Create config files for the depots.
10. Add the new config files to the target CINDEX.
11. Modify file system sizes if needed.
12. Check configuration syntax.
13. Move scenario: Disable the source system.
14. Deploy the configuration to the target system.
15. Boot and test the target system.
16. If the target is not as desired, return to the source system, and make adjustments as necessary.
Post migration steps
Confirm successful vPar boot and data visibility
You can boot and install a virtual partition in several ways. If you have assigned pre-installed boot disks, a physical DVD
drive with the installation disk in it, or an ISO image of an installation disk, then you simply enter:
# vparboot –p {vpar_name}
# vparconsole –p {vpar_name}
and interact with the EFI prompts in the same way you would on a standalone system:
Shell> fs0:
fs0:\> hpux