<p>We need to backup PV on an on-premise Kubernetes cluster, so we installed Velero, linked to MinIO, with Velero's File System Backup. No PV are backed up and no error is shown, only this mention appears in the logs &quot;Persistent volume is not a supported volume type for snapshots, skipping&quot;. Does someone have a clue to be able to backup PV on an on-premise cluster without having to use external Cloud providers ?</p>
<h3>Details</h3>
<p>Velero was installed using the following command (credentials-minio containing the MinIO's bucket access keys):</p>
<pre><code>velero install \
    --provider aws \
    --plugins velero/velero-plugin-for-aws:v1.2.1 \
    --bucket ka-backup \
    --secret-file ./credentials-minio \
    --use-node-agent \
    --backup-location-config region=minio,s3ForcePathStyle=&quot;true&quot;,s3Url=http://minio-1679064025.minio.svc:9000 \
    --snapshot-location-config region=minio
</code></pre>
<p>The result of a backup of namespaces shows no error, nor warnings as seen below and the status of the phase is completed.</p>
<pre><code>velero backup describe acme -n velero --kubeconfig ../VKATEST.config
Name:         acme
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:  velero.io/source-cluster-k8s-gitversion=v1.25.6
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=25

Phase:  Completed

Errors:    0
Warnings:  0

Namespaces:
  Included:  acme
  Excluded:  &lt;none&gt;

Resources:
  Included:        *
  Excluded:        &lt;none&gt;
  Cluster-scoped:  auto

Label selector:  &lt;none&gt;

Storage Location:  default

Velero-Native Snapshot PVs:  auto

TTL:  720h0m0s

CSISnapshotTimeout:  10m0s

Hooks:  &lt;none&gt;

Backup Format Version:  1.1.0

Started:    2023-03-20 14:40:18 +0100 CET
Completed:  2023-03-20 14:40:29 +0100 CET

Expiration:  2023-04-19 15:40:18 +0200 CEST

Total items to be backed up:  437
Items backed up:              437

Velero-Native Snapshots: &lt;none included&gt;
</code></pre>
<p>In the logs we can read at the end of the following extract, that: &quot;Persistent volume is not a supported volume type for snapshots, skipping&quot;.</p>
<pre><code>level=info msg=&quot;Backing up item&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:132&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= resource=persistentvolumes
level=info msg=&quot;Executing takePVSnapshot&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:412&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= resource=persistentvolumes
level=info msg=&quot;label \&quot;topology.kubernetes.io/zone\&quot; is not present on PersistentVolume, checking deprecated label...&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:445&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= persistentVolume=cassandra-logs-local-storage-fra-vkatest-ml5 resource=persistentvolumes
level=info msg=&quot;label \&quot;failure-domain.beta.kubernetes.io/zone\&quot; is not present on PersistentVolume&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:449&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= persistentVolume=cassandra-logs-local-storage-fra-vkatest-ml5 resource=persistentvolumes
level=info msg=&quot;zone info not available in nodeAffinity requirements&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:454&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= persistentVolume=cassandra-logs-local-storage-fra-vkatest-ml5 resource=persistentvolumes
level=info msg=&quot;No volume ID returned by volume snapshotter for persistent volume&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:478&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= persistentVolume=cassandra-logs-local-storage-fra-vkatest-ml5 resource=persistentvolumes volumeSnapshotLocation=default
level=info msg=&quot;Persistent volume is not a supported volume type for snapshots, skipping.&quot; backup=velero/acme logSource=&quot;pkg/backup/item_backupper.go:489&quot; name=cassandra-logs-local-storage-fra-vkatest-ml5 namespace= persistentVolume=cassandra-logs-local-storage-fra-vkatest-ml5 resource=persistentvolumes

</code></pre>
<p>Please let us know if you have a clue to be able to backup PV on an on-premise cluster without having to use external Cloud providers.</p>

Eric Hemmerlin
<p>have you add option --default-volumes-to-restic(for older versions like 1.7) or --default-volumes-to-fs-backup(new versions) when doing velero backup?
could be same problem like: <a href="https://stackoverflow.com/questions/75803242/velero-volume-snapshots-contain-no-data-when-restoring-a-backup">Velero - Volume Snapshots contain no data when restoring a backup</a></p>
