Re: [GENERAL] Backup "Best Practices"

On Mon, Nov 28, 2016 at 11:20 PM, Thomas Kellerer wrote: > Israel Brewster schrieb am 28.11.2016 um 23:50: > >> >>> pg_archivecleanup -n /mnt/server/archiverdir >>> 00010010.0020.backup >>> >> >> Ok, but where does that "00010010.0020.backup" >> come from?

Re: [GENERAL] Backup "Best Practices"

On Nov 29, 2016, at 8:12 AM, Israel Brewster wrote: > > On Nov 28, 2016, at 10:04 PM, Jeff Janes > wrote: >> >> On Mon, Nov 28, 2016 at 2:50 PM, Israel Brewster > > wrote: >> >>> - What is the "best" (or just a good) method of keeping

Re: [GENERAL] Backup "Best Practices"

On Nov 28, 2016, at 10:20 PM, Thomas Kellerer wrote: > > Israel Brewster schrieb am 28.11.2016 um 23:50: >>> >>> pg_archivecleanup -n /mnt/server/archiverdir >>> 00010010.0020.backup >> >> Ok, but where does that "00010010.0020.backup" >> come from? I me

Re: [GENERAL] Backup "Best Practices"

On Nov 28, 2016, at 10:04 PM, Jeff Janes wrote: > > On Mon, Nov 28, 2016 at 2:50 PM, Israel Brewster > wrote: > >> - What is the "best" (or just a good) method of keeping the WAL archives >> under control? Obviously when I do a new basebackup I can "cleanup" any o

Re: [GENERAL] Backup "Best Practices"

Israel Brewster schrieb am 28.11.2016 um 23:50: pg_archivecleanup -n /mnt/server/archiverdir 00010010.0020.backup Ok, but where does that "00010010.0020.backup" come from? I mean, I can tell it's a WAL segment file name (plus a backup label), but I don'

Re: [GENERAL] Backup "Best Practices"

On Mon, Nov 28, 2016 at 2:50 PM, Israel Brewster wrote: > > - What is the "best" (or just a good) method of keeping the WAL archives >> under control? Obviously when I do a new basebackup I can "cleanup" any old >> files that said backup doesn't need, >> > > You have said you might be interested

Re: [GENERAL] Backup "Best Practices"

On Nov 28, 2016, at 2:13 PM, John R Pierce wrote: > > On 11/28/2016 2:50 PM, Israel Brewster wrote: >>> >>> Why wouldn't the streaming replica salvage that? Are they expected to fail >>> together? Is the NFS share onto which you want to store your basebackup >>> and WAL also expected to fail

Re: [GENERAL] Backup "Best Practices"

On 11/28/2016 2:50 PM, Israel Brewster wrote: Why wouldn't the streaming replica salvage that? Are they expected to fail together? Is the NFS share onto which you want to store your basebackup and WAL also expected to fail together with them? That's why I specified *total* failure. If only

Re: [GENERAL] Backup "Best Practices"

On Nov 25, 2016, at 1:00 PM, Jeff Janes wrote: > > On Wed, Nov 23, 2016 at 10:16 AM, Israel Brewster > wrote: > I was wondering if someone could inform me about, or point me to an online > article about best practices for backing up a postgresql database cluster? A

Re: [GENERAL] Backup "Best Practices"

On Wed, Nov 23, 2016 at 10:16 AM, Israel Brewster wrote: > I was wondering if someone could inform me about, or point me to an online > article about best practices for backing up a postgresql database cluster? > At the moment, I have two servers running with streaming replication for > failover

Re: [GENERAL] Backup "Best Practices"

On Wed, Nov 23, 2016 at 1:16 PM, Israel Brewster wrote: > I was wondering if someone could inform me about, or point me to an online > article about best practices for backing up a postgresql database cluster? > At the moment, I have two servers running with streaming replication for > failover p

Re: [GENERAL] Backup "Best Practices"

Am 23. November 2016 20:31:21 MEZ, schrieb John R Pierce : >On 11/23/2016 11:20 AM, Israel Brewster wrote: >> How do I determine which those are? Just based on the timestamp if >the >> WAL file, such that I could do something like take the timestamp of >> the last basebackup and delete all WAL

Re: [GENERAL] Backup "Best Practices"

On 11/23/2016 02:50 PM, Israel Brewster wrote: > On Nov 23, 2016, at 10:31 AM, John R Pierce > there's a tool, barman, I've never used but its supposed to greatly >> simplify this whole process... >> >> http://www.pgbarman.org/ > > Definitely looks like something to try. Thanks! I'd recommend you

Re: [GENERAL] Backup "Best Practices"

On Nov 23, 2016, at 10:31 AM, John R Pierce wrote: > > On 11/23/2016 11:20 AM, Israel Brewster wrote: >> How do I determine which those are? Just based on the timestamp if the WAL >> file, such that I could do something like take the timestamp of the last >> basebackup and delete all WAL files

Re: [GENERAL] Backup "Best Practices"

On 11/23/2016 11:20 AM, Israel Brewster wrote: How do I determine which those are? Just based on the timestamp if the WAL file, such that I could do something like take the timestamp of the last basebackup and delete all WAL files older than that? Or is there a better way? there's a tool, bar

Re: [GENERAL] Backup "Best Practices"

---Israel BrewsterSystems Analyst IIRavn Alaska5245 Airport Industrial RdFairbanks, AK 99709(907) 450-7293---BEGIN:VCARD VERSION:3.0 N:Brewster;Israel;;; FN:Israel Brewster ORG:Frontier Flying Service;MIS TITLE

Re: [GENERAL] Backup "Best Practices"

On 11/23/2016 10:16 AM, Israel Brewster wrote: To mitigate these issues, I am thinking of supplementing the individual dumps with a full base backup and WAL archiving to a NFS share. This should enable (relatively) quick/easy recovery from backup, plus the ability to do PIT Recovery. I do hav

[GENERAL] Backup "Best Practices"

I was wondering if someone could inform me about, or point me to an online article about best practices for backing up a postgresql database cluster? At the moment, I have two servers running with streaming replication for failover purposes, and then I do nightly database dumps for recovery/backup