Re: [ADMIN] pg_backrest no longer backing up
От | David Steele |
---|---|
Тема | Re: [ADMIN] pg_backrest no longer backing up |
Дата | |
Msg-id | 72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net обсуждение исходный текст |
Ответ на | [ADMIN] pg_backrest no longer backing up (Aldo Sarmiento <aldo@bigpurpledot.com>) |
Ответы |
Re: [ADMIN] pg_backrest no longer backing up
|
Список | pgsql-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
В списке pgsql-admin по дате отправления: