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 mdione.ext@orange.com
 designates 193.251.215.91 as permitted sender)
From: <mdione.ext@orange.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Tue, 24 Jul 2012 15:36:04 +0200
Subject: going back in time
Thread-Topic: going back in time
Thread-Index: Ac1poUWEBgPxFDvyRDuitx0ynMk2KQ==
Message-ID: 
 <32156_1343136969_500EA4C9_32156_2308_1_9632480C9F82B44294C2302320958E980849EDD383@PUEXCB2F.nanterre.francetelecom.fr>
Accept-Language: en-US, fr-FR
Content-Language: fr-FR
acceptlanguage: en-US, fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

  One of the scenarios I have to have in account for a small Cassandra clus=
ter (N=3D4) is
restoring the data back in time. I will have full backups for 15 days, and =
it's possible
that I will need to restore, let's say, the data from 10 days ago (don't as=
k, I'm not=20
going into the details why).=20

  I know/suspect that restores by KeySpace/ColumnFamily are possible (we ha=
ven't tested=20
yet), but I wonder if it would there any side effects of stopping all the n=
odes=20
(assuming cut to the other KS are OK), restoring the SSTables, and starting=
 the nodes=20
one by one.

  So far we're thinking in RF=3D4, but also in RF=3D3 or at least RF<N in t=
he future. Is=20
all this crazy talk or is it possible? Any side effects in the KS system an=
d/or indexes=20
to have in account?

--
Marcos Dione
SysAdmin
Astek Sud-Est
pour FT/TGPF/OPF/PORTAIL/DOP/HEBEX @ Marco Polo
04 97 12 62 45 - mdione.ext@orange.com


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.