Versions Compared

Old Version 5

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: headings level update for PDF export

TopMigrationPage
Anchor
TopMigrationPage
Anchor
TOC
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 VAX system to CHARON-VAX. We will use a sample MicroVAX 3600 system to demonstrate the migration procedure. The process is similar for all CHARON-VAX models.

...

Info

If CHARON-VAX based virtual system needs to be created from scratch, refer to this Application Note describing how to find proper Qbus addresses and Vectors for each virtul device.

...


Div
classpagebreak


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 Removed

Image Added


Div
classpagebreak


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


The VM will be created:

Image RemovedImage Added


Div
classpagebreak


Select the VM and switch to the "VM Configuration" tab.Press from the left pane and press the "Edit Configuration file" button:

Image RemovedImage Added

The VM configuration file will be opened in Windows default text editorNotepad. Now we are ready to update this file to reprocude the file can be updated to reproduce the target HP VAX configuration.

...

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

Div
classpagebreak


Collecting information about the source VAX system

The first step is to determine the exact configuration of your VAX hardware in order to create the CHARON VM configuration file.

Turn on your source VAX system. At the ">>>" prompt, issue the "show qbus" and "show device" commands:

>>>show qbus
Scan of Qbus I/O Space
-200000DC (760334) = FFFF (300) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-200000DE (760336) = 0B40
-20000124 (760444) = FFFF (304) TQK50/TQK70/TU81E/RV20/KFQSA-TAPE
-20000126 (760446) = 0BC0
-20000140 (760500) = 0080 (310) DHQ11/DHV11/CXA16/CXB16/CXY08
-20000142 (760502) = F081
-20000144 (760504) = DD18
-20000146 (760506) = 0140
-20000148 (760510) = 0000
-2000014A (760512) = 0000
-2000014C (760514) = 8000
-2000014E (760516) = 0000
-20000150 (760520) = 0080 (320) DHQ11/DHV11/CXA16/CXB16/CXY08
-20000152 (760522) = F081
-20000154 (760524) = DD18
-20000156 (760526) = 0140
-20000158 (760530) = 0000
-2000015A (760532) = 0000
-2000015C (760534) = 8000
-2000015E (760536) = 0000
-20001468 (772150) = FFFF (154) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-2000146A (772152) = 0B40
-20001920 (774440) = FF08 (120) DELQA/DEQNA/DESQA
-20001922 (774442) = FF00
-20001924 (774444) = FF01
-20001926 (774446) = FF02
-20001928 (774450) = FFD2
-2000192A (774452) = FF14
-2000192C (774454) = C000
-2000192E (774456) = 1030
-20001940 (774500) = FFFF (260) TQK50/TQK70/TU81E/RV20/KFQSA-TAPE
-20001942 (774502) = 0BC0
-20001F40 (777500) = 0020 (004) IPCR

Scan of Qbus Memory Space
>>>

...

To find out the exact types of controllers please refer to the source VAX system documentation.

...

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

Div
classpagebreak


Creation of CHARON-VAX configuration file

Using the above infoinformation, the following configuration parameters and values can be createdset in the configuration file:

...

#
# First RQDX3 controller on address 772150
#
load RQDX3/RQDX3 DUA address=017772150
set DUA container[0]="C:\My disks\rz23.vdisk"
set DUA container[1]="C:\My disks\rz24.vdisk"

#
# Second RQDX3 controller on address 760334
#
load RQDX3/RQDX3 DUB address=017760334
set DUB container[2]="C:\My disks\rz25.vdisk"
set DUB container[3]="C:\My disks\rz26.vdisk"

#
# First TQK50 controller on address 774500
#
load TQK50/TQK50 MUA address=017774500
set MUA container[0]="C:\My tapes\tape1.vtape"

#
# Second TQK50 controller on address 760444
#
load TQK50/TQK50 MUB address=017760444
set MUB container[3]="C:\My tapes\tape2.vtape"

#
# First DHQ11 controller on address 760500
#
load DHQ11/DHV11 TXA address=017760500
load virtual_serial_line/chserial TXA0 port=10010
set TXA line[0]=TXA0

