> 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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
No comments:
Post a Comment