Migration to CHARON-AXP for Linux
Table of Contents
Introduction
This section describes how to migrate your HP Alpha system to CHARON-AXP. We will use a sample HP AlphaServer ES40 system running OpenVMS to demonstrate the migration procedure. This chapter also contains some instructions for Tru64 UNIX, but it mainly concentrates on how to migrate OpenVMS hosts. The process is similar for all CHARON-AXP models.
Collecting information about the source HP Alpha system
The first step is to determine the exact configuration of your HP Alpha hardware in order to create the CHARON-AXP configuration file.
Turn on your source HP Alpha system. At the ">>>" prompt, issue a "show device
" command:
>>> |
To get more detailed information, boot OpenVMS and issue a "show device /full" command:
Disk PFCAXP$DKA0:, device type RZ28, is online, mounted, file-oriented device, Disk PFCAXP$DKA100:, device type RZ22, is online, file-oriented device, Disk PFCAXP$DKA200:, device type RZ23, is online, file-oriented device, Disk PFCAXP$DQA0:, device type TSSTcorpCDDVDW SH-222BB, is online, file-oriented Disk $1$DGA0: (PFCAXP), device type RZ24, is online, file-oriented device, Magtape PFCAXP$MKA600:, device type Virtual SCSI Tape, is online, file-oriented Terminal OPA0:, device type VT102, is online, record-oriented device, carriage Device EWA0:, device type DE500, is online, network device, device is a template Device FGA0:, device type KGPSA Fibre Channel, is online, shareable, error Device PGA0:, device type SCSI FCP, is online, error logging is enabled. ... Device PKA0:, device type Qlogic ISP1020 SCSI port, is online, error logging is Device $1$GGA32767:, device type Generic SCSI device, is online, shareable. $ |
In case of Tru64 UNIX V5 running on the host system it is recommended to use the following commands to get information on the host configuration:
Command | Description | |
---|---|---|
| Get detailed information about the host hardware configuration | |
| Get specific information about the host SCSI controllers and attached disks | |
| Get information about the host controllers |
Please reference to the Tru64 UNIX User's Guide for more details.
The source HP Alpha peripheral configuration in this example is:
Controller | Devices on controller | Description |
---|---|---|
KZPBA | -DKA0 (RZ28) | SCSI disk/tape controller |
KGPSA-CA | -DGA0 (RZ24) | FC disk controller |
OPA0 | System console | |
-DQA0 | IDE CD-ROM controller | |
EWA0 | Network interface, MAC address: "F8-D1-11-00-67-E6" |
Now collect some general information about the HP AlphaServer ES40 system:
>>> |
>>> |
So the collected information about the HP AlphaServer ES40 system is:
Component | Value |
---|---|
System Type | AlphaServer ES40 6/667 |
Serial Number | SN01234567 |
Number of CPUs | 4 |
System memory | 512 Mb |
In some particular situations it is also important to know the exact placement of all the peripheral devices on HP Alpha PCI bus. To get that information issue a "show config" command at ">>>" prompt of HP Alpha console, for example:
>>> |
The "show config" command collects the following information of placement of peripheral devices on PCI bus:
- Bus number
- Slot number
- Function number
To find out the exact types of controllers and other useful information refer to the source HP Alpha system documentation.
Creation of CHARON-AXP configuration file
Using the above information, the following configuration can be created:
|
Making disk images
In our example, possible mappings of the KZPBA SCSI controller include disk and tape images. Tape images have not to be manually created whereas you have to provision disk images, as described below.
Our example creates disk images of the original physical type. In reality, this step is the best opportunity in the migration to provision larger disks to get extra storage space.
Create special directories for storing disk and tape images, as needed. These directories are referenced in the sample configuration file above.
$ mkdir /my_disks $ mkdir /my_tapes |
Next, create the disk images using the "mkdskcmd" utility:
|
Installation of HP Alpha operating system
The next step is to transfer the data from the source HP Alpha system to CHARON-AXP. The easiest way to do this is via backups over the network. For this operation we need a bootable, network-enabled operating system on a CHARON-AXP disk image or physical disk.
The example configures the CHARON-AXP AlphaServer ES40 system for installation of HP OpenVMS from a distribution CD-ROM (usually it is "/dev/cdrom" if the host has only one CD-ROM drive):
|
DKA300 will be the disk where all the source disks will be copied so its size needs to be large enough to store all the disk backup images.
Create an empty disk image for installation of HP OpenVMS and another one for storing backups from the source HP Alpha system as it is shown in the section above.
Run CHARON-AXP and boot from the CDROM named "dqa0" ("migration.cfg" is the configuration file we use in this example):
|
Install HP Alpha/VMS including DECnet on "dka400". The DECnet address must belong to the same area as the source HP Alpha system.
Login to the newly installed OpenVMS system and initialize the disk intended for backups storage. Let's assume it's prompt is "newvms$
".
|
Making remote backups
Now we are ready to create disk backups from the source HP Alpha system to CHARON-AXP.
Boot the CHARON-AXP virtual machine and make sure that the source HP Alpha system is reachable via DECnet.
Login to the source HP Alpha system, stop all the batch queues, kick off the users, stop all applications and close databases if any. The commands listed in the SYS$MANAGER:SYSHUTDWN.COM file may be helpful. The goal is to close as many files as possible. The system disk will have several files opened (pagefile, swapfile, etc.), this is a normal situation.
The use of the "SHOW DEVICE /FILES" command would be of help to know files opened on a disk
Let's assume the CHARON-AXP system is node 1.400 in this example. Issue then the following commands from the source HP Alpha whose prompt is set to "source$
":
|
When the backup procedure will be completed, the disk "DKA300" of the CHARON-AXP virtual machine will contain 3 savesets: "DKA0.BCK", "DKA100.BCK" and "DKA200.BCK"
Restore backups to CHARON-AXP disks
Next, restore the new savesets to their corresponding virtual disks. Login to CHARON-AXP and issue this sequence of commands to restore all the savesets created in the previous step:
|
If you are going to have the CHARON-AXP and the original physical HP Alpha on the network at the same time, you must change the network identity of one (usually the CHARON-AXP).
The easiest way is to boot the CHARON-AXP virtualized system on the restored system disk with the network disabled and to configure new addresses, as needed.
The NIC can be disabled with a "disabled" statement in the CHARON configuration file.
Then Enable the network and reboot.
Alternative ways of data transfer
Some alternative methods of data transfer are also possible. For example:
- Connect a SCSI tape drive to the CHARON-AXP host via a PCI card
- Map the tape drive in the CHARON-AXP configuration file
a. Restore the source HP Alpha system backups from tape to disk images via OpenVMS running on CHARON-AXP.
b. Boot from standalone backups and restore the content to CHARON-AXP virtual disks. - Dump the source HP Alpha system backups to tape images with the "mtd" utility and:
a. Boot from the freshly installed OpenVMS system and restore the tape images to CHARON-AXP virtual disks.
b. Boot from standalone backups and restore the content to CHARON-AXP virtual disks.
- Map the tape drive in the CHARON-AXP configuration file
Create a network cluster between the source HP Alpha system and CHARON-AXP (it is possible to use the source system as a boot server) then perform backups from one disk to another:
$ BACKUP/IMAGE/IGNORE=INTERLOCK REAL$DKA0: DKA0:
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.