[Request] Separate Config and Backup data paths #435

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

Originally created by @Stitch10925 on 11/5/2025

Hi developer,

I was trying to test out your backup tool on docker swarm, but I have run into an issue:

Currently the config and backup data paths are located under the same folder:

/postgresus-data

This causes issues if you want to separate your backup data from your config data. If I separate the paths like this:

volumes:
- backups:/postgresus-data/backups
- temp:/postgresus-data/temp
- /mnt/postgresus/pgdata:/postgresus-data/pgdata

I get the following error:

save to storage: failed to move file from temp to backups: rename /postgresus-data/temp/c598c1e0-51db-4165-b904-a886987f9668 /postgresus-data/backups/c598c1e0-51db-4165-b904-a886987f9668: invalid cross-device link

If the data and config paths were separated from each other this will not be a problem and it gives the user more flexibility in where to store their data. An example could be:

volumes:
- backups:/postgresus-data
- config:/postgresus-config

Where:

"/postgresus-data" would contain the "temp" and "backup" folders
"/postgresus-config" would contain the "pgdata" folder

Thank you for considering this!

*Originally created by @Stitch10925 on 11/5/2025* Hi developer, I was trying to test out your backup tool on docker swarm, but I have run into an issue: Currently the config and backup data paths are located under the same folder: > /postgresus-data This causes issues if you want to separate your backup data from your config data. If I separate the paths like this: > volumes: > - backups:/postgresus-data/backups > - temp:/postgresus-data/temp > - /mnt/postgresus/pgdata:/postgresus-data/pgdata I get the following error: > save to storage: failed to move file from temp to backups: rename /postgresus-data/temp/c598c1e0-51db-4165-b904-a886987f9668 /postgresus-data/backups/c598c1e0-51db-4165-b904-a886987f9668: invalid cross-device link If the data and config paths were separated from each other this will not be a problem and it gives the user more flexibility in where to store their data. An example could be: > volumes: > - backups:/postgresus-data > - config:/postgresus-config Where: "/postgresus-data" would contain the "temp" and "backup" folders "/postgresus-config" would contain the "pgdata" folder Thank you for considering this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/databasus#435