also consider queue depth requirements for other LUs presented on the same front-end ports to all servers.
Hitachi recommends setting HBA queue depth on a per-target basis rather than per-port basis.
To calculate queue depth, use the following formula:
512 ÷ total number of LUs presented through the front-end port = HBA queue depth per host
For example, suppose that four servers share a front-end port on the storage system, and between the four
servers, 16 LUs are assigned through the shared front-end port and all LUs are constantly active. The
maximum dynamic queue depth per HBA port is 32, that is:
512 command data blocks ÷ 16 LUs presented through the front-end port = 32 HBA queue depth setting
Basic Storage System Setup
The Hitachi Adaptable Modular Storage System 2000 family has no system parameters that need to be set
specifically for a Hyper-V environment. With the 2000 family’s Dynamic Load Balancing Controllers that feature
symmetric active-active controller architecture, the LUN-ownership concept no longer exists and the associated
parameters (for example, LUN ownership change disable mode) that are available on predecessor storage
systems are obsolete.
Fibre Channel Storage Deployment
When deploying Fibre Channel storage on a 2000 family system in a Hyper-V environment, it is important to
properly configure the Fibre Channel ports and to select the proper type of storage for the child partitions that
are to be hosted under Hyper-V.
Fibre Channel Front-end Ports
Provisioning storage on two Fibre Channel front-end ports (on one port per controller) is sufficient for
redundancy on the Hitachi Adaptable Modular Storage Systems 2000 family. This results in two paths to each
LU from the Hyper-V host's point of view. For higher availability, ensure that the target ports are configured to
two separate fabrics to make sure multiple paths are always available to the Hyper-V server.
Hyper-V servers that access LUs on 2000 family storage systems must be properly zoned so that the
appropriate Hyper-V parent and child partitions can access the storage. With the 2000 family, zoning is
accomplished at the storage level by using host storage domains (HSDs). Zoning defines which LUs a
particular Hyper-V server can access. Hitachi Data Systems recommends creating a HSD group for each
Hyper-V server and using the name of the Hyper-V server in the HSD for documentation purposes.
Selecting Child Partition Storage
It is important to correctly select the type of storage deployed for the guest OS that is to be virtualized under
Hyper-V. Consider also whether VHD or pass-through disks are appropriate. The following questions can help
you make this determination:
•
Is the child partition’s I/O workload heavy, medium, or light?
If the child partition has a light workload, you might be able to place all the storage requirements on one VHD
LU. If the child partition is hosting an application such as SQL or Exchange, allocate files that are accessed
heavily, such as log and database files, to individual VHD LUs. Attach each individual LU to its own synthetic
controller.
•
What is the maximum size LU required to support the child partition?
If the maximum LU is greater that 2040GB, you must either split the data or utilize pass-through disks. This is
due to the size limitation of 2040GB for a VHD LU.
9
