Minor Description
I ran the config command twice and when providing the archive directory as a relative path it gets created, however if I then run the same command again it complains that the path should be absolute.
[vagrant@node1-cb650-centos7 ~]$ /opt/couchbase/bin/cbbackupmgr config -a ./backup -r zzz
|
Backup repository `zzz` created successfully in archive `./backup`
|
[vagrant@node1-cb650-centos7 ~]$ /opt/couchbase/bin/cbbackupmgr config -a ./backup -r zzz
|
Backup repository creation failed: Lockfiles must be given as absolute path names
|
Also noticed that if we use the '~' expansion we get a different, and expected, result
[vagrant@node1-cb650-centos7 ~]$ /opt/couchbase/bin/cbbackupmgr config -a ~/backup -r zzz
|
Backup repository creation failed: Backup Repository `zzz` exists
|
Another result from the running the final command is that it's creating the lock file which it should not do at this stage? And furthermore it does not remove it.
[vagrant@node1-cb650-centos7 ~]$ ls backup/
|
lock.lk logs zzz
|
The next observation is that running a `backup` is not blocked due to the lock file and executes as expected?
[vagrant@node1-cb650-centos7 ~]$ /opt/couchbase/bin/cbbackupmgr backup -a ~/backup -r zzz -u Administrator -p password -c localhost
|
|
|
Backing up to 2020-03-11T20_36_20.15790492Z
|
Copied all data in 22.373837455s (Avg. 977.93KB/Sec) 31591 items / 21.01MB
|
travel-sample [===========================================================================================================================================] 100.00%
|
|
|
Backup successfully completed
|
Backed up bucket "travel-sample" succeeded
|
Mutations backedup; 31591, Mutations failed to backup: 0
|
Deletions backedup: 0, Deletions failed to backup: 0
|
[vagrant@node1-cb650-centos7 ~]$ ls ./backup/
|
logs zzz
|
[vagrant@node1-cb650-centos7 ~]$
|
