Regarding "cbrestore"

Hello All,

While restoring the data and design documents using “cbrestore” utility i’m getting below exception:

error: could not restore design doc id: _design/Ajit/myOwnView; response: None; err: error: unable to access REST API:; please check source URL, username (-u) and password (-p); response: 400; reason: consume_design

  1. Couchbase server version: Version: 2.2.0 enterprise edition (build-821).
  2. I have used below command to export the data and views:

./cbbackup /home/schakkir/CouchbaseViewsBackup -b Sportsbook --single-node -u admin -p defaultpassword -k ‘^CLASS.*’

  1. After the above step i have used below command to import the data again into a Couchbase bucket:

/cbrestore -u admin -p defaultpassword /home/schakkir/CouchbaseViewsBackup --bucket-source=Sportsbook --bucket-destination=Content

This command is able to import all documents into the target bucket but while loading the views data it is failing with above exception.

I’m not sure where i’m going wrong, Can some one please assist me to over come this issue?


Remember that if you are using the Enterprise Edition you probably have an enterprise support account. Do not hesitate to log a ticket there.

In the meantime I am trying to reproduce/understand this.


Hi Tug,

Thanks for the response. We are in the process of procuring an enterprise support account as of now we don’t have it.


Well, the cbrestore only restores the view definition. We do not backup or restore the view data.
You can easily recreate those views to get around this if needed until we figure out the issue with the restore command itself.

Hi Tug,

I’m getting this error only with the views whose “Design Document Name” includes “forward slash(/)” character init. For example in the above error we have given the “Design Document Name” as “Ajit/myOwnView”. I have given a try after removing the above view and it is working fine.

Could you please give me an idea why it is showing this behavior if we have the “forward slash(/)” in “Design Document Name”?


Just in case it’s a forward slash problem, too, here’s a bug to track this down…