Re: pg_basebackup: error: could not create directory

I’m not sure what’s the use case. But if you are taking the base backup
with default format you need to make sure all tablespace directories should
be empty as it tries to create backup file under it. So try with tar format
and make sure -D directory is empty then it will create all tablespace
backups in that directory with <<tablespace our>>.tar and you should be
good.
While doing PITR or setting HA server you need to create table space
directory on target server and copy the corresponding tar file and untar
it. You will get tablespace directory information from tablespace_map file
from backup.

On Thu, Sep 5, 2024 at 8:00 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> On Thu, Sep 5, 2024 at 3:41 AM Samir Mamun <samir(dot)mamun(dot)sn(at)fujifilm(dot)com>
> wrote:
>
>> Hi,
>>
>>
>>
>> Need help with replication setup, pg_basebackup failing with:
>>
>>
>>
>> pg_basebackup -P -R -X stream -c fast -h <node_name> -U <user_name> -p
>> <port#> -D <dat_location> -v
>>
>> Password:
>>
>> pg_basebackup: initiating base backup, waiting for checkpoint to complete
>>
>> pg_basebackup: checkpoint completed
>>
>> pg_basebackup: write-ahead log start point: 6/67000028 on timeline 2
>>
>> pg_basebackup: starting background WAL receiver
>>
>> pg_basebackup: created temporary replication slot "pg_basebackup_3720137"
>>
>> pg_basebackup: error: could not create directory "……": File exists
>>
>
> It's explicitly telling you the problem: a file already exists in the
> replicated $PGDATA.
>
>
>> pg_basebackup: removing contents of data directory "…………"
>>
>> pg_basebackup: changes to tablespace directories will not be undone
>>
>
>
> --
> Death to America, and butter sauce.
> Iraq lobster!
>