Product data

Chapter 3. Standalone SCSI rootvg to virtual SCSI 53
repository you can also create all the media up front and not revisit this step
again:
$ mkvopt -name cd_image_82472.vol2 -file
/updates/cd_image_82572.vol2 -ro
27.Load the next virtual optical media file that was created earlier using the
Virtual I/O Server loadopt command:
$ loadopt -disk cd_image_82472.vol2 -vtd vtopt1
On the target partition
28.From the logical partition terminal session or console, you can now press
Enter to continue the restore process.
Once all your media files have been processed, you will be presented with the
AIX login panel. You should now be able to log into the logical partition and
correct any issues such as IP addresses.
On the Virtual I/O Server: cleanup stage
29.Once the restore is finished you can unload the last of your virtual media files
using the Virtual I/O Server unloadopt command:
$ unloadopt -vtd vtopt1
Cleanup any images not required in the repository using the rmvopt
command.
Your migration is now complete.
3.2 Moving rootvg disks to SAN
This method uses the AIX migratepv command to move the rootvg onto a
SAN-attached disk. The local SCSI disk is then removed from the root volume
group and the volume group now containing the SAN disk is presented to the
Virtual I/O Server where it is mapped to the target logical partition.
In this example, both the standalone client and the Virtual I/O Server require
access to a Fibre Channel adapter. You may therefore be required to relocate the
Fibre Channel adapter from the standalone client to the Virtual I/O Server once
Note: No instructions are provided in this book for SAN functions such as
modifying zones or mapping storage to hosts from SAN disk platforms. Users
should be familiar with these operations before starting the migration task or
have appropriately trained people who can perform those tasks.