automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
Automation Suite on EKS/AKS installation guide
Last updated Mar 9, 2026
Velero backup fails with FailedValidation error
Description
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.
Solution
To address the issue, take the following steps:
-
Verify the backup storage locations configured for Velero:
kubectl get backupstoragelocations -n velerokubectl get backupstoragelocations -n veleroConfirm whether the DEFAULT column is empty.
-
Edit the backup storage location to set the default value:
kubectl edit backupstoragelocation default-bs1 -n velerokubectl edit backupstoragelocation default-bs1 -n velero -
Under the
specsection, add the following line:default: truedefault: true -
Save the changes.
-
Restart the Velero pods to apply the configuration:
kubectl delete pod -n velero --allkubectl delete pod -n velero --allAlternatively, perform a rolling restart:
kubectl -n velero rollout restart deploy/velerokubectl -n velero rollout restart deploy/velero -
Verify the fix:
kubectl get backupstoragelocations -n velerokubectl get backupstoragelocations -n velero
Confirm that the PHASE is Available and the DEFAULT column shows Yes.