<p>Couchbase cbbackup failing from the remote server, which has full connectivity to the Couchbase running on K8s.</p>
<ul>
<li>Couchbase Server version: couchbase: community-6.0.0</li>
<li>Couchbase running on Kubernetes 1.17.</li>
</ul>
<p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>cbbackup -m full http://{IP}:61006 /backup-1 -u admin -p password -vvv</code></pre>
</div>
</div>
</p>
<blockquote>
<p>error: SASL auth socket error: 192.168.72.10:11210, timed out</p>
</blockquote>
<p>cbbackup log added below,</p>
<p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>mt cbbackup...
mt  source : http://{IP}:61006
mt  sink   : /backup-1
mt source_class: &lt;class 'pump_dcp.DCPStreamSource'&gt;
mt Starting new HTTP connection (1): {IP}
mt "GET /pools/default/buckets HTTP/1.1" 200 19966
mt sink_class: &lt;class 'pump_bfd.BFDSink'&gt;
mt source_buckets: bucket-1
mt bucket: bucket-1
mt  source_nodes: 192.168.72.10:8091
mt  enqueueing node: 192.168.72.10:8091
mt rest_request: &lt;ud&gt;admin&lt;/ud&gt;@{IP}:61006/pools/default/buckets/bucket-1/stats/curr_items; reason: total_msgs
w0  node: 192.168.72.10:8091
w0 sink_bucket: bucket-1
w0   DCPStreamSource connecting mc: 192.168.72.10:11210
s0   create_db: /backup-1/2020-07-28T083342Z/2020-07-28T083342Z-full/bucket-bucket-1/node-192.168.72.10%3A8091/data-0000.cbb
s0   connect_db: /backup-1/2020-07-28T083342Z/2020-07-28T083342Z-full/bucket-bucket-1/node-192.168.72.10%3A8091/data-0000.cbb
mt rest_request: &lt;ud&gt;admin&lt;/ud&gt;@{IP}:61006/pools/default/buckets/bucket-1/stats/vb_active_resident_items_ratio; reason: total_msgs
w0   pump (http://{IP}:61006(bucket-1@192.168.72.10:8091)-&gt;/backup-1(bucket-1@192.168.72.10:8091)) done.
w0   source : http://{IP}:61006(bucket-1@192.168.72.10:8091)
w0   sink   : /backup-1(bucket-1@192.168.72.10:8091)
w0          :                total |       last |    per sec
w0  node: 192.168.72.10:8091, done; rv: (u'error: SASL auth socket error: 192.168.72.10:11210, timed out', None)
(u'error: SASL auth socket error: 192.168.72.10:11210, timed out', None)</code></pre>
</div>
</div>
</p>
<p><em>Raised issue in Couchbase forum as well. Refer <a href="https://forums.couchbase.com/t/couchbase-cbbackup-fails-from-remote-server/26950" rel="nofollow noreferrer">here</a>.</em></p>
<p>Any idea about this? I am stuck with this issue.</p>
<p><strong>Update</strong>
I can't use the exposed memcached port for cbbackup as no option added in the official <a href="https://docs.couchbase.com/server/6.0/cli/cbbackup-tool.html" rel="nofollow noreferrer">document</a>..
<a href="https://forums.couchbase.com/t/how-to-cbbackup-on-kubernetes-docker-issues/10544/3" rel="nofollow noreferrer">This</a> answer posted in the Couchbase forum gives some details. If that is true then, its not possible to run a successful cbbackup from a remote system. But I don't think the Couchbase team has designed in that way. Hope there is way to achieve the same.</p>
<ul>
<li>Backing up and Restoring a Couchbase is tested and working using Kubernetes Jobs. But looking for a remote Couchbase backup.</li>
</ul>

<p>Unfortunately, backup from an external network is not possible with Couchbase 6.0.</p>
<p><a href="https://docs.couchbase.com/server/6.0/cli/cbbackup-tool.html#description" rel="nofollow noreferrer">https://docs.couchbase.com/server/6.0/cli/cbbackup-tool.html#description</a></p>
<blockquote>
<p>The cbbackup, cbrestore, and cbtransfer tools do not communicate with external IP addresses for server nodes outside of a cluster. Backup, restore, or transfer operations are performed on data from a node within a Couchbase Server cluster. They only communicate with nodes from a node list obtained within a cluster. This also means that if Couchbase Server is installed with a default IP address, an external hostname cannot be used to access it.</p>
</blockquote>
<p>This caveat is not present in the documentation for 6.5... I think that's because 6.5 introduced <a href="https://docs.couchbase.com/server/6.5/learn/clusters-and-availability/connectivity.html#alternate-addresses" rel="nofollow noreferrer">alternate addresses</a> for connecting from outside the network.</p>
