Hyper-v storage


hi everyone,

i reading lot best practices storage distribution regarding hyper-v in order best perfomance.

i need setup host 3 vm's client (35-to 50 user environment) , read seems need following:

1drive host operating system

guests:

dc: 1 ide drive os, 1 scsi logs+sysvol, 1 scsi page file

file server: 1 ide os, 1 scsi for page file

rds:(session based desktop deployment) 1 ide os, 1 scsi page file.

in addition need separate scsi drive old custom application , additional scsi disk general data.

all of above result of endless reading , wondering: small environment needs 10 disks?? , raid?

would make difference if raid 10 4 drives (host os separate on raid1) , put each vm on different partition? create different partitions data , applications , different partitions page files?

thanks.

hi everyone,

i reading lot best practices storage distribution regarding hyper-v in order best perfomance.

i need setup host 3 vm's client (35-to 50 user environment) , read seems need following:

1drive host operating system

guests:

dc: 1 ide drive os, 1 scsi logs+sysvol, 1 scsi page file

file server: 1 ide os, 1 scsi for page file

rds:(session based desktop deployment) 1 ide os, 1 scsi page file.

in addition need separate scsi drive old custom application , additional scsi disk general data.

all of above result of endless reading , wondering: small environment needs 10 disks?? , raid?

would make difference if raid 10 4 drives (host os separate on raid1) , put each vm on different partition? create different partitions data , applications , different partitions page files?

thanks.

1) boot os cheap sata raid1. i'd recommend use wd re because of better ure rate. 

2) keep vms on raid10. calculate typical vm iops load, multiple safe factor 1.5 or 2, keep in mind raid10 write penalty of 1/2 (reads sum of spindle iops because raid10 wide striping) , you'll see how many spindles need. go sas or need sata (preferred because of capacity).

3) decent dr plan have single point of failure (your storage). consider having virtual san if want run @ least dual hypervisor hosts (that naturally better way spread load , provide uptime). many hosts , virtual san overkill rto/rpo , amount of vms. maybe not... vm backup must. free hyper-v replica (a bit ugly in terms of usage , not support set of production workloads exchange , sql server, problem you, pain deal non-windows vms pretty job virtualized desktop windows os).

4) you're done perfect virtualization setup :)


starwind iscsi san & nas



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Event ID 64,77,1008 Certificates Events Windows Server 2008, 2008R2