As I already mentioned on my blog, here is some information on a somewhat confusing subject. I added two more questions about MSDTC that we hear often: Over the years, the best practi...
Published Jan 17, 2005
Version 1.0
Blog Post
Good points, Doug! In most cases, it would be as simple as carving out a little bit of extra logical space from the SAN and making it visible to the OS. Only in rare cases will disks exposed logically to the OS map 1:1 to spindles on the SAN.
That said, whether they are dedicated spindles or simply "stealing some capacity off the top", it still requires extra resources taken from the SAN to provide this service on the cluster. Although the performance characteristics of this logical disk should be insignificant, they may not be and you'd have to take this into consideration when designing the cluster storage.
Also consider that if you segment it all off to its own group, you'll also have to provide an additional IP and network name.
Overall, none of this is insurmountable. But it's extra work and resource consumption that is typically unnecessary.
Thanks for your comment!
Evan
That said, whether they are dedicated spindles or simply "stealing some capacity off the top", it still requires extra resources taken from the SAN to provide this service on the cluster. Although the performance characteristics of this logical disk should be insignificant, they may not be and you'd have to take this into consideration when designing the cluster storage.
Also consider that if you segment it all off to its own group, you'll also have to provide an additional IP and network name.
Overall, none of this is insurmountable. But it's extra work and resource consumption that is typically unnecessary.
Thanks for your comment!
Evan