Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3EF99AA5 for ; Thu, 28 Apr 2011 19:58:01 +0000 (UTC) Received: (qmail 2114 invoked by uid 500); 28 Apr 2011 19:57:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 2093 invoked by uid 500); 28 Apr 2011 19:57:59 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 2085 invoked by uid 99); 28 Apr 2011 19:57:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 19:57:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates 74.125.83.172 as permitted sender) Received: from [74.125.83.172] (HELO mail-pv0-f172.google.com) (74.125.83.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 19:57:52 +0000 Received: by pvh1 with SMTP id 1so2435614pvh.31 for ; Thu, 28 Apr 2011 12:57:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ci8jbCopgg4nf9ey9MLfhPdEejyss5Zp/c6FUAhgOks=; b=Qvj3sGvYpBjV/+N/yNegCccQPRGcXNB+09oiBC6C4/9/0Sx6J7gZN5UmUYFCHVo3qd S5heYO99xlInh5e4fZ55QVAuhh+EDYXXQ3mq183+QgEydPixqCmLXGe5mY90Ll2dS2ua QQc63mbmCb5LgUS39hRrXfFHEDB04rIsGE7rE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=d+V2IUbMo6mvxU8BugzheQdvUmDd1HuREwoTnj/l3gZe0fau/YqnkxVU9kv8qv0GlF SrqVuSeDYWd6k6eslbPI+6EeCkuz/EbKgJKReCShwXI/5BMcXngKa3OSXmkQVYdSnQup Q+2pPppEzBcHN3/UfkLfSCHR6OnNjpFHqU/8I= MIME-Version: 1.0 Received: by 10.143.153.18 with SMTP id f18mr1414837wfo.114.1304020651177; Thu, 28 Apr 2011 12:57:31 -0700 (PDT) Received: by 10.143.159.7 with HTTP; Thu, 28 Apr 2011 12:57:30 -0700 (PDT) Received: by 10.143.159.7 with HTTP; Thu, 28 Apr 2011 12:57:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 21:57:30 +0200 Message-ID: Subject: Re: best way to backup From: Sasha Dolgy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636e0a59eb178ef04a1fff790 X-Virus-Checked: Checked by ClamAV on apache.org --001636e0a59eb178ef04a1fff790 Content-Type: text/plain; charset=ISO-8859-1 You could take a snapshot to an EBS volume. then, take a snapshot of that via AWS. of course, this is ok.when they -arent- having outages and issues ... On Apr 28, 2011 9:54 PM, "William Oberman" wrote: > Even with N-nodes for redundancy, I still want to have backups. I'm an > amazon person, so naturally I'm thinking S3. Reading over the docs, and > messing with nodeutil, it looks like each new snapshot contains the previous > snapshot as a subset (and I've read how cassandra uses hard links to avoid > excessive disk use). When does that pattern break down? > > I'm basically debating if I can do a "rsync" like backup, or if I should do > a compressed tar backup. And I obviously want multiple points in time. S3 > does allow file versioning, if a file or file name is changed/resused over > time (only matters in the rsync case). My only concerns with compressed > tars is I'll have to have free space to create the archive and I get no > "delta" space savings on the backup (the former is solved by not allowing > the disk space to get so low and/or adding more nodes to bring down the > space, the latter is solved by S3 being really cheap anyways). > > -- > Will Oberman > Civic Science, Inc. > 3030 Penn Avenue., First Floor > Pittsburgh, PA 15201 > (M) 412-480-7835 > (E) oberman@civicscience.com --001636e0a59eb178ef04a1fff790 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

You could take a snapshot to an EBS volume.=A0 then, take a snapshot of = that via AWS.=A0 of course, this is ok.when they -arent- having outages and= issues ...

On Apr 28, 2011 9:54 PM, "William Oberman&q= uot; <oberman@civicscience.c= om> wrote:
> Even with N-nodes for redund= ancy, I still want to have backups. I'm an
> amazon person, so naturally I'm thinking S3. Reading over the doc= s, and
> messing with nodeutil, it looks like each new snapshot conta= ins the previous
> snapshot as a subset (and I've read how cassan= dra uses hard links to avoid
> excessive disk use). When does that pattern break down?
>
&= gt; I'm basically debating if I can do a "rsync" like backup,= or if I should do
> a compressed tar backup. And I obviously want m= ultiple points in time. S3
> does allow file versioning, if a file or file name is changed/resused = over
> time (only matters in the rsync case). My only concerns with = compressed
> tars is I'll have to have free space to create the a= rchive and I get no
> "delta" space savings on the backup (the former is solved by= not allowing
> the disk space to get so low and/or adding more nodes= to bring down the
> space, the latter is solved by S3 being really c= heap anyways).
>
> --
> Will Oberman
> Civic Science, Inc.
> = 3030 Penn Avenue., First Floor
> Pittsburgh, PA 15201
> (M) 412= -480-7835
> (E) oberman@c= ivicscience.com
--001636e0a59eb178ef04a1fff790--