From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How do I set up automatic backups? |
Date: | 2008-07-30 08:10:06 |
Message-ID: | 489021DE.90801@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tomasz Ostrowski wrote:
> On 2008-07-29 23:47, John Cheng wrote:
>> Slony-I replication is also a viable choice for backups.
>
> No, it's not. Redundancy is not a substitute for backups. Slony will not
> help you if you do by mistake "delete from important_table" - as a copy
> will also have all rows deleted.
>
> For backups I'd recommend for example pg_dump and duplicity run from cron.
Yep ... there's nothing like having a plain-text, or at least stable
format (-Fc) copy of your data around for disaster recovery. It's not
particularly time and space efficient, but it's certainly reassuring.
For anything important, especially where you cannot afford to lose a
whole day's work, I'd also want to consider using log shipping based
PITR. That way, you lose at most (depending on configuration) say 15
minutes.
Real-time replication to a remote site with slony or similar can help
protect you against fire, theft, etc though.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Hunter | 2008-07-30 11:36:35 | Re: Must be table owner to truncate? |
Previous Message | hubert depesz lubaczewski | 2008-07-30 08:01:10 | Re: How do I set up automatic backups? |