[152106] in North American Network Operators' Group
Re: Network Storage
daemon@ATHENA.MIT.EDU (Dan Olson)
Thu Apr 12 17:45:32 2012
Date: Thu, 12 Apr 2012 16:44:41 -0500 (CDT)
From: Dan Olson <dolson@mcs.anl.gov>
To: "John T. Yocum" <john.yocum@fluidhosting.com>
In-Reply-To: <4F874B22.7020200@fluidhosting.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
If this is just for post analysis and you have another system (IDS) to identify the timeframe,
a tape based system might be a better approach, esp if you want to retain forever.
Maybe "Library LTFS"
----- Original Message -----
From: "John T. Yocum" <john.yocum@fluidhosting.com>
To: "Valdis Kletnieks" <Valdis.Kletnieks@vt.edu>
Cc: nanog@nanog.org
Sent: Thursday, April 12, 2012 5:37:38 PM
Subject: Re: Network Storage
On 4/12/2012 2:34 PM, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 12 Apr 2012 14:18:30 -0700, "John T. Yocum" said:
>> In that case, just keep adding disks to you capture system, or use a NAS
>> to do it.
>
> On Thu, 12 Apr 2012 13:43:49 -0700, Joel jaeggli said:
>> 1TB is 2.276 hours at 1Gb/s
>
> If he's got a gigabit of traffic, he's going to be adding another shelf of 12 1T
> drives to that NAS - every day. If he gets the high-density shelves with 60 drives,
> he's only adding one a week.
>
> He's going to have to work smarter, not harder.
He did indicate he's only storing the headers and a few bytes, not the
full payload.
--John
