pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PITR Recovery settings
3+ messages / 2 participants
[nested] [flat]

* PITR Recovery settings
@ 2011-03-24 01:10  Selva manickaraja <mavles78@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Selva manickaraja @ 2011-03-24 01:10 UTC (permalink / raw)
  To: pgsql-admin

Hi,

We have successfully implemented a  Backup and Recovery process in our
organization and currently testing it out. We took a previous day backup and
tried to restore it to a point in time.

The database is able to start applying the recovery settings. But it
recovered records past the recovery target date and time give by at least 30
minutes. But before that let me tell you that the check_timeout is set every
30 minutes. So logs get shipped every half an hour only. The PgSQL manual
say that recovery is always until end of WAL log. However we also set the
recovery_target_inclusive as false to ensure that transaction after the
specified time is not loaded to the recovered database. But in actual, this
is not happening. I understand that there is also a way to recover by
individual transaction. Would that be helpful in this kind of scenario?

Below is the recovery.conf file which was renamed as recovery.done after
starting the database.

recovery_target_time = '2011-03-23 16:05:00 MYT'
recovery_target_inclusive = 'false'
restore_command = 'cp /pgsbak/recovery/wal_archive/%f %p'
archive_cleanup_command = 'pg_archivecleanup /pgsbak/recovery/wal_archive
%r'

Kindly assist.

Thank you.

Regards.

Selvam

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Fwd: PITR Recovery settings
@ 2011-03-28 01:41  Selva manickaraja <mavles78@gmail.com>
  parent: Selva manickaraja <mavles78@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Selva manickaraja @ 2011-03-28 01:41 UTC (permalink / raw)
  To: pgsql-admin

Hi,

Any takers on this issue?

---------- Forwarded message ----------
From: Selva manickaraja <mavles78@gmail.com>
Date: Thu, Mar 24, 2011 at 9:10 AM
Subject: PITR Recovery settings
To: pgsql-admin@postgresql.org


Hi,

We have successfully implemented a  Backup and Recovery process in our
organization and currently testing it out. We took a previous day backup and
tried to restore it to a point in time.

The database is able to start applying the recovery settings. But it
recovered records past the recovery target date and time give by at least 30
minutes. But before that let me tell you that the check_timeout is set every
30 minutes. So logs get shipped every half an hour only. The PgSQL manual
say that recovery is always until end of WAL log. However we also set the
recovery_target_inclusive as false to ensure that transaction after the
specified time is not loaded to the recovered database. But in actual, this
is not happening. I understand that there is also a way to recover by
individual transaction. Would that be helpful in this kind of scenario?

Below is the recovery.conf file which was renamed as recovery.done after
starting the database.

recovery_target_time = '2011-03-23 16:05:00 MYT'
recovery_target_inclusive = 'false'
restore_command = 'cp /pgsbak/recovery/wal_archive/%f %p'
archive_cleanup_command = 'pg_archivecleanup /pgsbak/recovery/wal_archive
%r'

Kindly assist.

Thank you.

Regards.

Selvam

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Fwd: PITR Recovery settings
@ 2011-03-28 21:33  Kevin Grittner <Kevin.Grittner@wicourts.gov>
  parent: Selva manickaraja <mavles78@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Kevin Grittner @ 2011-03-28 21:33 UTC (permalink / raw)
  To: Selva manickaraja <mavles78@gmail.com>; pgsql-admin

Selva manickaraja <mavles78@gmail.com> wrote:
 
> We have successfully implemented a  Backup and Recovery process in
> our organization and currently testing it out. We took a previous
> day backup and tried to restore it to a point in time.
> 
> The database is able to start applying the recovery settings. But
> it recovered records past the recovery target date and time give
> by at least 30 minutes.
 
> recovery_target_time = '2011-03-23 16:05:00 MYT'
 
My guess would be that this is some sort of problem with time zone
configuration or clock settings.  Compare those closely between the
two machines and see if you can find any differences.
 
-Kevin



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2011-03-28 21:33 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-03-24 01:10 PITR Recovery settings Selva manickaraja <mavles78@gmail.com>
2011-03-28 01:41 ` Selva manickaraja <mavles78@gmail.com>
2011-03-28 21:33   ` Kevin Grittner <Kevin.Grittner@wicourts.gov>

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