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 74.125.44.29 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=AQVEMdK6RcuHg9oqoRUHbwme7qVnS05MGHcxPIpQkvq52AiYodTeU1+7o8KvGmlSk7
         qUM0oVtz4EthT+lyHqeYX3ur14qsH2z8t16ERF4WAHvR3EXMzzqqB8nSbH23iCeavU/G
         wA7pr++6YhrJ99eVYZz/e+Dxpm8QU8w2zko1w=
MIME-Version: 1.0
In-Reply-To: <4A197DBC.80507@borwankar.com>
References: <921000905240213y4eeee41dn7e201297382ffb6a@mail.gmail.com>
	 <e2111bbb0905240940vbd432ecy2430f597bee8c00b@mail.gmail.com>
	 <4A197DBC.80507@borwankar.com>
Date: Sun, 24 May 2009 13:08:19 -0400
Message-ID: <e2111bbb0905241008j4421bb28t830bfee88376cca7@mail.gmail.com>
Subject: Re: migrating data from a previous couch version
From: Paul Davis <paul.joseph.davis@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Nitin,

I would just pull a version of the subversion repository a couple
revisions before 753448. We didn't break the format twice or anything
so the fact that it doesn't work probably means that you had one prior
to that commit.

I'm pretty certain that was the commit that introduced the versioning
information so I can't point at anything better.

Paul Davis

On Sun, May 24, 2009 at 1:02 PM, Nitin Borwankar <nitin@borwankar.com> wrot=
e:
> Paul Davis wrote:
>>
>> Nitin,
>>
>> There's some info on how to upgrade on the wiki at [1] and [2]. If
>> your 0.9aXXXXXX version has XXXXXX < 753448 you'll need to use the
>> Ruby script at [2]. Otherwise you should be able to use couchdb-dump
>> and couchdb-load from couchdb-python or run two couchdb nodes and
>> replicate from the old version to the new version. If you're two
>> versions span that commit then you must use the Ruby script because
>> replication changes as well.
>>
>> Paul Davis
>>
>
>
> Hi Paul,
>
> Thanks much for those links and I hope to get to the point where I can us=
e
> them. =A0Currenty I only have my data in files with
> a) no older couch instance running and what's worse,
> b) no idea what version I was running in my old couch, although I know it
> was a 0.9a<something> from trunk.
>
> so I guess my question becomes
>
> a) how do I know just from the database binary files what exact couch
> version created them =A0 - is there some util or a specific set of bytes =
in
> the header or
> some voodoo that I can use and then I can go install that specific couch
> version from src. =A0Then use the database dump/load scripts.
>
> Nitin
>>
>> [1] http://wiki.apache.org/couchdb/Breaking_changes
>> [2] http://wiki.apache.org/couchdb/BreakingChangesUpdateTrunkTo0Dot9
>>
>>
>> On Sun, May 24, 2009 at 5:13 AM, Nitin Borwankar <nitin@borwankar.com>
>> wrote:
>>
>>>
>>> Hi guys,
>>>
>>> This a rather strange situation but I need to get out of it :-)
>>>
>>> I had a few Gig of data in a 0.9axxxxxx version.
>>> I wanted to upgrade couch to 0.9 tarball when it was released.
>>> I wasn't sure how it would go so I made a filesystem level backup of th=
e
>>> data directories.
>>>
>>> Then when 0.9 installed and was running fine I copied one of the
>>> databases
>>> from the old backed up dir to the new 0.9 couch's data dir.
>>> I got a "bad version" error from which I gather that the older version
>>> data
>>> is somehow not binary compatible with the newer one.
>>> I don't have a running older version couch - and it was installed from
>>> src
>>> anyway and I have no idea what minor rev of 0.9a it was.
>>>
>>> So how do I recover the old data from my files and upload it to the new
>>> version.
>>> Any ideas ?
>>>
>>> There's a lot of data in there and I absolutely need to get it out -
>>> help!
>>>
>>> Nitin
>>>
>>> 37% of all statistics are made up on the spot
>>>
>>> -----------------------------------------------------------------------=
--------------
>>> Nitin Borwankar
>>> nborwankar@gmail.com
>>>
>>>
>
>