Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cnWi5-0002va-BO for pgsql-admin@arkaria.postgresql.org; Mon, 13 Mar 2017 20:36:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cnWi4-0005X9-UM for pgsql-admin@arkaria.postgresql.org; Mon, 13 Mar 2017 20:36:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cnWgG-0000BU-Oa for pgsql-admin@postgresql.org; Mon, 13 Mar 2017 20:35:00 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cnWg8-0000pQ-7F for pgsql-admin@postgresql.org; Mon, 13 Mar 2017 20:35:00 +0000 Received: from Davids-iMac.local (c-73-55-5-246.hsd1.fl.comcast.net [73.55.5.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dsteele) by mail.thelabyrinth.net (Postfix) with ESMTPSA id 988655574D; Mon, 13 Mar 2017 20:34:49 +0000 (UTC) Subject: Re: pg_backrest no longer backing up To: Aldo Sarmiento , pgsql-admin@postgresql.org References: <72f3c86c-8b35-783d-a117-8a72d9abb2d9@pgmasters.net> From: David Steele Message-ID: <06ba49be-1ef6-b979-339b-a4af7e933ed1@pgmasters.net> Date: Mon, 13 Mar 2017 16:34:48 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hi Aldo, On 3/8/17 5:53 PM, Aldo Sarmiento wrote: > > Actually got it figured out. Main thing is that I should clarify that > the aforementioned crontab was irrelevant since I was looking at the > replica. > > Once logged into master, the crontab is intact and uncommented. That makes sense. > The > problem was that a backup failed and pg_backrest was failing to start. > > I tried adding auto-stop=true to conf, but it didn't help. In the end I > just did pg_stop_backup() and things are running smoothly now. The option is actually stop-auto: http://www.pgbackrest.org/user-guide.html#backup/option-stop-auto But it wasn't added until 0.80 so wouldn't work for you anyway. > As for the upgrade, yes that's a need we have. Just trying to see if we > can migrate our current backups to work with the new version so we don't > lose ability for PITR. It might be possible but would require specialized knowledge and custom code. We decided to make a clean break at 1.0 and require users to create a new repository due to the number of changes in the format. 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