public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Help with XFS
Date: Fri, 18 Jun 2010 07:55:14 -0500	[thread overview]
Message-ID: <4C1B6CB2.1020406@hardwarefreak.com> (raw)
In-Reply-To: <20100618140028.05650928@harpe.intellique.com>

Emmanuel Florac put forth on 6/18/2010 7:00 AM:
> A commodity 16TB NAS costs much less (10000 € or less)
> than the data it holds and makes a nice backup system. NOTHING replaces
> a backup. Your system WILL fail someday (well it has now apparently).

Since he already has a FC SAN, going with something like a 4Gb FC Nexsan
Sataboy w/16 1TB drives would be a better option.  Pricing should be around
$10-12k USD.  I bought an 8x500GB drive 2Gb FC Satablade back in 2006 for
approximately $9k USD because expanding our IBM FasTt 600 would have cost over
$20K USD for 1/4th the additional storage of thh Nexsan (the FasTt 600 wasn't
compatible with the EXP810, so the only expansion option was adding another FC
tray with 14x73GB 15k FC disks).

As long as the OP has a free SFP LC port on his FC switch (and the ability to
program zones) this is definitely the way to go.  No NFS/CIFS overhead.  And
given the default 1GB cache on the Sataboy, it'll likely have better
performance than the DS4700/EXP810 combo (at half the cost).  The web GUI
admin interface makes setting up and managing the Nexsan units a breeze.  I've
been really happy with ours, and with Nexsan support.  Great products, great
company.

http://www.nexsan.com/sataboy.php

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-06-18 12:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 13:18 Help with XFS Thomas Førde
2010-06-17 15:15 ` Michael Monnerie
2010-06-18 11:21 ` Emmanuel Florac
2010-06-18 11:27   ` Thomas Førde
2010-06-18 11:34     ` Emmanuel Florac
2010-06-18 11:43       ` Thomas Førde
2010-06-18 12:00         ` Emmanuel Florac
2010-06-18 12:17           ` Thomas Førde
2010-06-18 13:08             ` Emmanuel Florac
2010-06-18 13:35               ` Thomas Førde
2010-06-18 14:01                 ` Emmanuel Florac
2010-06-18 18:50                   ` Thomas Førde
2010-06-18 20:57                     ` Emmanuel Florac
2010-06-18 12:30           ` Thomas Førde
2010-06-18 12:48             ` Emmanuel Florac
2010-06-19 15:14               ` Robert Brockway
2010-06-18 13:00             ` Stan Hoeppner
2010-06-18 12:55           ` Stan Hoeppner [this message]
2010-06-18 14:04             ` Emmanuel Florac
2010-06-18 15:38               ` Help with XFS -- use DS4700 Volume Copy feature for backing up the seismic date LUN Stan Hoeppner
2010-06-18 12:47         ` Help with XFS Andi Kleen
2010-06-18 16:43         ` Michael Monnerie
2010-06-18 16:52           ` Emmanuel Florac
2010-06-19  8:29             ` Michael Monnerie
2010-06-18 17:21           ` Stan Hoeppner
2010-06-19 13:13             ` Emmanuel Florac
     [not found] <d4c731da0807251224m2632838bme52760a8a29c8871@mail.gmail.com>
2008-07-25 19:29 ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C1B6CB2.1020406@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox