tag:blogger.com,1999:blog-13073408.post4502135373537879807..comments2008-09-12T10:51:29.922-04:00Peter Lanoiehttp://www.blogger.com/profile/11480942345027154915noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13073408.post-2067574264290873382008-09-12T10:51:00.000-04:002008-09-12T10:51:00.000-04:00Great question, I certainly do...<BR/><BR/>We have an application that uses a 60 gigabyte content repository. Instead of duplicating it on every server on the web farm, all the content is on a fiber connected SAN disk system. One of the servers was experiencing a security problem with the SAN system. The application would intermittently crash or throw "content unavailable" errors when it was being served by the one culprit machine. Being able to identify which machine was having the problem allowed us to isolate it, troubleshoot and fix it.Peter Lanoiehttp://www.blogger.com/profile/11480942345027154915noreply@blogger.comtag:blogger.com,1999:blog-13073408.post-46296200147020659682008-09-11T15:46:00.000-04:002008-09-11T15:46:00.000-04:00Intresting and simple trick! <BR/>I am curious: do you have an examples from real world when this feature helped?Mr. Sergeyhttp://www.blogger.com/profile/03017917544961133765noreply@blogger.com