velero: With DataMover restored PV is Empty

What steps did you take and what happened:

• I made a Backup for Testing of an Application using this Schedule:

apiVersion: velero.io/v1
kind: Schedule
metadata:
  name: prod-30d-eu-central-1
  namespace: velero
  annotations:
spec: 
  paused: false
  schedule: "0 3 * * *" # 1x pro Tag um 3 Uhr
  useOwnerReferencesInBackup: false
  template:
    ttl: 730h # 30 Tage
    datamover: velero
    snapshotMoveData: true
    volumeSnapshotLocations:
    - csi-gp3
    storageLocation: default

• i tried restoring it using the follwoing command: velero create restore --from-backup <name of backup> --include-namespaces <namespace name>

What did you expect to happen:

• After everything finished Successfully, i expected the Data to be in the Volume, that was not the case. The Volume was just Empty

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

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help

bundle-2023-12-07-18-18-49.tar.gz

Anything else you would like to add:

• The DataUpload and DataDownload looked Good. The File size was realistic and both showed no errors

Environment:

• Velero version (use velero version): v1.12.2 (also Tried v1.12.1 and 1.12.2-rc2)
• Velero features (use velero client config get features): <NOT SET>
• Kubernetes version (use kubectl version): Client: v1.28.4
• Kubernetes installer & version: v1.27.7-eks-4f4795d
• Cloud provider or hardware configuration: EKS with CSI Plugin
• 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.

• 👍 for “I would like to see this bug fixed as soon as possible”
• 👎 for “There are more important bugs to focus on right now”