Full Backup failing at 87. 4% everytime (Running on Couchbase 5.0.1-5003)

Couchbase Server
1

Hi All,

I am running a full back up and it is failing at 87. 4% every time we are running with Couchbase 5.0.1-5003 version.

Running the Couchbase on
Linux 3.10.0-1160.36.2.el7.x86_64 #1 SMP Thu Jul 8 02:53:40 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

We see below error.

[################# ] 86.3% (10691584/estimated 12390668 msgs)
2021-11-18 23:52:48,429: w2 progress…
2021-11-18 23:52:48,430: w2 source : ******************************************************************
2021-11-18 23:52:48,430: w2 sink : /XFS/couchbase/backup/shopping-basket(shopping-basket@:8091)
2021-11-18 23:52:48,430: w2 : total | last | per sec
2021-11-18 23:52:48,430: w2 batch : 95999 | 2000 | 64.7
2021-11-18 23:52:48,430: w2 byte : 43802685573 | 922247960 | 29831048.8
2021-11-18 23:52:48,430: w2 msg : 1887613 | 49456 | 1599.7
2021-11-18 23:53:31,107: w2 source : http://:8091/(shopping-basket@:8091)
2021-11-18 23:53:31,108: w2 sink : /XFS/couchbase/backup/shopping-basket(shopping-basket@:8091)
2021-11-18 23:53:31,108: w2 : total | last | per sec
2021-11-18 23:53:31,108: w2 batch : 97849 | 1850 | 43.3
2021-11-18 23:53:31,108: w2 byte : 44635336285 | 832650712 | 19510106.6
2021-11-18 23:53:31,108: w2 msg : 2190995 | 303382 | 7108.6
[################# ] 87.4% (10995186/estimated 12575318 msgs)
bucket: shopping-basket, msgs transferred…
: total | last | per sec
batch : 490917 | 490917 | 47.2
byte : 223754296186 | 223754296186 | 21523770.9
msg : 10995277 | 10995277 | 1057.7
2021-11-18 23:53:31,411: mt Starting new HTTP connection (1):*******
2021-11-18 23:53:31,418: mt Starting new HTTP connection (1)****************
2021-11-18 23:53:31,522: mt Starting new HTTP connection (1): **************
2021-11-18 23:53:31,527: mt Starting new HTTP connection (1):***********
done

Need below help.

  1. Not sure why the full backup is failing. How to find it? any log level increase or parameter will help to get more details in the logs?
  2. There is no parameter for community version (–resume) if the full backup failed? any alternative to it.
  3. How to increase the log level and parameter to it?

Appreciate your help.

Regards,
Dhruva