1How current backup/restore tools deal with design docs?
2----------------------------------------
3
4   In the extended options for cbtransfer, we have the following two options 
5
6       "data_only":       (0,      "For value 1, only transfer data from a backup file or cluster"),
7       "design_doc_only": (0,      "For value 1, transfer design documents only from a backup file or cluster"),
8
9   By default, we back up or restore both the data and design docs, i.e. view definitions. But users can choose either data only or design doc only.
10
11   cbtransfer will use memcached/dcp protocol to backup/restore data. And data are groups by bucket/node pair.
12
13   cbtrasnfer will use REST api to backup/restore design docs. Design docs are bucket specific and applied to any node within a cluster.
14
15How will we extend the current backup/restore tool for 2i?
16----------------------------------------
17
18It will depend on how we deal with the current view feature in the coming release.
19
20If we keep the view feature,  we shoud introduce new options to cbtransfer tools.
21
22       "index_meta_only":  (0,     "For value 1, transfer index meta files from backup files or a cluster")
23
24Otherwise, we will obsolete the "design_doc_only" option and replace it with "index_meta_only" option.
25
26**Dependencies**
27
28It will depend on ns_server to provide REST api to get/put index meta inforamtion.
29
30**Scope**
31
32Similar to view data,  backup/restore tool won't backup/restore index data.
33
34
35