Large PVCs are canceled

What steps did you take and what happened: The data uploads of the largest pvcs failed.

velero create backup velero-schedule-s3-20241125000006 --resource-policies-configmap velero-efs-resourcepolicy --snapshot-move-data

kubectl get configmap cm -n velero velero-efs-resourcepolicy -o yaml

apiVersion: v1
data:
  efs-resourcepolicy.yaml: |
    version: v1
    volumePolicies:
    - conditions:
        csi:
          driver: efs.csi.aws.com
      action:
        type: skip
kind: ConfigMap
metadata:
  name: velero-efs-resourcepolicy
  namespace: velero

What did you expect to happen: Backup runs without problems.

The following information will help us better understand what's going on:

velero debug --backup velero-schedule-s3-20241125000006 bundle-2024-11-25-14-30-47.tar.gz

Parameters of backup:

csiSnapshotTimeout: 10m0s
itemOperationTimeout: 6h0m0s
uploaderConfig:
  parallelFilesUpload: 2

Parameters of daemonset (running in privileged mode):

  - --features=EnableCSI 
  - --data-mover-prepare-timeout=190m

Anything else you would like to add:

Environment:

Velero version (use velero version): v1.14.1
Velero features (use velero client config get features): None
Kubernetes version (use kubectl version): v1.28.15-eks-7f9249a
Kubernetes installer & version: EKS
Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release): Amazon Linux 2

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

:+1: for "I would like to see this bug fixed as soon as possible"
:-1: for "There are more important bugs to focus on right now"

vmware-tanzu / velero

Large PVCs are canceled #8454