| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | andy(dot)shellam(at)mailnetwork(dot)co(dot)uk |
| Cc: | "'Thomas F(dot) O'Connell'" <tfo(at)sitening(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PITR as Online Backup Solution |
| Date: | 2006-03-03 18:00:30 |
| Message-ID: | 1141408830.27729.512.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2006-03-03 at 10:23 +0000, Andy Shellam wrote:
> Then you would have to find a method of telling the script
> that you wish to bring the database up and it will exit and allow PGSQL to
> come up at the current state with the latest data.
> Replication sounds like a better option
If you want auto failover, then you will need a package that detects
that accurately and can initiate any required actions, whatever method
you choose of keeping multiple systems in sync.
IMHO auto failover needs *extensive* testing and failure analysis to
make it more robust and practically useful than manual failover, so is
not quite the magic bullet it may appear.
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F. O'Connell | 2006-03-03 18:03:28 | Re: PITR as Online Backup Solution |
| Previous Message | Simon Riggs | 2006-03-03 17:54:52 | Re: PITR as Online Backup Solution |