Cbbackup stops at 2/3 of the way

Here’s the console output:

2016-10-17 21:18:09,002: mt cbbackup...
2016-10-17 21:18:09,002: mt  source : http://localhost:8091
2016-10-17 21:18:09,002: mt  sink   : /root/couchbase-database-backup/backups
2016-10-17 21:18:09,002: mt  opts   : {'username': '<xxx>', 'verbose': 1, 'dry_run': False, 'extra': {'max_retry': 10.0, 'rehash': 0.0, 'dcp_consumer_queue_length': 1000.0, 'data_only': 0.0, 'uncompress': 0.0, 'nmv_retry': 1.0, 'cbb_max_mb': 100000.0, 'report': 5.0, 'mcd_compatible': 1.0, 'try_xwm': 1.0, 'backoff_cap': 10.0, 'batch_max_bytes': 400000.0, 'report_full': 2000.0, 'flow_control': 1.0, 'batch_max_size': 1000.0, 'seqno': 0.0, 'design_doc_only': 0.0, 'recv_min_bytes': 4096.0}, 'single_node': False, 'ssl': False, 'vbucket_list': None, 'threads': 2, 'mode': 'full', 'key': None, 'password': '<xxx>', 'id': None, 'silent': False, 'bucket_source': 'MY-BUCKET'}
2016-10-17 21:18:09,039: mt bucket: MY-BUCKET
2016-10-17 21:22:49,022: w1   source : http://localhost:8091(MY-BUCKET@CB1:8091)
2016-10-17 21:22:49,022: w1   sink   : /root/couchbase-database-backup/backups(MY-BUCKET@78.46.186.166:8091)
2016-10-17 21:22:49,023: w1          :                total |       last |    per sec
2016-10-17 21:22:49,023: w1    batch :                 1156 |       1156 |        4.1
2016-10-17 21:22:49,026: w1    byte  :            927873742 |  927873742 |  3316007.3
2016-10-17 21:22:49,026: w1    msg   :               113433 |     113433 |      405.4
2016-10-17 21:22:55,883: w0   source : http://localhost:8091(MY-BUCKET@CB2:8091)
2016-10-17 21:22:55,884: w0   sink   : /root/couchbase-database-backup/backups(MY-BUCKET@78.46.139.172:8091)
2016-10-17 21:22:55,884: w0          :                total |       last |    per sec
2016-10-17 21:22:55,884: w0    batch :                 1126 |       1126 |        3.9
2016-10-17 21:22:55,885: w0    byte  :            832810465 |  832810465 |  2903450.3
2016-10-17 21:22:55,885: w0    msg   :               113841 |     113841 |      396.9
2016-10-17 21:27:51,604: w0   source : http://localhost:8091(MY-BUCKET@CB3:8091)
2016-10-17 21:27:51,605: w0   sink   : /root/couchbase-database-backup/backups(MY-BUCKET@88.198.89.50:8091)
2016-10-17 21:27:51,606: w0          :                total |       last |    per sec
2016-10-17 21:27:51,607: w0    batch :                 1152 |       1152 |        3.9
2016-10-17 21:27:51,608: w0    byte  :            866617974 |  866617974 |  2930610.1
2016-10-17 21:27:51,608: w0    msg   :               113502 |     113502 |      383.8
2016-10-17 21:27:54,809: w1   source : http://localhost:8091(MY-BUCKET@CB4:8091)
2016-10-17 21:27:54,809: w1   sink   : /root/couchbase-database-backup/backups(MY-BUCKET@88.198.89.48:8091)
2016-10-17 21:27:54,810: w1          :                total |       last |    per sec
2016-10-17 21:27:54,810: w1    batch :                 1147 |       1147 |        3.8
2016-10-17 21:27:54,810: w1    byte  :            911383749 |  911383749 |  2980555.0
2016-10-17 21:27:54,811: w1    msg   :               113552 |     113552 |      371.4
  [#############       ] 67.0% (454328/estimated 678586 msgs)
bucket: MY-BUCKET, msgs transferred...
       :                total |       last |    per sec
 batch :                 4581 |       4581 |        7.8
 byte  :           3538685930 | 3538685930 |  6035213.7
 msg   :               454328 |     454328 |      774.9
done


After importing it to a new cluster, init sync with my app I don’t receive all documents and my app is not usable. I outlined this awhile back here: Some documents were not synced at initial sync. After trying 10x it worked without making any changes

Is it possible that the backup could not be successfully created? I don’t see any error message but why would it stop early?

Setup: CB 4.0; SG 1.2; 4 CB nodes; SG were running during backup but there was hardly any traffic. 50 ops/s

I’d like to add that I recently added conflict solving on the client side. The code for solving is in this thread: Solve conflicts on client side (Android)

I expected the backups to get smaller in size as many revisions could be pruned. So the backups are smaller, the backup process finishes without issues. It looks odd that the process is finished at around 70%