Академический Документы
Профессиональный Документы
Культура Документы
( Part 7 of 20 )
Windows Server 2012 and our completely FREE Hyper-V Server 2012 certainly have some really cost effective new storage options, with Storage Spaces and Hyper-V over SMB 3.0. However, many IT Pros have already invested in iSCSI shared storage and, as a result, many Hyper-V deployments also need to be able to leverage these existing storage investments. iSCSI? No problem! Windows Server 2012 and Hyper-V Server 2012 include native support for a software iSCSI initiator as well as MPIO ( Multipath IO ) for resiliency and load balancing of storage IO over multiple network paths. In this article, well walk through the process of connecting Windows Server 2012 and Hyper-V Server 2012 to common iSCSI storage arrays. Because most of my IT Pro friends are running Hyper-V either on Windows Server 2012 Server Core or Hyper-V Server 2012, both options without a local console GUI, Ill be providing my examples below in PowerShell. NOTE: In this article, I make the assumption that your iSCSI storage array is already configured and that your HyperV host is already physically attached and zoned into your iSCSI storage network.
Dont have an iSCSI Storage Array? Did you know that Windows Server 2012 includes an iSCSI Target role that, along with Failover Clustering, allows it to become a cost-effective and highly-available iSCSI Storage Array? Walk through the process of getting this configured in the following Step-by-Step Guide: DO IT: Step-by-Step: Build a Windows Server 2012 Storage Server
New-IscsiTargetPortal TargetPortalAddress <IP_Address or FQDN of storage array> $target = Get-IscsiTarget Connect-IscsiTarget NodeAddress $target.NodeAddress
If youre successfully connected to the target on your iSCSI storage array, you should see the connection status returned with the following cmdlet:
Get-IscsiConnection
Now, lets make the session for this iSCSI connection persist across reboots with the following command:
Get-IscsiSession | Register-IscsiSession
You can check to make sure the IsPersistent value is True for this session with the following command line:
Get-IscsiSession
Initialize-Disk Number <Disk_Number> PartitionStyle GPT PassThru | New-Partition AssignDriveLetter UseMaximumSize | Format-Volume
After this command completes, you can use the following command to confirm the drive letter assigned to the new partition on your iSCSI disk so that you can begin using this path for storing new virtual machines and virtual hard disks!
Get-Partition
Install-WindowsFeature Multipath-IO
After MPIO is installed, configure it to automatically claim all iSCSI devices for MPIO with the following command lines:
Set-MSDSMGlobalDefaultLoadBalancePolicy -Policy RR
NOTE: The above commands leverage the Microsoft MPIO DSM ( Device Specific Module ). Prior to attempting to implement MPIO between your hosts and storage array, be sure to check with your storage array vendor to confirm their compatibility with this DSM. In some cases, your storage vendor may require an alternate DSM and/or a different MPIO configuration. Many storage arrays that are SPC-3 compliant will work with the Microsoft DSM, but we recommend confirming compatibility with your storage vendor before proceeding.