Similar scenario here.
First, forget storage pools. Nice try - NOT THERE YET. Check google - they are a nice feature, but lack a lot of higher end stuff (expansion, rebalancing when you add discs) and have a SERIOUS performance problem. SERIOUS.
I work on similar stuff (8 disc, 24 disc servers) and I am just ignoring storage pools for the moment. Until MS handles capacity expansion nicely, and gets the performance under control, AND adds a 2nd level cache, I am just replacing my raid controllers with Adaptec 7805Q, add some SSD as transparent cache managed by the RAID controller, and keep going.
My main problem really is (a) the missing functionality along expansions and (b) - the horrific write speed (10x slower than a raid card):
Sorry, but I need performance.
Now, do not let me even start about the CRAPPY ISCSI service. Nice try - except...
...it does not work from VHDS files, only from VHD. Who had that glorious idea? TONS of nice advantages in VHDX, tons of white papers how important they are blablabla - and then the on board ISCSI service can not deal with them. GREAT. Using it for booting servers soon, but I can not say I am happy about this decision MS did.
Depending what you do with them you do not need ISCSI at all - really depends. Hyper-V can cluster shared nothing from a file share.
Now, for high availability - if you need to go that way - you need either:
- An ISCSI service that supports that on multiple machines (StarWind does that with replication between backends)
- A proper SAN
- 2 DAS with the accompanying LIS raid cards. THere is a cluster aware RAID functionality interface in windows, and LSI has the only raid controllers ready, but you need the supporting back end hardare (basically proper high available dual channel SAN enclosure).
Whatever you do with what you have in a server wont be highly available due to this server being able to fail.