HP Integrity Virtual Server Manager 6.3 User Guide

NOTE: You cannot delete a VM that is currently migrating online. You must wait until migration
completes.
NOTE: Using Integrity Virtual Server Manager with Matrix Operating Environment for HP-UX, if
you create a VM and then delete it before the new VM has been identified by Systems Insight
Manager, the VM might appear in HP Matrix OE visualization as though it had not been deleted.
The appearance of the VM in HP Matrix OE visualization depends on when the deletion occurred
during the Systems Insight Manager identification process. In addition, if you decide to delete the
VM soon after creating it, wait a few minutes before doing so. If the deleted VM does appear in
HP Matrix OE visualization, delete it from the Systems Insight Manager All System view. (From the
Systems Insight Manager Systems and Event Collections list in the navigation area on the left, select
All Systems.) For more information, see the HP Matrix Operating Environment Logical Server
Management User Guide.
This is not an issue when using Integrity Virtual Server Manager from HP SMH.
Migrating Guests
Overview
This topic presents an overview of guest migration and of the Migrate guest wizard that allows
you to set up and initiate migration of guests from your Integrity Virtual Server Manager's VSP (the
migration source) to another VSP (the migration target).
The wizard allows you to perform either online or offline migration:
• Online migration migrates a guest that is running, moving the guest OS and applications
without disrupting service. All guest I/O connections to network and storage devices remain
active throughout the migration, and the guest OS and its applications continue operating
without requiring a reboot or application restart.
• Offline migration migrates the configuration of a guest that is not running.
Some of the most common reasons for migrating guests online include the need to:
• Vacate the source VSP system for maintenance purposes without disrupting services
• Perform a rolling upgrade of a VSP, moving its running guests to another VSP, upgrading the
VSP, then moving the guests back
• Populate a new VSP with one or more guests already configured and tested on the source
• Move guests to take advantage of a particular resource or feature on the target VSP, without
losing application availability
• Balance VSP workloads
• Optimize physical resource utilization
Online migration of guests enables a higher level of workload-to-resource alignment, flexibility,
and agility.
Reasons for migrating a guest offline include the need to:
• Move a stopped guest's configuration information
• Save VSP resources while migrating guests (for example, memory and CPUs are not consumed
during offline migration)
• Copy local storage, logical volumes, or file-backed storage to the target VSP (such storage
cannot be migrated online)
• Migrate a guest between VSP that might have different processor types, making online migration
impossible
Working with VMs 97