Home | Forums | Couchbase | Couchbase Server 2.0

upgrading from 1.8 to 2.0

3 replies [Last post]
Thu, 11/15/2012 - 04:23
vimal_a
Offline
Joined: 11/15/2012
Groups: None

Hi,

Upgrading from 1.8.1 to 2.0 beta was not as smooth as I had expected it to be.

The install process itself completed without throwing any errors and it did create the existing buckets, however it chose to leave out the data!

Here is what I see in var/lib/couchbase/data
data
\
-Bucket1
-Bucket1-data
-Bucket2
-Bucket2-data

I believe Bucket1-data and Bucket2-data are from the previous install (v1.8.1), and they seem to have the previous data intact as well.

The directories Bucket1 and Bucket2 were created after the upgrade and both have 1027 items totaling a few MB in size.

I did take a backup before the upgrade (using cbbackup from v1.8.1 install). Unfortunately, trying to restore from that backup fails with "error: there is no bucket"

Can somebody please direct me to where I can find some doc on upgrading from 1.8.1 to 2.0?

Cheers,

Top
Thu, 11/15/2012 - 08:31
tgrall
Offline
Joined: 09/05/2012
Groups: None

Have you look at this chapter in the documentation:

http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-getting-sta...

Regards
Tug

__________________

Tug
@tgrall

Top
Sun, 12/02/2012 - 22:45
dipti
Offline
Joined: 11/02/2011
Groups:

Upgrades are not supported from 1.8.X to 2.0 BETA. It might work from 1.8.X to the most recent build http://www.couchbase.com/downloads-all#couchbase-server-2-0-builds . Guidance is to use backup and restore.

http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-backup-rest...

Both offline and online upgrade will be supported from 1.8.x to 2.0GA.

Top
Mon, 01/14/2013 - 02:37
vimal_a
Offline
Joined: 11/15/2012
Groups: None

Thanks for your inputs tgrall and dipti. Unfortunately, following the instructions in the links didn't get us anywhere and we had to finally re-populate all the data in 2.0beta.

More worrying is the fact that we encountered the same issues upgrading 2.0beta to 2.0. We did find a quirky way to get around though. Basically we re-created buckets with the same name and params and copied the files from 2.0beta to 2.0. Sounds stupid, but it worked. Everything else failed. Thanks again though.

Top