VCEM Profile Failover and Profile Moves

Profile Failover: an example
A simple example of Profile Failover follows. The infrastructure depicted in Figure 1
includes:
One VC Domain Group with two HP BladeSystem enclosures.
Virtual Connect with Ethernet and SAN interconnects.
(red box) represents a production server blade (left enclosure).
(blue box) represents a spare server blade (right enclosure).
A server profile that contains the MAC and WWN assignments. At any time a profile
may be associated at most with one bay and its resident server.
Figure 1. VCEM Profile Failover example
The following describes the Profile Failover operation depicted in Figure 1 above:
A workload, a SAN-boot system drive containing an operating system, an application and
the application’s data, is running on the production server
(red box). There is a need to
move the workload to another server. For example, there is a hardware problem or
planned server maintenance is due.
A Profile Failover on the production server
(red box) is initiated. As a result VCEM
executes the following automated actions:
The production server
(red box) is powered off.
A spare server blade
(blue box) is selected.
The production server’s profile is moved from the production bay
(red box) to the
spare bay
(blue box). After the move the spare server has the Ethernet and SAN
assignments previously held by the production server.