Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section describes how to migrate your HP Alpha system to CHARONCharon-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 CHARONall Charon-AXP models.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Collecting information about the

...

source Alpha system

The first step is to determine the exact configuration of your HP Alpha hardware in order to create the CHARONCharon-AXP configuration file that will accurately mimic the hardware.

Turn on your source HP source Alpha system. At the ">>>" prompt, issue a "show device" command:

>>>show device

sys0.0.0.0.0 SYS0 System 0    SYS0     System ROOT Device
ewa0.0.0.1.1 EWA0 F81    EWA0     F8-D1-11-00-67-E6
pka0.0.0.2.1 PKA0 Q1    PKA0     Q-Logic/ISP PCI SCSI HBA
pga0.0.0.3.1 PGA0 WWN 1    PGA0     WWN 1000-0000-0248-C550
pqa0.0.0.15.0 PQA0 ALi 0   PQA0     ALi 1553C Integrated IDE Controller
pqb0.0.1.15.0 PQB0 ALi 0   PQB0     ALi 1553C Integrated IDE Controller
dqa0.0.0.15.0 DQA0 TSSTcorpCDDVDW 0   DQA0     TSSTcorpCDDVDW SH-222BB
dka0.0.0.2.1 DKA0 DEC 1    DKA0     DEC RZ28 (C)DEC
dka100.1.0.2.1 DKA100 DEC 1  DKA100   DEC RZ22 (C)DEC
dka200.2.0.2.1 DKA200 DEC 1  DKA200   DEC RZ23 (C)DEC
mka600.6.0.2.1 MKA600 Virtual 1  MKA600   Virtual SCSI Tape

>>>



Div
classpagebreak


...

Div
classpagebreak


The source HP Alpha peripheral configuration in this example is:

...

Now collect some general information about the HP AlphaServer ES40 system:

>>>show cpu /full

System: PFCAXP, AlphaServer ES40 6/667

SMP execlet = 3 : Enabled : Streamlined.
Config tree = None
Primary CPU = 0
HWRPB CPUs = 4
Page Size = 8192
Revision Code =
Serial Number = SN01234567
Default CPU Capabilities:
System: QUORUM RUN
Default Process Capabilities:
System: QUORUM RUN

....

>>>

...

So the collected information about the HP AlphaServer ES40 system is:

...

Info

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:

>>>show config

...

PCI Bus

Bus 00 Slot 03: DECchip 21142 Network Controller
ewa0.0.0.3.0 00-00-F8-03-9A-6D

Bus 00 Slot 07: Cypress PCI Peripheral Controller

Bus 00 Slot 07: Function 1: PCI IDE

Bus 00 Slot 07: Function 2: PCI IDE

Bus 00 Slot 07: PCI USB

Bus 00 Slot 08: DECchip 21052 PCI to PCI Bridge

Bus 01 Slot 08: ISP1040 Scsi Controller
pka0.7.0.1008.0 SCSI Bus ID 7
dka0.0.0.1008.0 RZ2DD-KS
dka400.4.0.1008.0 RRD45

>>>

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.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Creation of

...

Charon-AXP configuration file

Using the above information, the following configuration can be created:

#
# HP # AlphaServer model: AlphaServer ES40 6/667
#

set session hw_model = AlphaServer_ES40
set ace cpu_architecture = EV67
set rom dsrdb[0] = 1820 system_name = "AlphaServer ES40 6/667"

...

#
# Override default System Serial Number, set it to "SN01234567"
#

set rom system_serial_number = SN01234567

#
# Specify RAM size: 512 Mb
#

set ram size=512

#
# Map OPA0 console to the xtem from which CHARON-AXP runs
#

set COM1 alias=OPA0 line=(console)

#
# Connect the emulator's DQA0 to the host's ATAPI CD/DVD-ROM drive.
#

set ide container="/dev/cdrom"

#
# Load optional DE500BA PCI Ethernet Adapter (EWA0) and map it to the "eth1" host network interface
#

load DE500BA/dec21x4x EWA interface=EWA0
load packet_port/chnetwrk EWA0 interface="eth1"

#
# Load DEC-KZPBA SCSI controller and map it to 3 disk containers and 1 tape container
#

load KZPBA PKA scsi_id = 7

set PKA container[0] = "/my_disks/bootable.vdisk"
set PKA container[100] = "/my_disks/RZ22.vdisk"
set PKA container[200] = "/my_disks/RZ23.vdisk"

