Skip site navigation (1) Skip section navigation (2)

Re: Base Backups from PITR Standby

From: Brian Wipf <brian(at)clickspace(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Base Backups from PITR Standby
Date: 2007-10-30 14:25:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On 29-Oct-07, at 11:06 PM, Tom Lane wrote:

> Brian Wipf <brian(at)clickspace(dot)com> writes:
>> The process I use that leads to the warnings is simple:
>> I use pg_controldata to determine the current checkpoint WAL location
>> of the standby server. I ensure I have this WAL file and all newer
>> WALs. I backup all files under the standby's database cluster
>> directory, including all tablespaces, which are soft linked. I  
>> restore
>> the database cluster directory to its new location and create soft
>> links in pg_tblspc to point to the proper tablespace directories just
>> backed up. I create the pg_xlog directory containing an  
>> archive_status
>> directory.
> This seems not exactly per spec.  Why are you not using  
> pg_start_backup
> and pg_stop_backup around the copying of the database files?

I'm trying to take a base backup from the standby server in archive  
recovery mode. I don't believe it's possible to connect to it to issue  

In response to


pgsql-general by date

Next:From: David FetterDate: 2007-10-30 15:01:42
Subject: Re: Problems with PostgreSQL DBI-Link / DBD-ODBC
Previous:From: paul riversDate: 2007-10-30 13:59:02
Subject: Re: Partitioning: how to exclude unrelated partitions?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group