K
Q

some backup storage locations are invalid: backup store for location "default" is invalid:

11/22/2019

Installed velero-client v1.1.0 from git.

Installed velero service with the following command

velero install --provider aws --bucket velero --secret-file credentials-velero \ 
--use-volume-snapshots=false --use-restic --backup-location-config \ 
region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000,publicUrl=http://<ip:node-port>

And I am getting following error:

An error occurred: some backup storage locations are invalid: backup store for location "default" is invalid: rpc error: code = Unknown desc = AccessDenied: Access Denied

I want to deploy it on k8s.

-- Priyanka
kubernetes
velero

Similar Questions

Airflow scheduler with kubernetes executor fails :- Unknown error in KubernetesJobWatcher
helm override list values with --set in Azure DevOps
How to display a pods age?
List of kubernetes pod status condition reason
RabbitMQ cannot start after upgrading Azure Kubernetes Service (AKS)

2 Answers

11/22/2019

The command you are using needs to be populated with actual information from your environment where:

  • --provider aws instructs Velero to utilize S3 storage which is running on-prem, in my case
  • --secret-file is our Minio credentials
  • --use-restic flag ensures Velero knows to deploy restic for persistentvolume backups
  • --s3Url value is the address of the Minio service that is only resolvable from within the Kubernetes cluster * --publicUrl value is the IP address for the LoadBalancer service that allows access to the Minio UI from outside of the cluster:

Example:

velero install --provider aws \
    --bucket velero \
    --secret-file credentials-velero \ 
    --use-volume-snapshots=false \
    --use-restic \
    --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000,publicUrl=http://10.96.59.116:9000

This example is available with more details in this blog post.

-- mWatney
Source: StackOverflow
11/28/2019

This issue is because of my aws access key and secret key are invalid. Later I have given valid credentials. So, now its working fine.

-- Priyanka
Source: StackOverflow