Starting a velero backup starts taking the backup, but when reaches 5% then skips to 100% and finishes with an error:
time="202#-0#-12T09:58:31Z" level=error msg="Error backing up item" backup=velero/###test error="pod volume backup failed: error to initialize data path: error to boost backup repository connection prod-minio-backup-wms-kopia: error to connect backup repo: error to connect repo with storage: error to connect to repository: repository not initialized in the provided storage" error. file="/go/src/github. com/vmware-tanzu/velero/pkg/podvolume/backupper.go:323" error.
Customer deleted some information on the repository as there was no space left on the device.
This generates orphan velero metadata, and repository was not manageable by velero.
Velero repository must be managed by velero.
If there is space problems you need to use velero CLI to remove data:
velero backup delete <backup>
If you use other tools, the repository will not be usable by velero. If this is the case, try to remove all data from the repository, and then run velero backup again.
As a last option, create a new repository and attach to velero.