HP Matrix Operating Environment 7.3 Release Notes

NOTE: VM logical servers manually created from Matrix OE visualization can also specify VM
disks on different data stores.
• Integrity VM disks must all use the same storage volume names, or be blank.
• Cloud server disks do not support storage volume names and must be blank.
• Hyper-V VM Linked Clone disks must have the same storage volume names, or be blank. They
cannot be spread across different datastores.
• Microsoft does not support VM Linked Clone using multiple data stores.
• If using Matrix recovery management to DR protect an IO service or logical server, all disks
and files of the VM must be in the same datastore.
Cross-technology logical servers are not supported by infrastructure orchestration
Cross-technology logical servers are not supported by Matrix OE infrastructure orchestration. Only
logical servers created or imported in Matrix OE logical server management, using Create→Logical
Server or Tools→Logical Servers→Import, can be moved from physical to virtual or virtual to
physical. A logical server created in infrastructure orchestration (by deploying a service template)
cannot be managed as a cross-technology logical server. For example, if a physical logical server
is created in infrastructure orchestration, it cannot be moved to a virtual machine using logical
server management. Similarly, if a virtual logical server is created in infrastructure orchestration,
it cannot be moved to a server with Virtual Connect using logical server management.
For more information about cross-technology logical servers, see the HP Matrix Operating
Environment Recovery Management User Guide at Matrix OE Information Library.
Number of networks provisioned to a logical server
The infrastructure orchestration designer does not restrict the number of networks that can be
connected to a logical server group. In practice, only four networks can be connected to virtual
logical servers, and 128 networks can be connected to physical logical servers designed to run
on HP c-Class server blades. These practical limits will increase over time as Virtual Connect and
hypervisors are enhanced.
If these limits are exceeded in an infrastructure template, provisioning operations using that template
will fail.
Suggested action
Limit the number of network connections to a logical server group to four for virtual logical servers
and 128 for physical logical servers.
Manually configure the SAN boot path for ProLiant DL/ML servers before provisioning
The job "Deploy ProLiant System Configuration (BL BFS),” contained in the Insight Control server
deployment software job folder deployed using infrastructure orchestration, cannot be used to
configure ProLiant DL/ML target servers. The job configures ProLiant/Integrity BL target servers. If
you attempt to configure ProLiant DL/ML servers using this job, the request will fail.
Suggested action
Manually configure the SAN boot path before you use infrastructure orchestration to provision a
ProLiant DL/ML target server on SAN boot LUN, as follows.
1. Create a server deployment job folder that does not contain the "Deploy ProLiant System
Configuration (BL BFS)" job.
2. Change the Boot Controller Order (from ROM-Based Setup Utility) for the ProLiant DL/ML
server to select Fibre Channel port (HBA) as the first in the boot order.
Infrastructure orchestration 21