X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id D83149FB259 for ; Thu, 3 Aug 2006 16:00:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 21000-09 for ; Thu, 3 Aug 2006 18:59:56 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id B91309FB205 for ; Thu, 3 Aug 2006 15:59:56 -0300 (ADT) Received: from andyshellam-gw.adsl.newnet.co.uk ([80.175.198.137]:54273 helo=[192.168.1.15]) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1G8iQE-0000bv-KN; Thu, 03 Aug 2006 19:59:54 +0100 Message-ID: <44D247A8.5060201@mailnetwork.co.uk> Date: Thu, 03 Aug 2006 19:59:52 +0100 From: Andy Shellam Reply-To: Andy Shellam Organization: The Mail Network User-Agent: Thunderbird 1.5.0.5 (X11/20060719) MIME-Version: 1.0 To: "Mr. Dan" CC: pgsql-admin@postgresql.org Subject: Re: On-line backup - /bin/tar: Error exit delayed from previous References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.133 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/31 X-Sequence-Number: 22575 We occasionally get the "file changed while being read" error, usually only once or twice a month (and we run nightly backups.) It's nothing to be concerned about, as someone else mentioned, the WAL logs will fix any internal inconsistencies. Regarding the file sizes, because it's zipped (I believe) the compression ratios can change depending on the contents of the files, hence the differences in size, but I wouldn't have thought it be that drastic. Thing I would do, is on a spare machine (or same one if you've got the space), unzip three of the files that are different sizes (e.g. 874MB, 5GB, 9GB) and then compare the sizes of the unzipped data. If it differs greatly in the same fashion, you've got a problem. Also just double check you're not backing up WAL logs as well (i.e. excluding pg_xlog.) Andy. Mr. Dan wrote: > > Another thing that conerns me is that the zipped file size keeps > changing. > I'm backing up 10GB total. One night the backup file was 9 GB, one > night it was 874 MB and just now, 5 GB. I'm expecting a file around > 1.5 GB (15% of the 10GB) that's there. > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > > !DSPAM:37,44d207ac143291676420085! > >