From: | Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "Andrew W(dot) Gibbs" <awgibbs(at)awgibbs(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: base backup requirements for PITR |
Date: | 2012-12-03 09:24:17 |
Message-ID: | 50BC6FC1.20208@2ndQuadrant.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Laurenz,
Il 01/12/12 12:18, Albe Laurenz ha scritto:
> Gabriele, I understand that you want to spread the word,
> but the OP's problem was a different one:
You are right. I totally missed that. I skimmed the email (very quickly)
and thought that in that particular context Andrew was referring to PITR
in general.
> He wants to create a base backup by just copying the
> data directory of an 8.4 warm standby server.
> There is no possibility to run pg_(start|stop)_backup,
> but the documentation seems to suggest that it could work
> anyway:
> http://www.postgresql.org/docs/8.4/static/warm-standby.html#BACKUP-INCREMENTAL-UPDATED
Yes, it is possible. I'd like to try and implement that in Barman, in
order to automate this. I'd try and follow this path though:
pg_start_backup() on the master, wait for the operation to be replayed
on the standby (with pg_controldata if < 9.0 or through hot standby),
rsync/tar from the standby, then pg_stop_backup() on the master. If you
think of following this path yourself, please make sure you test it
accurately (especially for production environment).
Sorry Andrew about misunderstanding the original question.
Cheers,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele(dot)bartolini(at)2ndQuadrant(dot)it | www.2ndQuadrant.it
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-12-03 10:19:17 | Re: base backup requirements for PITR |
Previous Message | Terry Khatri | 2012-12-01 20:53:20 | Transaction Log and Differential Backups in PostgreSQL |