Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJfEE-0003s3-5O for pgsql-admin@arkaria.postgresql.org; Tue, 28 Nov 2017 12:43:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJfED-0003nL-DR for pgsql-admin@arkaria.postgresql.org; Tue, 28 Nov 2017 12:43:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eJfED-0003nC-22 for pgsql-admin@lists.postgresql.org; Tue, 28 Nov 2017 12:43:09 +0000 Received: from mail.mnietz.de ([88.198.137.52]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eJfE9-0003wh-Gk for pgsql-admin@lists.postgresql.org; Tue, 28 Nov 2017 12:43:07 +0000 Received: from [192.168.1.113] (dslb-088-068-073-141.088.068.pools.vodafone-ip.de [88.68.73.141]) by mail.mnietz.de (Postfix) with ESMTPSA id 4D2B940350 for ; Tue, 28 Nov 2017 13:43:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mnietz.de; s=mail_201512; t=1511872983; r=y; bh=VCjJnujUIldNq+kVqWkAd0hzS8zYSJ985/bTedujH/c=; h=Subject:To:References:From:Date:In-Reply-To:From; b=AVGrwpgBv/XNG4zA97vHtb1Qo4AipSKN6y6GgVgo1FfvjEPRvfRHpWFMMs3SYVqP4 P+JvdCME6jzFOspWtj4pPCCLrQGpKQRiqlHJ9G6YHUkh8oVVFPRDDt58EyasDI5s6w ANChKMYLecmnnyBZMDrS9rt7Fvioy57qJRyCeJGo= Subject: Re: Barman WAL size issue To: pgsql-admin@lists.postgresql.org References: From: Marco Nietz Message-ID: <9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de> Date: Tue, 28 Nov 2017 13:43:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, which wal method are you using? Wal Streaming or archiving by using archive_command? In case of streaming, you could check if receive-wal process is running on the backup host and connected to the barman replication slot on the postgresql server. In the other case, check your postgresql logfile if you have errors about the archiving. Greetings, Marco Am 28.11.2017 um 11:51 schrieb Günce Kaya: > Hello, > > There are some cron which execute insert, update statement daily. It's > not possible nothing happened after previous backup. So, do you have > another idea about that? > > Regards, > Gunce > > On Tue, Nov 28, 2017 at 12:44 PM, Shreeyansh Dba > > wrote: > > > > On Tue, Nov 28, 2017 at 2:47 PM, Günce Kaya > wrote: > > Hi all, > > We use Barman for backup. I checked latest backup as to whether > having latest backup is success and I saw WAL size is 0 B. > > -bash-4.1$ barman list-backup dbalpha > dbalpha 20171127T190002 - Tue Nov 28 09:43:40 2017 - Size: 326.0 > GiB - WAL Size: 0 B .... > > I think it's not normal. Any help would be appreciated. > > > ​This is quite normal scenario, I suspect as not many transactions > have happened since its previous backup was taken which resulted in > WAL size to 0 B​ > > > Regards, > Gunce Kaya > > Linkedin  - Twitter >  - Blog > > > > > > -- > http://www.shreeyansh.com > > > > > -- > Gunce Kaya > > Linkedin  - Twitter >  - Blog >