Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAAvtoWQ4ZDaFbYim3CJq5+-fWcO-PDa6mDFEkznv-5kEeRgWYw@mail.gmail.com>
References: 
 <CAAvtoWQ4ZDaFbYim3CJq5+-fWcO-PDa6mDFEkznv-5kEeRgWYw@mail.gmail.com>
From: Maciek Sakrejda <maciek@heroku.com>
Date: Fri, 18 Sep 2015 11:09:30 -0700
Message-ID: 
 <CAKwe89AaRrKVjfDDZxJWtPoVVXrBhpscp0ytNPrAnUo4eDo_0Q@mail.gmail.com>
Subject: Re: What is your backup strategy for Cassandra?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11412e3833b9cb052009711a

--001a11412e3833b9cb052009711a
Content-Type: text/plain; charset=UTF-8

On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky <mtamsky@gmail.com> wrote:

> This seems like an apt time to quote [1]:
>
> > Remember that you get 1 point for making a backup and 10,000 points for
> restoring one.
>
> Restoring from backups is my goal.
>
> The commonly recommended tools (tablesnap, cassandra_snapshotter) all seem
> to leave the restore operation as a pretty complicated exercise for the
> operator.
>
> Do any include a working way to restore, on a different host, all of node
> X's data from backups to the correct directories, such that the restored
> files are in the proper places and the node restart method [2] "just works"?
>

As someone getting started with Cassandra, I'm very much interested in this
as well. It seems that for the most part, folks seem to rely on replication
and node replacement to recover from failures, and perhaps this is a
testament for how well this works, but as long as we're hauling out
aphorisms, "RAID is not a backup" seems to (partially) apply here too.

I'd love to hear more about how the community does restores, too. This
isn't complaining about shoddy tooling: this is trying to understand--and
hopefully, in time, improve--the status quo re: disaster recovery. E.g.,
given that tableslurp operates on a single table at a time, do people
normally just restore single tables? Is that used when there's filesystem
or disk corruption? Bugs? Other issues? Looking forward to learning more.

Thanks,
Maciek

--001a11412e3833b9cb052009711a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky <span dir=3D"=
ltr">&lt;<a href=3D"mailto:mtamsky@gmail.com" target=3D"_blank">mtamsky@gma=
il.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gm=
ail_quote"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><div class=3D"gmail_extra">This seems like an apt time to quote [1]:=
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">&gt;=
=C2=A0Remember that you get 1 point for making a backup and 10,000 points f=
or restoring one.</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">Restoring from backups is my goal.</div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra">The commonly recommended tools (ta=
blesnap, cassandra_snapshotter) all seem to leave the restore operation as =
a pretty complicated exercise for the operator.</div><div><br></div><div>Do=
 any include a working way to restore, on a different host, all of node X&#=
39;s data from backups to the correct directories, such that the restored f=
iles are in the proper places and the node restart method [2] &quot;just wo=
rks&quot;?<br></div></div></div></div></div></div></blockquote><div><br></d=
iv><div>As someone getting started with Cassandra, I&#39;m very much intere=
sted in this as well. It seems that for the most part, folks seem to rely o=
n replication and node replacement to recover from failures, and perhaps th=
is is a testament for how well this works, but as long as we&#39;re hauling=
 out aphorisms, &quot;RAID is not a backup&quot; seems to (partially) apply=
 here too.<br><br></div><div>I&#39;d love to hear more about how the commun=
ity does restores, too. This isn&#39;t complaining about shoddy tooling: th=
is is trying to understand--and hopefully, in time, improve--the status quo=
 re: disaster recovery. E.g., given that tableslurp operates on a single ta=
ble at a time, do people normally just restore single tables? Is that used =
when there&#39;s filesystem or disk corruption? Bugs? Other issues? Looking=
 forward to learning more.<br><br></div><div>Thanks,<br></div><div>Maciek<b=
r></div></div></div></div>

--001a11412e3833b9cb052009711a--