PowerVC 1.2.3 supports import, capture, and deploy of images and VMs with multiple volumes.  This means that images can reference multiple volumes and can be captured and deployed with multiple volumes.  You also have the choice to capture and deploy all the volumes or a subset of the volumes associated with a VM.

Let’s look at some concrete examples of what this allows you to do with capture and deploy in PowerVC 1.2.3.

  1. IBM i customers can now capture and deploy VMs that have *SYSBASE spanning multiple volumes.
  2. You can now capture both volumes comprising AIX root_vg when it is mirrored between volumes in different SANs.  On capture, a clone of each SAN volume is created in the respective SAN and the image contains copies of both volumes.  On deploy, the image volumes are cloned back to new volumes in each of the SANs.
  3. You can choose to capture / deploy just the operating system (root_vg) or the operating system and your applications or database in data volume groups.
  4. You can capture a ‘canned’ operating system image and then on deploy, choose to attach other existing volumes in your environment that could contain your databases.  This allows you to keep your images small and not clone all of your database volumes.
  5. You can also add blank volumes to a VM at deploy time.  These volumes could then be partitioned and have file systems put on them for additional user data space beyond what is in the image / root_vg disks.

Let’s walk through the deployment of a multi-disk image that contains a mirrored boot volume and a data volume group.  As part of the deploy, let’s also choose to attach another existing data volume and one new blank volume for some additional space.  Here is the screenshot of the deploy panel that shows the deploy of a multi-disk image that contains a mirrored AIX boot volume and two data volumes which are in a separate volume group.

Notice the New and Existing volumes section.  When the “Add Volume” button is pressed, it allows the user to attach additional existing volumes to the VM or specify that a new blank volume should be allocated and attached as part of the deploy.

Here is what the “Add Volume” screen looks like when attaching an existing volume:


If you choose to add a new volume to the VM deploy, you see this screen:


Finally, this screen shot shows the main deploy panel after additional volumes have been added to the deploy:


As you can see the multiple volume image support opens up a many new possibilities for the management of real world multi-volume VMs that was not previously possible with the single volume image support that exists in previous releases.

Join The Discussion

Your email address will not be published. Required fields are marked *