Supported upgrade paths

Supported upgrade paths

The supplied supported paths apply both to online and offline upgrades.

There are two basic upgrade paths for the Couchbase Server:

  • Couchbase 2.x to a later version of Couchbase 2.x.
  • Couchbase 2.x to Couchbase 3.0.

You must upgrade to the latest available production version before upgrading to Couchbase Server 3.0.x.

For Enterprise Edition customers, that version is Couchbase Server 2.5.2. For Community Edition users, that version is Couchbase Server 2.2.0.

Prior to upgrade, back up the files.

Platform Location
Linux /opt/couchbase/var/lib/couchbase/config/config.dat
Windows C:\Program Files\Couchbase\Server\Config\var\lib\couchbase\config\config.dat

Upgrading from Community Edition to Enterprise Edition

Note: Use the same Couchbase Server version number when upgrading to the Enterprise Edition. Version differences can result in a failed upgrade.

Upgrading from 1.8.0 to 2.x or later

There is no direct upgrade between versions 1.8.0 and 3.x. If you are upgrading from Couchbase Server 1.8 to Couchbase Server 2.0 or later, there are more steps for the upgrade because you must first upgrade to Couchbase 1.8.1 for data compatibility.

Follow the directions explained in Offline upgrade .

Upgrading to 3.0.x

With encryption access, the following port is reserved for client access to data nodes using SSL.

Port Description
11207 Internal/External Bucket Port for SSL

Upgrading to 2.5.x

Before upgrading to 2.5.x:

If buckets are using any of the following reserved ports, change the port for the bucket. Otherwise, XDCR data encryption won't be available. (This applies both to offline and online upgrades.)

Important: Verify that the Secure Socket Layer (SSL) reserved ports are available prior to using XDCR data encryption.

With XDCR data encryption, the following ports are reserved:

Port Description
11214 Incoming SSL proxy
11215 Internal outgoing SSL proxy
18091 Internal REST HTTPS for SSL
18092 Internal CAPI HTTPS for SSL
Note: If Couchbase Server 2.5 has more than two (2) replicas, the first swap rebalance takes additional time. This behavior is expected.
Restriction: The RPM package manager does not support the --relocate option because it cannot correctly detect which release must be kept and which must be replaced. As result, all binary files and their wrapper scripts cannot be correctly installed into the relocated bin directory during upgrade.