S3 backup location appends "/archive" to s3 bucket

I’m attempting to restore from an existing s3 cbbackup archive created by the backup service on a standard install CB 7.6 which was configured with the UI.

I’m attempting to restore it to a cluster on k8s using the cb operator. When I engage the restore - the error suggests that there are no repositories at the location - but the location has “/archive” which is not the location of the archive.

2024-09-30T12:40:53 ERROR Subprocess call exited with non-zero return code 1 │
│ 2024-09-30T12:40:53 ERROR Arguments: cbbackupmgr info --json --archive s3://flipt-couchbase-back │
│ up-qa/test/archive --obj-staging-dir /data/staging --s3-force-path-style │
│ 2024-09-30T12:40:53 ERROR Stdout: b’{“error”:“archive '/data/staging/archive' does not ex │
│ ist”}\n’ │
│ 2024-09-30T12:40:53 ERROR Stderr: b’’ │
│ 2024-09-30T12:40:53 ERROR Failed to list repositories │
│ 2024-09-30T12:40:53 ERROR Command ‘[‘cbbackupmgr’, ‘info’, ‘–json’, ‘–archive’, ‘s3://flipt-co │
│ uchbase-backup-qa/archive’, ‘–obj-staging-dir’, ‘/data/staging’, ‘–s3-force-path-style’]’ │
│ returned non-zero exit status 1. │
│ Stream closed EOF for default/my-restore-ckmq7 (cbbackupmgr-restore)

The existing archive in s3 has no path prefix - so it’s at the root of the bucket.

Is this a configuration error? How to correct?

Hey David,

Could you post your full CouchbaseBackupRestore resource here?

Thanks,

Justin Ashworth
Manager, Cloud Native Engineering

apiVersion: couchbase.com/v2
kind: CouchbaseBackupRestore
metadata:
name: my-restore
spec:
backup: my-backup
backoffLimit: 1
start:
str: oldest
end:
str: latest
objectStore:
secret: flipt-couchbase-backup-qa
uri: s3://flipt-couchbase-backup-qa
stagingVolume:
size: 20Gi
storageClassName: ebs-sc

Ok - more information - I find that when I create a backup using the backup object in k8s - it automatically appends “archive” to the s3 URI when it creates the backup, so if I specify “s3://mybucket/someprefix” the backup ends up in s3://mybucket/someprefix/archive" - Thus when I want to restore from a backup archive created using the UI on a non-k8s CB cluster, looks like I’m going to have to append “/archive” to its name.

Unfortunately that does look like the case David.

Thanks,

-Justin