Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jUd65-0005IT-QI for pgsql-bugs@arkaria.postgresql.org; Fri, 01 May 2020 21:21:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jUd64-0005I3-BM for pgsql-bugs@arkaria.postgresql.org; Fri, 01 May 2020 21:21:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jUd64-0005Hk-5O for pgsql-bugs@lists.postgresql.org; Fri, 01 May 2020 21:21:24 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jUd5z-0002PK-6A for pgsql-bugs@lists.postgresql.org; Fri, 01 May 2020 21:21:23 +0000 Received: from Davids-MacBook-Pro.local (c-73-39-102-148.hsd1.va.comcast.net [73.39.102.148]) (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 171C154682; Fri, 1 May 2020 21:21:18 +0000 (UTC) Subject: Re: BUG #16408: We are facing issue while taking the backup using pgbackrest 2.22 version To: singh.bpratap766@gmail.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <16408-0c3438a784ec2966@postgresql.org> From: David Steele Message-ID: <3a25807b-9b1b-4638-d260-b840b17a175a@pgmasters.net> Date: Fri, 1 May 2020 17:21:16 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <16408-0c3438a784ec2966@postgresql.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 5/1/20 4:27 PM, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 16408 > Logged by: Brajendra Pratap Singh > Email address: singh.bpratap766@gmail.com > PostgreSQL version: 10.11 > Operating system: CentOS 6.9 > Description: > > We are facing the below error in pgbackrest backup log while the backup > failed : > > ERROR: [074]: raised from local-11 protocol: unable to move > '/apayrman/pgbackrest/backup/odbserver/20200430-055502F/pg_tblspc/58339/PG_10_201707211/58347/82334143.gz.pgbackrest.tmp' > to > '/apayrman/pgbackrest/backup/odbserver/20200430-055502F/pg_tblspc/58339/PG_10_201707211/58347/82334143.gz': > [2] No such file or directory . > > INFO: backup command end: aborted with exception [074] . > > During the same time we saw the below mentioned error in postgresql log. > > WARNING: aborting backup due to backend exiting before pg_stop_backup was > called . > > Postgresql version : 10.11 > Pgbackrest version : 2.22 > > Please let me know if any further detail required it will be my pleasure. You have now reported this issue three times without paying any attention to my responses the first two times you reported it. This is most assuredly not a PostgreSQL issue. The error you see in the logs is because pgBackRest closes the connection that is running the backup once is encounters the problem. PostgreSQL is merely reporting that the backup never completed, which is true. Please follow the advice at https://github.com/pgbackrest/pgbackrest/issues/1019 and respond there if you are still seeing the issue. Regards, -- -David david@pgmasters.net