Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of matthieu.rakotojaona@gmail.com
 designates 74.125.82.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACrj35GbGLC8z50XUtMxUZOdVqssTqFis7oYAQkwbFcaRMK0ng@mail.gmail.com>
References: <DD067D4C-FDF6-4346-91DF-71ACBEB44C1A@thenoi.se>
 <CABzyt1HXGNM36aHw5ZVrW_HJ7R3JA4jaNCYUx4NzrkW=NC5FFQ@mail.gmail.com>
 <E5751DF4-AA54-412D-B39D-35C43C9545E8@thenoi.se>
 <CACrj35GbGLC8z50XUtMxUZOdVqssTqFis7oYAQkwbFcaRMK0ng@mail.gmail.com>
From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Date: Thu, 5 Apr 2012 19:33:54 +0200
Message-ID: 
 <CAMiZLn1g=gyTFS=Cq4t-Tr3MwDafFJg_WtGeoD1=mXCj7FMW5Q@mail.gmail.com>
Subject: Re: Best practice for backing up CouchDB
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 5, 2012 at 6:01 PM, Mark Hahn <mark@hahnca.com> wrote:
> Good backup gives you the ability to go back to an older version of data.
> =C2=A0Replication does not allow this.

Wouldn't a _changes feed provide you with the same kind of information
? Because rsync'ing the db file, only retrieving the diff from the
last time we checked it, looks a lot like getting
     _changes?since=3DN
with the drawbacks that you would have to store the
last_fetched_seqnum somewhere and that you couldn't compress it
directly.

Anyway, I didn't know that you could just copy the db files that
easily. Yet Another great feature !

--
Matthieu RAKOTOJAONA