Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jeremy.hanna1234@gmail.com
 designates 209.85.213.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=q2v0UkvrXbMkysxC473Uqs6rpY3SEzhbM+LJ5iUsNBZ6yTVwaqE6QSj4iN6dr6BYhn
         brF9gaTTWFyD2fWe/5CK7VUyIHD0m0BXKG9YbLc80uJZblma86tC9AyObHtncg+Vw95T
         22OaO1IApFOyl/eTEcGdFZpNGPxxTlsypaMkc=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: best way to backup
From: Jeremy Hanna <jeremy.hanna1234@gmail.com>
In-Reply-To: <BANLkTimvjQ5=59aNMn5h=K5q=jJ3LZFRbQ@mail.gmail.com>
Date: Thu, 28 Apr 2011 15:35:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C28D2BCD-92D3-4D55-A63E-B3FC98D76E65@gmail.com>
References: <BANLkTimvjQ5=59aNMn5h=K5q=jJ3LZFRbQ@mail.gmail.com>
To: user@cassandra.apache.org

one thing we're looking at doing is watching the cassandra data =
directory and backing up the sstables to s3 when they are created.  Some =
guys at simplegeo started tablesnap that does this:
https://github.com/simplegeo/tablesnap

What it does is for every sstable that is pushed to s3, it also copies a =
json file with the current files in the directory, so you can know what =
to restore in that event (as far as I understand).

On Apr 28, 2011, at 2:53 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? =20=

>=20
> 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).
>=20
> --=20
> Will Oberman
> Civic Science, Inc.
> 3030 Penn Avenue., First Floor
> Pittsburgh, PA 15201
> (M) 412-480-7835
> (E) oberman@civicscience.com