[FAQ] Hi--I'm using Velero v1.4.0 with the AWS plugin. After scheduled backups run, I'm getting this error for two volumes on the cluster: ConcurrentSnapshotLimitExceeded: Maximum allowed in-progress snapshots for a single volume exceeded. #3379
-
|
Hi--I'm using Velero v1.4.0 with the AWS plugin. After scheduled backups run, I'm getting this error for two volumes on the cluster: ConcurrentSnapshotLimitExceeded: Maximum allowed in-progress snapshots for a single volume exceeded. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
If Velero triggers a persistent volume snapshot, it uses the storage provider API. In AWS, if a snapshot is triggered, the API function returns immediately, but the snapshot creating process might still be running in the background on AWS side. All AWS snapshots which are not finished yet get the label pending . You can only have 5 snapshots with this label at a time. The next one will run into the error you mentioned. So, in your case, you could lower the schedule frequency, to give the snapshots more time to finish on AWS side. You can find more details here, in section "Considerations": https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html |
Beta Was this translation helpful? Give feedback.
If Velero triggers a persistent volume snapshot, it uses the storage provider API. In AWS, if a snapshot is triggered, the API function returns immediately, but the snapshot creating process might still be running in the background on AWS side. All AWS snapshots which are not finished yet get the label pending . You can only have 5 snapshots with this label at a time. The next one will run into the error you mentioned. So, in your case, you could lower the schedule frequency, to give the snapshots more time to finish on AWS side. You can find more details here, in section "Considerations": https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html