...
Turn on your source HP Alpha system. At the ">>>" prompt, issue "show device" command:
>>> |
To get more detailed information, boot OpenVMS and issue a "show device /full" command:
Disk PFCAXP$DKA0:, device type RZ28, is online, mounted, file-oriented device, Disk PFCAXP$DKA100:, device type RZ22, is online, file-oriented device, Disk PFCAXP$DKA200:, device type RZ23, is online, file-oriented device, Disk PFCAXP$DQA0:, device type TSSTcorpCDDVDW SH-222BB, is online, file-oriented Disk $1$DGA0: (PFCAXP), device type RZ24, is online, file-oriented device, Magtape PFCAXP$MKA600:, device type Virtual SCSI Tape, is online, file-oriented Terminal OPA0:, device type VT102, is online, record-oriented device, carriage Device EWA0:, device type DE500, is online, network device, device is a template Device FGA0:, device type KGPSA Fibre Channel, is online, shareable, error 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 Device $1$GGA32767:, device type Generic SCSI device, is online, shareable. $ |
Info | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
In case of Tru64 UNIX V5 running on the host system it is recommended to use the following commands to get information on the host configuration:
Please reference to the Tru64 UNIX User's Guide for more details. |
The source HP Alpha peripheral configuration in this example is:
Controller | Devices on controller | Description |
---|---|---|
KZPBA | -DKA0 (RZ28) | SCSI disk/tape controller |
KGPSA-CA | -DGA0 (RZ24) | FC disk controller |
OPA0 | System console | |
-DQA0 | IDE CD-ROM controller | |
EWA0 | Network interface, MAC address: "F8-D1-11-00-67-E6" |
Now collect some general information about the HP AlphaServer ES40 system:
>>> |
>>> |
So the collected information about the HP AlphaServer ES40 system is:
Component | Value |
---|---|
System Type | AlphaServer ES40 6/667 |
Serial Number | SN01234567 |
Number of CPUs | 4 |
System memory | 512 Mb |
Div | ||
---|---|---|
| ||
|
Info | |
---|---|
In some particular situations it is also important to know the exact placement of all the peripheral devices on HP Alpha PCI bus. To get that information issue a "show config" command at ">>>" prompt of HP Alpha console, for example:
The "show config" command collects the following information of placement of peripheral devices on PCI bus:
|
...
Using the above info, the following configuration can be created:
|
...
Create special directories for storing disk and tape images, as needed. Created directories are referenced in the sample configuration file above.
$ mkdir /my_disks $ mkdir /my_tapes |
Next, create disk images using the "mkdskcmd" utility:
|
...
The example configures the CHARON-AXP AlphaServer ES40 system for installation of HP OpenVMS from a distribution CD-ROM (usually it is "/dev/cdrom" if the host has only one CD-ROM drive):
|
DKA300 will be the disk where all the source disks will be copied, so its size needs to be big enough to store all the disk backup images
...
Run CHARON-AXP and boot from the CDROM named "dqa0" ("migration.cfg" is the configuration file we use in this example):
|
Install HP Alpha/VMS including DECnet on "dka400". 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$
"
|
...
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 the backup procedure completes, the disk "DKA300" of CHARON-AXP 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 the previous step:
|
If you are going to have 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).
...
- Connect a SCSI tape drive to CHARON-AXP host via a PCI card
- Map the tape drive in the CHARON-AXP configuration file
a. Restore source HP Alpha system backups from tape to disk images via OpenVMS running on CHARON-AXP.
b. Boot from standalone backups and restore its content to CHARON-AXP virtual disks - Dump source HP Alpha system backups to tape images with "mtd" utility and:
a. Boot from freshly installed OpenVMS system and restore the tape images to CHARON-AXP virtual disks
b. Boot from standalone backups and restore its 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 boot server); then simple backup from one disk to another:
$ BACKUP/IMAGE/IGNORE=INTERLOCK REAL$DKA0: DKA0: