We’re trying to incorporate incremental backups in our couchbase cluster and I noticed that if the cbbackupmgr process fails (e.g. creating a repo that already exists), it does not delete the lock that it creates (lock.lk), causing subsequent calls to cbbackupmgr to fail. We’re using couchbase 6.5. It’s a problem for us since we are using cron jobs to schedule the backup regularly and lock failures causes the backups to stop. Is this a known problem? If not, what are your suggestions to get around that?
./cbbackupmgr config --archive ~/backup --repo users Backup repository creation failed: Backup Repository `users` exists ls ~/backup lock.lk logs user