Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: one table migrated to fixed width

Anchor
TopMigrationPageTOCTopMigrationPage
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Table of Contents

Table of Contents
excludeTable 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. The process is similar for all CHARON-AXP models.

...

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

Creating CHARON Virtual Machine

As a first step it is required to create a CHARON Virtual Machine (VM) using the CHARON Virtual Machines Manager in the following way:

Press the "Create VM from Template" button:

Image RemovedImage Added

Specify the HP Alpha model to be emulated and the name of the VM , then press the "Create" button. :

Image Added

The VM will be created:

Image RemovedImage Added

Select the VM from the left pane and switch to the "VM Configuration" tab.

Press In order to reproduce the target HP Alpha configuration, press the "Edit Configuration file" button:

Image Removed

...

Image Added

(info) Alternatively it is possible to select the target CHARON VM and press the "Edit Configuration" button.

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

Div
classpagebreak

Collecting information about the source HP Alpha system

The next step is to determine the exact configuration of your the HP Alpha hardware in order to create the CHARON VM configuration file.

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

>>>show device

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

>>>


Div
classpagebreak


To get more detailed information, boot OpenVMS and issue the "show dev device /full" command:

$ show device /full

Disk

PFCAXP$DKA0:,

device

type

RZ28,

is

online,

mounted,

file-oriented

device,

shareable,

available

to

cluster,

error

logging

is

enabled.
...

Disk

PFCAXP$DKA100:,

device

type

RZ22,

is

online,

file-oriented

device,

shareable,

available

to

cluster,

error

logging

is

enabled.
...

Disk

PFCAXP$DKA200:,

device

type

RZ23,

is

online,

file-oriented

device,

shareable,

available

to

cluster,

error

logging

is

enabled.
...

Disk

PFCAXP$DQA0:,

device

type

TSSTcorpCDDVDW

SH-222BB,

is

online,

file-oriented

device,

shareable,

available

to

cluster,

error

logging

is

enabled.
...

Disk

$1$DGA0:

(PFCAXP),

device

type

RZ24,

is

online,

file-oriented

device,

shareable,

available

to

cluster,

error

logging

is

enabled.
...

Magtape

PFCAXP$MKA600:,

device

type

Virtual

SCSI

Tape,

is

online,

file-oriented

device,

available

to

cluster,

error

logging

is

enabled,

device

supports

fastskip

(per_io).
...

Terminal

OPA0:,

device

type

VT102,

is

online,

record-oriented

device,

carriage

control.
...

Device

EWA0:,

device

type

DE500,

is

online,

network

device,

device

is

a

template

only.
...

Device

FGA0:,

device

type

KGPSA

Fibre

Channel,

is

online,

shareable,

error

logging

is

enabled.
...

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

enabled.
...

Device

$1$GGA32767:,

device

type

Generic

SCSI

device,

is

online,

shareable.

$


Info

In case of If Tru64 UNIX V5 is running on the host system, it is recommended to use the following commands to get information on the host configuration:

CommandDescription
# /sbin/hwmgr view devices

Get detailed information about the host hardware configuration

# /sbin/hwmgr show scsi

Get specific information about the host SCSI controllers and attached disks

# /sbin/hwmgr view hierarchy

Get information about the host controllers

Please reference refer to the Tru64 UNIX User's Guide for more details.

...

ControllerDevices on controllerDescription
KZPBA

-DKA0 (RZ28)
-DKA100 (RZ22)
-DKA200 (RZ23) 
-MKA600 (tape) 

SCSI disk/tape controller
KGPSA-CA-DGA0 (RZ24)FC disk controller
OPA0
System console

TSSTcorpCDDVDW SH-222BB

-DQA0IDE CD-ROM controller
EWA0
Network interface, MAC address: "F8-D1-11-00-67-E6"

...

>>>show mem

System Memory Resources on 5-FEB-2015 2018 09:29:16.42

Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (512.00MB) 65536 56496 8610 430

...

>>>

...

Info

In some particular situations it is also important to know the exact placement of all the peripheral devices on the HP Alpha PCI bus. To get that information issue do so, issue the "show config" command at ">>>" prompt of the SRM prompt (>>>) on the HP Alpha console, for . 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 the 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 the CHARON-AXP configuration file

Using the above infoinformation, the following configuration parameters and values can be created instead of set in the template configuration file:

#
# 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 "Putty" terminal emulator (included in CHARON-AXP kit)
#

load virtual_serial_line set COM1 alias = OPA0 port = 10003 application = "putty -load OPA0 -P 10003"

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

set ide container="\\.\CdRom0"

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

load DE500BA/dec21x4x EWA interface=EWA0
load packet_port/chnetwrk EWA0 interface="connection:Charon"

#
# 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] = "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[600] = "C:\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] = "C:\My disks\RZ24.vdisk"

...

...

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

Div
classpagebreak


Making disk images

In our example, possible mappings the mapping of the KZPBA SCSI controller include disk and tape images. Tape The tape images have not to be manually created whereas you the disk images have to provision disk images, be created 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 bigger larger disks to get extra storage space.

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

...

(info) Alternatively it is possible to put the tape and disk images in the CHARON VM Home Directory.

Start the "MkDisk" utility by pressing the "Virtual Disk Image generatorTool" button in the "Host Information & Utilities" tab of the CHARON Virtual Machines Manager:

