X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 70EFE5380C for ; Fri, 29 Apr 2005 11:33:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 03410-08 for ; Fri, 29 Apr 2005 14:33:34 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126]) by svr1.postgresql.org (Postfix) with ESMTP id 7D16B53811 for ; Fri, 29 Apr 2005 11:33:32 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id j3TEXaa11184; Fri, 29 Apr 2005 10:33:36 -0400 (EDT) From: Bruce Momjian Message-Id: <200504291433.j3TEXaa11184@candle.pha.pa.us> Subject: Re: Postges 8.0.2 Online backup Errors! In-Reply-To: <42724333.3060708@deg.cc> To: Pallav Kalva Date: Fri, 29 Apr 2005 10:33:36 -0400 (EDT) Cc: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.01 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/404 X-Sequence-Number: 17417 Pallav Kalva wrote: > Hi , > > I got this error while doing my online backups on the new postgres > 8.0.2. I follow the same procedure as mentioned in the docs and the way > i do in brief is > > 1) Put the database in backup mode with pg_start_backup > 2) copy data cluster, I use tablespaces and my tables and indexes are in > different partition so i copy them also here using tar and gzip > 3) And put the database back in normal mode with pg_stop_backup > 4) copy archive log directory with tar and gzip. > > and today I go this error , i am not sure if this is normal or is > this something to worry about ? does anybody experienced anything like > this before ? > > ERROR Durring Backup > -------------------------------------------------------------------------------- > bash-2.05b$ ./backup.sh b > 17/8E3DA9F0 > tar: tabledata/165899758/165958430: file changed as we read it > tar: Error exit delayed from previous errors > 17/8E8CB0A8 > bash-2.05b$ > ---------------------------------------------------------------------------------- This is expected. Tar is backing up a changing file system but the WAL logging will bring the system back to a consistent state. However, read the current version of the docs online because you have to be sure you have the WAL files that were active during the backup to use the tar file, and those files might still be sitting in pg_xlog and not archived at the time the tar finishes. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073