pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Steele <david@pgmasters.net>
To: Aldo Sarmiento <aldo@bigpurpledot.com>
To: pgsql-admin@postgresql.org
Subject: Re: pg_backrest no longer backing up
Date: Wed, 8 Mar 2017 14:18:07 -0800
Message-ID: <72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net> (raw)
In-Reply-To: <CAHX=r6yti58x1z4y8q_zqr_P+8_Aq5_uPKSJDu1xDaV+rtjQmA@mail.gmail.com>
References: <CAHX=r6yti58x1z4y8q_zqr_P+8_Aq5_uPKSJDu1xDaV+rtjQmA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hi Aldo,

On 3/8/17 11:48 AM, Aldo Sarmiento wrote:

> Sometime in December in 2016 we ran out of space for our backup
> directory, which we increased promptly. However, it appears that
> backrest stopped taking backups since the incident.
>
> Versions of things:
>
> pg_backrest 0.75

This is an incredibly old, pre-1.0 version of pgBackRest. I suggest you 
upgrade to a current version.  1.X will not be compatible with your 
current repo so it will need to be a fresh install.

> *postgres@pgdedicated:/backup/backrest/log$ cat
> prod-9.4-backup-20170308.log*
> -------------------PROCESS START-------------------
> 2017-03-08 01:30:02.034 T00   INFO: backup start: type = diff
> 2017-03-08 01:30:02.835 T00   INFO: last backup label =
> 20161204-025729F, version = 0.75
> 2017-03-08 01:30:02.911 T00   INFO: executing pg_start_backup() with
> label "pg_backrest backup started 2017-03-08 01:30:02": backup will
> begin after the requested immediate checkpoint completes
> 2017-03-08 01:30:02.976 T00  ERROR: process terminated on signal or
> exception, 0 threads stopped

This could be any number of things and there's not enough information 
given here to even begin to guess.

> Question: Not sure when the backrest cron was commented out, but how is
> it still attempting to do backups without this setup? I'm assuming it's
> being invoked some other way?

I'm guessing it's being invoked in some other way, perhaps the postgres 
user's crontab?

> Also, any idea what the issue is with the error?

Again, there's not enough information given for me to form an opinion.

Regards,
-- 
-David
david@pgmasters.net


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (4+ messages)  latest in thread

Message-ID: <72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net>
Permalink:  ../72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net/
Also on:    postgresql.org/message-id/72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: david@pgmasters.net, aldo@bigpurpledot.com
  Subject: Re: pg_backrest no longer backing up
  In-Reply-To: <72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox