When Serviceguard manages a configuration that contains Integrity
VM, failover of a virtual machine changes the UUID of the
virtual machine. Several components of VSE Management software use
the UUID as a search key, and they treat the single virtual machine
as two distinct virtual machines, one with the previous UUID and one
with the later UUID. Capacity Advisor treats this as two or more
different system traces for a failed over virtual machine. By default
these system workloads are named domainname, domainname.2, domainname.3, and so on. Each system
workload has data for only when the virtual machine was running on
a particular virtual machine host.
This process affects only the system workload for the virtual
machine. If monitored workloads are defined inside the virtual machine,
their data is tracked correctly even when the virtual machine fails
over to a new host. It is a good idea to create a workload inside
of any virtual machine that you intend to fail over using Serviceguard
to ensure that the utilization data of the virtual machine is kept
whole.
If there is no monitored workload, then utilization data for
the failed over system is split across two or more workloads. To
prevent this, use the following procedure to treat these multiple
workloads as a single workload:
Create a scenario and include the current virtual
machine host.
Within that scenario, create a new workload and import
data from the unrepresented workload. (Create two or three workloads,
if needed.)
Place these new workloads in the current virtual machine.
When you edit or move one of these workloads, do the
same with the others.
The virtual machine containing the multiple workloads can be moved within
the scenario and can give a complete picture of past utilization.
The collection of these multiple workloads gives you a nearly uninterrupted
view of the historical utilization for the virtual machine.
Virtual machines that are moved between hosts using the hpvmmigrate command preserve their UUIDs and are not
seen as two virtual machines.