From: | Israel Brewster <israel(at)ravnalaska(dot)net> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Backup "Best Practices" |
Date: | 2016-11-29 17:13:52 |
Message-ID: | D486BFCE-C8F7-4E00-AB65-77D3E9FE5740@ravnalaska.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Nov 28, 2016, at 10:20 PM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
>
> Israel Brewster schrieb am 28.11.2016 um 23:50:
>>>
>>> pg_archivecleanup -n /mnt/server/archiverdir 000000010000000000000010.00000020.backup
>>
>> Ok, but where does that "000000010000000000000010.00000020.backup"
>> come from? I mean, I can tell it's a WAL segment file name (plus a
>> backup label), but I don't have anything like that in my WAL
>> archives, even though I've run pg_basebackup a couple of times. Do I
>> have to call something to create that file? Some flag to
>> pg_basebackup? At the moment I am running pg_basebackup such that it
>> generates gziped tar files, if that makes a difference.
>
> The .backup file will be inside the tar file if I'm not mistaken
Oh, ok - thanks. I'll check on that. Although since I am generating gziped tar files, that's not the easiest thing in the world - I'll have to decompress the file first, then extract the .backup file. Still, worth looking into I suppose :-)
-----------------------------------------------
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Israel Brewster | 2016-11-29 18:33:01 | Re: Backup "Best Practices" |
Previous Message | Israel Brewster | 2016-11-29 17:12:14 | Re: Backup "Best Practices" |