# Error with message "envs: fs-pvc storage has unsupported type filesystem"

**URL:** <https://forums.percona.com/t/error-with-message-envs-fs-pvc-storage-has-unsupported-type-filesystem/27719>\
**Category:** Percona XtraDB Cluster\
**Tags:** kubernetes\
**Created:** [January 11, 2024, 2:25pm UTC](https://forums.percona.com/t/error-with-message-envs-fs-pvc-storage-has-unsupported-type-filesystem/27719 "2024-01-11T14:25:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manuel\_Galan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/manuel_galan/32/14574_2.png) [@Manuel\_Galan](https://forums.percona.com/u/Manuel_Galan)\
**Post date:** [January 11, 2024, 2:25pm UTC](https://forums.percona.com/t/error-with-message-envs-fs-pvc-storage-has-unsupported-type-filesystem/27719/1 "2024-01-11T14:25:49Z")

</div>

Hello all, I have both backup and pitr configured in the configuration of a perconaxtradbcluster in Vanilla Kubernetes. In the extract that configures this part I have established the following:

```auto
backup:
    allowParallel: true
    image: percona/percona-xtradb-cluster-operator:1.13.0-pxc8.0-backup-pxb8.0.32
    pitr:
      enabled: true
      storageName: fs-pvc
      timeBetweenUploads: 60
    storages:
      fs-pvc:
        type: filesystem
        volume:
          persistentVolumeClaim:
            storageClassName: nfs-csi
            accessModes: ["ReadWriteOnce"]
            resources:
              requests:
                storage: 2G
    schedule:
      - name: "daily-backup"
        schedule: "0/10 12 * * *"
        keep: 6
        storageName: fs-pvc

```

However, even though the BACKUP WORKS correctly, the PITR reports the ERROR below:

```
   message: >-
     get binlog collector deploy for cluster 'clusterdb': get storage
     **envs: fs-pvc storage has unsupported type filesystem**
   reason: ErrorReconcile
   status: 'True'
   type: error

```

If someone could help me. thank you.

---

<div class="post-metadata">

**Author:** ![anil.joshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anil.joshi/32/13100_2.png) [@anil.joshi](https://forums.percona.com/u/anil.joshi)\
**Post date:** [January 16, 2024, 11:15am UTC](https://forums.percona.com/t/error-with-message-envs-fs-pvc-storage-has-unsupported-type-filesystem/27719/2 "2024-01-16T11:15:06Z")

</div>

@Manuel_Galan

The configuration looks fine.

Can you please share a few details in order to dig down this further ?

**Storage /volume info.**

```auto
shell> kubectl get pvc
shell> kubectl describe pvc pvc_name 
shell> kubectl get pv volume-name
shell> kubectl get storageclass 
shell> kubectl get storageclass nfs-csi -o yaml

```

**Operator related logs:**

kubectl logs percona-xtradb-cluster-operator-6f4f56f5d5-qp2hb \> operator.log

**Individual PXC pod logs**

```auto
kubectl -n pxc logs cluster1-pxc-1 --prefix --all-containers > PXC1.log
kubectl -n pxc logs cluster1-pxc-2 --prefix --all-containers > PXC2.log
kubectl -n pxc logs cluster1-pxc-3 --prefix --all-containers > PXC3.log

```

**Note:-** Please change the information as per your environment.

Also, could you please confirm the OS environment where you have hosted the operator ? Was **PITR** working before or you facing issue since the initial setup ? Any latest changes in the environment or configurations ?