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 -- use DS4700 Volume Copy feature for backing up the seismic date LUN
Date: Fri, 18 Jun 2010 10:38:15 -0500	[thread overview]
Message-ID: <4C1B92E7.1050900@hardwarefreak.com> (raw)
In-Reply-To: <20100618160410.034bc72f@harpe.intellique.com>

Emmanuel Florac put forth on 6/18/2010 9:04 AM:
> Le Fri, 18 Jun 2010 07:55:14 -0500
> Stan Hoeppner <stan@hardwarefreak.com> écrivait:
> 
>> 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. 
> 
> Why not, actually anything that could hold a backup will do :)

That really depends on the size of one's filesystem(s) to be backed up and the
required backup schedule.

Backup times, optimal configurations:

            10TB FS     20TB FS    40TB FS

4Gb FC      7 hours     14 hours   28 hours
1GbE NFS   28 hours     56 hours  111 hours


With 4Gb FC one could backup 40TB in just over a day.  Using a 1GbE NAS filer
it would take 4.6 days, almost an entire standard business _week_.  Now,
depending on the data, one could always tar the FS with compression and
substantially decrease these wire xfer times with either FC or NAS, which most
OPs would probably do with given the FS sizes involved.

And this is where the really nice high end arrays start to be worth their
price tag.  Even some upper midrange arrays, both SAN and NAS, have PIT
snapshot and LUN mirroring backup capabilities.  Both operations are much
faster than a filesystem level backup over the wire.

The DS4700 offers both a PIT snapshot feature called "FlashCopy" and a LUN
mirroring feature called "Volume Copy".  It would seem in the OP's case that
making use of the DS4700's Volume Copy feature would be of great benefit.  He
would simply make a Volume Copy of the current LUN holding the processed
seismic data using the System Storage DS4000 Storage Manager software.  He
should be able to schedule this operation to occur nightly, every other day,
weekly, biweekly, etc, or he could just run it manually occasionally if the
dataset doesn't change after it's been processed.

Again, given the OP's SAN hardware, this is really the only way to fly in this
case.

-- 
Stan


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

  reply	other threads:[~2010-06-18 15:35 UTC|newest]

Thread overview: 26+ 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
2010-06-18 14:04             ` Emmanuel Florac
2010-06-18 15:38               ` Stan Hoeppner [this message]
2010-06-18 12:47         ` 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

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=4C1B92E7.1050900@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