HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

6. To revert a VM to a snapshot, expand the tree, select a snapshot, and click Revert. The Revert
to snapshot? dialog appears.
Reverting a snapshot returns the virtual machine's memory (if selected when the snapshot was
created), settings, and virtual disks to the state they were in when the snapshot was created.
a. (Optional) Click to select Do not power on after revert to suppress powering on the virtual
machine after reverting to a snapshot. If the snapshot does not include memory state, the
VM will be powered off and this option has no effect.
b. Click Revert to complete the request, or Cancel to cancel the action.
Attaching physical disks to virtual servers
Matrix infrastructure orchestration allows you to map physical disks to virtual machine hosts
supporting ESX, Hyper-V, and HP Integrity VM hypervisors. HP recommends creating user-defined
portability groups in Matrix OE logical server management and then configuring virtual machine
hosts that contain physical disks to be mapped to virtual servers into the user-defined portability
groups. HP also recommends creating RDM-based Storage Pool Entries (SPE) in the user-defined
portability groups so that IO can allocate or reserve resources from the same Portability Group.
You can also use storage tags to guide IO during allocation or reservation to correctly identify
RDM-based SPEs. This means that the virtual machine hosts will be part of only two Portability
Groups, the default portability and a user portability group.
NOTE: Currently, you cannot attach physical disks to High Availability Hyper-V virtual machines.
You can, however, attach physical disks to non-High Availability Hyper-V virtual machines.
For more information, see HP Matrix Operating Environment Logical Server Management User
Guide.
Provisioning physical servers using local disk
Matrix infrastructure orchestration includes support for Virtual Connect logical servers using a local
disk for boot. (Local disk is also referred to as DAS, or Direct Attached Storage.) Although these
logical servers lack the flexible movement of those using boot from SAN, a logical server using
local disk boot can be initially activated on a server, have the operating system installed on the
local disk, and then later be suspended and activated on the same physical server. If the logical
server is activated on a different physical server (with a local disk of suitable size), the operating
system must be re-deployed.
In a Virtual Connect environment, the Matrix OE software automatically gathers information about
server blades (memory, processors, and potential connectivity). Local disk information is not currently
gathered, so it is necessary to annotate the collected server information to indicate if it has a local
disk with particular properties. Local disk boot volumes are not represented by storage pool entries.
You can enable Matrix infrastructure orchestration to provision to a physical server using local
disk. This involves some manual edits of property files to ensure that Matrix is aware of the servers
that have local disks and that have mobility restrictions.
See “Modifying physical servers with local disk information” in the HP Matrix Operating Environment
Logical Server Management User Guide at http://www.hp.com/go/matrixoe/docs.
Allocating servers to a VM Host
Matrix infrastructure orchestration uses the following guidelines to determine the VM Host that will
host a newly provisioned virtual machine.
Matrix infrastructure orchestration filters VM Hosts based on service template requirements, including:
• Linked clone support (if applicable)
• High availability (HA) support (if applicable)
• VM template compatibility (if specified as Automatic OS deployment)
106 Matrix infrastructure orchestration provisioning and allocation