Details
Description
Background
cbbackupmgr backup command creates a new backup directory on every run.
cbbackupmgr list command lists the content of those directories.
Whenever either one of these commands runs, all backup directories are updated.
In particular, shrd_0.fdb file in each directory gets bigger every time.
Problem
cbbackupmgr list is a "passive" command, it should not be updating anything.
Request
1) Why is cbbackupmgr list making changes?
2) Is cbbackupmgr backup supposed to just create a new backup directory or change other dirs as well?
Steps to reproduce
1) Create a backup, e.g.:
/opt/couchbase/bin/cbbackupmgr backup --archive /home/vagrant/backups --repo example --host couchbase://10.112.150.101 --username=Administrator --password=<password>
|
2) List the content a few times, like
/opt/couchbase/bin/cbbackupmgr list --archive /home/vagrant/backups --repo example
|
observe that shard_0.fdb is updated after each run, and its size increases.
Additional notes
If you run forestdb_dump with every cbbackup list, e.g.:
/opt/couchbase/bin/forestdb_dump shard_0.fdb > shard1.txt
|
the former command produces a file of the same size every time
-rw-rw---- 1 root root 53915648 Jul 25 19:54 shard_0.fdb
|
-rw-r--r-- 1 root root 458207 Jul 25 19:49 shard1.txt
|
-rw-r--r-- 1 root root 458207 Jul 25 19:51 shard2.txt
|
-rw-r--r-- 1 root root 458207 Jul 25 19:55 shard3.txt
|
the file content is different
[root@node1-cb450-centos7 data]# diff shard3.txt shard2.txt
|
2c2
|
< BID: 13162 (0x336a, byte offset: 53911552)
|
---
|
> BID: 13120 (0x3340, byte offset: 53739520)
|
4c4
|
< DB header revision number: 1044
|
---
|
> DB header revision number: 1042
|
9c9
|
< DB header BID of the last WAL flush: 13162 (0x336a, byte offset: 53911552)
|
---
|
> DB header BID of the last WAL flush: 13120 (0x3340, byte offset: 53739520)
|
Attachments
Issue Links
- blocks
-
MB-19612 4.5.1 Minor Release
-
- Closed
-