I have a share set up on my array at /mnt/user/d/. There are specific users that have permissions to read and write.

I recently installed Postgresql in a Docker container. I'm migrating PSQL from a Windows machine to Unraid.

It's database folder is on the shared drive, at a similar place as it was on the prior Windows server. (On Windows D: was a physical drive, on Unraid, d is a share)

/var/lib/postgresql <--> /mnt/user/d/postgresql18/

I'm finding that /mnt/user/d/postgresql18/ is not accessible by users of /mnt/user/d/

Looking at the /mnt/user/d/postgresql18/ in an SSH terminal, I see the user and group are all 999.

root@T440:/mnt/user/d/postgresql18/18/docker# ls -l

total 64

-rw------- 1 999 999 3 Nov 28 11:46 PG_VERSION

drwx------ 1 999 999 53 Nov 29 10:49 base/

drwx------ 1 999 999 38 Dec 10 13:29 global/

drwx------ 1 999 999 10 Nov 28 11:46 pg_commit_ts/

drwx------ 1 999 999 10 Nov 28 11:46 pg_dynshmem/

-rw------- 1 999 999 5743 Nov 30 13:19 pg_hba.conf

-rw------- 1 999 999 2681 Nov 28 11:46 pg_ident.conf

...

Since PSQL is accessed over the network, I generally don't need direct file access. However the d share is for files that needs layers of backup, not just the array and parity. I have a script for periodic offline/offsite backup that runs from another machine. It has permission for the d share. It should be including the PSQL files, and it is failing.

What is the best approach to insure the PSQL databases get backed up?

Docker containers use their own permissions, and they should be in a separate share that is typically not accessed over the network, like appdata, but you could use a different one, but in that case it's probably best to use a specific share just for that.

@JorgeB Thanks for the reply.
So if I want to move the PSQL data off the primary share I would just shut down the PSQL Container, run a command like this from Unraid SSH:

mv /mnt/user/d/postgresql18/* /mnt/user/some/other/share/

Then change the volume mapping of the docker container to /var/lib/postgresql <--> /mnt/user/some/other/share/

To my original question on how to back up PSQL, I presume use something like

pg_dumpall > /mnt/user/d/postgresqlbackup/psql_dumpfile.dat

That can create a backup while the psql container is running.

Set it up as a user scripts scheduled process once a day or something? That would write its output to the d share and get backed up automatically.

That should work, as for the backup, can't really help, as I've never used it, recomend asking in the existing container support thread.