| From: | Tom Arthurs <tarthurs(at)jobflash(dot)com> | 
|---|---|
| To: | Tom Davies <tgdavies(at)gmail(dot)com> | 
| Cc: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: Backup of live database | 
| Date: | 2008-01-17 01:02:00 | 
| Message-ID: | 478EA908.9040607@jobflash.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
If you don't start archiving log files, your first backup won't be valid 
-- well I suppose you could do it the hard way and start the backup and 
the log archiving  at exactly the same time (can't picture how to time 
that), but the point is you need the current log when you kick off the 
backup.  If you kick off archiving first, you are assured of a valid 
backup (when the recovery is done.)  You may get some extra log files 
that way, but better too many than too few.  (been there, done that.)
Tom Davies wrote:
> 
> On 17/01/2008, at 4:42 AM, Tom Arthurs wrote:
>> The important thing is to start archiving the WAL files *prior* to the 
>> first OS backup, or you will end up with an unusable data base.
> 
> Why does the recovery need WAL files from before the backup?
> 
> Tom
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>               http://www.postgresql.org/docs/faq
> 
> 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Krajmalnik | 2008-01-17 05:16:50 | Re: Strange client encoding issue | 
| Previous Message | Scott Marlowe | 2008-01-16 23:27:34 | Re: Backup of live database |