set PKA container[600] = "/my_tapes/my_tape.vtape" 

#
# Load DEC-KGPSA-CA PCI FC adapter and map it to a disk container
#

load KGPSA FGA

set FGA container[0] = "/my_disks/RZ24.vdisk"

...

...

In our example, possible mappings of the KZPBA SCSI controller include disk and tape images. Tape images do not have not to be manually created whereas you have to provision disk images, as described below.

Our The example below 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 spaceYou should avoid the temptation to create identically-sized virtual disks, and regard the migration as an opportunity to create larger virtual disks than the original disks, if needed. Of course, if you increase the size of the disks, you will have to migrate a logical backup ("VMS Backup") of the filesystem, as opposed to a physical backup of the original disk.

Create special directories for storing disk and tape images, as needed. These directories are referenced in the sample configuration file above.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Installation of

...

Alpha operating system

The next step is to transfer the data from the source HP Alpha system to CHARONCharon-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 CHARONCharon-AXP disk image or physical disk.

The example configures the CHARONCharon-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):

#
# DEC-KZPBA SCSI controller is mapped to 5 disk containers; one of them (DKA300) - for migration purposes;
# another one (DKA400) - for installation of fresh HP OpenVMS system from distributive

#

load KZPBA PKA scsi_id = 7

set PKA container[0] = "C:\my_disks\bootable.vdisk"
set PKA container[100] = "C:\my_disks\RZ22.vdisk"
set PKA container[200] = "C:\my_disks\RZ23.vdisk"
set PKA container[300] = "C:\my_disks\migration.vdisk"
set PKA container[400] = "C:\my_disks\fresh_openvms.vdisk"

#
# CD-ROM for HP OpenVMS installation (DQA0)
#

set ide container="/dev/cdrom"

...

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.

Div
classpagebreak


Run CHARONCharon-AXP and boot from the CDROM named "dqa0" ("migration.cfg" is the configuration file we use in this example):

$ es40.exe migration.cfg

initializing ...

polling for units on kzpba0, slot 2, bus 0, hose 1 ...
pka0.0.0.2.1 PKA0 Q-Logic/ISP PCI SCSI HBA

... enter console

CHARON-AXP/ES40 for Linux (AlphaServer ES40 6/667), Version 4.11.20403
(C) 2009-2020 STROMASYS SA.
All rights reserved.

P00>>>boot dqa0

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$ "'s prompt is "newvms$ ".

Note: The qualifier /NOHIGH is used here since highwater marking is no generally required for these operations as the disk will be overwritten by the savesets.  This will speed up the process significantly.

newvms$ INIT/NOHIGH DKA300: SCRATCH
newvms$ MOUNT/SYSTEM/NOASSIST DKA300: SCRATCH

...

Now we are ready to create disk backups from the source HP Alpha system to CHARONCharon-AXP.

Boot the CHARONCharon-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.

(info) The use of the "SHOW DEVICE /FILES" command would be of help to know files opened on a disk

Let's assume the CHARONCharon-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 CHARONCharon-AXP virtual machine will contain 3 savesets: "DKA0.BCK", "DKA100.BCK" and "DKA200.BCK"

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Restore backups to

...

Charon-AXP disks

Next, restore the new savesets to their corresponding virtual disks. Login to CHARONCharon-AXP and issue this sequence of commands to restore all the savesets created in the previous step:

...

If you are going to have the CHARONCharon-AXP and the original physical HP Alpha on the network at the same time, you must change the network identity of one (usually the CHARONCharon-AXP).

The easiest way is to boot the CHARONCharon-AXP virtualized system on the restored system disk with the network disabled and to configure new addresses, as needed.

(info) The NIC can be disabled with a "disabled" statement in the CHARON the Charon configuration file.

Then Enable the network and reboot.

...

  • Connect a SCSI tape drive to the CHARONCharon-AXP host via a PCI card 
    • Map the tape drive in the CHARONCharon-AXP configuration file

           a. Restore the source HP Alpha system backups from tape to disk images via OpenVMS running on CHARONCharon-AXP.
           b. Boot from standalone backups and restore the content to CHARONto 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 CHARONCharon-AXP virtual disks.
           b. Boot from standalone backups and restore the content to CHARONto Charon-AXP virtual disks.
  • Create a network cluster between the source HP Alpha system and CHARONCharon-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:


...