Minor Description
Need to Engineering to update descriptions for cbtransfer --h to match with documentation. We just edited these for 2.0.2 in the docs and made them readable/understandable.
Not sure what this release this should be in.
-h, --help Command help
-b BUCKET_SOURCE Single named bucket from source cluster to transfer
-B BUCKET_DESTINATION, --bucket-destination=BUCKET_DESTINATION Single named bucket on destination cluster which receives transfer. This allows you to transfer to a bucket with a different name as your source bucket. If you do not provide defaults to the same name as the bucket-source
-i ID, --id=ID Transfer only items that match a vbucketID
-k KEY, --key=KEY Transfer only items with keys that match a regexp
-n, --dry-run No actual transfer; just validate parameters, files, connectivity and configurations
-u USERNAME, --username=USERNAME REST username for source cluster or server node
-p PASSWORD, --password=PASSWORD REST password for cluster or server node
-t THREADS, --threads=THREADS Number of concurrent workers threads performing the transfer. Defaults to 4.
-v, --verbose Verbose logging; provide more verbosity
-x EXTRA, --extra=EXTRA Provide extra, uncommon config parameters
--single-node Transfer from a single server node in a source cluster. This single server node is a source node URL
--source-vbucket-state=SOURCE_VBUCKET_STATE Only transfer from source vbuckets in this state, such as 'active' (default) or 'replica'. Must be used with Couchbase cluster as source.
--destination-vbucket-state=DESTINATION_VBUCKET_STATE Only transfer to destination vbuckets in this state, such as 'active' (default) or 'replica'. Must be used with Couchbase cluster as destination.
--destination-operation=DESTINATION_OPERATION Perform this operation on transfer. "set" will override an existing document, 'add' will not override, 'get' will load all keys transferred from a source cluster into the caching layer at the destination.
The following are extra, specialized command options you use in this form cbtransfer -x [EXTRA OPTIONS]:
batch_max_bytes=400000 Transfer this # of bytes per batch.
batch_max_size=1000 Transfer this # of documents per batch
cbb_max_mb=100000 Split backup file on destination cluster if it exceeds MB
max_retry=10 Max number of sequential retries if transfer fails
nmv_retry=1 0 or 1, where 1 retries transfer after a NOT_MY_VBUCKET message. Default of 1.
recv_min_bytes=4096 Amount of bytes for every TCP/IP batch transferred
report=5 Number batches transferred before updating progress bar in console
report_full=2000 Number batches transferred before emitting progress information in console
try_xwm=1 As of 2.0.2, transfer documents with metadata. 1 is default. 0 should only be used if you transfer from 1.8.x to 1.8.x.
For 2.0.2
<row>
<entry>data_only=0</entry>
<entry>For value 1, only transfer data from a backup file or cluster.</entry>
</row>
<row>
<entry>design_doc_only=0</entry>
<entry>For value 1, transfer design documents only from a backup file or cluster. Defaults to 0.</entry>
</row>
For 2.0.2