Configure Data Movement Backup PVC in Helm

[ehemmerlin]

Describe the problem/challenge you have
We would like to configure Data Movement Backup PVC in Helm to use a specific storage class.

In the documentation about BackupPVC Configuration for Data Movement Backup this sample backupPVC config is given:

{
    "backupPVC": {
        "storage-class-1": {
            "storageClass": "backupPVC-storage-class",
            "readOnly": true
        },
        "storage-class-2": {
            "storageClass": "backupPVC-storage-class"
        },
        "storage-class-3": {
            "readOnly": true
        }        
    }
}

Where and how should it be included in the Helm values file?

Describe the solution you'd like
A clear example of how to configure Data Movement Backup PVC in Helm to use a specific storage class would help.

Environment:

• helm version (use helm version): 3.12.3
• helm chart version and app version (use helm list -n <YOUR NAMESPACE>): velero-7.2.1
• Kubernetes version (use kubectl version): 1.28.3
• Kubernetes installer & version:
• Cloud provider or hardware configuration: on-prem
• OS (e.g. from /etc/os-release): Ubuntu 20.04

[ehemmerlin]

As VolumeSnapshots created by the Velero CSI plugins are retained only for the lifetime of the backup even if the DeletionPolicy on the VolumeSnapshotClass is set to Retain, we don't need anymore to set a different backup storage class for data movement backups. This question can be closed.

VolumeSnapshots created by the Velero CSI plugins are retained only for the lifetime of the backup even if the DeletionPolicy on the VolumeSnapshotClass is set to Retain. To accomplish this, during deletion of the backup the prior to deleting the VolumeSnapshot, VolumeSnapshotContent object is patched to set its DeletionPolicy to Delete. Deleting the VolumeSnapshot object will result in cascade delete of the VolumeSnapshotContent and the snapshot in the storage provider.

See more here: https://velero.io/docs/main/csi/#implementation-choices