...
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 the CHARONCharon-VAX based virtual system needs to be created from scratch, refer to the appendix "Configuring devices on the Qbus of a VAX or CHARON-VAX" describing how to find proper Qbus addresses and Vectors for each 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:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Creation of
...
Charon-VAX configuration file
Using the above information, the following configuration can be created:
...
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 | ||||
|---|---|---|---|---|
|
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 backups over the network. 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):
...
|
Run CHARONCharon-VAX and boot from "dua4" ("migration.cfg" is the configuration file we use in this example):
...
Now we are ready to create disk backups from the source VAX system to CHARONCharon-VAX.
Boot the CHARONCharon-VAX virtual machine and make sure that the source VAX system is reachable via DECnet.
...
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 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$ ":
...
When the backup procedure will be completed, the disk "DUA3" of the CHARONCharon-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 in the previous step:
...
If you are going to have the CHARONCharon-VAX and the original physical VAX system on the network at the same time, you must change the network identity of one (usually the CHARONCharon-VAX).
The easiest way is to boot the CHARONCharon-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 the Charon configuration file.
Then Enable the network and reboot.
...
- Connect a SCSI tape drive to the CHARONCharon-VAX host via a PCI card
- Map the tape drive in the CHARONCharon-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 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 the content to CHARONto Charon-VAX virtual disks.
- Map the tape drive in the CHARONCharon-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 perform backups from one disk to another:
$ BACKUP/IMAGE/IGNORE=INTER REAL$DUA0: DUA0:
...