HP Matrix Operating Environment Software - Manual (Page 32)

Capabilities and limitations
Using the tools and procedures described in this chapter you can:
•
Configure and manage a logical server that can perform physical to virtual cross-technology
movements within the datacenter.
•
Configure and manage a DR Protected logical server that can be failed over across data
centers in a cross-technology movement.
The following limitations should be noted:
•
Configuration of a cross-technology logical server requires additional steps (however, no
additional steps are required at the time of the move, within or across sites).
•
Virtual machines running Windows 2008 or later are supported. Virtual machines must be
configured to emulate either the LSI Logic Parallel or LSI Logic SAS storage type.
•
Because DR Protection for IO services is supported for VM based IO services only,
cross-technology movement of IO services workloads across data centers does not apply.
•
VMware ESX guest tools are not automatically installed.
•
There is no explicit support NPIV .
•
Preparation of the portable system image so it can run on both physical and virtual servers is
done from an OS installed on a physical server. You cannot prepare the portable system
image from an OS installed on a virtual machine.
•
Virtual machines must be configured to use RDM Fibre Channel SAN storage presented to the
VM host for boot and data. This is the same storage that a logical server uses when running
on a physical server.
•
Each boot and data LUN must use the same LUN number across the physical and virtual targets
for a logical server as illustrated in
Figure 4 (page 33) .
32 Dynamic workload movement with CloudSystem Matrix