• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hyper-V & EqualLogic

WicKeD

Golden Member
Hi All,

I am setting up my first SQL Hyper-V environment. Here is the setup

Host:Windows 2012 R2 Data Center
7 pNIC's

2 - Teamed for Hyper-V Management
2 - Teamed for Hyper-V Virtualization
1 - iSCSI
1 - iSCSI
1 - Live Migration

SAN: EqualLogic PS6100

V/M Guest: Windows 2012 R2 with SQL
I have the vNIC connected to the network

I have created in Hyper-V - two Virtual Switches for connection to the EQL. These vSwitches are connected to the pNICS for iSCSI on the host.

I have a volume on the EQL for the .VHDX's connected to the host. Inside resides our SQL VHDX.

I have another volume on the EQL that is for the SQL Data and Logs - I am connecting this directly to the V/M Guest via disk management.

The question I have... is this setup in a suitable way? I do not say "best" way, as that is subjective. I do not have additional pNIC's to use for iSCSI traffic on the guest, so I am using the iSCSI pNIC's of the host.

Thanks!
 
Last edited:
It'll work, if that's what you mean. I'm guessing these are 1 Gbps NICs since you have so many of them. Without knowing anything about the size of your database, the I/O profile, or the disk layout on your PS6100, I couldn't make any comments as far as whether or not that's optimal.

One thing I would suggest is separating the SQL logs - put them on their own volume. SQL logs writes are sequential while SQL data traffic is going to be mostly random. Separating them will result in better performance for both.
 
Last edited:
Back
Top