...
Turn on your source HP Alpha system. At the ">>>" prompt, issue a "show device" command:
>>> |
...
Creation of CHARON-AXP configuration file
Using the above infoinformation, the following configuration can be created:
...
In our example, possible mappings of the KZPBA SCSI controller include disk and tape images. Tape images 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:
...
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 backups over the network. But for For this operation we need a bootable, network-enabled operating system on a CHARON-AXP disk image or physical disk.
...
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 backups from the source HP Alpha system as it is shown in the section above.
...
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$ ".
|
...
Now we are ready to create disk backups from the source HP Alpha system to CHARON-AXP.
Boot the CHARON-AXP virtual machine and make sure that the source HP Alpha system is available reachable via DECnet.
Login to the source HP Alpha system. S, 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.), but this is a normal situation.
The use of the "SHOW DEVICE /FILES" command would be of help to know files opened on a disk
Let's assume the CHARON-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$ ":
|
Once When the backup procedure completeswill be completed, the disk "DKA300" of the CHARON-AXP virtual machine will contain 3 savesets: "DKA0.BCK", "DKA100.BCK" and "DKA200.BCK"
...
Next, restore the new savesets to their corresponding virtual disks. Login to CHARON-AXP and issue this sequence of commands to restore all the savesets created on in the previous step:
|
If you are going to have the CHARON-AXP and the original physical HP Alpha on the network at the same time, you must change the network identity of one (usually the CHARON-AXP).
The easiest way is to boot the CHARON-AXP virtualized system on the restored system disk with the network Disabled disabled and to configure new addresses, as needed.
...
- Connect a SCSI tape drive to the CHARON-AXP host via a PCI card
- Map the tape drive in the CHARON-AXP configuration file
a. Restore the source HP Alpha system backups from tape to disk images via OpenVMS running on CHARON-AXP.
b. Boot from standalone backups and restore its the content to 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 CHARON-AXP virtual disks.
b. Boot from standalone backups and restore its the content to CHARON-AXP virtual disks.
- Map the tape drive in the CHARON-AXP configuration file
Create a network cluster between the source HP Alpha system and CHARON-AXP (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=INTERLOCK REAL$DKA0: DKA0:
...