Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of rcoli@eventbrite.com
 designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOvGnNxqHvcRp3gNvyKhQZQMuLgoisZGYNEKf_SSjYh3kR+fJw@mail.gmail.com>
References: 
 <CAOvGnNxqHvcRp3gNvyKhQZQMuLgoisZGYNEKf_SSjYh3kR+fJw@mail.gmail.com>
Date: Tue, 5 Nov 2013 17:27:54 -0800
Message-ID: 
 <CAEDUwd1uodMheNqEPgBUQ8VpF2d=afDiV+YZFOzJPQM+gcRdUw@mail.gmail.com>
Subject: Re: Backup strategy
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=047d7b3a83d4f1345804ea780e08

--047d7b3a83d4f1345804ea780e08
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 5, 2013 at 4:36 PM, Sridhar Chellappa
<schellap2009@gmail.com>wrote:

>
>    1. *If not, what is the right  backup strategy ?*
>
> You didn't specify, but it sounds like you are doing a snapshot and then a
full offhost backup of the sstables?

Perhaps instead of point in time full backups, you could continuously back
up with something like tablesnap [1]? tablesnap watches the datadir for
newly created SSTables and then writes the file and a manifest containing
which other files were also in the directory at the time. These two pieces
of information allow you to restore to the point in time when any given
(immutable) data file was created.

=Rob

[1] https://github.com/synack/tablesnap

--047d7b3a83d4f1345804ea780e08
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Nov 5, 2013 at 4:36 PM, Sridhar Chellappa <span di=
r=3D"ltr">&lt;<a href=3D"mailto:schellap2009@gmail.com" target=3D"_blank">s=
chellap2009@gmail.com</a>&gt;</span> wrote:=A0<div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div style=3D"text-indent:0px;letter-spac=
ing:normal;font-variant:normal;text-align:start;font-style:normal;font-weig=
ht:normal;line-height:normal;color:rgb(34,34,34);text-transform:none;font-s=
ize:13px;white-space:normal;font-family:arial,sans-serif;word-spacing:0px">
<ol><li><b style=3D"color:rgb(153,0,255);font-size:13px">If not, what is th=
e right=A0 backup strategy ?</b><br></li>
</ol></div></div>
</blockquote></div><div class=3D"gmail_extra">You didn&#39;t specify, but i=
t sounds like you are doing a snapshot and then a full offhost backup of th=
e sstables?</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e=
xtra">
Perhaps instead of point in time full backups, you could continuously back =
up with something like tablesnap [1]? tablesnap watches the datadir for new=
ly created SSTables and then writes the file and a manifest containing whic=
h other files were also in the directory at the time. These two pieces of i=
nformation allow you to restore to the point in time when any given (immuta=
ble) data file was created.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">=3DRob</div=
><div class=3D"gmail_extra"><br></div>[1] <a href=3D"https://github.com/syn=
ack/tablesnap">https://github.com/synack/tablesnap</a></div></div>

--047d7b3a83d4f1345804ea780e08--