Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265063AbTF1Dxw (ORCPT ); Fri, 27 Jun 2003 23:53:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265065AbTF1Dxw (ORCPT ); Fri, 27 Jun 2003 23:53:52 -0400 Received: from orngca-mls01.socal.rr.com ([66.75.160.16]:29924 "EHLO orngca-mls01.socal.rr.com") by vger.kernel.org with ESMTP id S265063AbTF1Dxv (ORCPT ); Fri, 27 Jun 2003 23:53:51 -0400 Subject: Re: bkbits.net is down From: Joshua Penix To: Linux Kernel Mailing List In-Reply-To: <20030628031920.GF18676@work.bitmover.com> References: <20030627145727.GB18676@work.bitmover.com> <20030627163720.GF357@zip.com.au> <1056732854.3172.56.camel@dhcp22.swansea.linux.org.uk> <20030627235150.GA21243@work.bitmover.com> <20030627165519.A1887@beaverton.ibm.com> <20030628001625.GC18676@work.bitmover.com> <20030627205140.F29149@newbox.localdomain> <20030628031920.GF18676@work.bitmover.com> Content-Type: text/plain Message-Id: <1056773286.10255.5.camel@granite> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 27 Jun 2003 21:08:06 -0700 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1603 Lines: 35 On Fri, 2003-06-27 at 20:19, Larry McVoy wrote: > On Fri, Jun 27, 2003 at 08:51:40PM -0400, Scott McDermott wrote: > > Larry McVoy on Fri 27/06 17:16 -0700: > > > I don't know if you all realize this but at one point we > > > had corrupted data in several repositories and the backups > > > were also shot. > > > > ever hear of tapes? > > bkbits is 45GB of data and growing. Tapes are completely impractical, > that's why we have hot spares. Boy you do need a good admin :) Done correctly, tapes are quite practical for that amount of data. A LTO or SDLT drive would back the entire 45GB thing up on a single tape, with room for at least one to two more full backups. Granted, you're not going to have tape act as your hot backup, but it is a good third line of defense. Plus data backed up to tape is immune from human or software error that may otherwise affect the hard-drive based data. 45GB of code is very compressible and I'm sure good chunks of that don't change on a weekly basis. I'd imagine you could get a weekly or bi-weekly full backup to tape in the span of about two hours, and then do nightly differentials which would probably be only 15 minutes in length. A filesystem capable of doing snapshots would ensure consistency of the repositories on tape and would prevent you from having to shutdown bkbits while backing up. --Josh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/