In a SQL 2012 cluster with SAN storage infrastructure, what is best practice or common LUN/volume provisioning scheme? Does the following list make sense?:
| NAME | PURPOSE | VOLUME | SIZE | LOCATION |
| Quorum | Cluster Witness Disk | Q: | 1 GB | Shared |
| TempDB | TempDB | E: | TBD | Local |
| Sys | SQL System | F: | TBD | Shared |
| Data | SQL Data | G: | TBD | Shared |
| Logs | SQL Logs | H: | TBD | Shared |
Should it be simplified by putting system and user databases on the same drive? Any reason to separate them?
Above volume letters would be used on both nodes, right? I.E, when you're adding the disk resources to each node, can the same letters be used?
If the cluster was multi-instance with two SQL Failover Cluster Instances, then Instance 2 would have to use I:, J:, K:, L:, right?
Thanks.