Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 81987 invoked from network); 8 Jul 2010 05:51:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Jul 2010 05:51:54 -0000 Received: (qmail 33391 invoked by uid 500); 8 Jul 2010 05:51:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33164 invoked by uid 500); 8 Jul 2010 05:51:50 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 33143 invoked by uid 99); 8 Jul 2010 05:51:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jul 2010 05:51:49 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of daveviner@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-px0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jul 2010 05:51:41 +0000 Received: by pxi20 with SMTP id 20so249543pxi.31 for ; Wed, 07 Jul 2010 22:50:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=/ITB4Xc2Hgon0xxcJPQPJZ7lxqv1A6JM0gNvEEzCEuw=; b=IbIDOTmbsIWhzkYEW9+0TpxJYSLKWmW262DmOgcA4mAUKgh2/BIx4TmjLE+lkxgB32 8udUcP1AuJPklpweeW65szw2X72ZdsC59mXUhwYglG3zoHDf3Ti+ZU5P/quRbaeAfynf ne7fOaPfRqb+53C6njoYvVvQLTIsw8vGupjBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=i+HT3knN5wll4K2uYUM07klz29pohwbvTuKFtT/GLyXCQ/3xN/5OXMOtLn4ysjW5p9 KUAWSptoatyiQOz991nXLECFYwylCRoczfR8WMYhwyAsogbTrH2zY7XxMJZp+EVsEHxd YjqmGDXgyFZHzLXace/md8uqR4yOaI4nYtdss= MIME-Version: 1.0 Received: by 10.142.223.12 with SMTP id v12mr9894132wfg.86.1278568219912; Wed, 07 Jul 2010 22:50:19 -0700 (PDT) Sender: daveviner@gmail.com Received: by 10.143.163.17 with HTTP; Wed, 7 Jul 2010 22:50:19 -0700 (PDT) Date: Wed, 7 Jul 2010 22:50:19 -0700 X-Google-Sender-Auth: ZOJ4AJGXdFFRFRP2WquYChRReis Message-ID: Subject: Backing up the data stored in cassandra From: Dave Viner To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd17cc491ab84048ad9dced X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd17cc491ab84048ad9dced Content-Type: text/plain; charset=ISO-8859-1 Hi all, What is the recommended strategy for backing up the data stored inside cassandra? I realized that Cass. is a distributed database, and with a decent replication factor, backups are "already done" in some sense. But, as a relatively new user, I'm always concerned that the data is only within the system and not stored *anywhere* else. In an earlier email in the list, the recommendation was: Until tickets 193 and 520 are done, the easiest thing is to copy all the sstables from the other nodes that have replicas for the ranges it is responsible for (e.g. for replication factor of 3 on rack unaware partitioner, the nodes before it and the node after it on the right would suffice), and then run nodeprobe cleanup to clear out the excess. Is this still the recommended approach? If I backed up the files in DataDirectories/*, is it possible to restore a node using those files? (That is, bring up a new node, copy the backed up files from the crashed node onto the new node, then have the new node join the cluster?) Thanks Dave Viner --000e0cd17cc491ab84048ad9dced Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

What is the recommended strategy for backing up = the data stored inside cassandra?

I realized that = Cass. is a distributed database, and with a decent replication factor, back= ups are "already done" in some sense. =A0But, as a relatively new= user, I'm always concerned that the data is only within the system and= not stored *anywhere* else.

In an earlier email in the list, the recommendation was= :
Until tickets 193 and 520 are done, the easies=
t thing is to copy all
the sstables from the other nodes that have replicas for the ranges it
is responsible for (e.g. for replication factor of 3 on rack unaware
partitioner, the nodes before it and the node after it on the right
would suffice), and then run nodeprobe cleanup to clear out the
excess.
=
Is this still the recommended approach?  If I backed up the files in DataDi=
rectories/*, is it possible to restore a node using those files?  (That is,=
 bring up a new node, copy the backed up files from the crashed node onto t=
he new node, then have the new node join the cluster?)

Th=
anks
Dave Viner
--000e0cd17cc491ab84048ad9dced--