Image Removed Image Added

Div
classpagebreak


The main following dialog of the utility will appear:

Image RemovedImage Added

Select "Alpha AXP" in the "Select System" drop-down menu, "SCSI" in the "All Controllers" drop-down menu and "RZ24" (for example) in the "Select Disk Type" drop-down menu.

...

Press then the "Create Disk Image" button:

Image RemovedImage Added

 

Div
classpagebreak


The utility will ask you to specify the output file name. Select the "C:\My disks" directory created just before (that has been created earlier, or create it directly in the dialog) , and press the "Save" button:

The "MkDisk" utility will create the requested disk image:

...

Repeat this sequence for the disks "RZ28.vdisk", "RZ22.vdisk" and "RZ23.vdisk". Place them in the same folder. 

...

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

Div
classpagebreak


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 backup over the network . But but for this operation we need a bootable , network-enabled operating system on a CHARON-AXP disk image or physical disk is needed.

The example configures the CHARON-AXP AlphaServer ES40 system for installation of HP OpenVMS from a distribution CD-ROM (usually it is "\\.\CdRom0" if the host has only one CD-ROM drive):

...

(warning) DKA300 will be the disk where all the source disks will be copied , so its size needs to be big large enough to store all the disk backup images.

Create an empty disk image for installation of HP OpenVMS and another one for storing the backups from the source HP Alpha system as it is shown in the section above.

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

CHARON-AXP/ES40 for Windows x64 (AlphaServer ES40 6/667), Version 4.810.1810020200
(C) 2009-2016 2019 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 storagethat will be used to store the backups. Let's assume it's its prompt is "newvms$ "

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

...

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

Making remote backups

Now we are ready to create the disk backups from of the source HP Alpha system to on the CHARON VM.

Boot the CHARON VM and make sure that the source HP Alpha system is available via DECnet. 

Login to the source HP Alpha system. Stop all the batch queues, kick off the users, stop all the applications and close the databases if anythere are. The commands listed in SYS$MANAGER:SYSHUTDWN.COM may be helpful.  The goal is to close as many files as possible. The system disk will have several files opened (pagefile, swapfile, etc.) , but and this is a normal situation.

(info) The use of the "SHOW DEVICE /FILES" command would be of help to list opened files on a disk
Let's assume .

In this example, the CHARON VM system is node 1.400

...

.

Issue

...

the following commands from the source HP Alpha

...

. Let's assume its prompt is

...

"source$ ":

source$ BACKUP/IMAGE/IGNORE=INTERLOCK DKA0: 1.400"username password"::DKA300:[000000]DKA0.BCK/SAVE
source$ BACKUP/IMAGE/IGNORE=INTERLOCK DKA100: 1.400"username password"::DKA300:[000000]DKA100.BCK/SAVE
source$ BACKUP/IMAGE/IGNORE=INTERLOCK DKA200: 1.400"username password"::DKA300:[000000]DKA200.BCK/SAVE 

Once When the backup procedure completesoperation will be completed, the disk "DKA300" of the CHARON VM will contain 3 savesets: "DKA0.BCK", "DKA100.BCK" and "DKA200.BCK"

...

.

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

Restore backups to CHARON-AXP disks

...

The savesets have now to be restored on their corresponding virtual disks. Login to the CHARON VM guest OS and issue this sequence of commands to restore all the savesets created on the previous step:


Div
classcommandline

newvms$ MOUNT/FOREIGN DKA0:

newvms$ BACKUP/IMAGE DKA300:[000000]DKA0.BCK/SAVE DKA0:

newvms$ DISMOUNT DKA0:

newvms$ MOUNT/FOREIGN DKA100:

newvms$ BACKUP/IMAGE DKA300:[000000]DKA100.BCK/SAVE DKA100:

newvms$ DISMOUNT DKA100:

newvms$ MOUNT/FOREIGN DKA200:

newvms$ BACKUP/IMAGE DKA300:[000000]DKA200.BCK/SAVE DKA200:

newvms$ DISMOUNT DKA200:


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

The easiest way is to boot the CHARON VM virtualized system on the restored system disk with the network Disabled disabled and to configure new addresses , as neededthen enable the network and reboot.

(info) The NIC can be disabled with a interface="connection:(disabled)" statement in the CHARON VM  configuration configuration file.

Then Enable the network and reboot.

...

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

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 VM configuration file

           a. Restore the source HP Alpha system backups from tape to disk images via OpenVMS running on the CHARON VM.
           b. Boot from standalone from standalone backups and restore its the content to CHARON to the CHARON VM virtual disks

    • Dump the source HP Alpha system backups to tape images with using the "mtd" utility and:
           a. Boot from the freshly installed OpenVMS system and restore the tape images to the CHARON VM virtual disks
           b. Boot from the standalone backups backup and restore its the content to CHARON to the CHARON VM virtual disks
  • Create a network cluster between the source HP Alpha system and the CHARON VM (it is possible to use the source system as a boot server); then perform simple backup backups from one disk to another:

    $ BACKUP/IMAGE/IGNORE=INTERLOCK REAL$DKA0: DKA0:


Include Page
KBCOMMON:

...

DOC-GoToToc
KBCOMMON:DOC-GoToToc