Dynamic workload movement with BladeSystem Matrix: Fluid movement between physical and virtual resources for flexibility and cost-effective recovery

4
virtual machine hosts that may be potential targets for the Logical Server – the same as used
to present the Logical Unit to a physical server target. Likewise, the target WWN(s) used to
present the Logical Unit must be the same across virtual and physical targets. (Note that the
recovery Logical Server that provides DR protection at the remote site will have its own set of
target WWN/LUN values that will differ from the Logical Server at the local site.)
On a movement between physical and virtual servers within a site, the following server IDs
are not preserved
- Network MAC addresses
- Server/Initiator WWNs (on the virtual machine, the storage adapter is a virtual
SCSI controller)
- Logical Serial Number
- Logical UUID
In a DR configuration, the primary site must have both physical servers and virtual machine
hosts available so that a Logical Server can be configured to run on both types of servers and
tested. The recovery site may have a physical/virtual combination also or have only virtual
machine hosts.
Supported Platforms
The procedures for enabling movement between physical and virtual servers documented in this paper
are supported for the following hypervisors and workload OSs (consult HP Insight Software 6.2
Support Matrix available at www.hp.com/go/insightdynamics/docs):
Hypervisors
- VMware Hypervisor versions specified as supported on managed systems by Insight
Dynamics
Workload OS
- Windows 2008 versions specified as supported on managed systems by Insight
Dynamics
The procedures for enabling movement between physical and virtual servers are not supported on
Integrity managed nodes.
The procedures for enabling movement across different physical servers documented in this paper are
supported for managed systems specified as supported by Insight Dynamics, with the following
restriction
HP Insight Recovery (HP IR), the component of HP ID that provides disaster recovery across
sites does not support Integrity managed nodes
A physical server target configured for cross-technology movements must be a HP C-class blade with
Virtual Connect.
Overview of Cross-technology Configuration
In this section, we provide an outline of the steps involved in configuring cross-technology Logical
Servers.