Partitions on virtual servers
Just query about how other people handle partitions when commissioning their new virtual servers.
On most of our physical servers we have:
C: RAID 1 (OS and applications)
D: RAID 5 (Data)
The logical drives map closely to the physical storage configuration and users get the performance benefit of having OS I/O and Data I/O on seperate arrays.
However, the performance argument for retaining this convention on virtual servers is a weak (as they are stored on the same storage unit and won't see much, if any, peformance benefit).
We have kept the convetion of C: and D: for our new virtual servers, mainly as a logical partition of OS from Data. But I do suspect that there are other specific technical reasons for wanting to maintain the seperation, but I can't actually think what they would be. I know, for example, that for a Bare Metal Recovery backup, WSBACKUP has to backup all folders on the System volume (and any volume containing system data), so keeping data away from the OS should reduce the amount of data that needs to be backed up. Having said that, what would be the point in doing a BMR backup within a VM when you can backup a VM at the host level, and therefore restore the entire VM without needing to use BMR.
It got me wondering what other people are doing when creating partitions for their new virtual servers.