| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
...
|
Introduction
This section describes how to migrate your VAX system to CHARONCharon-VAX. We will use a sample MicroVAX 3600 system to demonstrate the migration procedure. The process is similar for all CHARONall Charon-VAX models.
| Info |
|---|
If CHARONthe Charon-VAX based virtual system needs to be created from scratch, refer to this Application Note the appendix "Configuring devices on the Qbus of a VAX or CHARON-VAX" describing how to find proper Qbus addresses and Vectors for each virtul virtual device. |
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||||
|---|---|---|---|---|
| ||||
Collecting information about the source VAX/VMS system
The first step is to determine the exact configuration of your VAX hardware in order to create the CHARONCharon-VAX configuration file.
Turn on your source VAX system. At the ">>>" prompt, issue the "show qbus" and "show device" commands:
|
...
|
| Div | ||
|---|---|---|
| ||
| ||
The source VAX configuration in this example is:
| Controller | Address | Devices on controller | |
|---|---|---|---|
| RQDX3 | 772150 | -DUA0 (RZ23) -DUA1 (RZ24) | |
| RQDX3 | 760334 | -DUB2 (RZ25) -DUB3 (RZ26) | |
| TQK50 | 774500 | -MUA0 (TK50) | |
| TQK50 | 760444 | -MUB3 (TK50) | |
| DHQ11 | 760520 | ||
| DHQ11 | 760500 | ||
| DESQA | 774440 | -XQA0 |
To find out the exact types of controllers please refer to documentation on the source VAX system.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
| ||
Creation of
...
Charon-VAX configuration file
Using the above infoinformation, the following configuration can be created:
...
Note the Qbus addresses specification: The the number is prefixed with "0", meaning it is an octal value. The number of digits reflects the 22 bit bits Qbus architecture.
Additional DHQ11 serial lines can be mapped later. For now, only 2 lines are configured. They , they are mapped to IP ports 10010 and 10011.
DESQA is mapped to the "eth1" network interface. This interface will be used for CHARONCharon-VAX (see the Installation section for more details) on this particular host.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Making disk images
In our example, possible mappings of the RQDX3 and TQK50 tapes include physical devices and disk and tape images. Tape Tape images should 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 bigger larger disks to get extra storage space.
Create special directories for storing disk and tape images, as needed. Created 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:
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Installation of VAX/VMS operating system
The next step is to transfer the data from the source VAX system to CHARONCharon-VAX. The easiest way to do it is via backup backups over the network. But for For this operation we need a bootable, network-enabled operating system on a CHARONCharon-VAX disk image or physical disk.
The example configures the CHARONCharon-VAX MicroVAX 3600 system for installation of VAX/VMS from a distribution CD-ROM (usually it is "/dev/cdrom" if the host has only one CD-ROM drive):
|
DUA3 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.
| Div | ||
|---|---|---|
| ||
| ||
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 CHARONCharon-VAX and boot from "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 VAX/VMS system and Initialize the disk intended for backups storage:
...
. Let's assume it's prompt is "newvms$ ".
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Making remote backups
Now we are ready to create disk backups from the source VAX system to CHARONCharon-VAX.
Boot CHARONthe Charon-VAX virtual machine and make sure that the source VAX system is available reachable via DECnet.
Login to the source VAX system. S, shut down all the batch queues, kick off the users, stop all applications and close databases if any databases. 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.), but this is a normal .Issue (letsituation.
The use of the "SHOW DEVICE /FILES" command would be of help to know files opened on a disk
Let's assume that the CHARONCharon-VAX system is node 1.400 in this example). Issue then the following commands from the source VAX system whose prompt is set to "source$ ":
$ |
Once When the backup procedure completes will be completed, the disk "DUA3" of CHARONthe Charon-VAX virtual machine will contain 4 savesets: "DUA0.BCK", "DUA1.BCK", "DUB0.BCK" and "DUB1.BCK"
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||||
|---|---|---|---|---|
| ||||
Restore backups to
...
Charon-VAX disks
Next, restore the new savesets to their corresponding virtual disks. Login to CHARONCharon-VAX and issue this sequence of commands to restore all the savesets created on in the previous step:
$ $ $ $ |
Now reboot CHARONIf you are going to have the Charon-VAX and boot from the same boot disk as you do on the source VAX system.
...
the original physical VAX system on the network at the same time, you must change the network identity of one (usually the Charon-VAX).
The easiest way is to boot the Charon-VAX virtual ized 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.
| Include Page | ||||
|---|---|---|---|---|
|
Alternative ways of data transfer
Some alternative methods of data transfer are also possible, for . For example:
- Connect a SCSI tape drive to CHARONthe Charon-VAX host via a PCI card
- Map the tape drive in CHARONthe Charon-VAX configuration file
a. Restore the source VAX system backups from tape to disk images via VAX/VMS running on CHARONCharon-VAX.
b. Boot from standalone backups and restore its the content to CHARONto Charon-VAX virtual disks. - Dump the source VAX system backups to tape images with the "mtd" utility and:
a. Boot from the freshly installed VAX/VMS system and restore the tape images to CHARONCharon-VAX virtual disks.
b. Boot from standalone backups and restore its the content to CHARONto Charon-VAX virtual disks.
- Map the tape drive in CHARONthe Charon-VAX configuration file
Create a network cluster between the source VAX system and CHARONCharon-VAX (it is possible to use the source system as a boot server) ; then simple backup perform backups from one disk to another:
$ BACKUP/IMAGE/IGNORE=INTER REAL$DUA0: DUA0:
| Include Page | ||
|---|---|---|
|
...
|