The storage design is in essence similar to the original clusterbuild however there are some slight changes. I’m using a QNAP TS-659 Pro+ (12Tb raw storage) to be the iSCSI target and provide the mapped LUN’s. The QNAP is configured as 2-disk RAID1 and 4-disk RAID5 and the latter will contain the LUN’s for the Binsfeldius Cluster.
Boot storage
Each cluster node will use an iSCSI Remote Boot LUN of 50 Gb. This LUN contains the installed Hyper-V Server 2008R2 operating system.
- Node 1 connects to iSCSI LUN “ttgbootn1″ (50Gb)
- Node 2 connects to iSCSI LUN “ttgbootn2″ (50Gb)
- Node 3 connects to iSCSI LUN “ttgbootn3″ (50Gb)
Cluster storage
The cluster itself will connect to a Cluster Shared Volume (CSV) of 930 Gb, presented as iSCSI LUN “HyperStorage“. No rocket science to this number, it’s just where the slider stopped when I took it up to a terabyte 
DC1 storage
A separate LUN for the DC1 allows for the cluster to start. This LUN is presented as “TTGDC1” and is 50 Gb. I will attach this LUN only to cluster node N1BC.
DFS storage
I will be using DFS for centralized sharing of files, a central place to put user profiles and as a location for System Center Virtual Machine Manager library for templates and ISO’s. This storage is 200 Gb and will be connected to a VM through the clusternodes and provisioned by Failover Cluster Manager as the VM’s do not have access to the storage network. The LUN is presented as “TTGDFS”.
DPM storage
A separate disk to be used by Microsoft Data Protection Manager (DPM) as part of the backup strategy (separate future post). This disk is 1500 Gb and presented as “TTGDPM”.