Thank you Magnus, Bruce...!!
On Tue, Apr 20, 2010 at 7:20 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Magnus Hagander wrote:
> > .
> > On Fri, Apr 16, 2010 at 11:55 AM, raghavendra t
> > <raagavendra(dot)rao(at)gmail(dot)com> wrote:
> > > Hi All,
> > >
> > > For?some setups reason, i started taking Hot backup. In this course I
> have first issued pg_start_backup('backup') and went to the data directory
> for backing up in OS format using the command "tar -cf backup.tar? /data" .
> When i issued this command , tar was generating some errors as show below.
> > >
> > > bash-3.00# tar -cf 16aprilstandby.tar /db-data/
> > > tar: Removing leading `/' from member names
> > > tar: /db-data/base/24643/151667: file changed as we read it
> > > tar: /db-data/base/24643/151764.2: file changed as we read it
> > > tar: /db-data/base/24643/151766: file changed as we read it
> > > tar: /db-data/base/24643/151768: file changed as we read it
> > > tar: /db-data/base/66412/151969: file changed as we read it
> > >
> > > After sometime tar has ended and i also issued pg_stop_backup() and i
> continued the process.
> > >
> > > My question here is, is this errors generated by tar are to worrisome
> or whats happening in the backend.
> > > Is "tar" file is safewell to use. Could you please tell me.
> > Those are not errors, they are warnings. As long as you use
> > pg_start_backup() and pg_stop_backup() before and after the tar, they
> > are perfectly harmless, and can be ignored.
> Yes, and the manual does mention this issue:
> Some file system backup tools emit warnings or errors if the files
> are trying to copy change while the copy proceeds. When taking a
> backup of an active database, this situation is normal and not an
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
In response to
pgsql-general by date
|Next:||From: Takahiro Itagaki||Date: 2010-04-21 01:50:26|
|Subject: Re: [GENERAL] trouble with to_char('L')|
|Previous:||From: Greg Smith||Date: 2010-04-21 00:28:50|
|Subject: Re: Performance impact of log streaming replication|