I have been running Exchange databases on a F720 for about three months. While documenting our Disaster Recovery procedure, I managed to fill the disks, causing a failure. I should have disabled snapshots while I was doing this, as my frequent changes caused snapshots to consume way too much disk space. I got great support from Network Appliance in restoring the database -- after I had the case escalated. The first support engineer I was talking to had very little experience with Exchange. While I understand they all need to learn about SnapManager, the time to do this was not during my emergency.

Since this problem occurred, I have started using SnapMirror, and could now get back to any time within the past 4 hours from my mirrored volume. Linda Loux Systems Administrator Rosetta Inpharmatics

-----Original Message----- From: Jennifer Armenta [mailto:ArmentaJ@mascorp.com] Sent: Monday, March 19, 2001 11:30 AM 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."