<div>
i was thinking 6 x 1.2tb SAS drives in RAID 10 to give a total of 3.6tb (os runs off a hp enterprise sd card)
</div>


i was thinking 6 x 1.2tb SAS drives in RAID 10 to give a total of 3.6tb (os runs off a hp enterprise sd card)

<div>
<div class="content wysiwyg-content">
Looking at running up a Hyper V server. Will need to serve about 50 people. Will have RDS farm, with two RDS servers, a RDS broker server, a file and print server to host the RDS profile disks and data, a couple of DC's, and a Utility server. I also need to have a SQL server as well that runs the clients software / DB. Im planning to run RAID 10 for the RDS servers, etc, and a RAID 10 array for the SQL (Controller is a HP 440AR /2Gb flash back) I just want to make sure that the RDS / and SQL are not affected by IOPS from one another.<br />
Is this an over kill, or do you think a single RAID 10 for all vm's would suffice? Disks are 2.5&quot; SAS 10k drives (HP Proliant DL 380 G9 server)
</div>
</div>


Looking at running up a Hyper V server. Will need to serve about 50 people. Will have RDS farm, with two RDS servers, a RDS broker server, a file and print server to host the RDS profile disks and data, a couple of DC's, and a Utility server. I also need to have a SQL server as well that runs the clients software / DB. Im planning to run RAID 10 for the RDS servers, etc, and a RAID 10 array for the SQL (Controller is a HP 440AR /2Gb flash back) I just want to make sure that the RDS / and SQL are not affected by IOPS from one another.
Is this an over kill, or do you think a single RAID 10 for all vm's would suffice? Disks are 2.5" SAS 10k drives (HP Proliant DL 380 G9 server)

RAID / Array setup for HyperV Server

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

RAID stands for Redundant Array of Independent Disks.

RAID is data storage technology that allows multiple drives to be used together as a single virtual drive for reasons such as fault tolerance, reliability and performance. 

There are several different levels of RAID that determine how the data is stored and the level of redundancy achieved across the drives.