Upgrading to Integrity VM Version 4.0 from 3.X
12
If the return code is 0, then virtual partitions are running. They should be removed with the swremove
command.
Special Considerations for Serviceguard: Rolling Updates
There are two ways that Integrity VM guests can be integrated with Serviceguard. The first way is for
the entire guest to be treated as a single “package”. In this configuration, the VM hosts are cluster
nodes and the guest instance is restarted on a different host in the event of failure. The second way is
for the guest(s) to be cluster nodes themselves and for the various applications running on them to be
the packages. In this case, only the applications are restarted in the event of a VM host (or guest)
failure. A white paper, Designing high-availability solutions with HP Serviceguard and HP Integrity
Virtual Machines, covers both of these configurations in detail.
In either case, it is important to be sure that the Operating Environment, Serviceguard, and Integrity
VM versions are compatible. This is guaranteed if you update to the Data Center Operating
Environment. For all other situations, please refer to the table below: