Sorry for not responding to this email for so long.
Alan,
We had mentioned the following line in recovery.conf file (we had given
pg_xlog location since we did not have WAL archives) -
restore_command = 'cp /pg_xlog/%f %p'
We found where the problem was -
Here is what i did -
1. We had taken
> > rsync works fine. Why exactly can't the recovery find the backed up copy
> > of 000105390076? Please post your archive_command settings,
> > the contents of any script(s) called by that, and the recovery.conf file
> > you're using that's having problems, as well as the complete proc
The recovery is unable to find the WAL archive because, it was generated on
26th September.
Whereas the backup is as taken on Oct 2nd, 2011. We deleted all the files.
I do not have that WAL archive copy.
The problem area -
I found that a pg_clog file dated 26th Sep, 2011 is not synced (its not
On October 3, 2011 05:33:35 AM Venkat Balaji wrote:
> Did anyone observe this behavior ?? Please help !
>
> This is critical for us. I want to recommend not to use "rsync" (use cp or
> scp instead) for production backup.
>
rsync works fine. Why exactly can't the recovery find the backed up copy
Another problem in recovery (probably because of "rsync") -
As said earlier, we are taking a production backup everyday incrementally
using "rsync".
But, Postgres some how misses to sync few files in between and keeps on
asking the back dated archive files (more than 1 week ago).
I restored Octo
Venkat Balaji wrote:
> Our problem is -
>
> We had mistakenly executed "rsync" on the running PostgreSQL data
directory (production) and we did
> not run "pg_start_backup()".
>
> Will this harm production ? can this lead to corruption ?
I assume that you used rsync to copy *from* the data direc
Thanks for all your inputs !
Our problem is -
We had mistakenly executed "rsync" on the running PostgreSQL data directory
(production) and we did not run "pg_start_backup()".
Will this harm production ? can this lead to corruption ?
Thanks -
On Mon, Sep 26, 2011 at 10:29 PM, Alan Hodgson wro
On September 26, 2011 05:49:50 AM Venkat Balaji wrote:
> I tried restoring the backup, after taking the full backup.
>
> Below is what i see in the "archive destination".
>
> Postgres was asking for "00010193006F" and i tried to find the
> same and below is what i find...
>
> -rw
Venkat Balaji wrote:
> We have had situations where-in "rsync" was executed without executing
"pg_start_backup()" on the
> production data directory and on the next runs, "pg_start_backup()"
has been executed with "rsync".
> This was to avoid high IO load on production. We ended up getting
unmatche
I tried restoring the backup, after taking the full backup.
Below is what i see in the "archive destination".
Postgres was asking for "00010193006F" and i tried to find the
same and below is what i find...
-rw--- 1 postgres postgres 3.3M Sep 26 02:06 00010193006F.gz
-
Hello Everyone,
We have had situations where-in "rsync" was executed without executing
"pg_start_backup()" on the production data directory and on the next runs,
"pg_start_backup()" has been executed with "rsync". This was to avoid high
IO load on production. We ended up getting unmatched files (e
11 matches
Mail list logo
