How to backup PV/PVC from rancher.io/local-path ?

[VladoPortos]

Hi all,
from documentation its kind of unclear how to backup local storage provider. Like the one that come default in k3s... I have single node clustes, and all my PVC are from local storage provider:

root@forge ~/velero # kubectl get storageClass
NAME                   PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
local-path (default)   rancher.io/local-path   Delete          WaitForFirstConsumer   false                  9d

I have Velero installed and working with s3 bucket but it doe snot seems to backup the persistent files.

Backup command:

velero create backup full-backup
root@forge ~/velero # velero backup describe forge-io-full-new
Name:         full-backup
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:  velero.io/resource-timeout=10m0s
              velero.io/source-cluster-k8s-gitversion=v1.27.6+k3s1
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=27
Phase:  Completed

Warnings:
  Velero:     <none>
  Cluster:   resource: /persistentvolumes name: /pvc-98aaf4ef-0892-43f4-8630-d9e8cda952ef
             resource: /persistentvolumes name: /pvc-4a53813a-0d54-4344-b696-0c2603fba936
             resource: /persistentvolumes name: /pvc-27d960b4-60fb-4955-aec0-e5d48ede6f50
             resource: /persistentvolumes name: /pvc-c55cbc04-1392-46a0-b171-6a732a6f9ebc
             resource: /persistentvolumes name: /pvc-bd1d0e55-33e8-4806-a9d2-413e17405ee8
             resource: /persistentvolumes name: /pvc-fc899bcb-2271-4721-8252-22d4206a1132
             resource: /persistentvolumes name: /pvc-a9e57651-7d95-44c5-ab1d-db3e213ced2b
             resource: /persistentvolumes name: /pvc-8a6308b2-8373-4d60-b72a-d243f7bac91b
             resource: /persistentvolumes name: /pvc-5f166a8f-103f-4614-add9-d3a26f61d4ba
             resource: /persistentvolumes name: /pvc-6a36f10b-2b12-42e4-b431-4366c1116272
             resource: /persistentvolumes name: /pvc-5a5fc95d-9b72-4555-abd7-8d2f26aae330
  Namespaces: <none>

Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  <none>

Storage Location:  default

Velero-Native Snapshot PVs:  auto
Snapshot Move Data:          auto
Data Mover:                  velero

TTL:  720h0m0s

CSISnapshotTimeout:    10m0s
ItemOperationTimeout:  4h0m0s

Hooks:  <none>

Backup Format Version:  1.1.0

Started:    2023-10-15 14:07:53 +0200 CEST
Completed:  2023-10-15 14:08:06 +0200 CEST

Expiration:  2023-11-14 13:07:53 +0100 CET

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

Velero-Native Snapshots: <none included>

Any idea how to do it ?

[VladoPortos]

I also found this in logs:

[{\"approach\":\"volumeSnapshot\",\"reason\":\"no applicable volumesnapshotter found\"}]},{\"name\":\"pvc-c55cbc04-1392-46a0-b171-6a732a6f9ebc\",\"reasons\":[{\"approach\":\"volumeSnapshot\",\"reason\":\"no applicable volumesnapshotter found\"}]}

[sseago]

VolumeSnapshotter plugins only work for aws/ebs, gcp, and azure volumes. For other volumes (if it's not a CSI storageclass), you need to use the fs backup feature.
https://velero.io/docs/main/file-system-backup/