[TriLUG] "basement" SAN

Reginald Reed reginald.reed at gmail.com
Fri Oct 8 14:56:49 EDT 2004


In addition, its good to note that many NAS implementations actually
use SANs for the the block level I/O - generally via fiber channel or
iSCSI connections.  This provides much more flexibility in how you
maintain your physical disks and the view to your users on the other
side of your NAS.

--Reggie

On Fri, 08 Oct 2004 11:51:45 -0400, Dan Monjar <dan at daijin.dissimulo.com> wrote:
> --On Friday, October 08, 2004 08:50:25 AM -0400 Ryan Leathers
> <Ryan.Leathers at globalknowledge.com> wrote:
> 
> > I think the conventional wisdom these days Dan is that we have either file
> > level access or block level access being NAS and SAN respectively.  So for
> > example, while a Fiber Channel SAN clearly uses its own network you might
> > also have an iSCSI SAN which shares the same IP/GigE network used for all
> > sorts of other traffic.  SAN is less about the "dedicatedness" of the
> > network or protocol and more about the type of I/O - file or block.
> >
> > A practical example might help...
> > A NAS might be selected for use by a mail server which needs tons of
> > storage but need not be fast.
> > A SAN might be selected for use by a database system where read/write
> > speeed is everything.
> >
> >
> 
> Interesting... thanks!
> 
> 
> --
> Dan Monjar
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>



More information about the TriLUG mailing list