I thought NetApp only made NAS boxes, not SANs. Oh, yeah - snapshots don't work, but a local backup to disk (with NTBackup) would most likely smoke.
-------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. > -----Original Message----- > From: Couch, Nate [mailto:[EMAIL PROTECTED] > Sent: Friday, September 19, 2003 12:34 PM > To: Exchange Discussions > Subject: RE: Exchange and SAN > > > I have run into this in a couple of situations. One where we > had a cluster > communicating to a SAN and the other where we had a single > member server > talking to a SAN. In both cases I have seen network > communications problems > result in the IS shutting down because the SA can't talk to > it. In the > cluster environment the Cluster Server restarts the service > just fine after > about 5 minutes. In the single server environment I have > seen this occur as > well. However, I have also seen where the SAN (Network > Appliance) corrupted > the file because there was a backup going on at the same time > the snapshot > was being taken. In this case we simply do a snapshot > restore and we are > back up in about 15-20 minutes. In this case we adjusted the > backup job to > start well after the snapshot was taken and haven't had any > problems since. > > I hope this helps. > > Nate Couch > EDS Messaging > > > > ---------- > > From: Rosales, Mario > > Reply To: Exchange Discussions > > Sent: Friday, September 19, 2003 11:16 AM > > To: Exchange Discussions > > Subject: Exchange and SAN > > > > Has anyone ran Exchange in a SAN, and were there any issues > with it? I've > > always had a raid array attached to it which could be the > same thing but > > did > > not know if there were any major differences? Any help would be > > appreciate > > it. > > > > Thanks, > > Mario > > > > > > > ************************************************************** > ************ > > * > > The contents of this communication are intended only for > the addressee > > and > > may contain confidential and/or privileged material. If you > are not the > > intended recipient, please do not read, copy, use or disclose this > > communication and notify the sender. Opinions, conclusions > and other > > information in this communication that do not relate to the official > > business of my company shall be understood as neither given > nor endorsed > > by > > it. > > > ************************************************************** > ************ > > * > > > > > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Web Interface: > > > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t ext_mode=&la > ng=english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
