Scott Ribe a écrit :
> I prefer the approach of keeping the backup server up to date, whether using
> PITR or Slony or your own home-grown synching, and then changing IPs. My
> process involves someone making the decision that server is indeed down,
> then UNPLUGGING it from the network, then changing the IP of the backup.
> Actually bringing the backup online involves a bit more than changing the
> IP, because PG is not the only service running on it, but there's a simple
> script for the user to run.
>
> Of course this requires that the backup be on the same subnet as the server,
> a restriction which is not shared by the alternate app/DSN nor the DNS
> techniques...
I am going towards this solution.
Quite hard to test the backup script in real situation, but I
believe this is the way to go.
--
Arnaud
