Heh .... When a new in house project went live and was put on the production SAN, it pushed all our already hard pressed services over the edge. We had already identified performance issues on Exchange two years ago which I mitigated by using some Outlook steps (though only for a portion of the user base) and our poor file cluster finally just locked up and refused to play anymore.
The combination of the two, plus Microsoft politely saying 'if you do just _one_ of the recommended steps we'd be glad to help you, but otherwise please don't make your engineers open cases again' finally got us management buy in. On the bright side, we have the archival project underway already, just can't implement do to fires. :O Steven On Feb 12, 2008 2:16 PM, Kevin Lundy <[EMAIL PROTECTED]> wrote: > Yeah we should be good from that perspective. We run that when we build a > new SAN attached server. Although I would be interested in that one > particular patch if it happens to jump back in your memory. > > And to Steven (save an extra email), definately not simply assuming SAN > issues. Thanks for that link, it's actually a better description of the > ones I have read before. We do have lots of PST users. If it proves to be > PST related, I might jump for joy as it will help justify a proper email > archive tool. > > > > On Feb 12, 2008 4:41 PM, Greg Olson <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > Make sure you have all the required hotfixes for 2003 applied as > recommended by EMC. There is one patch that I know has to be applied > otherwise you'll see this issue (But of course I can't remember the exact > one). Up on pwerlink (The EMC support site) grab the Clarion (Assuming your > using a Clarion) procedure generator (Support>>>product and diagnostic > tools>>>Clarion Tools>>>Clarion procedure generator). Run it and input your > server info, etc and it will generate a word doc of everything you need to > have on the host machine including all required os patches. > > > > > > > > > > > > > > From: Kevin Lundy [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 12, 2008 1:01 PM > > To: NT System Admin Issues > > Subject: File server lockup > > > > > > > > > > > > > > > > We have a 2003 file server attached to a 1T LUN on an EMC SAN. The server > locked up today. Stopped responding, couldn't even login locally. Power > cycled and the problem returned within about 15 minutes. Thinking the > problem was server related, we mounted the LUN on another 2003 server and > updated DFS, back in operation. > > > > > > > > > > > > We thought. > > > > > > > > > > > > About an hour later, the new server locked up in the exact same fashion. > Reboot, locked again. So the problem moved with the LUN. > > > > > > > > > > > > We are on the phone now with EMC (India) to rule out the storage. > > > > > > > > > > > > These servers are pure file servers, nothing else. When it locks, it does > not appear to be a sudden increase in CPU or memory. Our current thought > from the OS side is maybe either some NTFS corruption or some file that is > corrupted that causes a problem when accessed. There is absolutely nothing > in the event logs. After we moved the LUN, the original server is working > just fine. > > > > > > > > > > > > Any thoughts or suggestions on where to troubleshoot? > > > > > > > > > > > > Thanks > > > > > > Kevin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
