HP Matrix Operating Environment 7.0 Recovery Management User Guide

Configuring logical servers for movement between dissimilar physical servers
The HP Matrix Operating Environment provides the ability to fine tune the list of failover targets
that are considered most suitable for a DR protected logical server to be activated on. The ability
to modify target attributes is useful to ensure a successful failover. Target attributes are included in
the data transferred by the Matrix recovery management export/import sequence — an expansion
in the target list at the exporting site will be reflected at the importing site. For more information,
see the Target Attributes section in: “Configuring and managing cross-technology logical servers”
(page 33)
Configuring and managing portable OS images
Mobility of server workloads is hampered by the fact that most operating systems are configured
at install time for the specific platform they are installed on. Examples include:
• Only the device drivers necessary for the target platform are installed and configured;
attempting to boot the same OS instance on a different server may result in device errors or
system failures.
• Configuration settings, such as IP addresses or storage identifiers, may be bound to specific
devices whose names may change. For example, the same subnet may be attached to the
first NIC port on one server, while it is attached to the third NIC port on another.
The HP Matrix Operating Environment supports mechanisms to prepare a server image (logical
server) so it will continue to work when moved to a different physical or virtual server. The three
areas that HP determined to be key to achieving this objective are:
• Driver installation
• HBA configuration
• NIC configuration
The tools developed for this purpose are:
• Portable Images Storage Assistant (PISA)
• Portable Images Network Tool (PINT)
Portable Images Storage Assistant (PISA)
When Windows is installed on a SAN LUN attached to a server, it installs a driver that is specific
to the HBA controller on that server. If that LUN is subsequently reassigned to a virtual machine
on a server running VMware ESX, ESX presents only SCSI direct-attached devices to the virtual
machine. Windows is still configured to use the HBA controller for the original server and is therefore
unable to start up. PISA enables the appropriate Windows drivers allowing Windows to start in
the virtual machine.
PISA assumes that the virtual machine is configured to use the Raw Device Mapping feature in ESX
to configure a LUN on a SAN as a disk drive available to the virtual machine. The virtual machine
must also be configured to emulate either the LSI Logic Parallel or LSI Logic SAS storage type with
Windows 2008, or the LSI Logic Parallel storage type with Windows 2003.
In all versions of Windows 2008, the driver needed to properly operate the virtual version of the
LSI controller is installed, but disabled. In Windows 2003 the necessary driver needs to be installed
and enabled.
PISA is used to enable LSI support in the Windows image. How PISA operates is different depending
on whether it is on Windows 2008 or Windows 2003.
PISA is a simple command line tool that only accepts a few command line options. It needs to be
executed only once after Windows has been installed on a physical server. The changes it makes
are persistent and do not need to be repeated nor reversed. However, repeatedly running PISA
will have no negative impact. PISA can also be used to disable the driver used by the virtual
machine.
32 Dynamic workload movement with CloudSystem Matrix: Fluid movement between physical and virtual resources for flexibility
and cost-effective recovery