Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.223.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=gu/A6I+kt4TuysLyygpjdL6xYBuV710wz4bh+AvIfvi2YFk5ZlV3ReTZJUoP62WlWa
         Awi+mPfImV15MSnysYRKZhTIDTSfnI5WmB7weZyrpqjmwmiu8pK/4BQMukRClrzKVC2M
         Og1JvS/uzJySKOI8AFgkgsJ0+ugQPJLBy6iOU=
MIME-Version: 1.0
In-Reply-To: <8098243e0910191218p7176c2eflc090a1516a41f5e@mail.gmail.com>
References: <8098243e0910191218p7176c2eflc090a1516a41f5e@mail.gmail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Mon, 19 Oct 2009 15:23:16 -0400
Message-ID: <e2111bbb0910191223v3ea7d9adhd41146cfcc0f7ce4@mail.gmail.com>
Subject: Re: couch behavior for san snapshots
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 19, 2009 at 3:18 PM, Alex P <apedenko@kolosy.com> wrote:
> hello,
>
> we ran into an issue this weekend where taking a SAN (amazon ebs) snapshot
> of a couchdb mount somehow brought over only part of the data. specifically,
> there were two small dbs (call them db1 and db2) on the couch instance, each
> with several hundred documents. taking the snapshot and bringing it up again
> showed both databases, but one had 0 documents and an update sequence of 0.
> the instance the snapshot was taken from still has both databases showing
> with several hundred databases. we repeated this process several times, with
> the same effect, on the same db.
>
> any thoughts would be much appreciated, as we are about to go live, and not
> being able to do a backup of our db is ... disturbing.
>
> thanks,
> alex.
>

Alex,

That's most odd. What happens if you try and cp the database file to a
new name? Something like:

$ cp /usr/local/var/lib/couchdb/db1.couch /usr/local/var/lib/couchdb/db3.couch

Another thing to try would be:

$ curl -X POST http://127.0.0.1:5984/db1/_ensure_full_commit

And then try to snapshot or copy again. I highly doubt that POST would
affect anything, but it might be worth a shot.

Paul Davis