Product data

Chapter 2. Core procedures 13
10.If you have multiple media created and the procedure that you are running
asks for the next CD in the sequence, use the Virtual I/O Server unloadopt
command to unload the current virtual media and repeat step 8 on page 12 to
load the next image.
$ unloadopt -vtd vcd1
$ loadopt -disk cd_image_15364.vol2 -vtd vcd1
If your repository size was not able to store all the images, repeat step 6 on
page 12 to remove unneeded images with the rmvopt command and add the
next image with the mkvopt command before using the unloadopt command in
this step.
11.Run a final Virtual I/O Server unloadopt command at the end of the procedure
to ensure that the virtual media is cleaned up.
12.Depending on your requirements, you may keep the current media repository
or remove the virtual media objects using the Virtual I/O Server rmvopt
command:
rmvopt cd_image_15364.vol1
On the target system
13.On the target system, look for a CD drive in the list of devices and use it as
any other CD drive. The restore/recovery will read your virtual media image
rather than physical media to complete the task.
2.2 Checking unique disk identification
Recognition of the correct disks is paramount in the physical-to-virtual migration
processes regardless of the type of disk. SAN volumes and SCSI/SAS disks will
be referred to with the generic term
disk in this section.
There are three signatures that a disk may have written to it in the AIX/VIOS
environment, which allow identification of that disk when it is migrated:
򐂰 Physical volume identifier (PVID)
򐂰 IEEE volume identifier
򐂰 Unique device identifier (UDID)