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

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.
Overview of the Ignite-UX Recovery Method
The overall approach for the Ignite-UX recovery method 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 identify - 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 between these
similar scenarios, the first is called the
move scenario, and the second is called the clone scenario.
The following migration steps are described in more detail in the remainder of this whitepaper:
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 config to the target config.
4. Clone scenario: Give the target read access to the source recovery archive.
5. Remove or modify the network information for the target.
6. Change a recovery-related variable in control_cfg.
7. Create depots with additional software for the target.
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.
Assumptions for the Ignite-UX Recovery Method
The following assumptions are made in using this method for the migration of a system to new
hardware:
• The HP-UX major release installed on the source system is 11iv3 or above. The use of the
“match” specification when installing an Operating Environment requires 11iv3.
• The target system will run on the same major release running on the source system. The
potential installation of the Operating Environment depot after the restore of the recovery
image requires that the recovery image and Operating Environment depot be the same major
release of HP-UX.