I might not have explained this in enough detail, my bad.
Steps to reproduce:
Create a backup backup config and do a backup:
$ /opt/couchbase/bin/cbbackupmgr config --archive /tmp/entbackup --repo backup
|
$ /opt/couchbase/bin//cbbackupmgr backup --archive /tmp/entbackup --repo backup --cluster http://10.112.191.101:8091 --username Administrator --password password --no-progress-bar
|
Run collect-logs on the backup archive:
$ /opt/couchbase/bin/cbbackupmgr collect-logs -a /tmp/entbackup
|
Observation
In the logs directory, we see both backup-0.log, alongside the zipped logs archive:
$ ls /tmp/entbackup/logs/
|
backup-0.log cbbackupmgr-collectinfo-entbackup-2019-07-12T120351.zip
|
If we extract the logs archive, we find a backup-0.log file within that is identical to the backup-0.log we observed at the top level, alongside the backup archive:
$ cd /tmp/entbackup/logs/
|
$ unzip cbbackupmgr-collectinfo-entbackup-2019-07-12T115813.zip
|
$ diff backup-0.log cbbackupmgr-collectinfo-entbackup-2019-07-12T120351/logs/backup-0.log
|
If this is intended then by all means mark this closed. However, my understanding was the log collection was intended to give additional information by extracting the logs with relevant additional metadata and also save space by cleaning up rotating log files and compressing them into a zip file.
I could not reproduce this issue.