Once Couchbase Server 6.5 CE is available (presumably in a couple of months) I think cbbackup will still be the recommended option to create backups. Is this correct?
Sorry that was a typo on my behalf. I have corrected the comment above. Just to be clear:
For CE (Community Edition) - cbbackup/cbrestore is the only commands to use for backup and restore
For EE (Enterprise Edition) - cbbackupmgr is the recommended tool to use.
/opt/couchbase/bin/cbbackup http://localhost:8091 ~/backups -u Administrator -p mypass
Exception in thread w0:
Traceback (most recent call last):
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 865, in run
self._target(*self._args, **self._kwargs)
File "/opt/couchbase/lib/python/pump.py", line 446, in run_worker
curx).run()
File "/opt/couchbase/lib/python/pump.py", line 504, in run
rv_batch, batch = self.source.provide_batch()
File "/opt/couchbase/lib/python/pump_dcp.py", line 254, in provide_batch
rv, batch = self.provide_dcp_batch_actual()
File "/opt/couchbase/lib/python/pump_dcp.py", line 413, in provide_dcp_batch_actual
msg = (cmd, vbucket_id, key, flg, exp, cas, rev_seqno.to_bytes(4, 'big'), val, seqno, dtype, metalen,
OverflowError: int too big to convert
â/opt/couchbase/lib/python/runtime/lib/python3.7/threading.pyâ, line 917:
Exception in thread w0:] 0.4% (28578/estimated 7339843 msgs)
Traceback (most recent call last):
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 865, in run
self._target(*self._args, **self._kwargs)
File "/opt/couchbase/lib/python/pump.py", line 446, in run_worker
curx).run()
File "/opt/couchbase/lib/python/pump.py", line 504, in run
rv_batch, batch = self.source.provide_batch()
File "/opt/couchbase/lib/python/pump_dcp.py", line 254, in provide_batch
rv, batch = self.provide_dcp_batch_actual()
File "/opt/couchbase/lib/python/pump_dcp.py", line 413, in provide_dcp_batch_actual
msg = (cmd, vbucket_id, key, flg, exp, cas, rev_seqno.to_bytes(4, 'big'), val, seqno, dtype, metalen,
OverflowError: int too big to convert
successfully import backup of production bucket which was created with Couchbase Server 6.0 CE
run backup command
Exception in thread w0:
Traceback (most recent call last):
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/couchbase/lib/python/runtime/lib/python3.7/threading.py", line 865, in run
self._target(*self._args, **self._kwargs)
File "/opt/couchbase/lib/python/pump.py", line 446, in run_worker
curx).run()
File "/opt/couchbase/lib/python/pump.py", line 504, in run
rv_batch, batch = self.source.provide_batch()
File "/opt/couchbase/lib/python/pump_dcp.py", line 254, in provide_batch
rv, batch = self.provide_dcp_batch_actual()
File "/opt/couchbase/lib/python/pump_dcp.py", line 413, in provide_dcp_batch_actual
msg = (cmd, vbucket_id, key, flg, exp, cas, rev_seqno.to_bytes(4, 'big'), val, seqno, dtype, metalen,
OverflowError: int too big to convert
^Cinterrupted.
I did the same as in this post: Cbbackup fails after upgrading to 6.5 but with Ubuntu 18.04. Same results. Is there anything else I can do to solve the issue?
The same backup works fine in version 4 database. I am upgrading to 6.5 CE and backup stopped working due to the above error. For the time being I am using a v4 instance to take the remote backup of a v6.5 instance.
Why is the meta.rev value so high? It is not a heavily used database with just a single node and few thousands of documents. How do I make cbbackup work?
Thank you for bring this issue to our attention, I have opened MB-38683,. The issue is that cbbackup is converting the Rev field to 4 bytes when it should convert it to 8 bytes.
Could you please help me understand why this rev number is so large in my case when the database is pretty small and not much happens really? I canât think of a scenario where documents are mutated more than a couple of times during their entire existence.
I have closed this topic as the original point has been addressed. With regards to the overflowError please update @Nikâs post. For new questions and issues itâs always best to open a new post rather than comment on an old one, unless youâre 100% sure it is the same issue with the same root cause.