Search:

Search all manuals
Search this manual
Manual
Couchbase Server Manual 2.0
Community Wiki and Resources
Download Couchbase Server 2.0
Couchbase Developer Guide 2.0
Client Libraries
Couchbase Server Forum
Additional Resources
Community Wiki
Community Forums
Couchbase SDKs
Parent Section
3 Administration Basics
Chapter Sections
Chapters

3.1. Couchbase Data Files

By default, Couchbase Server will store the data files under the following paths:

PlatformDirectory
Linux/opt/couchbase/var/lib/couchbase/data
WindowsC:\Program Files\couchbase\server\var\lib\couchbase\data
Mac OS X~/Library/Application Support/Couchbase/var/lig/couchbase/data

This path can be changed for each node at setup either via the Web UI setup wizard, using theREST API or using the Couchbase CLI:

Warning

Changing the data path for a node that is already part of a cluster will permanently delete the data stored.

Linux:

shell> couchbase-cli node-init -c node_IP:8091 \
    --node-init-data-path=new_path \
    -u user -p password

Windows:

shell> couchbase-cli node-init -c \
    node_IP:8091 --node-init-data-path=new_path \
    -u user -p password

Note

When using the command line tool, you cannot change the data file and index file path settings individually. If you need to configure the data file and index file paths individually, use the REST API. For more information, see Section 8.5.3, “Configuring Index Path for a Node”

For Couchbase Server 2.0, once a node or cluster has already been setup and is storing data, you cannot change the path while the node is part of a running cluster. You must take the node out of the cluster then follow the steps below:

  1. Change the path on a running node either via the REST API or using the Couchbase CLI (commands above). This change will not actually take effect until the node is restarted. For more information about using a REST-API request for ejecting nodes from clusters, see Section 8.7.4, “Removing a Node from a Cluster”.

  2. Shut the node down.

  3. Copy all the data files from their original location into the new location.

  4. Start the service again and monitor the "warmup" of the data.