| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | akp geek <akpgeek(at)gmail(dot)com> |
| Cc: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>, Alan Hodgson <ahodgson(at)simkin(dot)ca>, Greg Stark <gsstark(at)mit(dot)edu>, Jing Tan <jing(at)iheavy(dot)com>, Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Incremental Backups in postgres |
| Date: | 2009-11-11 21:14:16 |
| Message-ID: | 4AFB2928.9040207@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
akp geek wrote:
> Got it almost. Thanks a lot. One final question, please bear with me.
>
> 1. select pg_start_backup('label') ==> 10 AM
> 2. PGDATA folder backup ==> 10:05 AM
> 3. select pg_stop_backup => 10.10AM
> 4. The archiving will start writing files
>
You've got step (4) in the wrong place. The archiver will generate
files you are compelled to save as soon as you issue pg_start_backup in
(1). That's how you're able to recover from a failure at any time after
that. When you issue pg_stop_backup, it will tell you what files it
expects to be copied over to the slave system in order to recovery from
a failure, and that list will go back to when you started the backup.
Saving those is actually part of the base backup process, as documented
in the manual if you read that section more carefully.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond O'Donnell | 2009-11-12 00:07:00 | pgday.eu |
| Previous Message | akp geek | 2009-11-11 20:54:49 | Re: Incremental Backups in postgres |