From user-return-33982-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue May 7 20:54:56 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98978F284 for ; Tue, 7 May 2013 20:54:56 +0000 (UTC) Received: (qmail 50986 invoked by uid 500); 7 May 2013 20:54:54 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 50960 invoked by uid 500); 7 May 2013 20:54:54 -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 50952 invoked by uid 99); 7 May 2013 20:54:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 20:54:54 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [206.225.165.112] (HELO HUB024-nj-6.exch024.serverdata.net) (206.225.165.112) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 20:54:47 +0000 Received: from MBX024-E1-NJ-6.exch024.domain.local ([10.240.10.56]) by HUB024-NJ-6.exch024.domain.local ([10.240.10.45]) with mapi id 14.03.0123.003; Tue, 7 May 2013 13:54:06 -0700 From: Kanwar Sangha To: "user@cassandra.apache.org" Subject: backup strategy Thread-Topic: backup strategy Thread-Index: Ac5LZK1UFkmu+85ESeOQCj3TholK3w== Date: Tue, 7 May 2013 20:54:05 +0000 Message-ID: <57C7C3CBDCB04F45A57AEC4CB21C0CCD1DBABAC7@mbx024-e1-nj-6.exch024.domain.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [38.122.186.90] Content-Type: multipart/alternative; boundary="_000_57C7C3CBDCB04F45A57AEC4CB21C0CCD1DBABAC7mbx024e1nj6exch_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_57C7C3CBDCB04F45A57AEC4CB21C0CCD1DBABAC7mbx024e1nj6exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi - If we have a RF=3D2 in a 4 node cluster, how do we ensure that the bac= kup taken is only for 1 copy of the data ? in other words, is it possible f= or us to take back-up only from 2 nodes and not all 4 and still have at lea= st 1 copy of the data ? Thanks, Kanwar --_000_57C7C3CBDCB04F45A57AEC4CB21C0CCD1DBABAC7mbx024e1nj6exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi – If we have a RF=3D2 = in a 4 node cluster, how do we ensure that the backup taken is only for 1 c= opy of the data ? in other words, is it possible for us to take back-up onl= y from 2 nodes and not all 4 and still have at least 1 copy of the data ?

 

Thanks,

Kanwar

 

 

 

--_000_57C7C3CBDCB04F45A57AEC4CB21C0CCD1DBABAC7mbx024e1nj6exch_--