Hi Jens – I put together a couple of simple scripts a couple of years ago
that might do exactly what you need. These leverage nodetool snapshot and
sstableloader to create keyspace snapshots, collect up all the necessary
SSTable files in an easy-to-move file, rename the keyspace, restore it to
On 2 November 2016 at 22:10, Jens Rantil wrote:
> I mean "exposing that state for reference while keeping the (corrupt)
> current state in the live cluster".
The following should work:
1. Create a new table with the same schema but different name (in the
same or a
Hi Jens,
Looks like what you need is an "any point in time" recovery solution. I
suggest that you go back to the snapshot that you issued that was closest
to "20161102" and restore that snapshot using the bulk loader to a new
table called "users_20161102". If you need to recover precisely to a
Bryan,
On Wed, Nov 2, 2016 at 11:38 AM, Bryan Cheng wrote:
> do you mean restoring the cluster to that state, or just exposing that
> state for reference while keeping the (corrupt) current state in the live
> cluster?
I mean "exposing that state for reference while
Thanks Anubhav,
Looks like a Java project without any documentation whatsoever ;) How do I
use the tool? What does it do?
Cheers,
Jens
On Wed, Nov 2, 2016 at 11:36 AM, Anubhav Kale
wrote:
> You would have to build some logic on top of what’s natively supported.
>
>
Hi Jens,
When you refer to restoring a snapshot for a developer to look at, do you
mean restoring the cluster to that state, or just exposing that state for
reference while keeping the (corrupt) current state in the live cluster?
You may find these useful:
You would have to build some logic on top of what’s natively supported.
Here is an option:
https://github.com/anubhavkale/CassandraTools/tree/master/BackupRestore
From: Jens Rantil [mailto:jens.ran...@tink.se]
Sent: Wednesday, November 2, 2016 2:21 PM
To: Cassandra Group