The size of the log data file is 56 Mb and these 20 records are getting updated 2-3 times every day from last 3-4 months.
My requirement is to copy UAT Environment data (Linux Server)to my local machine (Windows) for issue reproduction.
It’s not related with node swapping.
I also tried data export using cbexport and cbbackupmgr but these tool are not able to connect and copy data from Linux server to my local machine.
@inder, cbbackupmgr is the way to go here if you want to build the same indexes again on windows. What is the exact error that you saw when trying to use cbbackupmgr?
Backing up to 2020-01-24T12_31_40.4835966+05_30
Copying at 0B (estimating time remaining) 0 items / 0B
books [ ] 100.00%
Error backing up cluster: dial tcp 13.93.72.143:8094: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Even checking this folder - 2020-01-24T12_31_40.4835966+05_30, I can see folder for each bucket.
But i am not sure whether export is happened correctly because of the above error.
Below is the output for -
C:\Program Files\Couchbase\Server\bin>cbbackupmgr list -a C:/data/local
Size Items Name
291.14KB - /
291.14KB - + devcluster
291.14KB - + 2020-01-24T12_37_49.2115594+05_30
28.00KB - + books
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + chats
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + email
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + locale
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + misc
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + news
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + qna
28.00KB 0 + data
28.00KB 0 shard_0.fdb
39.14KB - + staging
411B 0 bucket-config.json
28.00KB 0 + data
28.00KB 0 shard_0.fdb
10.74KB 7 gsi.json
2B 0 views.json
28.00KB - + tutorials
28.00KB 0 + data
28.00KB 0 shard_0.fdb
28.00KB - + user
28.00KB 0 + data
28.00KB 0 shard_0.fdb
We can see the process crashed while trying to communicate with the Full Text Search Service to backup the Full Text Index definitions. Based on the error, the reason why I think this happening is that cbbackupmgr is trying to communicate using the internal IP for the Full Text Search Service. The version of cbbackupmgr included with 6.0.x doesn’t support alternative address (support was added in 6.5.0).
There are two options here:
Use the config command to disable backing up Full Text Search. Note however, that this issue may arise when attempting to backup the Index Service.
If this is for non production use, attempt the backup again using cbbackupmgr from 6.5.0.
Without any system collection logs we can’t guarantee that this is the exact issue you are experiencing but it’s likely that this is the issue.