I have run Exchange 5.5 (sp3) on a Filer for 2 years now without incident. The front end boxes serve up data to greater than 3000 users in a 3 state area. No problem. In fact, my ability to recover from ANY incident is greatly enhanced by this configuration. (I also use Snapmanager for Exchange). I think the KB article referenced speaks more to MS political leanings than actual technical issues. Which is weird, when you know that Netapp is a full partner with Intel and Microsoft concerning implementations of Exchange (and SQL) on Filers. I think the left hand does not know what the right hand is doing.

Ours likes Oracle as well - so go figure. Big high transaction DB's are its meat and potatoes.

And I wouldn't waste my money on EMC crap. Poor design and a million bucks everytime they open their mouths.

Feel free to email me for more details on our SUCCESS story.

Thanks

Brian Cooper BOkf Technical Services Tulsa, Oklahoma bcooper@mail.bokf.com

-----Original Message----- From: Jennifer Armenta [mailto:ArmentaJ@mascorp.com] Sent: Monday, March 19, 2001 1:30 PM To: 'Mike Sphar'; toasters@mathworks.com Subject: RE: MS Exchange on Netapps

Yes my point exactly, MS is protecting themselves. Is anyone running Exchange with/without issues. As for Oracle on NetApp I heard it doesn't like high transaction dbases. What is the ideal place for Exchange dbase ?(my bet EMC since that pretty close to have local disk)

-----Original Message----- From: Mike Sphar [mailto:mikey@Remedy.COM] Sent: Monday, March 19, 2001 11:21 AM To: toasters@mathworks.com Subject: RE: MS Exchange on Netapps

My thoughts are that any article that refers to gigabit Ethernet as an "emerging technology" is highly suspect.

I wonder if Microsoft is trying to insinuate that Oracle databases (which can run over NAS) are less "robust" and "high-performance" than their jet-based exchange DB, which allegedly can't.

Having said that, I probably wouldn't put my Exchange DBs on a filer. Too much risk of something going wrong and MS saying "Sorry, we told you not to. You're on your own."