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

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. 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.
Use the DRD clone to migrate to new hardware
Step 1: Create a DRD clone of the source system
The DRD clone must be created on storage that can be moved to the target (such as a SAN LUN or
hot-pluggable SAS disk) and must be supported as a boot device on the target.
To ensure that the latest technology and enhancements are used for creating the DRD clone,
download the most recent release of DRD from http://www.hp.com/go/drd
.
Step 2: Modify file system sizes on the clone if needed
Use /usr/bin/bdf on the source system to determine how fully allocated the source file systems
are. If more free space is desirable, refer to the white paper Dynamic Root Disk: Quick Start and Best
Practices, available at http://www.hp.com/go/drd-docs
for information about resizing clone file
systems.
Step 3: Identify and install additional target software on the clone
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 a
web search of the model and the string “Errata”. There may be both an HP-UX Errata site and a
System Errata site for a given model.
Create one or more depots containing all needed software. It is probably more convenient to create
the depots so that any single depot does not contain multiple versions of the same software.
For example, if the target system is a BL860C i2 system, the Errata document available in May, 2010
indicates that HP-UX 11iv3 OE Update Release for March 2010 and additional software listed in the
document are required. For migration to a BL860C i2 system, it is probably most convenient to
create or use an existing depot containing the Operating Environment (Data Center, Virtual Server,
High Availability, or Base) from March 2010 that you intend to install, and create one or more
additional depots with the remaining software documented in the Errata and applicable to your
environment. Note that software that implements firmware changes cannot be installed on the clone.
Firmware-modifying software must be installed on the target system after the drd rehosting procedure
is complete.
If desired, you can use the swcopy command to copy software from various source depots to one or
more directory depots. Note that if you are copying a serial (tar format) depot, you need to issue the