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 dave@muse.net.nz designates
 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABBkcAfdNsy_Fjxdy1drtGYV5LXyJSgCAGRpR9D5umSLkqP2ig@mail.gmail.com>
References: 
 <CABBkcAfdNsy_Fjxdy1drtGYV5LXyJSgCAGRpR9D5umSLkqP2ig@mail.gmail.com>
Date: Mon, 11 Jun 2012 15:27:00 +0200
Message-ID: 
 <CAHZBNKZsb_V8RPbsQEBvxLko3tOf1yZgjzC+uY5pqcTSzujjsg@mail.gmail.com>
Subject: Re: How to split the data over a period of time.
From: Dave Cottlehuber <dave@muse.net.nz>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 11 June 2012 14:50, Harikrishnan R <harikrishnan@inxsasia.com> wrote:
> Hi,
>
> =A0 =A0 My application uses couch-db for storing events. Daily on an aver=
age
> my database size increases up-to 4GB. =A0So If I keep the database for 3-=
6
> months my disk space
> get reduced.

Presumably this happens by CouchDB compaction? Or do you aggregate
and then make a summary dataset yourself?

> What is the best strategy for
>
> =A01) taking the backup of couch-db after a period of time.

This really depends on what you want to be able to restore, and how
frequently you expect to do that.

some options:

backup of couchdb file only

-> able to restore any/all docs from that time, and rebuild views from that=
.

backup view & db files

-> able to switch back to production-ready state without waiting for view
rebuilds. This works nicely if you have CoW storage (snapshots).

wire up _changes feed to a log file.

-> able to retrieve state of doc changes throughout the time period.

Consider that compaction will remove data from older revisions, keeping
only the revision tree information, to save space.

So if history of documents is important then you need to either track chang=
es
and store them separately, or consider if a simply backup prior to compacti=
on
is enough.

> =A02) how to retrieve the data from backup and from the current on demand=
.

See above, depends on what / how you want to do. You can restore any
couch db file and rename it, the docs will be accessible under the new file=
name.

> =A03) When to index the documents.

Not clear what you mean here?

A+
Dave