Technical data

DATA CENTER TECHNICAL BRIEF
TEST CONFIGURATION
The test infrastructure, shown in Figure 2, included four servers:
 Windows Domain Controller (DC)
 Microsoft SQL Server, SCOM, and SCVMM server (referenced as the “management server”) on
Windows 2008 Standard (64 bit)
 Two servers with Hyper-V on Windows 2008 Enterprise Edition (64 bit)
All servers had patches applied that were available on 2/26/2009, with the Hyper-V servers having
additional patches as recommended in Microsoft KB articles.
Installed in the Hyper-V servers were
Brocade 825 (dual ports) 8 Gbps Fibre Channel to PCIe
HBAs with firmware version 1.1.0.1 and driver version 1.1.0.1 and Brocade Host Connectivity Manager
(HCM) version 1.1.0.1. Each port was connected to a Brocade 5100 Switch with Fabric OS
®
(FOS) 6.1.1d.
The storage used in the testing was a Hewlett-Packard MSA 2000; components in your production
environment should be chosen to meet your company’s availability requirements..
Brocade 5100
Storage
Brocade 825
Fibre Channel
HBAs
Microsoft
Hyper-V
Microsoft
Hyper-V
Microsof
t
:
SQL Server
SCOM
SCVMM
Domain
Controller
Figure 1. Solution architecture
STORAGE CONSIDERATIONS
If you are planning to deploy Hyper-V using NPIV with a Brocade HBA, consider the information in the next
few sections.
Guest Files
Several files are associated with the guest in addition to the virtual disk (if you are using one):
 <vmguid>.bin file The .bin file is used to allocate enough space to store the contents of the memory
for the Virtual Machine if it needs to be saved; it will be the size of memory defined for the child
partition.
 <vmguid>.vsv file. The .vsv file is the saved state for devices. When a VM is rebooted, 20 MB is
reserved for the .vsv. When the VM is placed into a saved state, this file can shrink or expand to 50 MB,
depending on the number of devices configured for the VM.
 .VHD file. The VHD file is the file that stores the disk when you use a virtual disk.
Setting Up NPIV with Brocade HCM and Microsoft Hyper-V 4 of 12