Automation Suite on EKS/AKS installation guide

Last updated Mar 31, 2026

Velero backup fails with FailedValidation error

When attempting to run a scheduled backup in Automation Suite on EKS/AKS, Velero may return the following error:

Phase: FailedValidation
Validation errors: an existing backup storage location was not specified at backup creation time and the server default default does not exist.
Error: BackupStorageLocation.velero.io "default" not found
Phase: FailedValidation
Validation errors: an existing backup storage location was not specified at backup creation time and the server default default does not exist.
Error: BackupStorageLocation.velero.io "default" not found

This occurs due to the default-bs1 BackupStorageLocation not being marked as default in the Velero configuration.

To address the issue, take the following steps:

Verify the backup storage locations configured for Velero:
```
kubectl get backupstoragelocations -n velero
kubectl get backupstoragelocations -n velero
```
Confirm whether the DEFAULT column is empty.

Edit the backup storage location to set the default value:

kubectl edit backupstoragelocation default-bs1 -n velero
kubectl edit backupstoragelocation default-bs1 -n velero

Under the spec section, add the following line:
```
default: true
default: true
```
Save the changes.

Restart the Velero pods to apply the configuration:

kubectl delete pod -n velero --all
kubectl delete pod -n velero --all

Alternatively, perform a rolling restart:

kubectl -n velero rollout restart deploy/velero
kubectl -n velero rollout restart deploy/velero

Verify the fix:

kubectl get backupstoragelocations -n velero
kubectl get backupstoragelocations -n velero

Confirm that the PHASE is Available and the DEFAULT column shows Yes.

Was this page helpful?

PREVIOUSLog streaming does not work in proxy setups

NEXTAccessing FQDN returns RBAC: access denied error