Error transferring backup to permanent storage #98

Closed
opened 2026-04-05 16:15:45 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @BabaninFV on 2/24/2026

Databasus version

v3.16.2 (containerd)

Operating system and architecture

Host: Armbian + Kubernetes

Describe the bug (please write manually, do not ask AI to summarize)

I have two storage devices connected:

  • Longhorn - for storing configuration files.
  • NFS(ZFS) - for long-term storage.

The settings are as follows:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: databasus-data-pvc
spec:
  storageClassName: "data-nvme"
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

---
...
spec:
  containers:
    - name: databasus
      image: databasus/databasus:v3.16.2
      imagePullPolicy: IfNotPresent
      volumeMounts:
        - name: data
          subPath: databasus-data
          mountPath: /databasus-data
        - name: nfs-data
          subPath: backups
          mountPath: /databasus-data/backups
  volumes:
    - name: data
      persistentVolumeClaim:
        claimName: databasus-data-pvc
    - name: nfs-data
      nfs:
        path: /cluster/storage/databasus
        server: xxx.xxx.xxx.xxx

When creating a backup, I get the following error:

save to storage: failed to move file from temp to backups: rename /databasus-data/temp/OWU-20260224-145437-3ee840a4-2a60-4cbf-accd-587d6fa0c3ba /databasus-data/backups/OWU-20260224-145437-3ee840a4-2a60-4cbf-accd-587d6fa0c3ba: invalid cross-device link

Could you add the ability to set paths for backups and temporary files via environment variables?

It would be great if you could set an arbitrary path on the disk in the storage settings.

*Originally created by @BabaninFV on 2/24/2026* ## Databasus version v3.16.2 (containerd) ## Operating system and architecture Host: Armbian + Kubernetes ## Describe the bug (please write manually, do not ask AI to summarize) I have two storage devices connected: - Longhorn - for storing configuration files. - NFS(ZFS) - for long-term storage. The settings are as follows: ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: databasus-data-pvc spec: storageClassName: "data-nvme" accessModes: - ReadWriteOnce resources: requests: storage: 1Gi --- ... spec: containers: - name: databasus image: databasus/databasus:v3.16.2 imagePullPolicy: IfNotPresent volumeMounts: - name: data subPath: databasus-data mountPath: /databasus-data - name: nfs-data subPath: backups mountPath: /databasus-data/backups volumes: - name: data persistentVolumeClaim: claimName: databasus-data-pvc - name: nfs-data nfs: path: /cluster/storage/databasus server: xxx.xxx.xxx.xxx ``` When creating a backup, I get the following error: ``` save to storage: failed to move file from temp to backups: rename /databasus-data/temp/OWU-20260224-145437-3ee840a4-2a60-4cbf-accd-587d6fa0c3ba /databasus-data/backups/OWU-20260224-145437-3ee840a4-2a60-4cbf-accd-587d6fa0c3ba: invalid cross-device link ``` Could you add the ability to set paths for backups and temporary files via environment variables? It would be great if you could set an arbitrary path on the disk in the storage settings.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/databasus#98