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 rajkumars@gmail.com designates
 209.85.212.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=eeAY0tpUUDYOnAWLEoJX4sHvMIDvDnS2/miraodkD/f0ejwtLSowJHd6NUkFwh1ZJw
         rZZDOUXuBzOCgjZEJKwG0wISXoITA4dQK6BLVPntoSxXDOFQTEeGdH5odnHrPOfenJM5
         wzX4u6fvwfKFo9pkcHy57w8YzwMPFZpuFcajk=
MIME-Version: 1.0
Date: Sat, 10 Apr 2010 12:50:12 +0530
Message-ID: <z2l64de5c8b1004100020g4613eab7t50f02d2008c495a1@mail.gmail.com>
Subject: Speeding up views after a backup/restore
From: Rajkumar S <rajkumars@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

Hello,

I am using rsync to backup the couchdb database. I have multiple dbs
with size in the range of 50G and growing. While I have configured
replication and takes backup using rsync, If at some point the entire
service collapses, I need to restore my service as quickly as
possible. This include restoring the database as well as the views
that are being used by web interface.

Right now if I restore the .couch files It will take me a lot of time
to index all views all over again. So what is the best practice to
restore a service (ie, not just the couch database, but the entire web
service)  using couchdb quickly after a catastrophic failure?

with regards,

raj