From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Pallav Kalva <pkalva@deg.cc>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postges 8.0.2 Online backup Errors!
Date: Fri, 29 Apr 2005 10:33:36 -0400 (EDT)
Message-ID: <200504291433.j3TEXaa11184@candle.pha.pa.us> (raw)
In-Reply-To: <42724333.3060708@deg.cc>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pgman@candle.pha.pa.us, pkalva@deg.cc
Subject: Re: Postges 8.0.2 Online backup Errors!
In-Reply-To: <200504291433.j3TEXaa11184@candle.pha.pa.us>
References: <42724333.3060708@deg.cc> <200504291433.j3TEXaa11184@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox