Hello,
I am using velero in my k8s environments and currently I am trying to migrate our velero deployment from using restic to kopia (since restic is getting deprecated).
I updated the velero deployment and I can see that the PVC snapshots are getting created successfully by Kopia. Describing a backup would return the following:
Backup Volumes:
Velero-Native Snapshots: <none included>
CSI Snapshots: <none included>
Pod Volume Backups - kopia:
Completed:
{namespace}/{podname}: pvc-etc, pvc-var
{namespace}/{podname}: pvc-etc, pvc-var
{namespace}/{podname}: pvc-etc, pvc-var
{namespace}/{podname}: pvc-etc, pvc-var
{namespace}/{podname}: pvc-etc, pvc-var
HooksAttempted: 0
HooksFailed: 0
It also looks like the kopia repo is healthy:
~ % kopia repository status
Enter password to open repository:
Config file: {path}/repository.config
Description: Repository in S3: object.storage.eu01.onstackit.cloud {bucket}
Hostname: {hostname}
Username: {user}
Read-only: false
Format blob cache: 15m0s
Storage type: s3
Storage capacity: unbounded
Storage config: {
"bucket": "{bucketname}",
"endpoint": "object.storage.eu01.onstackit.cloud",
"accessKeyID": "***************",
"secretAccessKey": "****************************************",
"sessionToken": ""
}
Unique ID: {uniqueID}
Hash: {hash}
Encryption: {Encryption}
Splitter: {Splitter}
Format version: 3
Content compression: true
Password changes: true
Max pack length: 21 MB
Index Format: v2
Epoch Manager: enabled
Current Epoch: 0
Epoch refresh frequency: 20m0s
Epoch advance on: 20 blobs or 10.5 MB, minimum 24h0m0s
Epoch cleanup margin: 4h0m0s
Epoch checkpoint every: 7 epochs
~ % kopia blob list
Enter password to open repository:
_log_20250210151349_1235_1739193229_1739193230_1_927e42ff61e336f99c991922520a0236 766 2025-02-10 15:13:51 EET
_log_20250210154827_523c_1739195307_1739195311_1_eb788bf91a97de11775d9cc062daaddf 1396 2025-02-10 15:48:31 EET
kopia.blobcfg 30 2025-02-10 15:13:46 EET
kopia.maintenance 1152 2025-02-10 15:48:31 EET
kopia.repository 1101 2025-02-10 15:13:46 EET
qb5819eab5f3fb88afe6916799481a170-sca46a09fbbba2a00131 4298 2025-02-10 15:13:49 EET
xn0_c71d4cb84529678f3fc78be1c0c1d466-sca46a09fbbba2a00131-c1 143 2025-02-10 15:13:50 EET
backups/ 0 0001-01-01 01:33:16 LMT
kopia/ 0 0001-01-01 01:33:16 LMT
Within the kopia & the backups folders I can see:
~ % s3cmd ls -c .qss3cfg s3://{bucket}/kopia/qs-splunk/
2025-02-10 13:24 782 s3://{bucket}/kopia/qs-splunk/_log_20250210132426_1a30_1739193866_1739193868_1_a11d0dea40a1e7d10f6b905d0815acc1
...
{multiple similar}
...
2025-02-10 13:24 30 s3://{bucket}/kopia/qs-splunk/kopia.blobcfg
2025-02-11 12:27 1893 s3://{bucket}/kopia/qs-splunk/kopia.maintenance
2025-02-10 13:24 1075 s3://{bucket}/kopia/qs-splunk/kopia.repository
2025-02-10 13:25 24121647 s3://{bucket}/kopia/qs-splunk/p00019366802e2c50c74975ca90459516-s46e19a024baaf3c1131
...
{multiple similar starting p01, p02, ... p09, pff...., then starting with q, s, and xn0}
...
--------------------------
~ % s3cmd ls -c .qss3cfg s3://{bucket}/backups/velero-qs-splunk-backup-20250211020006/
2025-02-11 02:02 3639 s3://{bucket}/backups/velero-qs-splunk-backup-20250211020006/velero-backup.json
2025-02-11 02:02 29 s3://{bucket}/backups/velero-qs-splunk-backup-20250211020006/velero-qs-splunk-backup-20250211020006-csi-volumesnapshotclasses.json.gz
{multiple similar}
But when i run the following nothing gets returned:
~ % kopia snapshot list --all
Enter password to open repository:
~ %
Maybe its a trivial issue, but cannot find what the root cause might be.
If further info is needed, please let me know.
Thanks in advance for your answers!