#
# Second DHQ11 controller on address 760520
#
load DHQ11/DHV11 TXB address=017760520
load virtual_serial_line/chserial TXB0 port=10011
set TXB line[0]=TXB0

#
# DESQA controller on address 774440
#
load DESQA/DEQNA XQA address=017774440 interface=XQA0
load packet_port/chnetwrk XQA0 interface="connection:Charon" 

...

Note the Qbus addresses specification:

  • The number is prefixed with "0", meaning it is an octal value.
  • The number of digits reflects the 22 bit Qbus architecture.

Additional DHQ11 serial lines can be mapped later. For now, only 2 lines are configured. They are mapped to IP ports 10010 and 10011.

The DESQA controller is mapped to a network interface having the name "Charon". This interface will be used for the CHARON VM (see the Installation section for more details) on this particular host.

...

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

Div
classpagebreak


Making disk images

In our example, possible mappings the mapping of the RQDX3 controller and the TQK50 tapes include physical devices and disk and tape images. Tape  The tape images should 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 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 "VAX" in the "Select System" drop-down menu, "MSCP" 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 VAX operating system

The next step is to transfer the data from the source VAX system to CHARON VM. 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-VAX disk image or physical disk is needed.

The example configures the CHARON-VAX MicroVAX 3600 system for installation of VAX/VMS from a distribution CD-ROM (usually it is "\\.\CdRom0" if the host has only one CD-ROM drive):

...

(warning) DUA3 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 VAX/VMS and another one for storing backups from the source VAX system as it is shown in the section above.

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

...

Install VAX/VMS including DECnet on "dua2". The DECnet address must belong to the same area as the source VAX system.

Login to the newly installed VMS 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 DUA3: SCRATCH
newvms$ MOUNT/SYSTEM/NOASSIST DUA3: SCRATCH

...

: SCRATCH

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

Making remote backups

Now we are ready to create disk backups from of the source VAX system to on the CHARON -VAXVM.

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

Login to the source VAX system. Stop all the batch queues, kick off the users, stop all application 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 know files opened on a disk
Issue (let's assume that the CHARON-VAX .

In this example, the CHARON VM system is node 1.400 in this example).

Issue the following commands from the source VAX. Let's assume it's login its prompt is "source$ ":

source$ BACKUP/IMAGE/IGNORE=INTERLOCK DUA0: 1.400"username password"::DUA3:[000000]DUA0.BCK/SAVE
source$ BACKUP/IMAGE/IGNORE=INTERLOCK DUA1: 1.400"username password"::DUA3:[000000]DUA1.BCK/SAVE

Once When the backup procedure completesoperation will be completed, the disk "DUA3" of the CHARON VM will contain 2 savesets: "DUA0.BCK" and "DUA1.BCK"

...

.

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

Restore backups to CHARON-VAX disks

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

 

newvms$ MOUNT/FOREIGN DUA0:
newvms$ BACKUP/IMAGE DUA3:[000000]DUA0.BCK/SAVE DUA0:
newvms$ DISMOUNT DUA0:

newvms$ MOUNT/FOREIGN DUA1:
newvms$ BACKUP/IMAGE DUA3:[000000]DUA1.BCK/SAVE DUA1:
newvms$ DISMOUNT DUA1:

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

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

(info) The NIC can be disabled with a interface="connection:(disabled)" statement in the CHARON VM cfg 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-VAX / CHARON-PDP host via a PCI card 
    • Map the tape drive in the CHARON VM configuration file

           a. Restore the source VAX system backups from tape to disk images via VMS/RSX11/RT11 running on the CHARON VM
           b. Boot from standalone backups and restore its the content to CHARON to the CHARON VM virtual disks

    • Dump the source VAX/PDP11 system backups to tape images with using the "mtd" utility and:
           a. Boot from the freshly installed VMS/RSX11/RT11 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 VAX/PDP11 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$DUA0: DUA0:


Include Page
KBCOMMON:

...

DOC-GoToToc
KBCOMMON:DOC-GoToToc