Hi
I've got a 3PAR 7200 with ~20TB of 15K SAS available to me for use in a new Hyper-V cluster using Server 2012. Four hosts, each with four 10GbE NICs - 2 for iSCSI, 2 for everything else.
I'm at the point in the build where I'm about to start provisioning storage and I'm curious what the best approach is. There's not going to be any unusual workloads, just Exchange 2013, SharePoint 2013, Lync 2013, SQL 2012 (guest clustering with 2 nodes). 1000 users for now with growth in the next couple of years.
I'm wondering if with all the storage virtualisation and abstraction going on in the 3PAR whether I need to create LUNs per VM or several LUNs for different CSVs or whether I should just RAID1 the lot (equiv. to RAID10 in the 3PAR) and just have 1, maybe 2 CSVs for all the VMs.
I'm thinking that If I keep the underlying LUNs few but large, then for workloads like Exchange and SQL, there's no need to separate out Logs and Data to separate LUNs when everything is going across all the spindles anyway. I can just logically separate them with different VHDs or even different partitions in a single VHD and the performance should be the same. The 3PAR is doing all the performance gains with its chunklets.
Am I missing something? I really don't want to just do something a traditional way simply because that's what worked best before, I want to keep things as simplified as possible without compromising performance.
I guess there are no right or wrong answers here. Well, maybe some wrong ones, but I'd be interested to hear how other people approach carving up their storage for Hyper-V clusters.